Recent versions of vDos are now hosted at: https://www.vdos.info
vDos derived from the DOSBox project (http://sourceforge.net/projects/dosbox/).
DOSBox is targeted at gaming and available for many operating systems.
If you consider using DOSBox for a database application in a multi-user setting, DON’T, you’ll end up with corrupted data.
vDos is for serious (mainly text mode) DOS applications to run in Windows 32/64 bits (XP and later).
It lacks many of the hardware emulations of DOSBox (no joysticks, basic VGA...).
Instead it adds a live file system, file/record locking, Windows printing, a scalable screen font and more.
You should be able to run your DOS application quickly in a safe and convenient way.
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!!!
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.
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.
Excelente emulador. Necesité usar un programa Clipper en Windows 8.1 y se ejecutó perfecto.
Apart from ascii data or file entry problems with Fortran programs, a very effective emulation under 64-bit Windows systems, of most of MS-DOS V5.00, and which can run every one of over 200 commercial programs and compilers I tested, that normally run perfectly under MSDOS and 32-bit Windows command line execution.. The major problem in Fortran is that carriage return is not correctly processed, requiring a <Ctl-enter> (i.e. a linefeed) immediately after the return key for any keyboard or ascii record entry..I hope this will be fixed. This vDos offers a solution to Microsoft NOT CURRENTLY offering emulation of MSDOS in 64-bit Windows systems So if you load 64 bit Windows instead of 32-bit Windows, you may NEED vDos!. There is an efficient replacement of traditional Config.sys and Autoexec.sys files by similar well-documented .txt stand-ins. Installation is fast and easy. I found the 2014 version, used with 4DOS shell, to be the best common solution for emulating every program type tested. . There are some problems; 1) the 2015 version does not execute programs compacted by exepack.exe (but will run under the 2014 version, or under v 2015 with a modified configuration file). 2) in text entry to a program (not the shell), a cr AND a ctl-cr are needed since the return key code is not replaced with cr-lf as Microsoft defines for ascii line termination. 3) in text entry, there is no effective correction possible for mis-typing; backspace stores that character; the delete key is not replaced with ascii 07h nor left arrow with 1Bh. 4) Not being able to abort with Ctl-C means the task manager has to be invoked after an input error. Some very few services (like get disk ID number) do nothing; or or are not supported yet. Some read-with-file-handle services do not provide the internal editing of delete, abort, or lf replacement (by cr-lf). But the programs WORK; although screen-keyboard interfacing has the mentioned bugs! T.B.Wright, Sydney