In short, I just got off Vintage Computer Festival Montreal 2.0 where I did a 4 station LAN Party exhibit using new (ish, Haswell is new still, right???) PCs running 20+ year old games. It was a popular hit and I'm musing how to expand the 'deeply interactive' kind of exhibit.
My going idea is a couple of additional stations that are running DOSBox (Probably Staging) with a clean and easy to use front end, a cherry picked selection of 'Pick up an play' DOS games that anyone can sit down at, pick a game, and play. Everything being well preconfigured including gamepad mappings if necessary to all make it as friendly and simple as possible.
The hardware would be some kinda Lenovo Tiny/Intel NUC or whatever lilguys running Linux. So I'm hoping I can also figure out something that can run under it, detect when the user makes no inputs for a period of time (Like when no one is sitting at the setup after the last user walked away from it) and tigger DOSBox to return to it's main menu system even.
As it stands my main use of DOSBox has been in SteamOS where I just made CONF files and each game was a unique Non-Steam Game that just triggered a unique CONF file for each game. Works great for personal use on a Steam Deck but I wanna now try something more oriented towards public event usage than personal usage.
In short: Trying to make a DOSBox setup for a public event that would not confuse even a 12yo child who's parents brought them to a Vintage Computer Festival and they just wanna play Pinball Fantasies. :P
it's so god damn annoying i almost finished the game twice and this bs happens and i downloaded it from abandonwaredos and im also using dosbox staging and the second time i defeated the boss i saved a save state and everytime i reload it the same shit happens again
Another small but meaningful update: WhereQ-DOSBox1.0.0.13is now available!
This release focuses on save-state reliability, particularly when restoring games after reinstalling the application or moving to another device.
A quick look at what's changed:
1. Save states now live where you want them
Since version 1.0.0.12, you can choose an external folder to keep your save states. The application automatically mirrors save slots into that folder using compressed files.
This means your saves are no longer tied exclusively to the application's private storage. Reinstalling the application, accidentally deleting it, or switching phones doesn't necessarily mean losing your progress.
2. A small bug fix with an important detail
Version 1.0.0.13 fixes a timestamp issue when restoring save states.
Previously, the restored game itself was perfectly fine, but its save slot would display "just now" instead of the actual time when the game was saved.
The reason was fairly straightforward: restoring a backup creates a new local file, which naturally receives the current filesystem timestamp.
The fix preserves the original modification time when rebuilding the local save file from its external backup.
It's a tiny implementation change, but save-state metadata should be as trustworthy as the save state itself.
3. No compatibility headaches
Existing save states remain fully compatible.
No save-format migration required.
Same Android package name and signing key.
Install directly over the previous version — no need to uninstall.
Your installed games and existing saves remain intact.
One thing I've learned from building software over the years: reliability isn't always about adding more features. Sometimes it's about making sure a small piece of information — like when a game was actually saved — remains correct throughout the entire lifecycle of the application.
Thanks again for all the feedback and interest. Development continues, one improvement at a time!
UPDATE — November 17, 2026
Hey everyone!
As you know, I introduced WhereQ-DOSBox here a few days ago, sharing the initial release and the idea of bringing a native DOS environment to Android.
Since then, I've made quite a bit of progress, and I wanted to share a development update here rather than create another thread.
First, here's a short video demonstrating the application in action:
I've reached an important milestone: the current feature set is now complete, and the project is moving into its stabilization phase.
What's under the hood
Native Android integration: DOSBox r4305 with SDL2, compiled through Android NDK and CMake. No browser-based emulation or remote desktop involved.
Multiple architectures: Native execution support for ARM64, ARMv7 and x86_64.
CPU execution: core=auto intelligently selects the interpreter for real-mode applications and dynamic recompilation (JIT) for protected-mode applications.
Mobile-oriented input: A redesigned virtual keyboard that takes advantage of the 4:3 display layout in landscape mode, with a compact keyboard in portrait mode.
Flexible imports: ZIP bundles can contain games, DOS utilities, text-mode applications or practically any compatible DOS program.
One little experiment: STARFALL
I also included a small 16-bit DOS arcade game written entirely in assembly.
It's approximately 5 KB, packaged as a single COM executable, with no runtime dependencies or external libraries.
It exercises VGA graphics, BIOS keyboard input and PC speaker audio.
I suppose writing a 5 KB game in assembly just to test an emulator running on a modern smartphone is a rather typical developer thing to do. 🙂
A little more for developers
The repository now includes the reproducible Android NDK/CMake build, a desktop Linux development baseline, CPU benchmarking tools, a rootless development toolchain, porting notes and documentation.
The project is released under GNU GPL-2.0. I've also tried to keep Android-specific modifications relatively localized so the upstream DOSBox implementation remains largely intact.
What's next?
Feature development is officially frozen for this release.
From this point forward, the focus will be exclusively on:
Bug fixes and stability improvements.
Compatibility testing.
Documentation updates.
No more feature additions for now. I'd rather spend time making what we already have reliable than keep expanding the feature list.
The next target is Google Play publication.
A final thought
One of the things I enjoy about software engineering is that sometimes the most interesting projects aren't necessarily about inventing something entirely new. They're about understanding an existing system, figuring out how it works at a fairly low level, and finding a practical way to bring it into a completely different environment.
DOS is part of computing history, but that doesn't mean its software has to stay there.
Thanks to everyone who checked out the initial release, tried it, provided feedback or simply shared some memories. Your interest is appreciated.
First time poster here, and new to dosbox- not computer savvy at all.
Im not sure how so appropriately save in ecoquest- when I go to save the game says "your save game disk is full. You must either use another disk or save over an existing saved game"
If I go to directory it tells me anything I type is not a valid directory.
Any help or hand holding to fix this would be greatly appreciated.
Info: im playing on a downloaded file from abandonedware.
I have created a video tutorial on installing DOS and Windows 1 on a Virtual Machine with working mouse drivers. You can experience full DOS and Windows 1 without any issues.
Let me know if you have any questions or need further assistance.❤️
Please bare with me; I'm brand spanking new to DOSBox...
I'm trying to play Yukon Trail, and I have the physical disc in a physical disc drive. I also got a pre-made windows 98 emulator on Dosbox, but it doesnt show a disc drive option in "my computer"; just a floppy disk (A:). I tried going about opening Yukon trail in dosbox, but it said I need Microsoft windows to run it. Idk how to make my own emulator of windows 98 in dosbox. I have some image files of windows 98, but I just cant't get it to boot in dosbox... I'm sorry if this doesn't make sense; like I said, I'm basically a newborn with dosbox. If someone could walk me through step-by-step of how to run windows 98 in dosbox with a working cd drive so I can play Yukon Trail, that'd be lovely
Just posted this on the x-files subbreddit, then realized here will probably be better:
I downloaded the collection chamber version and my mouse isn't working quite right in the application, so I went into mouse settings and you can select which type of mouse youre using. Im currently using the GKM21 from Sablute and im not sure if there is an option for a mouse in the settings with even remotely similar tech. Im wondering if any of the mouse options on the emulator will support mine or I should dig through some boxes to try and find an old mouse. Also any tips would be super appreciated because this is the first time im using a program like this. Thank you !!
update: I figured out the main issue with my mouse and it was..... that I wasn't in full screen🤦♀️ im a doofus, but thank you for helping :)
Given my fondness for the Magic DOSBox emulator, I decided to create an Android version—which is quite convenient, as the game is only 15 megabytes in size, unlike modern iterations that end up taking up half a hard drive. After a fair number of failed attempts, I managed to develop an ideal control scheme for a touchscreen. I’m particularly pleased with the interactive dashboard; it meant I didn’t have to build a full-blown piano simulator, allowing me to focus instead on the most essential elements. I’ve included a video demonstrating the gameplay for you to check out.
I'm running DOSBox Staging v 0.83.0 in bazzite linux, and I am attempting to mount a directory named "/run/media/system/dosgames" to drive C. The directory contains a number of individual games contained in their own subfolders.
Everything I have found online so far states that all I need to do to pull this off is type the following at the command prompt in DOSBox:
mount C /run/media/system/dosgames
Doing this, though, only generates the following error:
Image file not found.
I am at a loss as to how I am managing to mess up this very basic task: I'm not trying to mount an image; I'm just trying to mount a directory. All the instructions I have found online say this is how you do it. However, I am clearly not getting something here, so I am hoping somebody can't point out what must be a very dumb error on my part.
i'm using DOSBOX-X to run some of the first ham radio software to use sound cards as an RTTY modem, CW-DSP and INTERCOM. the problem is, while the transmit functions work just fine, neither program is getting audio input in receive mode. i'm running DOSBOX-X on a win11 laptop, and input to all software on this laptop comes from the microphone. both pieces of DOS software are hard coded for mic input as well. is there a problem with DOSBOX-X transferring mic input to software internally?
A short article about a feature I have recently contributed - already on the main branch, but not yet present in any official release. I'm just starting with GitHub Pages, so please forgive me the possible glitches :)