DOSBoxWiki - User contributions [en]

Building DOSBox with MinGW

2012-03-04T13:06:32Z

Jez9999: /* 5. Compiling DOSBox */ - you need to run autogen first!

== Building your own version of DOSBox ==

Why to do this?<br>
Because any resource-intensive program can benefit greatly from optimization for your exact processor.<br>
[[System_Requirements|System Requirements]] states that a P3 1Ghz can emulate a 3/486 - early dos games. I have compiled Dosbox and SDL myself for this processor, 1Ghz P3, and I can run games from 95/96 OK (Caesar 2, C&C: Red Alert).
So, if you have the skill, the performance increase is recommended.

=== 1. Grab the source ===

First, grab the latest version of the DOSBox source code. A fairly often updated SVN-Dump can be found at: http://source.dosbox.com/dosboxsvn.tgz

Download it and extract it to a separate directory.

=== 2. SDL ===

DOSBox uses SDL (Simple DirectMedia Layer) to access your graphics and sound hardware, so you'll need to download it as well. Grab the latest source at

: http://www.libsdl.org/

and extract to a separate directory.

When working on Windows, you might want to save a lot of effort and just use the SDL (and optionally SDL_net) .DLL files included with the latest official DOSBox release, as compiling SDL with full options (e.g. DirectX support) is a bit involved. There are also pre-built .DLL files on the SDL web site (Runtime Libraries -> Win32) that you can try at

: http://www.libsdl.org/download-1.2.php

Note that as of 12 Dec 2004, ddraw (DirectDraw) rendering mode will not work in DOSBox unless you either use the SDL.dll included with the latest version of DOSBox, or build your own SDL.dll with the changes mentioned in the "Compiling SDL" section below.

=== 3. Compiling environment ===

When working on Windows, you'll most likely need a compiling environment. We suggest using the combination of MinGW and MSYS, which can be found at

: http://prdownloads.sf.net/mingw/

You'll need to download both the latest MinGW and MSYS. After downloading, install MinGW and MSYS (in this order). The MSYS-Installer should ask for the installation directory of MinGW, so you should pick the path where you installed it. After the installation, run the MSYS.BAT and you should see a unix-like command prompt.

=== 4. Compiling SDL ===

Navigate to the directory where you extracted the SDL-source (using unix commands) and type

./configure
make
make install

Some MinGW-specific info on compiling SDL under Windows is available at

: http://www.libsdl.org/extras/win32/mingw32/README.txt

If you are having trouble with a message like 'no acceptable ld found in $PATH' try 'export LD=/c/gxx-2.95.2/bin/ld.exe' (or wherever you have the exe; GCC 2.95 in this case).

Also, if you have trouble getting ddraw (DirectDraw) working in DOSBox, see this post on the DOSBox forum for a possible fix:

: http://vogons.zetafleet.com/viewtopic.php?p=48050&highlight=#48050

==== 4b. SDL-net (optional) ====

If you want to benefit from DOSBox's Modem-Emulation or IPX-Support, you'll also need the SDL-net library, which can be found at

: http://www.libsdl.org/projects/SDL_net/

Download, extract, and compile as you did with SDL.

If you skipped building your own SDL.dll, you can use the one included with the latest official release of DOSBox or you can get a SDL_net win32 binary (.DLL) release on the SDL web site at the URL above.

=== 5. Compiling DOSBox ===

After compiling you'll need to adjust the PATH variable to point at the directory where the freshly built SDL-Library can be found.

''Note: if you want to use SDL-net, do the same with that library.''

Then, change to the directory where you extracted the DOSBox-Source and type

./autogen.sh
./configure
make

to compile DOSBox. If everything worked, you should have a <tt>DOSBOX.EXE</tt> in the <tt>./src</tt> - directory.

=== 6. Running ===

The easiest way to run the new executable is to copy it (and your fresh <tt>SDL.dll</tt> ''and maybe even the SDL_net.dll'') to the installation-directory of a non-SVN-version of DOSBox. That way, you have the needed directory structure and configuration files.

=== Example for Building DOSBox 0.71 on OpenSUSE 10.2 Linux ===

