winevdm VS ntvdmx64

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

The link in the post to NTVDMx64 at Columbia seems to be broken, but the associated GitHub project appears to be at https://github.com/leecher1337/ntvdmx64

  "What is it?

ntvdmx64 might also be an option.

People who absolutely need to run 16-bit DOS apps on x64 Windows can use NTVDMx64: https://github.com/leecher1337/ntvdmx64

If it's Windows, you can probably just use an external CD drive or look for an ISO copy online. For the most part, old Windows software still works with modern Windows (REALLY old software will be 16-bit and will need NTVDMx64 to work on 64-bit). Though I'm not sure about the driver itself. If it's a generic protocol, it might just be plug-and-play

I've seen NTVDMx64 mentioned in the BBS community, as it's supposed to install a 16-bit NTVDM on 64-bit editions of Windows. I've been trying to get this installed on my main desktop PC at home (running Windows 11 64-bit), but I always run into some errors trying to install it, and it doesn't seem to install completely (I am unable to run 16-bit DOS programs).

Looks like the NTVDMX64 link was taken down from the columbia.edu website and is now just at https://github.com/leecher1337/ntvdmx64

Well... Windows is always the best option because of its backwards compatibility. Even with some small apps (like NTVDMx64, or similar) you can even make Win10/Win11 run software made to run in 16-bit (or, Windows 3.1 or Win95). I've had to do that for some edutainment software for my son.

If you really want DOS apps on 64-bit there's https://github.com/leecher1337/ntvdmx64 or use a flavour of DOSBox.