vDos Icon


Run DOS applications in Windows.

4.8 Stars (23)
353 Downloads (This Week)
Last Update:
Download vDosNotice.pdf
Browse All Files



vDos is specific to run serious (mainly text mode) DOS applications in Windows 32 or 64-bit, XP up to and including Windows 10. You need at least already use such a DOS application to appreciate vDos. If you don’t, want to play with DOS (or its games): vDos isn’t meant for you!

You can easily “upgrade” your DOS application to run in a safe and convenient way in modern Windows environments, especially Windows 64-bit. File/record locking, Windows printing, a scalable screen font and more.

Recent versions (latest 2016.10.01) of vDos are now hosted at:

vDos Web Site


User Ratings

ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
Write a Review

User Reviews

  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Although I use Office in my Windows 7 environment, I still need to access files in WordStar and, believe it or not, Condor. vDos has been incredibly helpful! Thank you so much for providing this valuable product, it works like a charm!

    Posted 10/19/2016
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    My wife, who is an accountant, relies on a DBASE III program circa 1986. Her trusty XP computer bit the dust a few months back and she replaced it with a shiny new computer running Windows 10 64-bit. This turned out to be a massive Charlie Foxtrot as 64-bit Windows OS's don't support 16 bit (as I discovered) . I managed to get it running to a point using DosBox, but she hates it, and also flat refuses to use XP on Virtual box - "I've got a new computer, why do I need to install another computer"! Anyway, Vdos to the resuce - she can use her program pretty much the same as on her old XP machine! Thanks be to god, and the creator of Vdos!

    Posted 09/20/2016
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Having been a long-term user of DOSBox, I recently stumbled upon vDos, and was pleasantly surprised (***NOT*** about the vdos.info wbsite, stupid box-model makes many pages only partially visible, "overflow:hidden" should be removed ASAP!) However, I have found some problems with that old stalwart of DOS, Vern Buerg's LIST. It does not allow screen mode-switch, i.e. go from 80x25 to 80x43/50, and the ViewArc function results in an "FV" not found, even when LIST and FV are in the same directory. Also the integration with 4DOS is less than optimal, I would prefer to be able to use my own (PC DOS 2000) command interpreter and tools. Also one of my most favourite DOS programs (a TSR) does not work, it gives me just a blue screen and, when running vDos frameless, there is no way other than the TaskManager to kill it. Greatest problem: No FPU support, and this really is a show-stopper!!!

    Posted 05/30/2016
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    vDOS works great, and I'm finding that it's a valuable daily tool. I struggled for a few years with DOSbox, and vDOS is light-years ahead in usability. vDOS runs all old-time DOS biz programs like VisiCalc. It works flawlessly with SharkBase (VP-Info), and it's now become a valuable part of my daily toolkit. Many thanks to the people who put this lifesaver together. It should have a Wikipedia page that other apps could point to, but there's too many other tools called "vDOS", so there might be some confusion. There's a fright screen when accessing vDOS website, but pay no mind - vDOS has forgotten to fix up its security certificate, that's all. vDOS is a 10 out of 10 for this user.

    Posted 02/15/2016
  • 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    vDos works almost perfectly with Clipper-based server/client software called MKS Micro Key Central-1, at least when running as a client (the server instance requires an LPT dongle or dongle emulator). The only major shortcoming I found with vDos was its handling of LPT output. Central-1, which runs from a network share mapped to a drive letter, uses LPT1 for live line-printer logs and LPT2 for printed reports. Since the line-printer output on LPT1 never gets closed, I need a timeout for that port. But printed reports to LPT2, which does happen to close after each report, sometimes pause mid-page while the database is being searched -- a timeout here will cause undesired page breaks. And, in both cases, vDos is writing LPT output to the network share with the risk that multiple Central-1/vDos instances will stomp on each others printer output (I run vDos, itself, from the share too). Thankfully, the vDos source code was straightforward enough that it was easy to patch it so that LPT ports output to named pipes, pumping the output directly to a custom helper app to properly process everything. I was also able to add a CTRL + close box "force close" feature for the rare DOS app lockup and changed the Beep() call to a PlaySound() call so I could specify a .wav file for the beeps used regularly in Central-1.

    Posted 12/10/2015
Read more reviews

Additional Project Details

User Interface

Win32 (MS Windows)

Programming Language

C++, C



Thanks for helping keep SourceForge clean.

Screenshot instructions:
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks