Skip to content
FreeDOSHow-To Published Updated 5 min readViews unavailable

DOSBox-X Profiles and MIDI: Isolate Game Mounts, Machine Settings, and Audio Paths

Create repeatable DOSBox-X profiles with scoped host mounts, explicit configuration, verified machine settings, and separately routed General MIDI or MT-32 audio.

DOSBox-X is a DOS emulator with a broad configuration surface: its machine model, DOS environment, sound devices, mounted host directories, and MIDI output can all affect one title differently. A reproducible setup uses a named profile per game or collection, limits the host files exposed to DOS, and records the audio device instead of relying on whatever happened to be configured globally.

This guide covers configuration and audio routing, not acquisition of copyrighted games or synthesizer ROMs. Use only content and system files you are authorized to use. Keep original disks and preservation images read-only; use a separate working copy for software that writes save files or configuration.

Separate a profile from the global installation

DOSBox-X supports configuration files and the -conf command-line option. Its documentation describes platform-specific user configuration locations and a working-directory search order. One important detail: -conf loads the named file before DOSBox-X tries the current-directory or user configuration, so it is not necessarily an exclusive profile. Confirm the effective settings and load order on your build; do not assume a named file prevents all global settings from being read. -defaultconf deliberately ignores configuration files and is useful for a clean-default comparison, not for combining with a game profile.

For diagnosis, -defaultconf starts with the emulator’s defaults while ignoring configuration files. Use it as a comparison, not as a permanent way to bypass a profile. DOSBox-X also provides a graphical configuration tool and the CONFIG utility. After a change, inspect the active settings in the application and keep a copy of the profile under versioned backup.

A useful profile separates concerns into sections such as machine, video, memory, audio, MIDI, and autoexec. Keep only the settings that have a documented reason. Avoid copying a full configuration from a different DOSBox-X release without checking whether the option exists and whether its semantics changed.

Mount the smallest useful working directory

The [autoexec] section can run DOS commands at startup. Mount a directory containing only the game and its writable save/configuration files rather than exposing the host’s home directory, system drive, or whole collection. For example, an illustrative profile might contain:

[autoexec]
mount c /path/to/one/game-working-copy
c:
dir

Adjust the host path syntax for the actual operating system and DOSBox-X build. A DOS guest can modify files inside a mounted writable directory, so never mount a preservation master as the game’s writable C: drive. For an optical image, use DOSBox-X’s documented IMGMOUNT workflow and preserve the CUE or equivalent descriptor with all referenced tracks.

Keep installation media and mutable game state distinct where practical. If a game writes unexpectedly, close DOSBox-X cleanly and compare the working directory against its pre-run manifest. Do not make the mount world-writable as a generic troubleshooting step.

Configure General MIDI deliberately

The MPU-401 interface and the synthesizer output are separate decisions. DOSBox-X documents mpu401 modes such as intelligent, uart, and none, and platform MIDI handlers including FluidSynth, CoreAudio, CoreMIDI, and ALSA. A game expecting intelligent MPU-401 behavior may fail or lose timing when the interface is changed to UART just because a different title used it.

For a software General MIDI synth, the profile can select FluidSynth and an explicit SoundFont path, if FluidSynth is included in the build. The SoundFont is an external dependency, not part of every DOSBox-X installation. Record its filename and version, and use only a legally obtained SoundFont. On systems with external MIDI devices, configure and confirm the intended device before saving the profile; device indices can change after hardware or OS changes.

The DOSBox-X menu’s MIDI configuration display and the built-in MIXER /LISTMIDI command can help identify the active handler or MIDI device. Verify with a known MIDI/RMI/MUS test file, then launch the actual game and confirm that it selected the expected music driver during setup.

Treat MT-32 as a different target

An MT-32 or CM-32L path is not merely a different SoundFont preset. DOSBox-X documents an MT-32 emulation mode and a ROM directory containing control and PCM ROM files. Those files are copyrighted system firmware; the emulator documentation does not authorize downloading or redistributing them. If you have a lawful, verified source, keep the original dump unchanged, document its provenance and hash, and configure the profile to point to the exact directory without including the files in a public archive.

Use the game’s own setup program or documentation to determine whether it expects MT-32, General MIDI, AdLib, or another device. Picking a close-sounding device is not the same as matching the intended interface, and MT-32 titles can differ by ROM revision. If the ROMs are absent or the legal source is uncertain, use another documented music device supported by the game rather than seeking a firmware bundle.

Validate and preserve each profile

Test one title after creating its profile. Confirm the emulated machine type, DOS command, mounted directory, controller or keyboard input, graphics, sound effects, music output, save creation, and clean exit. Reboot DOSBox-X with the explicit profile and repeat the test; this catches settings that were applied only in the GUI session.

Keep the DOSBox-X version, profile, dependency paths, and game hash in a manifest. When changing emulator versions or sound drivers, preserve the old profile and compare one variable at a time. A portable profile is useful only when its external dependencies and host paths are understood.

Related:

Sources:

Comments