SERVICE · 05 / 07

Virtualization Service:
Empower your legacy applications.

Virtualization keeps an MS-DOS application running on current Windows, macOS, or Linux hardware, on premises or in the cloud, without changing the program. It is the right answer for a stable program that nobody needs to change, and a stopgap for one that does. The assessment says which case you are in.

Book a free 1-hour consultation →

At a glance

Legacy sources: MS-DOS · QuickBasic · Turbo Pascal · C · Assembly · BASIC PDS
Modern targets: DOSBox · VMware · AWS · Azure · On-prem or Cloud
Typical timeline: 2 to 6 weeks
Project range: $5,000–$40,000
U.S. delivery: 100% U.S. citizen workforce, U.S.-soil delivery

What to know before you modernize

An emulator or a virtual machine: how to choose

Two different technologies are both called virtualization here. A virtual machine on Hyper-V or VMware runs a real copy of DOS on virtual hardware, so the program sees a PC and behaves as it always did. An emulator such as DOSBox-X imitates the PC in software. It emulates CPUs from the 8086 up to the Pentium III, includes many DOS commands of its own, and runs on Windows, Linux, and macOS. The emulator is the easier route for programs that only touch files and the screen. The virtual machine is closer to the original machine and is the safer choice when a program depends on a specific DOS version, a driver loaded from CONFIG.SYS, or odd hardware timing. We test the real program under both and pick the one that passes.

Clipper applications on 64-bit Windows →

Why a DOS program runs too fast or too slow

DOS programs were written for CPUs measured in megahertz, and some time their work with loops instead of the clock. On an emulator that is a setting: DOSBox-X counts instructions emulated per millisecond through its cycles value. A fixed value such as 5000 runs every program at about 5 million instructions a second, max uses all the host CPU allows, and auto runs real-mode programs at 3000 cycles and switches protected-mode programs to max. DOSBox-X's own guide suggests roughly 750 cycles for a 286 at 8 MHz and about 6000 for a 386DX at 33 MHz, and it states that the emulator is not cycle accurate. Those numbers are starting points. We tune the value against the real program, with its real data, on the screens users spend their day in.

Serial ports, printers, and copy-protection dongles

Peripherals are where most DOS virtualization projects spend their time. In DOSBox-X a serial port is configured with the serial1 setting, for example directserial with a realport value such as COM1 on Windows or ttyS0 on Linux, which passes a host port through to the program. Parallel ports can be disabled, passed to a real port, written to a file, or sent to a virtual Epson ESC/P2 printer that produces PNG, BMP, or PostScript output or prints through Windows; that printer is black and white and does not support every command, such as custom fonts. Hardware dongles are the weak point: DOSBox-X documents its dongle emulation as incomplete and requiring source edits. A Hyper-V Generation 1 virtual machine provides a floppy controller and a UART for COM ports; Generation 2 has no floppy controller and offers a COM port only as an optional UART for debugging.

What changes when DOS moves to AWS or Azure

A cloud virtual machine is a good home for a DOS program that only needs files, a screen, and a network. Boot mode matters: Amazon EC2 launches Intel and AMD instance types in Legacy BIOS mode by default and Graviton types in UEFI. Azure Generation 1 virtual machines boot through a BIOS-style loader from an IDE disk, while Generation 2 uses UEFI and SCSI. DOS and the older Windows guests that often host it expect the BIOS-style boot, so the image has to be built for that mode. A cloud machine has no physical serial or parallel connector, so a device wired to one of those ports is reached through a network device server on site, or the hardware-facing piece stays on premises in a hybrid design.

Hybrid solutions →

Keeping data files and printouts outside the image

A virtualized DOS program should keep its code in the image and its data outside it. In DOSBox-X the MOUNT command presents a host directory to the program as a DOS drive, and IMGMOUNT presents disk image files. Mounting a dedicated data folder, rather than a whole Windows drive, means the files are backed up and restored with the normal file backup, and a damaged image can be replaced from a copy without touching the data. The same approach works in a virtual machine with a second virtual disk or a network share. Multi-user programs that locked records on a shared drive need a closer look, because the locking behavior depends on the network file system in between. We test two simultaneous users against the same data before the environment is accepted.

When virtualization is the answer, and when it is a stopgap

Virtualization is a complete answer when the program is stable, the rules rarely change, nobody asks for a new interface, and the environment is documented and backed up. It is a stopgap when the program must change, when it needs to exchange data with current systems, when users want mobile or browser access to features it does not have, or when the people who know how to maintain the emulator configuration are leaving. A virtualized program still has no source control, no tests, and no one who can edit it unless the source exists. We say which case applies in the assessment. If the answer is a stopgap, the virtual environment buys time and doubles as the reference for the replacement's parity tests.

How we modernize MS-DOS applications →

Why MS-DOS Virtualization?

MS-DOS virtualization offers a powerful solution for running legacy applications like QuickBasic and Turbo Pascal on modern hardware platforms, whether on-premises or in the cloud through AWS and Azure. This technology preserves the reliability of MS-DOS applications, which have been trusted in sectors such as manufacturing and government for critical operations like inventory management and accounting. Virtualization enables fast implementation and ensures compatibility with current systems, maintaining business continuity while allowing organizations to enjoy the benefits of modern computing without sacrificing the unique capabilities of their legacy applications.

The MS-DOS Virtualization Ecosystem

