dosbox-automation vs DOSVisor
dosbox-automation
dosbox-automation.orgDOSVisor
github.comSide by side
| Figure | dosbox-automation | DOSVisor |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | Yes |
| Linux | Yes | — |
| API | Yes | — |
| Plans published | 0 | 1 |
| Spec score · MS-DOS Emulators | 7.9 (#10) | 7.8 (#12) |
| Purpose | dosbox-automation is a DOSBox Staging fork that lets launchers, test harnesses, and scripts launch, drive, and inspect DOS applications and games. | DOSVisor is a DOS emulator that uses the Windows Hypervisor Platform API to run DOS programs in a virtualized 16-bit real-mode environment on modern Windows systems. |
Plans
In their own words
dosbox-automation
dosbox-automation is a free DOSBox Staging fork for automating the launch, control, and inspection of DOS applications and games. Its HTTP REST API uses bearer-token authentication and includes Swagger UI, while a sandboxed Lua engine can drive execution and input with frame-accurate timing. It can record and replay keyboard and mouse input, capture frames and video, read text in text modes, and inspect memory and CPU registers. TOML recipes can automate installations, including disk swaps, through the API and Lua engine. The project includes DOSBox Staging functionality, added fixes and hardening, and a FluidR3 General MIDI soundfont enabled by default. Official builds are available for Windows and Linux; the Linux build is statically linked and targets x86_64. There are no official macOS builds, and compiling from source is described as untested. The webserver is disabled by default. When enabled, it binds to localhost by default, requires a bearer token, restricts mounted paths, and runs Lua without filesystem or process access. Windows 9x is not supported.
DOSVisor
DOSVisor is a Windows project that runs some MS-DOS programs in a virtualized 16-bit real-mode environment using the Windows Hypervisor Platform API. It is presented as a demonstration of that API rather than a complete DOS emulator. Hardware virtualization handles the CPU, while software emulates the DOS layer. A custom Interrupt Vector Table uses CPUID instructions to trigger VM exits and intercept DOS interrupts. DOSVisor captures I/O requests but supports only a small set of common requests. Timing support includes the BIOS counter, RAM refresh toggle bit, system clock, RTC registers, clock interrupts, and DOS current-time calls; the 8253 PIT timer is not fully implemented. Keyboard handling monitors state, keeps a simple buffer, and passes input through interrupts. Basic terminal commands support simple text-based games and other basic programs. BIOS data areas and the Program Segment Prefix are allocated but mostly unpopulated. The free public repository contains bin and src directories, with no releases or packages listed.