I have literally used this emulator to run MASM in this way. I was traveling with an ARM Chromebook and wanted to mess with a retrocomputing project.
dosemu was out because my host wasn't x86. dosbox was out because I wanted to run a process with filesystem access, not a whole system. qemu's system emulation has the same problem as dosbox, and qemu's user-mode emulation runs Linux programs, not MS-DOS programs.
In DOSBox you can mount host directories to MS-DOS drives with the "mount" command (and of course you can use Linux bind mounts and mount namespaces along with it).
Agreed. I wanted to script stuff like linking together 200 .OBJs, and running tests' stderr through sed to make it comparable with a known-good log. A DJGPP install + ancient Python inside DOSBox would've also done the job. Or even period-accurate DOS tools, but that'd cross my "is this retrocomputing or masochism?" threshold for this project.
Comments
I have literally used this emulator to run MASM in this way. I was traveling with an ARM Chromebook and wanted to mess with a retrocomputing project.
dosemu was out because my host wasn't x86. dosbox was out because I wanted to run a process with filesystem access, not a whole system. qemu's system emulation has the same problem as dosbox, and qemu's user-mode emulation runs Linux programs, not MS-DOS programs.
In DOSBox you can mount host directories to MS-DOS drives with the "mount" command (and of course you can use Linux bind mounts and mount namespaces along with it).
Agreed. I wanted to script stuff like linking together 200 .OBJs, and running tests' stderr through sed to make it comparable with a known-good log. A DJGPP install + ancient Python inside DOSBox would've also done the job. Or even period-accurate DOS tools, but that'd cross my "is this retrocomputing or masochism?" threshold for this project.