3 ms·
My first assembly programs were written using debug.exe as the assembler. That allowed to go beyond batch files.
by dolmen 4y ago
My first assembly programs were written using debug.exe as the assembler. That allowed to go beyond batch files.
- EvanAnderson 4y agoI did something similar. I ended acting as a human two-pass assembler before I before I got a real assembler. My source was in text files. I'd script them into DEBUG to assemble them just like in the article. I'd put NOPs in place of branching instructions, script the source into DEBUG, and then use the output to get the calculated offsets for the intended branches. Then I'd go back and put the branches and offsets into the code. Nothing frustrated me more than having to insert code and recalculate all subsequent branches. I ended up peppering a lot of NOPs into my early programs so I'd have "spare" bytes to use for instructions I needed to add. Getting a real assembler made a huge difference in my workflow. Translating DEBUG scripts into MASM/TASM-compatible source wasn't awful either.