DOSBox

The people behind DOSBox

What DOSBox supports

• RetroArch and other libretro frontends
• Host OSes where RetroArch and the chosen core are built and distributed (commonly Windows, Linux, macOS, Android — availability depends on the core build/packaging)
• DOS game disk images and directories mounted as drives via core/RetroArch configuration
• Standard DOSBox config options via per-core config or generated config files

Download and availability

DOSBox setup guide

1. 1) Choose and install a core: Open RetroArch, go to Online Updater (or Core Updater) and select a DOSBox-related core (named dosbox, dosbox_core, or DOSBox-Pure depending on your RetroArch build). If your platform or build does not provide the core via the updater, fetch the core binary from the core's official source repository or your distribution's package (consult the core's README). Place the core binary (.so/.dll/.dylib/.wasm as appropriate) into RetroArch's cores directory and refresh RetroArch.
2. 2) Prepare your DOS content: Obtain the game files legally. For most DOS games you will either point the core at a folder containing the game's files, a disk image (IMG, ISO), or an executable. Do not expect the core to include commercial game files or BIOS; provide them yourself when required.
3. 3) Generating or placing a DOSBox config: Many libretro DOSBox cores use a per-core config directory under RetroArch's system or config directories. You can let the core generate a default config by launching the core and then using the core's built-in command (docs.libretro.com notes how to generate and save a config), or create a dosbox.conf-style file in the core/system directory. Consult the specific core docs for where the core looks for its config file.
4. 4) Mounting drives and launching a game: In RetroArch you can either: (A) Load Core, then Load Content — selecting the game's executable or image; or (B) from a shell/CLI run retroarch -L /path/to/core "path/to/game". Within the running core, use DOSBox-style commands (such as MOUNT C /path/to/game) if the core exposes the DOS prompt, or rely on the core to auto-mount content if it supports automatic mounting (behavior differs by core).
5. 5) MIDI, sound and OPL configuration: Cores may expose options for MIDI backend, OPL emulation and MT-32. Configure these via the RetroArch Quick Menu -> Options while a core is loaded, or by editing the core's config file. If you require external MIDI routing or MT-32 ROMs, provide them yourself and follow the core's documentation for specifying paths.
6. 6) Save states, input and performance: Use RetroArch features (save states, input mapping, shaders) normally. For CPU/cycle tuning and timing-sensitive games, adjust core-specific cycle or CPU options in the Quick Menu or config; consult the core docs because behavior and option names vary between dosbox_core, dosbox-pure and other forks.
7. 7) Advanced: manual core installation and config locations: If installing cores manually, place core files in RetroArch's configured cores directory and copy any example config files from the core repository into RetroArch's system/config directories. Check the core's repository for any required extra files or .info entries (some distros include a .info file listing supported extensions and checksums).

Sources and further reading

• Libretro docs — DOSBox core page
• Libretro docs — Core list
• GitHub — realnc/dosbox-core (libretro core repository)
• Libretro docs — Download cores (RetroArch core updater guidance)
• DOSBox (original project) — Wikipedia (origin year reference)
• Featured-image source and credit