if the value given for resb exceeds 0FFFFFFFh, NASM won't allocate any
space in the object file. in fact, the .OBJ will be identical to one
with no resb, unless there's code that depends on offsets (e.g. a
JMP over the resb statement). is there any particular reason for
this limit? while it's still incredibly generous, i would've thought
0FFFFFFFFh (that's one more F) would be the maximum.
also, is there a way to emit LIDATA records like "db 500 dup(3)" as in
Sent via Deja.com http://www.*-*-*.com/
Before you buy.