Major/noticeable changes to version 2022.05.01.
vDos.exe is again smaller, with a (final?) speed boost for FoxProX based programs.
UMB (Upper Memory Block) support dropped.
Support of external (non-Windows) code page definitions.
More comprehensive ASCII/Unicode conversions.
Support of UTF-8 encoded config.txt, autoexec.txt and batch files.
Retrieving (pasting) text from the Windows Clipboard could in specific situations keep the Clipboard locked.
Finger tipping (touch screen) fix for some DOS programs.
Fix for DOS programs not keeping up with Windows key stuffers.
With NumLock off, Shift NumPad digit didn't return correct ASCII value.
Taskbar notification when vDos isn't focused and goes idle (DOS program awaits input).
Updated FreeType library to version 2.11.0.
Set of alternative icons (file icons.icl) to eventually replace that of vDos.
Faster rendering (displaying) text, though that already was real fast.
More accurate rendering/positioning of external fonts.
DOS beep is Windows standard sound.
Support of UNC paths in DOS API if those resolve to a drive letter reference in vDos.
Config.txt directive FPUAWARE = 0-3 (0 = None, 1 = Present + conditional rounding (default), 2 = Rounding off, 3 = Rounding on.
Support of additional PCL print commands, and more accurate positioning.
Changed syntax of HORZ and VERT options. To be more intuitive (see Printing.pdf).
Download: Installation program 2022.05.01 | Source files and older versions
Questions/problems?
First read the little documentation vDos has to offer to make it run your application! Keep in mind you once had to configure DOS, the transition to Windows (XP?) took time. You forgot about that…

Have a look at the FAQs and Forum pages, eventually post your question/problem to the latter. The forum is monitored by Edward Mendelson and me, replies are mostly real quick.
If your issue however seems real specific to your situation/application, or you don’t want it public: Send an email to jas@vdos.info (change the "a" to an "o").

Submitting a problem or issue: Describe it as detailed as possible, eventually attach your autoexec and config.txt files. If your autoexec.txt starts another batch file, include that also. A mere “My DOS program won’t …” doesn’t help to come to a solution, how simple that even might be...
Trouble downloading: Check if you’re using a download accelerator and disable that.