Major/noticeable changes to version 2024.05.01.
•
High resolution (256x256) vDos icon was missing in version 2023.05.01.
vDos can start minimized.
More colorful dark mode (it's now just darker colors).
Added CAPTION command to set the title bar of the vDos window.
Slightly narrower optional left/right window spacing and some refinements to the internal TTF fonts.
Writing 16- or 32 bit values directly to VGA graphic memory was incorrect, eventually causing vertical bars.
Scaling VGA graphics in steps of 10% instead of 100% (2x, 3x...) and supported at runtime.
•
Less aggressive idle detection.
Extended Ctrl+C/Break checking support (programs hooking INT 1B/23h).
Ctrl+<char> returned an ASCII value always based on the US International keyboard layout.
Fix for FoxProX and Clipper shadow keyboard buffers dropping characters at pasting text.
•
Dropped log entries of programs just probing several system services for a cleaner log file.
DOS API 4Eh-FindFirst <device name> returned an error if CX register didn't have bit 5 set.
DOS API 5Ah-Create temporary file set the error code inadvertently to 5.
More robust virtual memory paging TLB handling.
XMS version 2.0 updated to 3.0.
•
Windows variables substituted for CMD/START. %%<unknown>%% dropped, %<unknown>% passed on as-is.
Support of %0-%9 in autoexec.txt.
WINEXEC config.txt option added. Set to off, it disallows starting a Windows program.
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. Replies are mostly real quick. If your issue however seems specific to your situation/application, or you don’t want it public: Eventually send an email to jas@vdos.info (change the "a" to an "o").
Submitting an issue: Describe it as detailed as possible, eventually attach your autoexec and config.txt files. If autoexec.txt starts another batch file, include that also. A mere “My program won’t …” doesn’t help to come to a solution, how simple that even might be...
