Importing and Managing MS-DOS Games with DOSBox

MS-DOS games are usually installed programs rather than single cartridge-style ROMs. One game may include an executable, data files, a sound setup utility, a DOSBox configuration, and one or more disc images. LaunchBox for Windows includes DOSBox support that can mount the game folder, start the correct program, and mount extra folders or images when needed.

Before you begin

Use game files you are legally entitled to use. Commercial DOS games remain copyrighted unless the rights holder says otherwise; “abandonware” is not a legal permission category.

Give every game a permanent, writable folder. Saves and game-specific settings are often written inside that folder, so do not run a game from a temporary extraction location. If you have a ZIP or another archive, extract it first.

Choose the correct LaunchBox workflow

• Several already-installed DOS games: go to Tools > Import > MS-DOS Games.... The importer is designed for installed games separated into folders.

• One game that still needs installation: go to Tools > Import > Install DOS Game.... The wizard can work with an already-installed game or guide installation from physical media, an ISO or BIN/CUE image, or a folder of installation files.

• One installed game you want to enter yourself: use Add, or Tools > Import > Manually Add Game, then configure the Launching, DOSBox, and, when needed, Mounts pages.

• A GOG release that already launches correctly: use Tools > Import > GOG Games.... GOG DOS releases commonly include their own launcher, DOSBox copy, and configuration. Preserve that working package instead of rebuilding it without a reason.

Import already-installed DOS games

1. Place each game in its own folder and identify the program that starts it, normally an .EXE, .COM, or .BAT file.

2. Open Tools > Import > MS-DOS Games....

3. Add the parent folders or individual startup files you want LaunchBox to scan.

4. Choose whether LaunchBox should leave the folders where they are, copy them, or move them. Review this choice carefully: moving changes the original location, while copying needs enough free space.

5. Choose metadata and media options.

6. Review the DOS-specific options. The wizard can look for PDF manuals, dosbox.conf files, and setup programs; it can also attempt to mount an ISO or CUE as CD-ROM drive D. Automatic detection is a starting point, not a guarantee.

7. On the final game list, verify each Title, Root Folder, and startup file. Correct a wrong guess before completing the import.

The importer creates or uses the MS-DOS platform and enables LaunchBox's integrated DOSBox support for the imported games. If copying or moving is selected, LaunchBox handles the whole selected game folder; the optional folder-renaming setting is shown only for those modes.

Install a game from media

Tools > Import > Install DOS Game... opens a separate installation wizard. It can launch the installer inside the DOSBox copy included with LaunchBox, create a destination inside your LaunchBox games area, and then ask you to identify the installed startup file. Depending on the source, it can copy installation files or an image and offer to keep the source mounted for games that require the disc while playing.

1. Choose whether the game is already installed or still needs installation.

2. Select the physical drive, image, or installation folder requested by the wizard.

3. Keep the proposed destination unless you have a deliberate folder plan.

4. Complete the game's installer inside DOSBox. When asked for a DOS destination, use the virtual path shown by the wizard—not the Windows path as DOS text.

5. Run the game's setup program for sound and controls before leaving the DOS environment.

6. Confirm that the installation completed and verify the startup file LaunchBox proposes.

7. After LaunchBox opens the game editor, check its title and metadata, then test the game.

How the integrated DOSBox launch works

When Use DOSBox to play this game (only for old MS-DOS games) is enabled, LaunchBox normally does the following at launch:

• Uses the DOSBox executable and default dosbox.conf included under LaunchBox's ThirdParty\DOSBox folder.

• Mounts the game's Root Folder as virtual drive C. If no valid root is set, LaunchBox falls back to the application folder.

• Changes to the subfolder containing the selected application, if necessary.

• Runs the filename in Application Path with its command-line parameters.

• Mounts any additional folders or disk images configured on the game's Mounts page.

Because LaunchBox builds these commands, a normal integrated setup does not require you to type MOUNT commands yourself.

Configure a game manually

Right-click the game and choose Edit, then review these pages:

• Launching: set Application Path to the program that starts the game and set Root Folder to the top of that game's DOS filesystem. Configuration Application Path is for the game's setup utility, such as SETUP.EXE, INSTALL.EXE, CONFIG.EXE, or SETSOUND.EXE.

• DOSBox: enable Use DOSBox to play this game (only for old MS-DOS games). Leave Custom DOSBox Configuration File (dosbox.conf) blank to use the default, or choose Create.../Browse... for a per-game configuration. Leave Custom DOSBox Version EXE Path blank to use the version included with LaunchBox.

• Mounts: use Add Folder... or Add Disk Image... for media that must be available in addition to the automatically mounted application/root folder. Select the virtual drive letter and check the proposed type and filesystem.

The disk-image picker recognizes ISO, CUE, and IMG files. It initially treats ISO/CUE as a CD-ROM/ISO mount and IMG as a floppy image, but you should verify the drive letter, type, and filesystem. For a BIN/CUE set, select the CUE descriptor and keep every referenced BIN track beside it. Mounting only one BIN can omit tracks or CD audio.

DOSBox, emulator-based launching, and ScummVM are separate launch modes in the game editor. LaunchBox prevents them from being enabled together for the same main game.

Example DOSBox commands