The MS-DOS virtualization ecosystem is a critical component for maintaining legacy operations that rely on applications developed in QuickBasic, Turbo Pascal, C, and assembly. Originally created for 16-bit and 32-bit environments, these applications remain indispensable for businesses that depend on legacy systems. Virtualization employs emulators or virtual machines, such as DOSBox and VMware, to recreate MS-DOS environments on modern hardware, ensuring compatibility with specific hardware and peripheral needs including serial ports and legacy printers. Our expertise spans 14 verticals, providing tailored solutions for the unique demands of various industries.

Challenges of Legacy MS-DOS Applications

Legacy MS-DOS applications were originally designed for 16-bit hardware, which is now obsolete and difficult to replace. Businesses relying on these systems encounter compatibility issues when attempting to run them on modern 64-bit operating systems, and the scarcity of replacement parts for outdated hardware further complicates maintenance, leading to increased downtime and operational costs. Another critical challenge is the dependency on external peripherals such as legacy printers and industrial sensors, which may not be supported by current systems. Unsupported operating systems like MS-DOS and Windows XP also pose significant security risks.

How we virtualize MS-DOS applications

We virtualize MS-DOS applications in the way that fits the program. On-premises virtualization uses tools such as DOSBox-X and VMware to run the application on current Windows, macOS, or Linux hardware, with serial ports and printers handled explicitly rather than assumed. Cloud virtualization on AWS or Azure makes the application reachable from any device, including phones and tablets, for programs that need only files, a screen, and a network. We handle specific hardware and peripheral requirements case by case, and we offer a transition path to full modernization in C# .NET, Go, or Rust when the virtual environment turns out to be a stopgap.

How we modernize MS-DOS applications →

Start with an assessment for a virtualization project

For a DOS virtualization project the read-only assessment inventories what decides the design: the executables and whether the source exists, the DOS version and the CONFIG.SYS and AUTOEXEC.BAT entries it needs, memory managers and drivers, the ports and devices the program uses, the printers and escape codes, any dongle, the data files and their locations, how many users share them, the machines it runs on now, and what the business expects from it over the next several years. Everything is read from files and configuration, and nothing in production is touched. The result is a written recommendation covering the emulator or virtual machine choice, the hosting location, the peripheral plan, and whether a migration should follow. The fee is quoted after the free 1-hour consultation and creditable toward a subsequent modernization project.

About the assessment →

Deliverables

  • On-prem virtualization with DOSBox or VMware
  • Cloud-based virtualization on AWS or Azure
  • Peripheral support (serial ports, printers, sensors)
  • Mobile access from phones and tablets
  • Optional path to full modernization (C# .NET / Go / Rust)

Common questions

Can MS-DOS programs run on Windows 11?

Not natively. Windows 11 is 64-bit only, and 64-bit Windows has no NTVDM and cannot run 16-bit x86 code. A DOS program on Windows 11 runs inside an emulator such as DOSBox-X or inside a virtual machine. Either way, the DOS application keeps working on current hardware.

What is the difference between DOSBox-X and a virtual machine for DOS?

DOSBox-X is an emulator that imitates a PC and DOS in software, and it runs on Windows, Linux, and macOS. A virtual machine runs a real copy of DOS on virtual hardware under a hypervisor such as Hyper-V or VMware. The emulator is simpler to deploy. The virtual machine is closer to the original machine for programs that depend on a specific DOS version or driver.

Can a virtualized DOS program use a serial port or a printer?

Usually. DOSBox-X can pass a host serial port through to the program and can send parallel port output to a real port, a file, or a virtual Epson ESC/P2 printer. Printer output from the virtual printer is black and white, and not every command is supported. Dongles and unusual hardware need testing before you commit.

Why does my DOS program run too fast in DOSBox?

The program was written for the speed of an old CPU, and some DOS programs time their work with loops instead of the clock. DOSBox-X lets you set the cycles value, the number of instructions it emulates each millisecond, to a fixed number, auto, or max. A lower fixed value slows the program. DOSBox-X is not cycle accurate, so the right value is found by testing.

Can DOS applications run in the cloud on AWS or Azure?

Yes, if they need only files, a screen, and a network. The program runs in an emulator or a BIOS-boot virtual machine hosted in the cloud and is reached remotely. Amazon EC2 uses Legacy BIOS by default on Intel and AMD instance types, and Azure Generation 1 machines use BIOS-style boot. Hardware on serial or parallel ports stays on site.

Can we keep using the DOS application while it is being virtualized?

Yes. The original machine stays in service while the virtual environment is built and tested beside it. The two run on the same inputs and the outputs are compared. Users switch only after the results are accepted, and the old machine is kept available as a fallback for an agreed period.

How much does MS-DOS virtualization cost and how long does it take?

The bands on this page apply: $5,000–$40,000, and 2 to 6 weeks. Straightforward programs that need only files and a screen sit at the low end. Programs with printers, serial devices, several users, or cloud hosting sit at the high end. The price and schedule are fixed after the Legacy Software Assessment.

Is virtualization a permanent solution for a DOS application?

It can be, if the program is stable, rarely changes, and the environment is documented and backed up. It is a stopgap if the program must change, exchange data with current systems, or gain new interfaces. The assessment states which case applies and, when it is a stopgap, plans the migration to C# .NET, Go, or Rust.

Sources

Not sure where to start?

Start with a fixed-scope Legacy Software Assessment: a read-only review of your application’s source, database, configuration, logs, and architecture, ending in findings with evidence and a written recommendation. Quoted after the free 1-hour consultation; creditable toward a subsequent modernization project.