NTVDMx64 by Leecher1337

[johnswolter]

I'm hoping you will find this information useful.  The detail seems useful & may suggest other ways or improvements to vDOS.

Came across this article on the Columbia.edu site about supporting NTVDM on more recent Windows version[1].  It refers to a developer Leecher1337 on GitHub[2] who created a patched version of NTVDM.  It used as its starting point a leaked version of NT's NTVDM source code.
[1] www.columbia.edu/~em36/ntvdmx64.html
[2] github.com/leecher1337/ntvdmx64

Leecher1337 then worked to understand how NTVDM could utilize the current Windows KernalCore to get NTVDM working in a 64-bit environment & work with the latest Intel CPUs.  He also discusses why DOSBOX and vDOS are have different but solvable problems.

Leecher1337's readme.txt[3] on GitHub has an in depth discussion of how the patches were developed.  The source of the patches is posted.
[3] github.com/leecher1337/ntvdmx64/blob/master/readme.txt

One issue for my current applications is the quality & performance of printing to Windows type printers.  I've attempted vDOS with an addon & DOSBOX Printfil installed via aSwift's installer.  I wonder if I could get it working using vDOS in a simpler fashion.

John S. Wolter, [e-mail], linkedin

[Jos]

I already added last week both links to the Reviews/links page of vdos.info (vDos links and alternatives - NTVDMx64).

Note that, despite the rather complicated installation, you won’t get the native (speedy) running NTVDM, but the apparently slow (slower than DOSBox or vDos) SoftPC emulator. The main advantage of this seems the tighter integration with Windows. Allowing you to start a DOS program directly, but not many will do that. In stead use a more convenient shortcut starting a batch file. So in that aspect no real advantage to using DOSBox or vDos.

Did you try vDos printing w/o an addon? A program like Printfil monitors a directory for files to print. If one detected, it will wait some time to allow the application to add more print data. That time is added to that vDos already eventually grants the DOS program to do the same. The #LPTx/#COMx.asc files are generated in one final instant sweep. If vDos own print processor is too limited, you should set that waiting time of for instance Printfil as short as possible (preferable none). NTVDMx64 doesn’t solve any print issues, it also needs an external print processor to print to Windows GUI printers. The quality of a hard copy is given by the printer.

BTW, several stated using vDos in Windows 32-bit. If NTVDM is the holy grail, why then use vDos?

Jos