-Remove the existing DOSBox version if you have it.

-Obtain and extract the DOSBox source code.

-SUSE linux 10.2 already has SDL and alsa installed, but you need to install the SDL-devel package and alsa-devel package (for header files and libs).

-Obtain the SDL_Sound src from http://icculus.org/SDL_sound/downloads. Extract the source somewhere.
Run configure --with-sdl-prefix=/usr/lib64 --with-sdl-exec-prefix=/usr
make
make install (need to be root)

-OK, now you have everything you need to compile DOSBox. cd to your DOSBox directory, then run this at the shell:
export CPPFLAGS="-I/usr/local/include/SDL"
export LDFLAGS="-L/usr/local/lib"
configure --with-sdl-prefix=/usr/lib64 --with-sdl-exec-prefix=/usr --with-alsa-prefix=/usr/lib64
--with-alsa-inc-prefix=/usr/include/alsa
make
make install (need to be root).

-The reason for the shell variables is that it seemed to be the only way configure could find the files it needed. There aren't any config options to find the SDL_sound library, and I tried giving it -libdir= and -includedir=, but that didn't work.

Building DOSBox with MinGW

2012-03-04T12:40:52Z

Jez9999: I'm guessing MiniGW is a typo of MinGW...

== Building your own version of DOSBox ==

Why to do this?<br>
Because any resource-intensive program can benefit greatly from optimization for your exact processor.<br>
[[System_Requirements|System Requirements]] states that a P3 1Ghz can emulate a 3/486 - early dos games. I have compiled Dosbox and SDL myself for this processor, 1Ghz P3, and I can run games from 95/96 OK (Caesar 2, C&C: Red Alert).
So, if you have the skill, the performance increase is recommended.

=== 1. Grab the source ===

First, grab the latest version of the DOSBox source code. A fairly often updated SVN-Dump can be found at: http://source.dosbox.com/dosboxsvn.tgz

Download it and extract it to a separate directory.

=== 2. SDL ===

DOSBox uses SDL (Simple DirectMedia Layer) to access your graphics and sound hardware, so you'll need to download it as well. Grab the latest source at

: http://www.libsdl.org/

and extract to a separate directory.

When working on Windows, you might want to save a lot of effort and just use the SDL (and optionally SDL_net) .DLL files included with the latest official DOSBox release, as compiling SDL with full options (e.g. DirectX support) is a bit involved. There are also pre-built .DLL files on the SDL web site (Runtime Libraries -> Win32) that you can try at

: http://www.libsdl.org/download-1.2.php

Note that as of 12 Dec 2004, ddraw (DirectDraw) rendering mode will not work in DOSBox unless you either use the SDL.dll included with the latest version of DOSBox, or build your own SDL.dll with the changes mentioned in the "Compiling SDL" section below.

=== 3. Compiling environment ===

When working on Windows, you'll most likely need a compiling environment. We suggest using the combination of MinGW and MSYS, which can be found at

: http://prdownloads.sf.net/mingw/

You'll need to download both the latest MinGW and MSYS. After downloading, install MinGW and MSYS (in this order). The MSYS-Installer should ask for the installation directory of MinGW, so you should pick the path where you installed it. After the installation, run the MSYS.BAT and you should see a unix-like command prompt.

=== 4. Compiling SDL ===

Navigate to the directory where you extracted the SDL-source (using unix commands) and type

./configure
make
make install

Some MinGW-specific info on compiling SDL under Windows is available at

: http://www.libsdl.org/extras/win32/mingw32/README.txt

If you are having trouble with a message like 'no acceptable ld found in $PATH' try 'export LD=/c/gxx-2.95.2/bin/ld.exe' (or wherever you have the exe; GCC 2.95 in this case).

Also, if you have trouble getting ddraw (DirectDraw) working in DOSBox, see this post on the DOSBox forum for a possible fix:

: http://vogons.zetafleet.com/viewtopic.php?p=48050&highlight=#48050

==== 4b. SDL-net (optional) ====

If you want to benefit from DOSBox's Modem-Emulation or IPX-Support, you'll also need the SDL-net library, which can be found at

