Forum unknown
· RAMBLINGS
#GRAPHICS QUESTION
7 messages in this thread
At least with Microsoft's MASM, I think it is about 3 lines of source code
per machine instruction (after you count in all the PROCs ENDPs SEGMENTs
ENDSs ASSUMEs and other mish-mosh you have to include to get something to
assemble and run).
Do yourself a favor. Get Speedware's TASM – the $100.00 version. It has a
halfway decent editor/assembler setup, produces object modules that you can
link up with a MASM module and has a VERY rudimentary debug facility. Tech
support can be a bear, though, but they DO give it. Make sure to tell the
secretary to get you through to Tech Support, otherwise you'll NEVER get
tech help at all. TASM has fewer bugs than MASM itself does and is MASM
compatible. Regards, Russ
Do yourself a favor. Get Speedware's TASM – the $100.00 version. It has a
halfway decent editor/assembler setup, produces object modules that you can
link up with a MASM module and has a VERY rudimentary debug facility. Tech
support can be a bear, though, but they DO give it. Make sure to tell the
secretary to get you through to Tech Support, otherwise you'll NEVER get
tech help at all. TASM has fewer bugs than MASM itself does and is MASM
compatible. Regards, Russ
You forgot to add in all the segment over-rides, which assemble out to two
lines of object code. Also, REPZ/REPNZ does it too. It will even out
fairly well, if you don;t go overboard with blank lines in the source
code.
Naw, the segment overrides *disassemble* in some debuggers as extra source
lines, but they don't normally appear that way in the source…
Naw, the segment overrides *disassemble* in some debuggers as extra source
lines, but they don't normally appear that way in the source…
You forgot to add in all the segment over-rides, which assemble out to two
lines of object code. Also, REPZ/REPNZ does it too. It will even out
fairly well, if you don;t go overboard with blank lines in the source
code.