dosbox-x VS winevdm

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

Not exactly what you were asking, but winevdm [0] does use code from Wine to run 16-bit Windows applications on 64-bit Windows installs that don't support it natively (via ntvdm).

[0] - https://github.com/otya128/winevdm

https://github.com/otya128/winevdm run 16 bit apps on 64 windows

This, along with Windows's own compatibility mode tweaks, should run almost any game that has ever been released on Windows.

WineVDM: https://github.com/otya128/winevdm/releases

It could work with the help with otvdm: https://github.com/otya128/winevdm

You can repeat this command as many times as you need to for additional records. More information can be found here. Total downtime in a VMWare environment is less than five minutes, barring any DNS server replication in play." Yet Another Free Tool winevdm enables you to keep old Windows programs on life support by running 16-bit Windows (1.x, 2.x, 3.0, 3.1, etc.) on a 64-bit Windows system. Ojakobe explains, "Had a special case of a user who clung to their Windows 7 PC because their work was reliant on a 16-bit program from 1997 (and even on 7 it didn't run properly). Used the program above to make it run reliably on 10." One Final Free Tool LocalAI is a self-hosted, OpenAI-compatible API that allows you to run language learning models locally or on-prem using consumer-grade hardware without the need for GPUs. This RESTful API supports multiple model families that are compatible with ggml format. Our thanks go to mudler_it for this one.

winevdm enables you to keep old Windows programs on life support by running 16-bit Windows (1.x, 2.x, 3.0, 3.1, etc.) on a 64-bit Windows system. Ojakobe explains, "Had a special case of a user who clung to their Windows 7 PC because their work was reliant on a 16-bit program from 1997 (and even on 7 it didn't run properly). Used the program above to make it run reliably on 10."

After that you should now be able to install software. One final sticking point is that some older programs are wrapped up in 16-bit installers, however these can be installed by running the installer with something like otvdm.

Try WineVDM because NTvdm never got a port to 64-bit since the CPU mode it relied on for fast 16-bit code execution gets disabled when a x86 processor is switched into long mode. WineVDM is likely translating 16-bit instruction calls to 32-bit and then passing that off to Windows