: http://www.libsdl.org/projects/SDL_net/

Download, extract, and compile as you did with SDL.

If you skipped building your own SDL.dll, you can use the one included with the latest official release of DOSBox or you can get a SDL_net win32 binary (.DLL) release on the SDL web site at the URL above.

=== 5. Compiling DOSBox ===

After compiling you'll need to adjust the PATH variable to point at the directory where the freshly built SDL-Library can be found.

''Note: if you want to use SDL-net, do the same with that library.''

Then, change to the directory where you extracted the DOSBox-Source and type

./configure
make

to compile DOSBox. If everything worked, you should have a <tt>DOSBOX.EXE</tt> in the <tt>./src</tt> - directory.

=== 6. Running ===

The easiest way to run the new executable is to copy it (and your fresh <tt>SDL.dll</tt> ''and maybe even the SDL_net.dll'') to the installation-directory of a non-SVN-version of DOSBox. That way, you have the needed directory structure and configuration files.

=== Example for Building DOSBox 0.71 on OpenSUSE 10.2 Linux ===

-Remove the existing DOSBox version if you have it.

-Obtain and extract the DOSBox source code.

-SUSE linux 10.2 already has SDL and alsa installed, but you need to install the SDL-devel package and alsa-devel package (for header files and libs).

-Obtain the SDL_Sound src from http://icculus.org/SDL_sound/downloads. Extract the source somewhere.
Run configure --with-sdl-prefix=/usr/lib64 --with-sdl-exec-prefix=/usr
make
make install (need to be root)

-OK, now you have everything you need to compile DOSBox. cd to your DOSBox directory, then run this at the shell:
export CPPFLAGS="-I/usr/local/include/SDL"
export LDFLAGS="-L/usr/local/lib"
configure --with-sdl-prefix=/usr/lib64 --with-sdl-exec-prefix=/usr --with-alsa-prefix=/usr/lib64
--with-alsa-inc-prefix=/usr/include/alsa
make
make install (need to be root).

-The reason for the shell variables is that it seemed to be the only way configure could find the files it needed. There aren't any config options to find the SDL_sound library, and I tried giving it -libdir= and -includedir=, but that didn't work.

Dosbox.conf

2010-05-24T18:41:55Z

Jez9999: /* [midi] */

