VDos 2026 Support

Help for running your DOS program in VDos 2026 and getting it to print. The two areas that need the most care are memory for FoxPro-style programs and printing.

Contact Support

Email support@jkirkerx.com with your Windows version, the VDos 2026 version, the DOS program and its version, what you were doing, and, if VDos 2026 closed unexpectedly, the newest vDos-exit report.

VDos 2026 keeps its settings, print logs, and exit reports in %LOCALAPPDATA%\vDos 2026. The Open folder button on the Configurator's Application screen opens it.

Known Issue: Memory in FoxPro and Other Protected-Mode Programs

Programs written for 286 and 386 PCs, such as FoxPro, use DOS extenders to reach memory beyond the original 640K. VDos 2026 has to imitate how a 386 manages that memory, and that is where most of the work on VDos 2026 has gone.

Version 2026.10.05 fixed a confirmed flaw in how memory mappings were cached. That fix is still being confirmed in production. Turn on DOSX compatibility and the FoxPro extender, set extended memory (XMS) to 32 MB, and report any crash with the vDos-exit report.

Printing

VDos 2026 sends each print job to the printer exactly as the DOS program produces it, without reformatting, for network printers, Windows printers, and Windows ports alike. Dot matrix printers need Epson or IBM codes; LaserJets need PCL or plain text.

80-column and condensed 132-column reports print correctly when the DOS program is set up for the printer. Graphics printing has not been confirmed yet. Printers that only work through their Windows driver cannot print DOS output.

VDos 2026 is installed and updated through the Microsoft Store at https://apps.microsoft.com/detail/9N122DMJRSN8.

jKirkerx connects software engineering, reseller operations, partnerships, and practical product work. Visit the project pages for Spark Journal, Spark Motion, Simple BOL, PCAD Toolkit, and VDos 2026.