WhereQ-DOSBox: Yesterday's Computing. Today's Pocket. Tomorrow's Possibilities.


Remember when computers had no app stores, no touchscreens, no cloud accounts, and somehow we still managed to spend entire weekends playing games? 😂
We used to type commands like C:\GAMES\DOOM.EXE and consider ourselves computer experts.
Well, DOS never really left. It was just waiting for a smaller computer.
Today, we're taking a meaningful step in bringing that world to Android with WhereQ-DOSBox.
Not a DOS emulator running inside a browser. Not a remote desktop connecting to an old PC. It's a native Android application with the actual DOSBox emulator core running as a native library inside the APK.
And there's quite a bit more behind it.
Watch it running
WhereQ-DOSBox on a phone: FIFA 96 in the middle, the two console pads in the letterbox bars either side, and the 1990 World Cup song under it. Everything on screen is the real DOSBox core, running as a native library inside the APK.
More than just running DOS games
Native Android architecture
DOSBox r4305 with SDL2, integrated through Android NDK and CMake. Native execution across ARM64, ARMv7 and x86_64.
Intelligent CPU execution
The core=auto configuration automatically uses the interpreter for real-mode applications and switches to dynamic recompilation (JIT) for protected-mode applications. DOS/4GW programs are part of the compatibility journey.
A keyboard that understands mobile
DOS games were designed for keyboards, not thumbs. We didn't simply shrink a desktop keyboard onto a phone.
The 4:3 DOS display stays in the middle, while frequently used controls occupy the left and right letterbox areas in landscape mode. Portrait mode gets a compact bottom keyboard.
Your DOS environment, your programs
Import ZIP bundles, install multiple bundles from a folder, or open ZIP files directly from Android's file manager.
And here's an important distinction: a bundle doesn't have to contain a game. It can be a DOS utility, a text-mode application, or practically any compatible DOS program.
No unnecessary storage permissions. Android's system file picker provides access only to the files you select.
A little game called STARFALL
We also built a tiny 16-bit DOS arcade game in assembly.
Approximately 5 KB. One COM executable. No runtime. No external libraries.
It exercises VGA graphics, BIOS keyboard input and PC speaker audio.
Sometimes the best way to demonstrate an entire emulator is with a game smaller than the average social media profile picture. 😂
And for developers, there's another story
We didn't want to deliver just an APK and hide everything else.
The project includes:
- A reproducible NDK/CMake Android build.
- A desktop Linux baseline for development and testing.
- CPU-core benchmarking tools.
- A rootless development toolchain — no root, no sudo required.
- Porting notes and benchmark documentation, plus the complete source code.
- GNU GPL-2.0 licensing, preserving the open-source lineage of DOSBox.
The Android-specific changes are kept relatively small and localized, leaving the upstream DOSBox implementation largely intact.
The whole implementation is written up in one place — the technical reference — with the diagrams, the source references and the measured numbers.
Why build this?
Technology moves forward, but that shouldn't mean everything behind us becomes inaccessible.
There are thousands of classic DOS games, educational programs, business utilities and pieces of software that deserve to remain usable and discoverable.
We believe preservation shouldn't be limited to museums, virtual machines or vintage hardware collectors.
Sometimes, preservation simply means making something old work on something new.
A phone in your pocket can now open a DOS prompt.
And somewhere, a 1990s computer enthusiast is probably wondering why we need 8 CPU cores to run a 5 KB game. 😁
A milestone, not an ending
The Android migration is finished, and the project carries a tag that says so:
milestone/android-migration-complete
The emulator core builds for three ABIs, the app layer works on a real device, save states carry the whole machine — the sound chips included — and the desktop baseline links. What comes next is maintenance: bug fixes and documentation polish, no new features.
Get it
WhereQ-DOSBox is open source, and the journey is ongoing.
👉 github.com/whereq/whereq-dosbox
If you grew up with DOS, we'd love to hear from you:
What's the one DOS application or game you would bring back to life first?
Let's keep the old machines running, even when the machines themselves are no longer around.
Thank you, DOSBox
None of this is possible without the DOSBox project.
DOSBox was written by the DOSBox Team — a volunteer crew who took an operating system from 1994 and made it runnable on every machine the world has produced since, including the ones that did not exist yet. They kept it alive for three decades and gave it away to anyone who wanted it. WhereQ-DOSBox is a thin layer on top of their work. The originality, the craft and the generosity are entirely theirs.
This port is built on Em-DOSBox, the Emscripten build of DOSBox r4305 by Boris Gjenero, which grew out of Ismail Khatib's first attempt to compile DOSBox with Emscripten, and rode on the Emscripten work of Alon Zakai. The SDL2 library by Sam Lantinga carries the window, the audio and the touch input.
DOSBox is a trademark of the DOSBox project; this port is not affiliated with or endorsed by the DOSBox team.
A phone in your pocket can open a DOS prompt. That is the whole idea, and it took longer than it should have. If you remember a DOS program that deserves another run, tell us which one — we might build it.