MS-DOS VS dosbox-x

This 4.0 code contains references to 4.00, though: https://github.com/microsoft/MS-DOS/blob/main/v4.0/src/BOOT/...

I recently stumbled across the MS-DOS 1.25 and 2.0 source code [1].

[1] https://github.com/microsoft/MS-DOS

“Despite this reduction in scope for MS-DOS 2.0, it did carry many bits of XENIX. The system adopted I/O redirection via less-than and greater-than symbols, piping, a hierarchical directory tree, file handles […]”

The source code for MSDOS 2 is available and the file descriptor stuff appears to be in https://github.com/microsoft/MS-DOS/blob/master/v2.0/source/... and XENIX2.ASM. It stands in contrast to the File Control Block API which MSDOS 1 (née 86-DOS) modeled after CP/M’s API.

Asynchronous I/O figures in prominently in Windows NT. I was really surprised to see[0]:

Each driver in the chain defines two entry points; the strategy routine and the interrupt routine. The 2.0 DOS does not really make use of two entry points (it simply calls strategy, then immediately calls interrupt). This dual entry point scheme is designed to facilitate future multi-tasking versions of MS-DOS. In multi-tasking environments I/O must be asynchronous, to accomplish this the strategy routine will be called to queue (internally) a request and return quickly. It is then the responsibility of the interrupt routine to perform the actual I/O at interrupt time by picking requests off the internal queue (set up by the strategy routine), and process them. When a request is complete, it is flagged as "done" by the interrupt routine. The DOS periodically scans the list of requests looking for ones flagged as done, and "wakes up" the process waiting for the completion of the request.

I didn't realize that kind of forwarding-looking perspective was going into the design of MS-DOS.

[0] https://github.com/microsoft/MS-DOS/blob/master/v2.0/source/...

>Any others I'm missing?

I would suggest MS-DOS: https://github.com/microsoft/MS-DOS

https://github.com/joncampbell123/dosbox-x

em-dosbox: https://github.com/dreamlayers/em-dosbox

Does dosbox [in WASM] support SBEMU?

There's a note about fpemu= and 80 bit precision for dosbox emulation.

docker-dosbox: https://github.com/schneidexe/docker-dosbox/blob/main/Docker...

Windows 98 apparently runs fine in dosbox (dosbox-x?). My dosbox install is locked on Win 3.11, since that's a better compatibility sweet spot for me.

Anyway, that should provide much higher-fidelity emulation than Wine, and is also easier to keep off the network, etc. Also, I guess it runs on Arm processors these days (since it's an emulator, and not a hypervisor):

https://github.com/joncampbell123/dosbox-x

Wine is generally more convenient if it works though.

I quoted from the README: https://github.com/joncampbell123/dosbox-x/

2: Download and run DOSBox-X (Github Link). The version I use is 0.84.3. Unzip the file, enter the dosbox-x folder (not sdl2), and drag and drop the program to applications. When you first attempt to run the application, an error will say "dosbox-x can't be opened because Apple cannot check it for malicious software". To bypass this, go to the apple logo on the top left of the screen> System Preferences> Security and Privacy> General> Open Anyway> Open. It will prompt you to select a folder where it will run the emulation. Select the folder that you created in step 1. Once you are done, close the app.

take into account that's a PC98 game and not MSDOS one, is not the same, try to look some tutorials about it (I don't really know much about it), but you need to start in pc98 mode first some links: https://github.com/joncampbell123/dosbox-x/issues/1504 https://dosbox-x.com/wiki/Guide%3APC%E2%80%9098-emulation-in-DOSBox%E2%80%90X

DOSBox-X from GitHub or dosbox-x.com