'''dosbox.conf''' is a configuration file that DOSBox can use globally and/or locally per game (and settings that are left out are taken from the global file). It contains various system settings and initialization values that define your emulated environment. Everything can be controlled by editing this file or if you like through more graphically oriented [[DOSBoxFrontends|Front Ends]]. You can also [[Dosbox.conf#Creation and Location |create]] separate '''dosbox.conf''' files for multiple host environments (which is helpful in playing various DOS games that expect various types of hardware).

The configuration file is broken into separate [[Dosbox.conf#Sections |sections]] which contain section settings. Many of these settings do not need to be fully understood to configure DOSBox, but it is helpful to know where to look. You should also be aware that anything to the right of the '''#''' to the end of the line is considered a comment as is totally ignored by DOSBox when it loads.

== Creation and Location ==
Depending on the version or host OS, the dosbox.conf file is located either inside the [[user profile folder]] or inside the same folder as dosbox.exe.

===Windows===
Dosbox.conf is created automatically in the Windows' [[user profile folder]]. The location is indicated by the DOSBox Status Window upon startup.

You can find the '''dosbox.conf''' by browsing '''Start > All Programs > Dosbox-{version}'''
[[Image:Dosbox_config.png]]

==== Windows XP ====
%USERPROFILE%\Local Settings\Application Data\DOSBox\dosbox-{version}.conf
==== Windows Vista & Windows 7 ====
''{system drive}'':\Users\''{username}''\AppData\Local\DOSBox\dosbox-{version}.conf

===Linux===
For Linux the configfile is created on the first run in ~/.dosbox/
The name is dosbox-version.conf where version is currently 0.73

On Ubuntu in the dosbox man file it is written:
Configuration and language files use a format similar to Windows .ini
files. First ~/.dosboxrc (if present) will be loaded. If no config‐
file is specified at the commandline, a file named dosbox.conf (if
present in the current directory) will be loaded automatically after‐
wards. If a configfile is specified at the commandline that one will be
used instead.

===Mac OS X===
If you are using Mac OS X, a preferences file will be created for you on the first time you run DOSBox (as of version 0.73). This file contains the same system settings and initialization values as the '''dosbox.conf''' file on other systems.

It can be found (and modified) at '''<tt>~/Library/Preferences/DOSBox 0.73 Preferences</tt>''', where ~/ is your [[user profile folder]] (usually <tt>/Macintosh HD/Users/''username''/</tt>). The exact folder name in the [http://en.wikipedia.org/wiki/Finder_(software) Finder] may vary, depending on the language you use for OS X.

== Sections ==

=== [sdl] ===
{{:Configuration:SDL}}

=== [dosbox] ===
{{:Configuration:DOSBox}}

=== [render] ===
{{:Configuration:RENDER}}

=== [cpu] ===
{{:Configuration:CPU}}

=== [mixer] ===
{{:Configuration:Mixer}}(see [[Sound]])
:Here you can define the quality of emulated audio.

=== [midi] ===
(see [[Sound]])

{{:Configuration:MIDI}}

=== [sblaster] ===
{{:Configuration:SBlaster}}(see [[Sound]])
:Sound Blaster related settings.

=== [gus] ===
{{:Configuration:GUS}} (see [[Sound]])
:Gravis Ultra Sound related settings.

=== [speaker] ===
{{:Configuration:PCSpeaker}} (see [[Sound]])
:PC Speaker related settings.

=== [joystick] ===
{{:Configuration:Joystick}} (see [[Sound]])
:Joystick related settings.

=== [serial] ===
{{:Configuration:SerialPort}}

=== [dos] ===
{{:Configuration:DOS}}

=== [ipx] ===
{{:Configuration:IPX}}

=== [autoexec] ===
{{:Configuration:AUTOEXEC}}

==Recommendations==

Different games will naturally work best with different configuration settings. Something to consider is to define a conf file for each game that will set the appropriate configurations and start the game for you. Then, create a shortcut such as DOSBox.exe -conf "DOSbox-GameName.conf" so that you can start your game in the least possible number of steps.

Configuration:MIDI

2010-05-24T18:41:21Z

Jez9999: /* mididevice = default | win32 | alsa | oss | coreaudio | coremidi | none */

Here you can define any MIDI related settings. The term MIDI is commonly used to refer to background music found in games, but specifically it refers to synthesizer audio (which can be passed directly from emulated games to modern hardware.

==== mpu401 = intelligent | uart | none ====
Specifies which type of MIDI Processing Unit to emulate.
:intelligent: (from Wikipedia) The MPU-401 can work in two modes, normal mode and UART mode. "Normal mode" would provide the host system with an 8-track sequencer, MIDI clock output, SYNC 24 signal output, Tape Sync and a metronome; as a result of these features, it is often called "intelligent mode", whereas...
:uart: ... this simply emulates UART mode, which reduces the MPU-401 to just relaying in-/outcoming MIDI data bytes.
:none: MIDI is not emulated.

==== mididevice = default | win32 | alsa | oss | coreaudio | coremidi | none ====
A slightly confusing config name, because this isn't so much which MIDI device to use as which MIDI '''interface''' to use. As DOSBox currently does not emulate MIDI, but instead passes it through to an interface that does give MIDI playback support, this setting tells DOSBox which interface to pass MIDI data through to.
:default: The default system MIDI playback device is used.
:win32: Win32 MIDI playback interface is used.
:alsa: Linux's Advanced Linux Sound Architecture playback interface is used.
:oss: Linux's Open Sound System playback interface is used.
:coreaudio: MacOS X's framework to render the music through the built-in OS X synthesizer.
:coremidi: MacOS X's framework to route MIDI commands to any device that has been configured in Audio MIDI Setup.
:none: MIDI is disabled.

==== midiconfig = ''id of MIDI device'' ====
As used by the MIDI interface described above, this specifies the ID which identifies the particular MIDI device to playback MIDI on. Can be determined on Windows using '''MIXER /LISTMIDI''' or on Linux using '''pmidi -l''' in the console.

Configuration:MIDI

2010-05-23T17:05:09Z

Jez9999:

Here you can define any MIDI related settings. The term MIDI is commonly used to refer to background music found in games, but specifically it refers to synthesizer audio (which can be passed directly from emulated games to modern hardware.

==== mpu401 = intelligent | uart | none ====
Specifies which type of MIDI Processing Unit to emulate.
:intelligent: (from Wikipedia) The MPU-401 can work in two modes, normal mode and UART mode. "Normal mode" would provide the host system with an 8-track sequencer, MIDI clock output, SYNC 24 signal output, Tape Sync and a metronome; as a result of these features, it is often called "intelligent mode", whereas...
:uart: ... this simply emulates UART mode, which reduces the MPU-401 to just relaying in-/outcoming MIDI data bytes.
:none: MIDI is not emulated.

==== mididevice = default | win32 | alsa | oss | coreaudio | coremidi | none ====
A slightly confusing config name, because this isn't so much which MIDI device to use as which MIDI '''interface''' to use. As DOSBox currently does not emulate MIDI, but instead passes it through to an interface that does give MIDI playback support, this setting tells DOSBox which interface to pass MIDI data through to.
:default: The default system MIDI playback device is used.
:win32: Win32 MIDI playback interface is used.
:alsa: Linux's Advanced Linux Sound Architecture playback interface is used.
:oss: Linux's Open Sound System playback interface is used.
:coreaudio: MacOS X???
:coremidi: MacOS X???
:none: MIDI is disabled.

==== midiconfig = ''id of MIDI device'' ====
As used by the MIDI interface described above, this specifies the ID which identifies the particular MIDI device to playback MIDI on. Can be determined on Windows using '''MIXER /LISTMIDI''' or on Linux using '''pmidi -l''' in the console.

Configuration:MIDI

2010-05-23T16:55:58Z

Jez9999:

:Here you can define any MIDI related settings. The term MIDI is commonly used to refer to background music found in games, but specifically it refers to synthesizer audio (which can be passed directly from emulated games to modern hardware.

==== mpu401 = intelligent | uart | none ====
Specifies which type of MIDI Processing Unit to emulate.
:intelligent: (from Wikipedia) The MPU-401 can work in two modes, normal mode and UART mode. "Normal mode" would provide the host system with an 8-track sequencer, MIDI clock output, SYNC 24 signal output, Tape Sync and a metronome; as a result of these features, it is often called "intelligent mode", whereas...
:uart: ... this simply emulates UART mode, which reduces the MPU-401 to just relaying in-/outcoming MIDI data bytes.
:none: MIDI is not emulated.

==== mididevice = default | win32 | alsa | oss | coreaudio | coremidi | none ====
A slightly confusing config name, because this isn't so much which MIDI device to use as which MIDI '''interface''' to use. As DOSBox currently does not emulate MIDI, but instead passes it through to an interface that does give MIDI playback support, this setting tells DOSBox which interface to pass MIDI data through to.
:default: The default system MIDI playback device is used.
:win32: Win32 MIDI playback interface is used.
:alsa: Linux's Advanced Linux Sound Architecture playback interface is used.
:oss: Linux's Open Sound System playback interface is used.
:coreaudio: MacOS X???
:coremidi: MacOS X???
:none: MIDI is disabled.

==== midiconfig = ''id of MIDI device'' ====
As used by the MIDI interface described above, this specifies the ID which identifies the particular MIDI device to playback MIDI on. Can be determined on Windows using '''MIXER /LISTMIDI''' or on Linux using '''pmidi -l''' in the console.

Dosbox.conf

2010-05-23T16:36:42Z

Jez9999: /* [midi] */

'''dosbox.conf''' is a configuration file that DOSBox can use globally and/or locally per game (and settings that are left out are taken from the global file). It contains various system settings and initialization values that define your emulated environment. Everything can be controlled by editing this file or if you like through more graphically oriented [[DOSBoxFrontends|Front Ends]]. You can also [[Dosbox.conf#Creation and Location |create]] separate '''dosbox.conf''' files for multiple host environments (which is helpful in playing various DOS games that expect various types of hardware).

The configuration file is broken into separate [[Dosbox.conf#Sections |sections]] which contain section settings. Many of these settings do not need to be fully understood to configure DOSBox, but it is helpful to know where to look. You should also be aware that anything to the right of the '''#''' to the end of the line is considered a comment as is totally ignored by DOSBox when it loads.

== Creation and Location ==
Depending on the version or host OS, the dosbox.conf file is located either inside the [[user profile folder]] or inside the same folder as dosbox.exe.

===Windows===
Dosbox.conf is created automatically in the Windows' [[user profile folder]]. The location is indicated by the DOSBox Status Window upon startup.

You can find the '''dosbox.conf''' by browsing '''Start > All Programs > Dosbox-{version}'''
[[Image:Dosbox_config.png]]

==== Windows XP ====
%USERPROFILE%\Local Settings\Application Data\DOSBox\dosbox-{version}.conf
==== Windows Vista & Windows 7 ====
''{system drive}'':\Users\''{username}''\AppData\Local\DOSBox\dosbox-{version}.conf

===Linux===
For Linux the configfile is created on the first run in ~/.dosbox/
The name is dosbox-version.conf where version is currently 0.73

On Ubuntu in the dosbox man file it is written:
Configuration and language files use a format similar to Windows .ini
files. First ~/.dosboxrc (if present) will be loaded. If no config‐
file is specified at the commandline, a file named dosbox.conf (if
present in the current directory) will be loaded automatically after‐
wards. If a configfile is specified at the commandline that one will be
used instead.

===Mac OS X===
If you are using Mac OS X, a preferences file will be created for you on the first time you run DOSBox (as of version 0.73). This file contains the same system settings and initialization values as the '''dosbox.conf''' file on other systems.

It can be found (and modified) at '''<tt>~/Library/Preferences/DOSBox 0.73 Preferences</tt>''', where ~/ is your [[user profile folder]] (usually <tt>/Macintosh HD/Users/''username''/</tt>). The exact folder name in the [http://en.wikipedia.org/wiki/Finder_(software) Finder] may vary, depending on the language you use for OS X.

== Sections ==

=== [sdl] ===
{{:Configuration:SDL}}

=== [dosbox] ===
{{:Configuration:DOSBox}}

=== [render] ===
{{:Configuration:RENDER}}

=== [cpu] ===
{{:Configuration:CPU}}

=== [mixer] ===
{{:Configuration:Mixer}}(see [[Sound]])
:Here you can define the quality of emulated audio.

=== [midi] ===
(see [[Sound]])
{{:Configuration:MIDI}}

=== [sblaster] ===
{{:Configuration:SBlaster}}(see [[Sound]])
:Sound Blaster related settings.

=== [gus] ===
{{:Configuration:GUS}} (see [[Sound]])
:Gravis Ultra Sound related settings.

=== [speaker] ===
{{:Configuration:PCSpeaker}} (see [[Sound]])
:PC Speaker related settings.

=== [joystick] ===
{{:Configuration:Joystick}} (see [[Sound]])
:Joystick related settings.

=== [serial] ===
{{:Configuration:SerialPort}}

=== [dos] ===
{{:Configuration:DOS}}

=== [ipx] ===
{{:Configuration:IPX}}

=== [autoexec] ===
{{:Configuration:AUTOEXEC}}

==Recommendations==

Different games will naturally work best with different configuration settings. Something to consider is to define a conf file for each game that will set the appropriate configurations and start the game for you. Then, create a shortcut such as DOSBox.exe -conf "DOSbox-GameName.conf" so that you can start your game in the least possible number of steps.

Dosbox.conf

2010-05-23T16:36:11Z

Jez9999: /* [midi] */

'''dosbox.conf''' is a configuration file that DOSBox can use globally and/or locally per game (and settings that are left out are taken from the global file). It contains various system settings and initialization values that define your emulated environment. Everything can be controlled by editing this file or if you like through more graphically oriented [[DOSBoxFrontends|Front Ends]]. You can also [[Dosbox.conf#Creation and Location |create]] separate '''dosbox.conf''' files for multiple host environments (which is helpful in playing various DOS games that expect various types of hardware).

The configuration file is broken into separate [[Dosbox.conf#Sections |sections]] which contain section settings. Many of these settings do not need to be fully understood to configure DOSBox, but it is helpful to know where to look. You should also be aware that anything to the right of the '''#''' to the end of the line is considered a comment as is totally ignored by DOSBox when it loads.

== Creation and Location ==
Depending on the version or host OS, the dosbox.conf file is located either inside the [[user profile folder]] or inside the same folder as dosbox.exe.

===Windows===
Dosbox.conf is created automatically in the Windows' [[user profile folder]]. The location is indicated by the DOSBox Status Window upon startup.

You can find the '''dosbox.conf''' by browsing '''Start > All Programs > Dosbox-{version}'''
[[Image:Dosbox_config.png]]

==== Windows XP ====
%USERPROFILE%\Local Settings\Application Data\DOSBox\dosbox-{version}.conf
==== Windows Vista & Windows 7 ====
''{system drive}'':\Users\''{username}''\AppData\Local\DOSBox\dosbox-{version}.conf

===Linux===
For Linux the configfile is created on the first run in ~/.dosbox/
The name is dosbox-version.conf where version is currently 0.73

On Ubuntu in the dosbox man file it is written:
Configuration and language files use a format similar to Windows .ini
files. First ~/.dosboxrc (if present) will be loaded. If no config‐
file is specified at the commandline, a file named dosbox.conf (if
present in the current directory) will be loaded automatically after‐
wards. If a configfile is specified at the commandline that one will be
used instead.

===Mac OS X===
If you are using Mac OS X, a preferences file will be created for you on the first time you run DOSBox (as of version 0.73). This file contains the same system settings and initialization values as the '''dosbox.conf''' file on other systems.

It can be found (and modified) at '''<tt>~/Library/Preferences/DOSBox 0.73 Preferences</tt>''', where ~/ is your [[user profile folder]] (usually <tt>/Macintosh HD/Users/''username''/</tt>). The exact folder name in the [http://en.wikipedia.org/wiki/Finder_(software) Finder] may vary, depending on the language you use for OS X.

== Sections ==

=== [sdl] ===
{{:Configuration:SDL}}

=== [dosbox] ===
{{:Configuration:DOSBox}}

=== [render] ===
{{:Configuration:RENDER}}

=== [cpu] ===
{{:Configuration:CPU}}

=== [mixer] ===
{{:Configuration:Mixer}}(see [[Sound]])
:Here you can define the quality of emulated audio.

=== [midi] ===
(see [[Sound]])
:Here you can define any MIDI related settings. The term MIDI is commonly used to refer to background music found in games, but specifically it refers to synthesizer audio (which can be passed directly from emulated games to modern hardware.
{{:Configuration:MIDI}}

=== [sblaster] ===
{{:Configuration:SBlaster}}(see [[Sound]])
:Sound Blaster related settings.

=== [gus] ===
{{:Configuration:GUS}} (see [[Sound]])
:Gravis Ultra Sound related settings.

=== [speaker] ===
{{:Configuration:PCSpeaker}} (see [[Sound]])
:PC Speaker related settings.

=== [joystick] ===
{{:Configuration:Joystick}} (see [[Sound]])
:Joystick related settings.

=== [serial] ===
{{:Configuration:SerialPort}}

=== [dos] ===
{{:Configuration:DOS}}

=== [ipx] ===
{{:Configuration:IPX}}

=== [autoexec] ===
{{:Configuration:AUTOEXEC}}

==Recommendations==

Different games will naturally work best with different configuration settings. Something to consider is to define a conf file for each game that will set the appropriate configurations and start the game for you. Then, create a shortcut such as DOSBox.exe -conf "DOSbox-GameName.conf" so that you can start your game in the least possible number of steps.