3 ms·
Mentioned it in another reply, you'd probably want to start with the MASM and LINK from the MS-DOS 2.0 release. https://github.com/microsoft/MS-DOS/tree/master
by oso2k 6y ago
Mentioned it in another reply, you'd probably want to start with the MASM and LINK from the MS-DOS 2.0 release.
https://github.com/microsoft/MS-DOS/tree/master/v2.0/bin https://github.com/microsoft/MS-DOS/tree/master/v2.0/bin
- acqq 6y agoAlso, as written in the blog post, the .ASM files are not the original sources, more a temporary expansion of these for the given target. Looking at their binary form, all .ASM files end with zero characters instead of, for example, 0x1a with which .H files end. It can be that some tools (different than those originally used) have problems with the zeroes at the end?
- bajsejohannes 6y agoThat's a good observation. I tried stripping zeroes, but unfortunately it's the same error message.
- bajsejohannes 6y agoUnfortunately, I can't get MS-DOS 2.0 to run in DOSBOX ("Invalid COMMAND.COM") and running MASM.EXE directly gives me some really interesting errors (looks like it's reading uninitialized memory). I think you're on to something here, though!
- juangacovas 6y agoProbably you want to try out PCem when dosbox doesn't do the trick. Was a lot of fun for me! I made a small page about PCem here: https://juangacovas.info/doku.php/windows/howtos/pcemu-page https://juangacovas.info/doku.php/windows/howtos/pcemu-page