No. According to the README:

- SoundBlaster 16 / SoundBlaster Pro I & II / SoundBlaster I & II
      By default DOSBox provides SoundBlaster 16 level 16-bit stereo sound.
      You can select a different SoundBlaster version in the configuration of
      DOSBox. AWE32 music is not emulated as you can use MPU-401 instead.

Basically you can often get equivalent or better results by selecting SB16 for digital effects, and General MIDI for music, in the games sound setup. For General MIDI you typically will want to set mididevice = fluidsynth in your DOSBox config file and specify a suitable sound-font. See the MIDI page for more information.

Further reading and comments available in this vogons forum discussion.

Their rates are controlled by the mixer rate, leaving only the pcrate, which can be adjusted to avoid harmonics, in rare cases.

A console message will describe the version of ROM being used, for example:

MT32: Initialized CM-32L/LAPC-I Control v1.02

Or possibly easier, run the mixer /listmidi command from DOSBox Staging.

[Top]

The location of the default dosbox-staging.conf config file depends on the host OS and method of packaging.

• Linux: ~/.config/dosbox/
• Linux Flatpak: ~/.var/app/io.github.dosbox-staging/config/dosbox/
• macOS: ~/Library/Preferences/DOSBox/
• Windows: C:\Users\<username>\AppData\Local\DOSBox\

Linux users can customize the parent (.config/) location by setting the XDG_CONFIG_HOME environment variable.

If you still cannot find dosbox-staging.conf on your system, open the relevant command prompt for your system, change to the Dosbox-Staging directory, then run one of the commands below accordingly:

• Linux - Bash: ./dosbox --printconf
• MacOS - Terminal: ./dosbox --printconf
• Windows - CMD: dosbox.exe --printconf
• Windows - Powershell: .\dosbox.exe --printconf

Instead of starting Dosbox-Staging, the --printconf switch will only display where dosbox-staging.conf is located on your system.

The third way to find the location of dosbox-staging.conf on your system is to open Dosbox-Staging, then click on the DOSbox Status Window. At the top of the DOSbox Status Window, look for the line CONFIG: Loaded primary config file ''. The location of dosbox-staging.conf will be displayed between the two single-quotation marks on that line.

After finding the location of dosbox-staging.conf, make a shortcut to this file so that you will be able to change Dosbox-Staging's settings as needed.

1. Download and extract Dosbox-Staging to a folder of your choice.

2. Open the relevant command prompt for your system, change to your newly created Dosbox-Staging directory, and create an empty file called dosbox-staging.conf:

• Linux - Bash: touch dosbox-staging.conf
• MacOS - Terminal: touch dosbox-staging.conf
• Windows - CMD: type nul > dosbox-staging.conf
• Windows - Powershell: New-Item dosbox-staging.conf

3. Double-click on Dosbox-Staging's executable to start Dosbox-Staging.

4. Open dosbox-staging.conf in a text editor. You will see that dosbox-staging.conf has now been populated with Dosbox-Staging's default program values.

Dosbox-Staging 0.81.2 and earlier use a default of 3000 cycles for real mode programs, and 100% (as fast as your host CPU can handle it) for protected mode programs. Examples of real mode games include but are not limited to Crystal Caves, Epic Pinball, Jetpack, Lemmings, and Wolfenstein 3D.

Dosbox-Staging 0.82 RC and later also use a default of 3000 cycles for real mode programs, but a default of 60000 cycles for protected mode programs. Examples of protected mode games include but are not limited to Blood, Doom II, Duke Nukem 3D, Jazz Jackrabbit, and Quake.

You can adjust the number of CPU Cycles that DOSBox Staging emulates per second in any of the following ways:

1. Open your dosbox-staging.conf, scroll down to [cpu], and change the number next to cpu_cycles or cpu_cycles_protected to the number of CPU cycles you want to use.

2. Open your dosbox-staging.conf, scroll down to [autoexec], and type cpu_cycles xxxxx or cpu_cycles_protected xxxxx, replacing xxxxx with the number of CPU cycles you want to use.

