... beautiful (eg, data aligned on 256-byte boundaries).

Also mentioned ...

... (if placing shift table on 256-byte boundary) by using JP (HL ...

... anywhere in memory. The high byte of this is initially 255 ... ; the low byte is 88. Combining the two ... . It should be one byte below the first address we ... to (remember the low byte setting of 88 hasn't ... system variable, to jump in 256-byte steps.

... number, where the upper byte is the number of ... whole pixels; the lower byte is the fractional part. ... like 128 angles (thus a 256 byte table).

... .5) in the lower byte is, lets say you ... subtraction carries into the upper byte, and so your bullet ...

... compression obv... Would need another byte or two for each tile ... do, although just an extra byte per tile can give 8 ... go with more than one byte per tile - that's a ... . I'd keep a separate 256 byte table that holds properties for ...

... go with more than one byte per tile - that's a ... . I'd keep a separate 256 byte table that holds properties for ...

... tile consists of :

[byte]
[00..31] - Pixel data ... /> next
you can use 256 byte table for tile description

... /> next
you can use 256 byte table for tile description

[QUOTE]you can use 256 byte table for tile description[/QUOTE ...

... right (don't forget the 256 byte table)

I found ... the player to a 3 byte buffer

copy the ... ) and on a couple of 256 byte tables for detection methods - thus ...

... right (don't forget the 256 byte table)

I found ... the player to a 3 byte buffer

copy the ... ) and on a couple of 256 byte tables for detection methods - thus ...

... the mirrroring table on a 256-byte page boundary, so you set ... the upper byte of a register to point ... the table, put your data byte in the lower 8 bits ...

Mirroring is done one of two ways, if you have memory, then you store it mirrored for speed.
If you don't have memory, then you use the 256 byte buffer page aligned.

... if I'm understanding the 256 byte table thing right, you could ...

... to get up to 21 256-byte sectors per track where an ... has 8 or 9 512-byte sectors. Therefore it's capable ...

... to get up to 21 256-byte sectors per track where an ... has 8 or 9 512-byte sectors. Therefore it's capable ...

... br /> db (table+10)%256
db 102
db (table+12)%256
db 116
db table%256
db 15
... table must be within single 256 byte block"
endif

... br /> ld a,(hl) ; da = 256 * y + cy

... with table restricted to single 256 byte block:

... br /> ld a,(hl) ; da = 256 * y + cy

... table must be within single 256 byte block"
endif
...

... is typically aligned to a 256 byte boundary. Here, if let's ... say you have the high byte of the table address in ... also need to reverse the byte order, therefore step over the ...

... br />
- 256-aligned data section
- 256-aligned data section ... br /> defc ORGADDR = $10000 - (256*((SIZE / 256) + 1))
ELSE
... is ORGed at a 256-byte aligned address and is ... it will also be a 256-byte aligned. du follows da2 ...

... has to be on a 256 byte boundary to work correctly. This ...

... placing the tables on a 256 byte boundary and effectively using 'l ...

... be located within 256-byte boundary,
; and last byte from this table ...

... (such as: JP HL or 256-byte aligned tables...)
1. Compile ... 101h? Because this affects 2 byte address. If you compiled your ...

... to work out the nearest 256-byte page boundary to an address ...

... (such as: JP HL or 256-byte aligned tables...)[/quote]

256-byte boundaries.

I ... settled on a 256-byte relocation limit (i.e. only ... wrapping of the low byte into the high byte.

...

... the two .bin files. Byte by byte. For identical binaries the differences ... of high and of low byte of these addresses will be ... HL, use stack to jump, 256-byte boundary allocations, etc...) are used ...

... HL, use stack to jump, 256-byte boundary allocations, etc...) are used ... work in all cases except 256-byte aligned unless you keep relocation ... offsets to multiples of 256 bytes. I hadn't thought ...

... work in all cases except 256-byte aligned unless you keep relocation ... offsets to multiples of 256 bytes. I hadn't thought ... , can you elaborate on the 256-byte alingment you talk about above ... correctly if aligned on a 256-byte boundary?

... you elaborate on the 256-byte alingment you talk about ... correctly if aligned on a 256-byte boundary?[/quote]

256-byte aligned table inside the executable ... generate code dependent on 256-byte aligned data structures so ...

... object doesn't cross a 256-byte boundary, unless the alignment is ...