You normally do not enter these commands when using LaunchBox's integrated fields, but knowing their purpose helps when editing a custom configuration's [autoexec] section or testing outside LaunchBox:

• mount c "C:\Games\DOS\DOOM"

• c:

• DOOM.EXE

• exit

A CD image might be mounted separately:

• imgmount d "C:\Games\DOS\DOOMCD\DOOM.cue" -t iso

• mount c "C:\Games\DOS\DOOMCD"

• c:

• DOOM.EXE

These are examples, not paths to copy literally. Keep the virtual drive layout consistent with the layout used during installation. Do not mount the root of your Windows system drive as writable DOS storage.

Per-game configuration and custom DOSBox builds

Games can need different CPU cycles, machine types, memory, sound devices, rendering, or joystick mapping. Create a per-game dosbox.conf from the game's DOSBox page and change only settings the game requires. A global change can affect every game still using the default configuration.

You can point Custom DOSBox Version EXE Path to another DOSBox executable. This keeps the game in LaunchBox's integrated DOSBox workflow, but compatible command-line behavior is still required. DOSBox Staging, DOSBox-X, and other projects have their own supported settings and flags; a configuration written for one build is not automatically portable to another.

Alternatively, you can define a DOSBox-family program under Tools > Manage > Emulators... and launch DOS content through it as an emulator. That is a different configuration model. Beginners should use one method per game and avoid mixing an emulator association with the integrated DOSBox checkbox.

CDs, floppy images, and multiple discs

• Reuse the virtual drive letter used during installation. Some games remember that letter and later report that the disc is missing if it changes.

• Keep descriptor and track files together. CUE/BIN is often preferable to an ISO when the original disc contains audio or multiple tracks.

• Add only the media the game needs. The Mounts page assigns additional images or folders to DOS drive letters; the game folder itself is mounted automatically.

• Multiple-disc behavior and the key used to cycle images can differ among DOSBox builds. Follow the documentation for the exact build selected in Custom DOSBox Version EXE Path.

Setup utilities and Additional Apps

The simplest way to expose a setup program is Launching > Configuration Application Path. LaunchBox can then offer its Configure action for the game and run that program through the same integrated DOSBox environment.

For other utilities, open Edit > Additional Apps, add an application, select its path, and enable Use DOSBox. A DOSBox-enabled Additional App uses the parent game's root folder, extra mounts, selected DOSBox executable, and DOSBox configuration. This is useful for alternate executables, editors, or a second setup tool. Do not enable the automatic run-before/run-after options unless the utility truly must run every time.

GOG and other preconfigured releases

The GOG importer looks for the package's intended Windows shortcuts and can attach other GOG shortcuts, such as DOSBox configuration, multiplayer, or settings, as Additional Apps. If the imported shortcut already works, keep that package together. Changing its DOSBox executable, configuration paths, or working directory can break a setup that GOG has already tailored for the game.

If you deliberately convert a storefront package to LaunchBox's integrated DOSBox mode, treat that as a new manual configuration: identify the real game root, startup file, configuration, mounts, and save location first.

Sound, controllers, and saves

Many DOS games require their own setup utility. Run it in the same mounted environment used for play, choose devices supported by your DOSBox configuration, and match any displayed port, IRQ, and DMA values. A game with no sound is usually fixed in the game's DOS setup or its DOSBox configuration, not in LaunchBox's general audio settings.

Keyboard, mouse, and joystick support varies by game. Configure the game first, then use the mapper belonging to the selected DOSBox build if a modern controller needs remapping. Preserve access to keyboard commands and test that your pause and exit bindings do not conflict.

Many DOS games save inside their installed folder. Keep the root folder writable and stable, and back up the whole game folder when the save location is unknown. Also include per-game .conf files, mapper files, and disc images in your backup.

Troubleshooting

• “Illegal command” or wrong program starts: check Application Path, Root Folder, and the selected startup filename. Confirm the executable is inside the root folder.

• The game asks for its CD: check the image path, CUE dependencies, mount type, and virtual drive letter. Match the letter used during installation.

• The game works in DOSBox but not from LaunchBox: compare the DOSBox executable, configuration file, root folder, mounts, application path, and parameters. Integrated LaunchBox launching automatically generates its mount/start sequence.

• No sound: run Configuration Application Path or the relevant Additional App and match the game's device choices to the per-game DOSBox configuration.

• Black screen, stutter, or excessive speed: start from the default configuration and adjust only the documented machine or CPU settings for that game.

• DOSBox closes before you can read the error: go to Tools > Options > Integrations > DOSBox and temporarily enable Don't exit DOSBox when exiting games, Pause before exiting DOSBox, or Show all DOSBox commands.

• Saves disappear: verify that LaunchBox mounts the same writable root folder every time and that no launcher is using a temporary or read-only copy.

• Wrong metadata match: use the MS-DOS platform, or set a custom platform's Scrape As value to MS-DOS, and search with a clean title. Choose the DOS release rather than a similarly named Windows, console, or Amiga release.

A reliable beginner test

Start with one installed game in its own writable folder. Import it with Tools > Import > MS-DOS Games..., verify the final startup file, and test it with the included DOSBox and default configuration. After basic launching works, add a setup program, CD image, per-game configuration, or controller mapping one change at a time.