3. At the DOSBox Staging command prompt, simply type cpu_cycles xxxxx or cpu_cycles_protected xxxxx and press Enter, replacing xxxxx with the number of CPU cycles you want to use. Note that if you do this from the DOSBox Staging command prompt, and then you close DOSBox Staging, you will have to adjust the cycles again when you open DOSBox Staging again at a later time.

4. Adding the line cpu_cycles xxxxx or cpu_cycles_protected xxxxx in your game's .bat file, replacing xxxxx with the number of CPU cycles you want to use.

Adjusting the CPU cycle count will be necessary for CPU Speed Sensitive Games that run too fast if the CPU Cycle count is set too high, such as Duke Nukem 2.

Other games, such as Perfect Assassin, crash if the CPU Cycle count is set to max.

(Chart is originally from https://dosbox-x.com/wiki/Guide%3ACPU-settings-in-DOSBox%E2%80%90X#_cycles.)

Within your dosbox-staging.conf in the [cpu] section, the cycles=auto and cycles=max settings can be parameterized to have different startup defaults.

The syntax is:

cycles=auto ["realmode default"] ["protected mode default"%] [limit "cycle limit"]

cycles=max ["protected mode default"%] [limit "cycle limit"]

Example:

cycles=auto 5000 80% limit 20000 will use cycles=5000 for real mode games, 80% CPU throttling for protected mode games along with a hard cycle limit of 20000.

In Dosbox-Staging 0.81 or later, the maximum supported memsize in dosbox-staging.conf is 3072, or 3072 MB.

In Dosbox-Staging 0.80.1 or earlier, the maximum supported memsize in dosbox-staging.conf is 63, or 64 MB.

1. Open Dosbox-Staging.

2. Type commandhere /? and press Enter.

• Important: Replace commandhere with the command of the help screen you want to access, such as mount, imgmount, dir, or loadfix.

• Commonly Used Examples: mount /?, imgmount /?, dir /?, or loadfix /?

Yes. You can use the -conf or -userconf parameters to load multiple "layered" configurations, where subsequent config files override settings from the prior ones (except the autoexec section, which is merged and launched in sequence). For example:

$ ./dosbox -userconf -conf A.conf -conf B.conf

1. First, your global configuration file is loaded (-userconf).
2. Second, A.conf is loaded, overriding any settings from your global configuration.
3. Finally, B.conf is loaded, further overriding settings applied by A and the global configuration.

Default behavior:

• If no -conf parameters are passed, then dosbox-staging.conf from current working directory is used (only this file; it doesn't matter directory is loaded as drive C or not).
• If there's no dosbox-staging.conf in current working directory, then global file is used (default path for stable release: ~/.config/dosbox/dosbox-staging.conf).
• If global file does not exist, then a new one is generated.

You can see exactly which files were loaded on stderr/terminal output (I know, not the best place); they are prefixed with CONFIG, e.g.:

$ ./dosbox 
dosbox-staging version 0.x
---
CONFIG: Loading primary file /home/dreamer_/.config/dosbox/dosbox-staging.conf

File a.conf has "@echo A" inside, file b.conf has "@echo B" inside - when user runs:

$ ./dosbox -c "@echo C" -conf a.conf -conf b.conf

Then DOSBox Staging shell will output:

A
B
C

[Reference #1] | [Reference #2]

After you upgrade your DOSBox Staging binary it's wise to update your dosbox-staging.conf as well. Your existing settings will be retained however extraneous comments will be dropped.

You have to run DOSBox Staging first then type in the following command:

C:\>config -wc

Modify the mouse_sensitivity = 100 setting in the [mouse] section of dosbox-staging.conf as you see fit.

Increasing the number increases the mouse sensitivity, while decreasing the number does the opposite.

Set mouse_raw_input = true in the [mouse] section of dosbox-staging.conf.

When running DOSBox-Staging, press any of the following key combinations below for their respective functions:

Additional keyboard shortcuts may be available, depending on the machine type being emulated. See the Video Cards section for more details.

[Top]

DOS video mode > SW Scaler > HW Processing output= > Host output texture_renderer=

1. DOS video mode: this is an emulated video mode used by the game. For example, the game might be drawing a 320x200 pixel image of VGA data to the emulated video card, thinking it's running on CRT at 70 Hz. But really its just writing to a 320x200 memory block in DOSBox.
2. SW Scaler: historically, the next step scaled up the image using software routines. Using things like normal2x are no longer needed because the next step can do that in hardware.
3. HW Processing: will use accelerated routines to scale the image to the desired window size. The output = setting also lets us fine-tune the type of scaling - be it "soft", nearest-neighbour (nb), or pixel-perfect (pp). If we're processing the image using OpenGL routines (output = opengl*) then the configured glshader = will also be applied. If we're processing using SDL's accelerated routines (output = texture*), then we forfeit the ability to apply GL shaders, however we still get accelerated scaling brokered by SDL.
4. Host output: Finally we have the interface to the host, and deciding what hardware API should be used to hand over the processed image. This is best left to auto to let SDL pick the best choice (be it OpenGLES2 on the Raspberry Pi, Vulkan on macOS, OpenGL on Linux, or Direct3D on Windows).

If you don't care about glshaders and prefer sharp pixels, then output = texturenb and texture_renderer = auto is universally compatible across platforms (macOS, RPi, Window, GNU/Linux, and even others). This works great on everything we've thrown at it.

... But if you want shaders, then use output = openglnb and texture_renderer = auto.

Additionally, you can switch from nb to pp, if you want pixel perfect (in both scenarios).

• Yes, in that both images will be scaled to nearest neighbour.
• No, in that output = opengl means the DOS output will be processed using OpenGL routines, and the selected glshader will be applied. Whereas output = texture means the DOS output will be processed using SDL's routines, so glshaders won't be applied.

[Reference]

For standard scaling, set scaler = none and let it be done in hardware instead (the only remaining use for scaler is for people who still want to use things like 2xsai, super2xsai, supereagle, etc..). [Reference]

[Top]

If a keyboard combination does not work in a DOS application, it is likely being caught either by DOSBox Staging or even earlier by the host operating system or window manager.

First check if the keyboard shortcut is being caught by DOSBox Staging by checking the keyboard mapper. If this is the case, you can use the keyboard mapper to change or delete the mapping to resolve the conflict.

If it is not DOSBox Staging that is catching the keyboard shortcut, it is probably the host OS or window manager. An example of a key that will typically be caught by the host OS is the Print Screen key, or the CTRL-ALT-DEL combination. For some host operating systems, such as Linux, you can typically change the keyboard shortcuts to prevent such clashes.

If you cannot prevent the clash, you may be able to use the DOSBox Staging keyboard mapper to remap the key combination to something else.

This usually refers to running in permanent mode. The command-line interpreter process fully takes over instead of being nested under DOSBox Staging's own COMMAND.COM.

To start DOSBox Staging with FreeDOS FreeCOM running in permanent mode add these lines to your global config file dosbox-staging.conf under the [autoexec] section (assuming FreeCOM is installed to C:\):

[autoexec]
C:
COMMAND.COM /P

Here's late DR-DOS DEVICE.COM that works with DOSBox Staging. We can't include it since its not open source:

Download link

Just press CTRL and F4 at the same time while in DOS mode and when asked by the program to cycle through your mounted CD/disc images while relying on IMGMOUNT. All CD images must have been properly declared in your [autoexec] section. Example given of such section with the game RAMA:

[autoexec]
imgmount d /home/pc/isos/rama/rama-1.iso /home/pc/isos/rama/rama-2.iso /home/pc/isos/rama/rama-3.iso -t cdrom
C:
CD RAMA
CALL RAMADOS.BAT
EXIT

Please note that some games like Under a Killing Moon do support multiple CD-Rom drives hence no need to swap disc each time, it will be transparent for users.

For a comprehensive list of DOS games that use CD Digital Audio tracks, please refer to https://www.vogons.org/viewtopic.php?p=673031#p673031.

If you plan on using CD images (CUE / BIN, CUE / GOG, DAT / GOG file pairs, etc) in Dosbox-Staging, please use only the imgmount command accordingly.

Do not mount CD / disc images in DOSBox Staging using Daemon Tools or other similar programs.

Instead, use Dosbox Staging's imgmount command only.

If you do use Daemon Tools or other similar programs with Dosbox Staging, you will run into game compatibility issues like this. In order to reduce the future likelihood of running into said compatibility issues, use imgmount only.

The ver setting generally functions the same as VER SET. The VER command itself shows the DOS version, whereas VER SET will set a DOS version. With the ver setting you can specify a DOS version at start. [Reference]

While working in DOS mode (the famous C:\> prompt) it's possible to add/remove files or directories from the host Operating System at the same time. For instance you're installing a game which takes few minutes to complete. In parallel you decide to copy over a patch (eg. patch.exe) into the game directory from your Operating System. At the end of the installation if you go the game directory and type in the DIR command patch.exe will not be listed there. For it to be listed you'll have to refresh the DOS drive's cache. You have several ways to accomplish such task.

The rescan command will force DOSBox to re-read the directory structure. At the DOS prompt simply enter this command:

C:\>rescan

Same as for the rescan command above. Just press CTRL and F4 at the same time while in DOS mode to have your drive's cache refreshed. It's the same key-combination to cycle through your mounted CD/disk images when using IMGMOUNT. Some games like Under a Killing Moon do support multiple CD-Rom drives hence no need to swap disc each time, it will be automatic.

Thanks again to @ripsaw8080 for this tip. The workaround is being described there. In short the cache is not used for floppy drives. Please do note there are potential drawbacks with this method.

PATH tells DOS which directory(ies) should be searched for external commands after DOS searches your current working directory. DOS searches the paths in the order specified in the PATH command. Therefore the leftmost location will take precedence over the other locations. If you enter the PATH command without options, the program will display the currently set path. You can tell DOS to search more than one path by specifying several pathnames separated by semicolons.

Let's assume you added a U: drive to your environment:

[autoexec]
mount u ~/.config/dosbox/utils
set PATH=u:\;%PATH%

Binaries located in the U: drive will take precedence over any other locations.

DOSBox Staging bundles the following translations: Dutch, French, German, Italian, Polish, Russian and Spanish. Thanks to the @translations team! Any help always welcome to improve the current ones or to add more.

DOSBox Staging defaults to using the same language as the host OS (if available), or to English otherwise. This can be overruled by manually setting the appropriately LANG environment variable, or by starting DOSBox Staging with the -lang option. e.g., dosbox -lang fr for French.

Alternatively the language can be specified by simply editing your global config file (dosbox-staging.conf):

[dosbox]
# de, en, es, fr, it, nl, pl, and ru
language = de

Translations files are located under the resources directory.

The Patches Scrolls usually is a good place to start with.

We include our Windows 32-bit binary download links on our GitHub releases page.

Follow the instructions as shown at https://github.com/dosbox-staging/dosbox-staging/pull/3052#issuecomment-1782134730.

[Top]

Each partition in the hard disk image must use the FAT16 filesystem, while the size of each partition must be 2 GB or less.

[Top]

1. Open your operating system's command line interface:

• Windows 11, 10, 8, and 7 - How to Open Command Prompt / CMD

• Windows - How to Open Powershell

• Linux - How to Open Bash

• MacOS - How to Open Terminal

2. In the command prompt window that opens, navigate to your Dosbox-Staging folder and run Dosbox-Staging.

3. If Dosbox-Staging crashes, the Dosbox-Staging status window will not disappear.

[Top]

The Dosbox-Staging team strongly discourages this because of real-time audio processing issues, such as sound stuttering.

Instead, please run Dosbox-Staging natively on a PC. Although you might be able to run Dosbox-Staging on a phone, Dosbox-Staging does not officially support that. As a result, do not expect any help from the dev team and do not raise any phone-related issue tickets either.

[Top]