DOSBoxWiki - User contributions [en]

Recording Video

2011-01-18T21:56:29Z

Ykhwong:

Starting with [[Version0.65|version 0.65]], DOSBox allows you to create movies out of screen output.

To record a movie, you have to press '''<tt>CTRL-ALT-F5</tt>'''.
To stop/end the recording, you have to press '''<tt>CTRL-ALT-F5</tt>''' again.

''Note: Under Linux, most Window Managers will use this key combination to go to''
''the 5th console terminal screen. You'll have to go to the [[Mapper|keymapper]] and change the''
''key combination used for "Video".''

The video mode currently being emulated will determine the resolution of the captured video, and the currently running [[GAMES|game]] or [[Software|application]] will determine the name of the captured file. If the current application is changed while a movie is being recorded the filename will not change, but if the video mode changes then the current recording will automatically be stopped and a new movie in the new resolution will be created with the name of the last executed application.

Like screenshots, any filters will not be recorded or affect the content of the captured video.

== Playing the captured movie ==
Each platform is different so you may need to search around for specific help. The file captured will end in '''<tt>.AVI</tt>''', which is a container format. Most computers may look like they are already configured to play the captures movie, but most likely they are not. The video portion of the movie is encoded with the 32bit ZMBV (Zip Motion Block Video) CODEC, which allows for reasonably fast encoding of low color content.

===Windows===
The Win 32 Release of DOSBox includes the necessary CODEC and install scripts needed to allow Windows Media Player (or almost any other movie player in Windows) to playback the recorded files. If you installed the Start Menu shortcuts simply select '''<tt>Install movie codec</tt>'''

[[Image:InstallVideoCodec.jpg]]

You might notice that your computer is performing some actions in the background but there will be no actual confirmation that this install was successful (other than trying to play your movie). If you are still experiencing difficulty playing your captured movie you can try alternative media players like [http://www.videolan.org/ VideoLAN] or [http://sourceforge.net/projects/guliverkli/ Media Player Classic]

===Linux===
[http://www.mplayerhq.hu/ MPlayer] (a popular command line video player) should be able to play the captured video without any special configuration.

===Mac OS X===
Mac users can use [http://perian.org/ Perian] to view the captured video in QuickTime Player.

DOSBoxFrontends

2011-01-18T21:51:58Z

Ykhwong:

= Frontends for DOSBox =

A [[DOSBoxFrontends|frontend]] pulls together the many functions of the program it is for and "stands in front of" it. It makes your life and the configuration a bit simpler.

'''DOSBox''' is controlled by its [[dosbox.conf|config file]]. [[DOSBoxFrontends|Frontends]] are a nice graphical way to maintain or edit that [[dosbox.conf|config file]].

If you are a newbie or you don't like editing [[dosbox.conf]] by hand then a [[DOSBoxFrontends|frontend]] is the solution for you.

== Incomplete overview of the Frontends available ==
=== Windows Frontends ===

* '''CBoxRun'''
: A Windows-based DOSBox frontend that emphasizes ease of use. It can automatically download game information and screenshots from Wikipedia, and it has a nice [[dosbox.conf|config file]] editor with help for every field. Requires .NET 3.51.
: '''Website''': http://cboxrun.wordpress.com/

* '''DOSShell'''
: x86 applications launcher plus convenient Explorer-like entries manager.
: '''Website''': http://www.loonies.narod.ru/dosshell.htm

* '''DOSBoxGui'''
: A portable DOSBox frontend. Currently confirmed to run on Linux and Windows flavors.
: Needs Tcl/Tk (which is an albeit free 20 MB big software compiler that you will need to assemble the program for your operating system).
: '''Website''': http://losfinkos.googlepages.com/dosboxgui

* '''DBFrontend''' - '''D'''OS'''B'''ox'''Frontend'''
: It's a very simple frontend which allows you to have thumbnails of screen shots so you can easy recognize the game you want to run.
: '''Website''': http://www.ingoknito.de/produkte/dbfrontend/

* '''D-Box'''
: A nice looking and easy-to-use frontend for DOSBox. It's open source and tries to distinguish itself from alternatives by having "the right set of features", which means not too few, and not too many features. Includes a fancy "floppy flow" user interface. Runs great on Windows 2000, XP, Vista and 7.
: '''Website''': http://dbox.truben.no

* '''D.O.G.'''
: D.O.G. is a work in progress DOSBox frontend, tested on Windows XP and 2000. D.O.G. is currently compatible with all DOSBox versions, from 0.58 up to 0.70. It will present you only with the available options of the selected DOSBox. D.O.G. also allows users to use not one DOSBox for their profiles, but an unlimited number. Switching between DOSBox versions is as easy as a click on a button. Besides the standard features of DOSBox, D.O.G. also extends these features with zip and 7-zip capability. Users can select a zip as a drive and D.O.G. will automatically unpack and repack the archive when running DOSBox. Besides this archiving capability D.O.G. also allows you to convert the captured Wave-files to the MP3 format of your choice and it allows you to convert the captured screen shots to a JPG format of your choice.
: '''Website''': http://www.freewebs.com/erikgg/

* '''DBGL''' - DOSBox Game Launcher
: DBGL is an open-source, multi-platform frontend for DOSBox, based largely upon the proven interface of D-Fend.
: '''Website''': http://home.quicknet.nl/qn/prive/blankendaalr/dbgl/

* '''DosBlaster'''
: Windows Explorer shell extension for DOSBox. You can launch DOSBox by right click on DOS executable files in your Windows Explorer.
: '''Website''': http://sourceforge.net/projects/dosblaster

* '''Turbo Dos Box'''
: x86/x64 very simple and small (~100KB no install needed) manager for configuration. Automatically mounts drives and can change all DOSBox options via XML setup, and can right click an EXE/COM/BAT and play it through DosBox by using the default configuration profile in "Right click and play" fashion.
: '''Website''': http://www.turboirc.com/tdb

* '''D-Fend Reloaded''' - '''D'''OSBox-'''F'''ront'''end''' Reloaded
: In some way D-Fend Reloaded is a successor of the discontinued software D-Fend. Both environments look alike and D-Fend Reloaded contains all the features of D-Fend. Even the D-Fend config files are compatible with D-Fend Reloaded. However, unlike D-Fend, D-Fend Reloaded is open source.
: The development objective for D-Fend Reloaded was (besides 100% D-Fend compability) to make the program operation more simple with respect to DosBox beginners. Simultaneously more features for administration and configuration became available.
: '''Website''': http://dfendreloaded.sourceforge.net/

* '''ScudoGR - ScummVM, Dosbox (and Windows) Game Runner'''
: It's a simple interface to crate/run games for Dosbox, Scummvm and Windows. Games are created and managed by zip-files, which are easily importable by drag and drop. It uses several configuration files, it manages mounting/unmounting file (by dosbox 'imgmount' command or with daemon tools), and it's language-configurable.
: '''Website''': http://www.scudogr.it

* '''GR-lida - ScummVM, Dosbox and VDMSound'''
: A front end written in QT4 and released under GPL license. Although the website is only available in Spanish, the program itself is also available in English. It can display games using pictureflow which is a clone of Apples Cover Flow.
: '''Website''': http://www.gr-lida.org/

=== Mac OS X Frontends ===

* '''Boxer'''
: Boxer makes it easy to run your favourite DOS games: without editing configuration files, without typing command line parameters, without mounting folders, without learning a confusing frontend; without doing any more than clicking on a game in Finder.
: '''Website''': http://boxer.washboardabs.net/

* '''DBGL''' - DOSBox Game Launcher
: DBGL is an open-source, multi-platform frontend for DOSBox, based largely upon the proven interface of D-Fend.
: '''Website''': http://home.quicknet.nl/qn/prive/blankendaalr/dbgl/

* '''D-Box'''
: A nice looking and easy-to-use frontend for DOSBox. It's open source and tries to distinguish itself from alternatives by having "the right set of features", which means not too few, and not too many features. Also includes a coverflow like "floppy flow" user interface.
: '''Website''': http://dbox.truben.no

* '''Radnor'''
: Sveinbjorn Thordarson has created the frontend "Radnor" for the MacOS X 10.3 or later version of DOSBox.
: '''Website''': http://sveinbjorn.vefsyn.is/radnor

* '''Petit dosbox'''
: Petit dosbox is a very easy to use interface to help you running the emulator, and will keep your last configuration for the next time you use it.
: New updates have included a Game Manager and more configuration options.
: '''Website''': http://web.jet.es/guilly/slouc/software_petitdosbox.html

=== Linux Frontend ===

* '''DOSBoxGui'''
: A portable DOSBox frontend. Currently confirmed to run on Linux and Windows flavors.
: Needs Tcl/Tk.
: '''Website''': http://losfinkos.googlepages.com/dosboxgui

* '''D-Box'''
: A nice looking and easy-to-use frontend for DOSBox created in Java. It's open source and tries to distinguish itself from alternatives by having "the right set of features", which means not too few, and not too many features.
: '''Website''': http://dbox.truben.no

* '''DBoxFE'''
: DBoxFE creates and manages configuration files for DOSBox. You can create different profiles for your games, etc.
: '''Need to run:'''
: * KDE 3.1.x / 3.2.x
: * Qt 3.1.x / 3.2.x / 3.3.x
: '''Website''': http://chmaster.freeforge.net/dboxfe-project.htm

* '''pyDOSBox'''
: The program is still in alpha stage but usable.
: '''Website''': http://www.panayotis.com/prog/scripts/pydosbox/index.html

* '''DBGL''' - DOSBox Game Launcher
: DBGL is an open-source, multi-platform frontend for DOSBox, based largely upon the proven interface of D-Fend.
: '''Website''': http://home.quicknet.nl/qn/prive/blankendaalr/dbgl/

* '''GR-lida - ScummVM, Dosbox and VDMSound'''
: A front end written in QT4 and released under GPL license. Although the website is only available in Spanish, the program itself is also available in English. It can display games using pictureflow which is a clone of Apples Cover Flow.
: '''Website''': http://www.gr-lida.org/

== Incomplete overview of discontinued Frontends ==
=== Windows Frontends ===

* '''D-Fend''' - '''D'''OSBox-'''F'''ront'''end'''
: The largest DOSBox Frontend availabe. This frontend has supports for all '''DOSBox''' features and allows you generate default profiles for your system. It's also the only frontend which supports the unsupported SVN features. Because of its profile system and its intelligent mount system it's great for newbies and people using the SVN version of '''DOSBox'''. *Now supports Screenshot viewing for each Game Profile*
However recently Anthony announced officially that he stopped his work on D-Fend.
: '''Website''': http://members.home.nl/mabus

* '''Boxer''' - DOS'''Boxer'''s
: The smallest (in filesize) of the frontends available. It tries to keep up with the stable '''DOSBox''' version and allows you to edit every aspect of ((dosbox.conf)). Great if you want a very small frontend which just gets the job done.
: '''Website''': unknown

* '''DOSBOXer'''
: Scott Duensing at Jaeger Technologies has created "DOSBOXer" for Windows. There is no mention of this software on his website anymore.
: '''Website''': http://www.jaegertech.net/

DOSBox and Mac OS X

2011-01-18T21:48:07Z

Ykhwong:

For long time users of the Apple Macintosh, the DOS environment might appear confusing at first. It helps to have experience with the '''<tt>System Terminal</tt>''' and the Command Line. Once set up however a simple shortcut will be all you need.

== Installing ==
This guide will use the [[Version0.74|0.74]] Mac OSX version which is available for [http://www.dosbox.com/download.php?main=1 download]. The [[Version0.74|0.74]] release is compiled as a Universal Binary, and will run on PowerPC and Intel based Macs. To install DOSBox, first expand the [[ZIP Files|.ZIP]] file and copy the contents into a folder like '''<tt>DOSBox</tt>'''. Move this folder into your '''<tt>Applications</tt>''' folder.

Now you need to create a folder to [[MOUNT]] as your [[CDrive|C: drive]] and hold your [[GAMES|games]]. The most convenient location for this folder would be your home folder (which can be referenced as '''<tt>~</tt>'''). In This example we will call our folder '''<tt>DOSGAMES</tt>'''. Inside this folder we can place all of the programs that we want to be available in our emulated DOS environment. Remember that while these files are buried deep in the file system with paths like '''<tt>~/DOSGAMES/TESTDRV</tt>''', inside DOSBox they appear as though they reside in the root of their mounted drive letter, so the above example in DOSBox would be located at '''<tt>C:\TESTDRV</tt>''' (assuming that '''<tt>~/DOSGAMES</tt>''' was mounted as [[CDrive|C:]]).

== Running DOSBox for the first time ==
Double click on the DOSBox icon in Finder to launch DOSBox for the first time. This will cause the DOSBox window to appear. By default no drives are mounted (except the DOSBox default [[ZDrive|Z:]]) From here you need to mount your '''<tt>DOSGAMES</tt>''' folder. Assuming you placed it inside your home folder you should be able to run this command to [[MOUNT]] the folder.

Z:\>'''MOUNT C ~/DOSGAMES'''
Drive C is mounted as local directory /Users/[your username]/DOSGAMES/

Now type this command to navigate to your newly mounted drive

Z:\>'''C:'''
C:\>

== Editing DOSBox preferences ==

After you first run DOSBox, go to the '''<tt>~/Library/Preferences/</tt>''' folder and open the newly created file '''<tt>DOSBox 0.74 Preferences</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.

By editing this file, you can set the [[Dosbox.conf|system settings and initialization values]] that define your emulated environment. You can also add '''MOUNT''' commands to the [[AUTOEXEC]] [[Dosbox.conf#.5Bautoexec.5D|section]] at the bottom of the configuration files, so that you do not have to type them in every time you start DOSBox.

Configuration:SDL

2011-01-18T21:28:49Z

Ykhwong:

This section contains all of the low level system settings for how DOSBox interacts with your real hardware. You can define what resolutions are emulated, how DOSBox should treat errors or listen to your keyboard and mouse. You can often achieve a fair level of optimization by working with these setting, though for the most part leaving them at their default settings will create the best experience. These settings are passed on to the SDL Library which handles low level things like input and thread priority.

;fullscreen = true | false
:Start DOSBox directly in fullscreen.
:Default is false.
:(since 0.??)

;fulldouble = true | false
:Use double buffering in fullscreen. See [http://en.wikipedia.org/wiki/Multiple_buffering]
:Default is false.
:(since 0.??)

;fullresolution = ''width'' x ''height'' | original | desktop
:Scale the application to this size IF the output device supports hardware scaling (i.e. any output other than surface). Original is the game's default or chosen (through setup.exe or in-game menu) resolution. If original resolution is less than desktop resolution, DOSBox will switch the screen resolution to the closest match requested by the game or application. For example, if a game in DOSBox is requesting a graphics screen resolution of (320 x 240) while your desktop is (1920 x 1200), DosBox will switch to (320x240) or the next highest resolution supported by your GPU drivers, e.g. (800 x 600) if the former is not available. Many games will be below the minimum resolution supported by modern video cards, so DosBox will scale the game up to at least that minimum. Note: the scaler setting under [render] is also able to scale up the original resolution to some degree. Those changes are performed before any additional scaling done with fullresolution setting.
:Default is original.
:(since 0.62)

;windowresolution = ''width'' x ''height'' | original | desktop
:Scale the window to this size IF the output device supports hardware scaling (i.e. any output other than surface). Original is the game's default or chosen (through setup.exe or in-game menu) resolution. Note: the scaler setting under [render] is also able to scale up the original resolution to some degree. Those changes are performed before any scaling done with windowresolution setting.
:Default is original.
:(since 0.62)

;output = surface | overlay | opengl | openglnb | ddraw
:What to use for output. Surface does not support scaling or aspect correction. More information here: [http://vogons.zetafleet.com/viewtopic.php?=&p=102291]
:Default is surface.
:(since 0.??)

;autolock = true | false
:Mouse will automatically lock, if you click on the screen.
:Default is true.
:(since 0.??)

;sensitivity = 1..1000
:Mouse sensitivity.
:Default is 100.
:(since 0.??)

;waitonerror = true | false
:Wait before closing the console if DOSBox has an error.
:Default is true.
:(since 0.??)

;priority = ''when-focused'',''when-minimzed''
:Priority levels for DOSBox. Second entry behind the comma is for when DOSBox is not focused/minimized. Valid priorities are: lowerest, lower, normal, higher, highest, and pause.
:Default is higher,normal.
:(since 0.??)

;mapperfile = ''path-to-mapper-file''
:File used to load/save the key/event mappings from.
:Default is mapper.txt.
:(since 0.??)

;usescancodes = true | false
:Avoid usage of symkeys, might not work on all operating systems.
:Default is true.
:(since 0.??)

====Deprecated parameters====
;fullfixed = true | false
:Deprecated as of 0.65. See fullresolution.
:(since 0.??)

;fullwidth = ''width''
:Deprecated with 0.62. See fullresolution.
:(since 0.61)

;fullheight = ''height''
:Deprecated with 0.62. See fullresolution.
:(since 0.61)

Configuration:SDL

2011-01-18T21:28:23Z

Ykhwong:

This section contains all of the low level system settings for how DOSBox interacts with your real hardware. You can define what resolutions are emulated, how DOSBox should treat errors or listen to your keyboard and mouse. You can often achieve a fair level of optimization by working with these setting, though for the most part leaving them at their default settings will create the best experience. These settings are passed on to the SDL Library which handles low level things like input and thread priority.

;fullscreen = true | false
:Start DOSBox directly in fullscreen.
:Default is false.
:(since 0.??)

;fulldouble = true | false
:Use double buffering in fullscreen. See [http://en.wikipedia.org/wiki/Multiple buffering]
:Default is false.
:(since 0.??)

;fullresolution = ''width'' x ''height'' | original | desktop
:Scale the application to this size IF the output device supports hardware scaling (i.e. any output other than surface). Original is the game's default or chosen (through setup.exe or in-game menu) resolution. If original resolution is less than desktop resolution, DOSBox will switch the screen resolution to the closest match requested by the game or application. For example, if a game in DOSBox is requesting a graphics screen resolution of (320 x 240) while your desktop is (1920 x 1200), DosBox will switch to (320x240) or the next highest resolution supported by your GPU drivers, e.g. (800 x 600) if the former is not available. Many games will be below the minimum resolution supported by modern video cards, so DosBox will scale the game up to at least that minimum. Note: the scaler setting under [render] is also able to scale up the original resolution to some degree. Those changes are performed before any additional scaling done with fullresolution setting.
:Default is original.
:(since 0.62)

;windowresolution = ''width'' x ''height'' | original | desktop
:Scale the window to this size IF the output device supports hardware scaling (i.e. any output other than surface). Original is the game's default or chosen (through setup.exe or in-game menu) resolution. Note: the scaler setting under [render] is also able to scale up the original resolution to some degree. Those changes are performed before any scaling done with windowresolution setting.
:Default is original.
:(since 0.62)

;output = surface | overlay | opengl | openglnb | ddraw
:What to use for output. Surface does not support scaling or aspect correction. More information here: [http://vogons.zetafleet.com/viewtopic.php?=&p=102291]
:Default is surface.
:(since 0.??)

;autolock = true | false
:Mouse will automatically lock, if you click on the screen.
:Default is true.
:(since 0.??)

;sensitivity = 1..1000
:Mouse sensitivity.
:Default is 100.
:(since 0.??)

;waitonerror = true | false
:Wait before closing the console if DOSBox has an error.
:Default is true.
:(since 0.??)

;priority = ''when-focused'',''when-minimzed''
:Priority levels for DOSBox. Second entry behind the comma is for when DOSBox is not focused/minimized. Valid priorities are: lowerest, lower, normal, higher, highest, and pause.
:Default is higher,normal.
:(since 0.??)

;mapperfile = ''path-to-mapper-file''
:File used to load/save the key/event mappings from.
:Default is mapper.txt.
:(since 0.??)

;usescancodes = true | false
:Avoid usage of symkeys, might not work on all operating systems.
:Default is true.
:(since 0.??)

====Deprecated parameters====
;fullfixed = true | false
:Deprecated as of 0.65. See fullresolution.
:(since 0.??)

;fullwidth = ''width''
:Deprecated with 0.62. See fullresolution.
:(since 0.61)

;fullheight = ''height''
:Deprecated with 0.62. See fullresolution.
:(since 0.61)

SVN Builds

2011-01-18T21:23:33Z

Ykhwong:

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. However, active development continues between releases, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://vogons.zetafleet.com/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://vogons.zetafleet.com/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://vogons.zetafleet.com/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes.

* '''EmuCR'''
** Last updated: October 18, 2010
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated a few times a week. Haven't tried these myself yet; thanks to NoVaTuRiEnT for pointing them out.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Tharos (by XTale)'''
** Last updated: March 28, 2010
** URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame.

* '''ykhwong'''
** Last updated: Jan 4, 2011
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 + x86-64 binaries?)
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32 emulation (MUNT), MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, Internal 3dfx voodoo chip emulation, etc.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: July 23, 2010
** URL: http://vogons.zetafleet.com/viewtopic.php?p=193022#193022 (Windows binary, source)
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

* '''Zirias'''
** Last Updated: May 12, 2010
** URL: http://vogons.zetafleet.com/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: November 18, 2010
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://vogons.zetafleet.com/viewtopic.php?t=26170 to discuss the Mac port
** Description: Builds of DOSBox focused on serial/networking support. Contains the NE2000 patch, parallel port passthrough and file forwarding, virtual printer, SVGA enhacements, OPL passthrough, and others. The Windows installer contains the debug-enabled build as option.

* '''gulikoza'''
** Last Updated: July 9, 2009
** URL: http://www.si-gamer.net/gulikoza/ (Windows binary, source)
** Description: Build of DOSBox focused on GLIDE support.

===Unofficial ports===
These builds are for other Operating Systems and are not in any way supported by the DOSBox team.

* '''DOSBox 0.74 for OS/2'''
** Last updated: September 17, 2010
** URL: http://www.os2site.com/sw/emulators/dosbox/index.html
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

* '''DOSBox 0.73 "aDOSBox" for Android OS'''
** Last Update: February 22, 2010
** URL: http://androiddosbox.appspot.com/

* '''DOSBox 0.73 for Pocket PC (by n0p)'''
** Last updated: July 6, 2009
** URL: http://n0p.tonych.info/?DOSBox_PPC (ARM & XScale builds)
** URL: http://www.e-lation.net/site/emufor_Pocket_PC.html#x86 (also contains links to other possible ports)

* '''DOSBox 0.72 for AmigaOS 4.0'''
** Last updated: June 14, 2009
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

* '''DOSBox 0.72 for GP2x'''
** Last updated: January 3, 2009
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** URL: http://wiki.gp2x.org/wiki/DosBox

* '''DOSBox 0.71 for IRIX'''
** Last Updated: 2007? (release dates not currently provided on the linked web site)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html
** Notes: Original enosnusnu.de link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on the latter site, but it appears that it may only offer a source code tarball and no binary.

* '''DOSBox 0.70 "Optimized" for PXA270 (by wellswang & kkazakov)'''
** Last Updated: March 19, 2007
** URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742
** URL: http://wells.osall.com/files/download.php?id=1727
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

* '''DOSBox 0.60 for PSP'''
** Last Update: June 6, 2007
** URL: http://www.dcemu.co.uk/vbulletin/showthread.php?t=65494
** URL: http://forums.ps2dev.org/viewtopic.php?t=3179&start=60 (link nonresponsive as of 10/28/10)

* '''DOSBox 0.60 for Dreamcast'''
** Last Updated: 2005? (release dates not currently provided on the linked web site)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===Obsolete SVN/CVS builds===
These builds are no longer maintained and are listed here for historical reference.

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: August 9, 2008
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: December 15, 2006
** URL: http://garni.ch/dosbox/
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: October 15, 2004
** URL: http://www.artworxinn.com/alex/downloads.htm
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/?view=log (auto-generated changelog created by sourceforge.net)
* http://github.com/Henne/dosbox-svn/commits/master (auto-generated changelog of unofficial git clone of DOSBox SVN)
* <s>http://dosbox.linuxsecured.net/dosboxcvs.txt</s> - '''broken link as of 10/25/10'''
* <s>http://cvscompile.aep-emu.de/cl/dosboxChangeLog.txt</s> - '''broken link as of 10/25/10'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* http://vogons.zetafleet.com/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)
* http://github.com/Henne/dosbox-svn (unofficial git clone of DOSBox SVN; auto-generated tarballs are also available there)
* <s>http://dosbox.linuxsecured.net/dosboxcvs.tgz</s> - '''broken link as of 10/25/10'''

Command Line

2010-11-17T13:57:16Z

Ykhwong: removed tag

:''This article is about Command Line inside DOSBox. For DOSBox Command Line Parameters, see [[Usage]]''.

Passing arguments to BAT file does not work exactly the same in DOSBox as is does in other environments (like Win98). Consider the following file (TEST.BAT)
<code><pre>echo -%1- 0%10 1%11 2%12</pre></code>
On Win98, '''TEST.BAT 99''' produces:
<code><pre>-99- 0990 1991 2992</pre></code>
Whereas DOSbox 0.70 produces:
<code><pre>-99- 0990 1 2</pre></code>
A work-around is to change TEST.BAT to:
<code><pre>SET X=%1
echo -%X%- 0%X%0 1%X%1 2%X%2</pre></code>
This coding style has the added benefit of allowing order of arguments to be changed at some future time without major impact on your script.

== NOTE ==
Please note that you will rarely encounter this problem (dosbox parses %11 as then eleventh parameter) This has been repaired in the SVN of dosbox. Please submit a bug report next time.

MIXER

2010-11-16T04:58:38Z

Ykhwong:

'''MIXER''' is an utility that makes DOSBox display its current volume settings.

==Command line parameters==

<code>MIXER channel left:right [/NOSHOW] [/LISTMIDI]

;channel: Can be one of the following:
:;MASTER
:;DISNEY
:;SPKR
:;GUS
:;SB
:;FM
:;[, CDAUDIO]: CDAUDIO is only available if a CD-ROM interface with volume control is enabled (CD image, ioctl_dx).

;left:The volume levels in percentages for the left channel.
;right:The volume levels in percentages for the right channel.

If you put a D in front it will be in decibel (Example: mixer gus d-10).

;/NOSHOW: Prevents DOSBox from showing the result if you set one of the volume levels.

;/LISTMIDI: Lists the available midi devices on your PC (Windows). To select a device other than the Windows default midi-mapper, add a line 'midiconfig=id' to the [midi] section in the configuration file, where 'id' is the number for the device as listed by LISTMIDI.

Basic Setup and Installation of DosBox

2010-11-16T04:57:33Z

Ykhwong:

== Basic Concepts ==

DOSBox is an emulator that recreates a MS-DOS compatible environment (complete with Sound, Input, Graphics and even basic networking). This environment is complete enough to run many classic MS-DOS games completely unmodified. In order to utilize all of DOSBox's features you need to first understand some basic concepts about the MS-DOS environment.

* [[MOUNT|Mount a Drive]]
* [[Drives]]
* [[Sound]]
* [[Display]]
* [[Input]]
* [[Connectivity]] (Modems/Networking)

== Installation ==

The first step is to install DOSBox. This guide will use the [[Version0.72|0.72]] Windows 32 version which is available for [http://www.dosbox.com/download.php?main=1 download]. Download the [[Releases|release]] for your operating system. If you are a Windows user, get the '''Win32 installer'''.

After downloading, install DOSBox to any directory. Also, make a folder to put all your old games in. I put DOSBox in '''<tt>C:\DOSBox</tt>''', and my old games directory is '''<tt>C:\OLDGAMES</tt>'''. I put a game in my '''<tt>OLDGAMES</tt>''' directory, '''<tt>TESTDRIV</tt>''', which is [[GAMES:TestDrive|Test Drive]], an old racing game. Your directories should look like this:

[[Image:DOSBox-Folders.jpg]]

== Running a game ==

Now, the hardest part, getting games to run. First, run '''dosbox.exe''' in your DOSBox folder. Remember that '''<tt>OLDGAMES</tt>''' directory you created in Step 1? You have to basically set that as new directory just for DOSBox. Essentially, it's going to become the '''[[CDrive|C:\>]]''' drive of DOSBox. So, type:
Z:\>'''MOUNT C C:\OLDGAMES'''
Drive C mounted as local directory C:\OLDGAMES\

To dissect the above:
*'''[[MOUNT]]''': Tells the program to [[MOUNT|mount]] a directory
*'''C''': Tells the program what you want your new drive to be called (leaving it as C: is fine)
*'''C:\OLDGAMES''': This is the directory I want to set as the new drive for DOSBox, because all my games are in it. If you created a different directory, write in the directory you created.

''(Note: If you want to [[MOUNT|mount]] a CD-ROM instead of a folder, type this:''
Z:\>'''MOUNT D D:\ -t cdrom'''
MSCDEX installed.
Drive D is mounted as CDRom D:\

''(Note: '''"cdrom"''' is case sensitive and must be lowercase!)''

In this example, '''D:\ -T cdrom''' tells DOSBox that my D:\ drive is a CD-ROM drive, and the first '''D''', tells DOSBox what my new drive name should be called. If you are running your game off a CD-ROM then make sure to use '''D:''' in place of '''C:''' in the following examples. You can find instructions on how to [[MOUNT|mount]] other devices, such as floppy drives, in the [[MOUNT|mount]] section).''

After you've done this, you will be prompted with a '''[[ZDrive|Z:\>]]'''. Now, just write what you wanted to call your new DOSBox drive, which as I said above, we called '''C'''. To navigate to that newly mounted drive just type in:

Z:\>'''C:'''

C:\>

Hopefully, you're all set! Now, it's time to run the game. Previously I had mentioned a game called '''<tt>TESTDRIV</tt>''' in my '''<tt>OLDGAMES</tt>''' folder. I now want DOSBox to go to that folder. So type in:

C:\>'''CD TESTDRIV'''

C:\TESTDRIV>

That's it! [[Commands#CD|CD]] stands for "Change Directory", so you've changed the directory to TESTDRIV. You can find instructions on how to use the [[Commands#CD|Change Directory]] command, in the [[Commands#CD|CD]] section of the [[Commands]] article.

One more step, running the game! Most games have an EXE file in their directory that you can run. However, some might require a BAT file, or COM file (common in demos and really old games). Most of the time, the file is in the root folder. Please consult the documentation of your game for which file is needed to start the game. In the case of [[GAMES:TestDrive|Test Drive]], it's '''TDCGA.EXE'''. So now, I just type this:

C:\TESTDRIV>'''TDCGA.EXE'''

That's it! Here's a picture of all of the commands I've written about in Step 2:

[[Image:Dosbox2.jpg]]

== Alternate methods for running a game ==

The steps described above are closely aligned with how DOS Based operating systems behave natively. However modern operating system allow for more user friendly (although less authentic) ways of playing your favorite games. If the steps above seem tedious or confusing you can try some of these other guides. In most cases these guides will still require you to setup a working DOSBox environment.

*[[DOSBoxFrontends|Using Frontends]]
*[[DOSBoxShortcuts|Creating desktop shortcuts]]
**[[DOSBoxShortcuts#Windows|in Microsoft Windows]]
**[[DOSBoxShortcuts#OSX|in Apple OSX]]
**[[DOSBoxShortcuts#GNOME|in Linux GNOME]]

NOTE: If you have problems with launching the game, unrecognizable errors being spit out, saving settings, or having the game drop out while running it, one thing to try is to make sure all the files are not set to Read Only. In Windows, select the folder of the game, right click and hit properties, uncheck '''Read Only''' if it is checked, and apply to all sub folders.

If you have other errors, please search the [http://vogons.zetafleet.com forums] first before posting a question.

== Performance ==
Yay, you've gotten your game to run! But maybe you're experiencing slowdown? How do you fix this? With the following commands:

'''<tt>CTRL+F7</tt>''' = Decreases frameskip 
'''<tt>CTRL+F8</tt>''' = Increases Frameskip 
'''<tt>CTRL+F11</tt>''' = Slows down the game 
'''<tt>CTRL+F12</tt>''' = Speeds up the game 

Press '''<tt>CTRL+ALT+DEL</tt>''' to open the Task Manager, and click the Performance tab. Start by pressing '''<tt>CTRL+F12</tt>''' until your CPU Usage level begins to go above 95%. After that, if you still need a performance boost, hit '''<tt>CTRL+F8</tt>''' to have DOSBox not render some frames. The console window will display all of the changes you've made, and the top of the game window will display the current settings. Adjust these settings as needed until your game goes smoothly. '''''Please keep in mind that not all games will run smoothly on DOSBox.'''''

[[Image:Dosbox3.jpg]]

== Other Useful features ==

=== Quick start ===

You can save yourself some time by having DOSBox automatically [[MOUNT]] your folders and change the drive to '''C:'''. In original DOS based operating systems a file called '''<tt>[[AUTOEXEC|AUTOEXEC.BAT]]</tt>''' contained any commands that the user wanted executed every time the computer booted up. This functionality is simulated by the [[dosbox.conf#.5Bautoexec.5D|[autoexec]]] section of the [[dosbox.conf]] file.

For DOSBox versions older than 0.73 browse into program installation folder and open the [[dosbox.conf]] file in any text editor. For version 0.73 go to Start Menu and click on "Configuration" and then "Edit Configuration". Then scroll down to the very end, and add these lines:

<code><pre>MOUNT C C:\OLDGAMES
C:</pre></code>

Now those commands will be executed automatically when starting! If you're having trouble with that, make sure it looks like this (look at the bottom):

[[Image:Dosbox4.jpg]]

=== Full Screen ===

Just press '''<tt>ALT+ENTER</tt>''' to go into and out of full screen.

Alternatively, you can open the [[dosbox.conf]] file as mentioned above and change "fullscreen=false" to "fullscreen=true". DOSBox will then run in full screen mode when you open it.

Basic Setup and Installation of DosBox

2010-11-16T04:56:24Z

Ykhwong: Undo revision 4215 by Mutagen (Talk)

>== Basic Concepts ==

DOSBox is an emulator that recreates a MS-DOS compatible environment (complete with Sound, Input, Graphics and even basic networking). This environment is complete enough to run many classic MS-DOS games completely unmodified. In order to utilize all of DOSBox's features you need to first understand some basic concepts about the MS-DOS environment.

* [[MOUNT|Mount a Drive]]
* [[Drives]]
* [[Sound]]
* [[Display]]
* [[Input]]
* [[Connectivity]] (Modems/Networking)

----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://irutubaj.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://irutubaj.co.cc CLICK HERE]=
----
</div>

== Installation ==

The first step is to install DOSBox. This guide will use the [[Version0.72|0.72]] Windows 32 version which is available for [http://www.dosbox.com/download.php?main=1 download]. Download the [[Releases|release]] for your operating system. If you are a Windows user, get the '''Win32 installer'''.

After downloading, install DOSBox to any directory. Also, make a folder to put all your old games in. I put DOSBox in '''<tt>C:\DOSBox</tt>''', and my old games directory is '''<tt>C:\OLDGAMES</tt>'''. I put a game in my '''<tt>OLDGAMES</tt>''' directory, '''<tt>TESTDRIV</tt>''', which is [[GAMES:TestDrive|Test Drive]], an old racing game. Your directories should look like this:

[[Image:DOSBox-Folders.jpg]]

== Running a game ==

Now, the hardest part, getting games to run. First, run '''dosbox.exe''' in your DOSBox folder. Remember that '''<tt>OLDGAMES</tt>''' directory you created in Step 1? You have to basically set that as new directory just for DOSBox. Essentially, it's going to become the '''[[CDrive|C:\>]]''' drive of DOSBox. So, type:
Z:\>'''MOUNT C C:\OLDGAMES'''
Drive C mounted as local directory C:\OLDGAMES\

To dissect the above:
*'''[[MOUNT]]''': Tells the program to [[MOUNT|mount]] a directory
*'''C''': Tells the program what you want your new drive to be called (leaving it as C: is fine)
*'''C:\OLDGAMES''': This is the directory I want to set as the new drive for DOSBox, because all my games are in it. If you created a different directory, write in the directory you created.

''(Note: If you want to [[MOUNT|mount]] a CD-ROM instead of a folder, type this:''
Z:\>'''MOUNT D D:\ -t cdrom'''
MSCDEX installed.
Drive D is mounted as CDRom D:\

''(Note: '''"cdrom"''' is case sensitive and must be lowercase!)''

In this example, '''D:\ -T cdrom''' tells DOSBox that my D:\ drive is a CD-ROM drive, and the first '''D''', tells DOSBox what my new drive name should be called. If you are running your game off a CD-ROM then make sure to use '''D:''' in place of '''C:''' in the following examples. You can find instructions on how to [[MOUNT|mount]] other devices, such as floppy drives, in the [[MOUNT|mount]] section).''

After you've done this, you will be prompted with a '''[[ZDrive|Z:\>]]'''. Now, just write what you wanted to call your new DOSBox drive, which as I said above, we called '''C'''. To navigate to that newly mounted drive just type in:

Z:\>'''C:'''

C:\>

Hopefully, you're all set! Now, it's time to run the game. Previously I had mentioned a game called '''<tt>TESTDRIV</tt>''' in my '''<tt>OLDGAMES</tt>''' folder. I now want DOSBox to go to that folder. So type in:

C:\>'''CD TESTDRIV'''

C:\TESTDRIV>

That's it! [[Commands#CD|CD]] stands for "Change Directory", so you've changed the directory to TESTDRIV. You can find instructions on how to use the [[Commands#CD|Change Directory]] command, in the [[Commands#CD|CD]] section of the [[Commands]] article.

One more step, running the game! Most games have an EXE file in their directory that you can run. However, some might require a BAT file, or COM file (common in demos and really old games). Most of the time, the file is in the root folder. Please consult the documentation of your game for which file is needed to start the game. In the case of [[GAMES:TestDrive|Test Drive]], it's '''TDCGA.EXE'''. So now, I just type this:

C:\TESTDRIV>'''TDCGA.EXE'''

That's it! Here's a picture of all of the commands I've written about in Step 2:

[[Image:Dosbox2.jpg]]

== Alternate methods for running a game ==

The steps described above are closely aligned with how DOS Based operating systems behave natively. However modern operating system allow for more user friendly (although less authentic) ways of playing your favorite games. If the steps above seem tedious or confusing you can try some of these other guides. In most cases these guides will still require you to setup a working DOSBox environment.

*[[DOSBoxFrontends|Using Frontends]]
*[[DOSBoxShortcuts|Creating desktop shortcuts]]
**[[DOSBoxShortcuts#Windows|in Microsoft Windows]]
**[[DOSBoxShortcuts#OSX|in Apple OSX]]
**[[DOSBoxShortcuts#GNOME|in Linux GNOME]]

NOTE: If you have problems with launching the game, unrecognizable errors being spit out, saving settings, or having the game drop out while running it, one thing to try is to make sure all the files are not set to Read Only. In Windows, select the folder of the game, right click and hit properties, uncheck '''Read Only''' if it is checked, and apply to all sub folders.

If you have other errors, please search the [http://vogons.zetafleet.com forums] first before posting a question.

== Performance ==
Yay, you've gotten your game to run! But maybe you're experiencing slowdown? How do you fix this? With the following commands:

'''<tt>CTRL+F7</tt>''' = Decreases frameskip 
'''<tt>CTRL+F8</tt>''' = Increases Frameskip 
'''<tt>CTRL+F11</tt>''' = Slows down the game 
'''<tt>CTRL+F12</tt>''' = Speeds up the game 

Press '''<tt>CTRL+ALT+DEL</tt>''' to open the Task Manager, and click the Performance tab. Start by pressing '''<tt>CTRL+F12</tt>''' until your CPU Usage level begins to go above 95%. After that, if you still need a performance boost, hit '''<tt>CTRL+F8</tt>''' to have DOSBox not render some frames. The console window will display all of the changes you've made, and the top of the game window will display the current settings. Adjust these settings as needed until your game goes smoothly. '''''Please keep in mind that not all games will run smoothly on DOSBox.'''''

[[Image:Dosbox3.jpg]]

== Other Useful features ==

=== Quick start ===

You can save yourself some time by having DOSBox automatically [[MOUNT]] your folders and change the drive to '''C:'''. In original DOS based operating systems a file called '''<tt>[[AUTOEXEC|AUTOEXEC.BAT]]</tt>''' contained any commands that the user wanted executed every time the computer booted up. This functionality is simulated by the [[dosbox.conf#.5Bautoexec.5D|[autoexec]]] section of the [[dosbox.conf]] file.

For DOSBox versions older than 0.73 browse into program installation folder and open the [[dosbox.conf]] file in any text editor. For version 0.73 go to Start Menu and click on "Configuration" and then "Edit Configuration". Then scroll down to the very end, and add these lines:

<code><pre>MOUNT C C:\OLDGAMES
C:</pre></code>

Now those commands will be executed automatically when starting! If you're having trouble with that, make sure it looks like this (look at the bottom):

[[Image:Dosbox4.jpg]]

=== Full Screen ===

Just press '''<tt>ALT+ENTER</tt>''' to go into and out of full screen.

Alternatively, you can open the [[dosbox.conf]] file as mentioned above and change "fullscreen=false" to "fullscreen=true". DOSBox will then run in full screen mode when you open it.

Commands

2010-11-16T04:54:48Z

Ykhwong: Undo revision 4225 by Isomequf (Talk)

== CD (Change Directory) ==
:Allows you to move up and down a directory tree. '''CD''' is simple to use, just type

CD [Directory-Name]

:And if the Directory-Name correctly refers to an available directory then you will be moved from your current working directory to the new one. Once completed, any command you issue will operate under the new working directory, and your prompt will be updated to reflect your current working directory. Multiple folders can be traversed at once (assuming you know the correct names) by typing their names together with the '''\''' separating them for example

C:\>'''CD SIERRA\KQ5'''
C:\SIERRA\KQ5>

:There are also 3 special directories that are available inside every directory which help you simply move around. They are

. which refers to the current directory

.. which refers to the directory directly above the current directory

/ which refers to the root directory

:Once you have moved into a sub directory, you can move back by typing

C:\SIERRA\KQ5>'''CD ..'''
C:\SIERRA>

:And like all other directories you can string them together

C:\SIERRA\KQ5>'''CD ..\..'''
C:\>

:If you ever need to move back to the root directory you can use the '''\''' alias.

C:\SIERRA\KQ5>'''CD \'''
C:\>

== CLS ==
:Clears the screen of all input and returns just the current prompt in the upper left hand corner.

== COPY ==
:Copy a file
:Syntax is COPY <Orignal Filename> <New Filename>

COPY Document.txt CopyOfDocument.TXT

== DIR ==
:Lists all of the available files and sub directories inside the current directory. Some variants of this are "dir/p" (pauses after each page) and "dir/w" (this gives a wide view)

== DEL ==
:Remove one or more files.

== EXIT ==
:Exit from DOSBox

== MD ==
:Makes a directory.

== MOVE (unsupported) ==
:DOSBox has no MOVE command. Use the REN command to move files.

== RD ==
:Removes a directory.

== TYPE ==
:Display the contents of a text-file.

== REN ==
:Renames one or more files.
:Note: Unlike MS-DOS, DOSBox doesn't require the source and target filenames to be in the same folder.

== LOADFIX ==
:Loads a program above the first 64K of memory.

== LOADHIGH ==
:Loads a program into upper memory (requires xms=true,umb=true)

== CHOICE ==
:Waits for a keypress and sets ERRORLEVEL. Displays the given prompt followed by [Y,N]? for yes or no respones.
:Used for batch scripts in most cases.

CHOICE "Text to ask"

== VER ==
:View and set the reported DOS version. Also displays the running DOSBox version.
:To set the reported DOS version use the following:

VER SET <MAJOR> [MINOR]

:where MAJOR is the number before the period, and MINOR is what comes after.
:Versions can range from 0.0 to 255.255. Any values over 255 will loop from zero. (That is, 256=0, 257=1, 258=2, etc)

DOSBox FAQ

2010-11-16T04:53:14Z

Ykhwong: Undo revision 4219 by Isomequf (Talk)

DOSBOX comes with a README.TXT that answers many Frequently Asked Questions. You can read an online version [http://dosbox.cvs.sourceforge.net/dosbox/dosbox/README?view=markup here]. If you still cannot find the answer, check this page.

== Performance ==

===Slow games/applications===
'''Q.''' My game/application runs slowly, how do I improve speed?

'''A.''' Increase cycles. Use core=dynamic. Try different output modes (e.g. output=overlay). Increase Frameskip. Disable unneeded components in the [[dosbox.conf]] such as [[Sound]], mouse or joystick emulation. A nice speedup can be achieved by using a [[Other compilers|different compiler]] than GCC. If all else fails, find a faster computer to run DOSBox on.
Also be sure to check the compatibility section of this FAQ as some game/applications are more trouble (or resource hogs) than others.

* See also [[Performance#How to speed up/slow down DOSBox|How to speed up/slow down DOSBox]]

===Problems in sound/music===
'''Q.''' The Sound/Music for my DOS game/application sounds terrible what can I do?

'''A.''' This is a complicated issue covered in the [[Sound]] section of the wiki. It's important to remember to install or setup game/applications correctly to use the correct sound devices (<tt>INSTALL.EXE</tt>, <tt>SOUNDSET.EXE</tt> and <tt>SETUP.EXE</tt> are popular program names to look for). The capabilities of the hardware as well as the preferences of the programmer vary: Therefore what may sound "best" on one particular game may not be the "best" for another. Sometimes changes need to be made to the [[dosbox.conf]] file (or a new conf file) to get the best results.
Also, game sound/music may have an impact on the speed at which the game/application runs and running DOSBox with limited resources may result in incomplete or 'choppy' sound being heard. (see previous question)

===Increasing memory size===
'''Q.''' How do I change the memory size so that I can run programs that require more than the default settings (eg. Windows 1.01 or some other demanding OS)?

'''A.''' See the memsize option detailed in [[Configuration:DOSBox]].

== Usage ==

===Problems with colors and fullscreen drawing in Mac OS X===
'''Q.''' Using Mac OS X 10.5.3 without a problem (MOO) and when upgraded to 10.5.4 MOO started flashing rainbow colors instead of the normal background in full screen mode (works fine in windowed mode.) I have a warning about the quickdraw capability being deprecated in my console window. Any suggestions?

'''A.''' Go to your users home directory e.g. /Users/asc/Library/Preferences and open "DOSBox 0.73 Preferences". In the [sdl] section edit the parameter "output" so that it says: "output=opengl". Afterwards restart DOS Box. Colors and drawing issues should now be gone.

===No backslash key===
'''Q.''' My backslash key is mapped to ']' with DOSBox on Windows. Is there a workaround?

'''A.''' This is usually a keyboard driver problem. You can either fix your driver or use the [[keymapper]] as a workaround. Here is a thread on VOGONS, detailing the problem:[http://vogons.zetafleet.com/viewtopic.php?t=18465 http://vogons.zetafleet.com/viewtopic.php?t=18465]

''' - Driver fix on Windows XP'''

Right click ''My Computer'', select ''Properties''. On the ''Hardware'' tab, select ''Device Manager''. Find your keyboard, right click, ''Update driver''. Select ''No, not this time'', then ''Install from a list or specific location (Advanced)''. Select ''Don't search''. You arrive to a screen where compatible drivers are listed. Changing from ''Microsoft Natural PS/2'' driver to ''PC/AT Enhanced PS/2'' driver reportedly solved this issue. You can experiment with any other compatible device you find on the list. If you are using an USB keyboard try the keyboard manufacturer's drivers.

''' - Driver fix on Windows Vista'''

Click on the ''Windows button'', right click on ''Computer'', select ''Properties''. Next, select ''Device Manager'' in the top left corner, and ''Continue'' on the User Account Control screen. Find your keyboard under ''Keyboards''. Right click on the keyboard entry, select ''Update Driver Software...''. Then select ''Browse my computer...'', and ''Let me pick...''. Here you can change your current driver to another compatible one, or use the disk provided by your manufacturer.

''' - Workaround using DosBox Keymapper'''

Press <tt>CTRL-F1</tt> to enter the [[keymapper]] and select the backslash with your mouse. Press the <tt>DELETE</tt> button that will show up on your screen. Then press <tt>ADD</tt> to bind backslash to another key. Simply press an unused key to bind it to this. Press <tt>SAVE</tt> and then <tt>EXIT</tt> to return to the main screen.

===Trapped mouse cursor===
'''Q.''' My cursor is trapped within the DOSBox window when I click inside. How do I get the cursor out?

'''A.''' DOSBox will capture your mouse when you click inside the display window (and you have '''<tt>autolock=true</tt>''' set in the [[Dosbox.conf]]). Simply press '''<tt>CTRL-F10</tt>''' to release the mouse.

=== Gnome scripting ===
'''Q.''' I have set Gnome to load DOSBox when I click on .COM files. How do I script it to exit DOSBox when I quit from the game?

'''A.''' With -exit as commandline parameter for DOSBox.

===Hard drive/CDROM access===
'''Q.''' How do I access my hard drive/cdrom in DOSBox?

'''A.''' See the information on the [[MOUNT]] command, or type <tt>intro mount</tt> or <tt>intro cdrom</tt> in DOSBox for the basics.

=== Accessing ISO images===
'''Q.''' I have an ISO image I made of files for backup purposes. How do I access it in DOSBox?

'''A.''' See the information on the [[IMGMOUNT]] command

=== Swapping CD images===
'''Q.''' How do I unmount or change images? I need to swap CD images in the drive.

'''A.''' You may assign more than one image file to [[IMGMOUNT]], to swap images use <tt>CTRL-F4</tt>. You can also unmount images by using the -u switch. See [[IMGMOUNT]] for more information.

===CD Audio tracks===
'''Q.''' I have created an image from a CD that includes CD audio tracks, when I access it in DOSBox only the first (data) track is available.

'''A.''' Be sure to use the bin/cue format for mixed mode CDs (CDs with a data and audio tracks) and always pass the cue file to [[IMGMOUNT]].

===Gibberish===
'''Q.''' When I write '':'' it turns out ''>'' or when i write ''å'' ''ä'' ''ö'' or any other non standard us character. How can I fix this for my keyboard?

'''A.''' Use the [[KEYB]] command to change your [[KEYB#Layout codes|Keyboard layout]].

===No ":" symbol===
'''Q.''' I can't find the ":" symbol anywhere in my dosbox. I am using Vista on a laptop. Please advice me how to fix the problem.

'''A.''' Use the left shift instead of the right shift. A number of keys are affected by this problem. For a workaround for other keys like "\", see the second answer.

===Scrolling up/down===
'''Q.''' How do you/I scroll up to see text that is not visible in the DOSBox window? Certain apps will print a long string of text, and you can't see it all.

'''A.''' Unlike the DOS window in Windows 2000, XP and Vista, DOSBox exactly emulates a full screen DOS session. Hence it doesn't support scrolling up and down. However, MS-DOS included a program to allow you to 'press any key' to scroll down called MORE.COM. This is how to do it on Windows:
# Try and find a copy of MORE.COM from MS-DOS 5.0 (good luck) or MORE.EXE from FreeDOS ([http://www.freedos.org/cgi-bin/lsm.cgi?mode=lsm&lsm=base/more.lsm easy])
# Put it in C:\C
# Edit C:\Program Files\Dosbox\dosbox.conf in Notepad
# Go to the bottom of the file, where it reads <tt>[autoexec]</tt>. Add to it or change it to read: <tt>[autoexec] MOUNT C C:\C PATH=%PATH%;C:\</tt> 
# Save it, close DOSBox and then re-open DOSbox.
# Now, say you wanted to use this command: <tt>C:\> type readme.txt</tt> Instead type this: <tt>C:\> type readme.txt | more</tt>

Linux/Unix users looking to capitalize on muscle memory may prefer [http://www.greenwoodsoftware.com/less/less381d.zip less compiled for DOS]. (Note: Old version. The author has stopped providing new precompiled binaries for DOS)

== Misc ==

===The main site's image===
'''Q.''' What is the picture in the dosbox www site in the title bar?

'''A.''' [[GAMES:Dune 2|Dune 2]].

=== What is DOS?===
DOS (see [[Wikipedia:DOS]]) is short for "Disk Operating System". It mainly refers to the series of operating systems that dominated the IBM PC compatible market from the 1980s and into the 1990s. But it may also refer to the DOS-based Microsoft Windows 9X/ME series of the late 1990s. The relevant systems were usually called "'''X''' DOS", "'''X'''-DOS" or "'''X'''DOS" with the X being the brand name. Despite common usage, none of them were actually called just DOS. Microsoft's system, MS-DOS, is probably the most known.

=== What is Abandonware?===
Abandonware (see [[Wikipedia:Abandonware]]) is the term people usually use to describe computer softwares and games which are neither sold nor supported anymore. As it is not an official term, it's important to remember that just because something is considered as abandonware doesn't mean it actually is, especially as the estimation is usually based strictly on age. Moreover, even if it is, it has no legal meaning. In other words, it still has just as much copyrights as if it was actively developed. In fact, the Entertainment Software Association (ESA - fomerly IDSA) actively pursuits those that disribute what they consider abandonware.

Building DOSBox with Visual Studio

2010-11-14T07:50:24Z

Ykhwong: 0.73 -> 0.74

Note: The title of this page should actually be "''Building DOSBox with Visual C++ 2008 Express''", but the Wiki software does not allow the use of the + character in a title.

DOSBox is a complicated project. This document aims to provide a step by step description of how to use the free Express Edition of Microsoft's Visual C++ 2008 to successfully build DOSBox.

== Get Visual C++ 2008 Express ==
Microsoft provides the Express edition of Visual C++ 2008 for free. Download VCE [http://www.microsoft.com/Express/vc/ directly from Microsoft] and install it. When installing, you don’t need to select any of the optional components like the Silverlight runtime, SQL Server or the MSDN Express Library. After the installation is complete, you will need to restart your computer.

== Get the SDL library ==
To be able to build DOSBox, you will also need the development libraries for SDL. At the time of writing, the most current release of SDL is 1.2.13. From the downloads section at the [http://www.libsdl.org/ SDL website] look for the Development Libraries for Win32, marked for Visual C++ 2005 Service Pack 1. The filename will be something like <tt>SDL-devel-1.2.13-VC8.zip</tt>. Unpack this file to the location of your choosing. For this discussion, I shall place it in <tt>C:\Development\SDL-1.2.13</tt>.

== Get the DOSBox sources ==
The next step is to get DOSBox itself. At the time of writing, the most current release of DOSBox is 0.74. Go to [http://www.dosbox.com/download.php?main=1 the DOSBox download page] and download the DOSBox source. Since the DOSBox sources come as a <tt>.tar.gz</tt> file, you may need a separate program to extract this. Unpack the source to the location of your choosing. For this discussion, I have chosen <tt>C:\Development\dosbox-0.74</tt>.

== Set up the environment ==
[[Image:Vce_guide1.png|thumb|Setting the include directories for SDL]]
From your start menu, start VCE. After a few moments, the IDE (Integrated Development Environment) will start. The first thing we need to do is tell VCE where to find SDL. From the "Tools" menu select "Options". When the Options menu appears, expand the category "Projects and Solutions" and choose "VC++ Directories". From the directories pulldown, choose to show the directories for include files, click the folder icon and add the folder for the SDL includes. If you have been following this guide literally, that would <tt>C:\Development\SDL-1.2.13\include</tt>. Next, elect to show the directories for library files. This time, add the folder for the SDL libraries. When you have followed this guide, that would be <tt>C:\Development\SDL-1.2.13\lib</tt>.

After you have done this, click OK to accept and close the options.

 
== Set up the solution ==
=== Conversion wizard ===
[[Image:Vce_guide2.png|thumb|Conversion wizard]]
Open the solution provided by DOSBox. It can be found as <tt>C:\Development\dosbox-0.74\visualc_net\dosbox.sln</tt>. If you have file extensions hidden (as they are by default), you may select "Solution files (*.sln)" from the object type dropdown to ensure you get the correct one. The first time you open the solution, VCE will present you with the Visual Studio Conversion Wizard, because the solution included in the DOSBox distribution is for an older version of Visual C++. You can simply click Finish and be done with it. If you want, you can take a look at the conversion log, but the information in there is not particularly interesting.
 
=== Dependencies ===
[[Image:Vce_guide3.png|thumb|Editing the additional dependencies]]
Now that the solution has been opened, it is necessary to disable some of the optional features of DOSBox. From the "Project" menu select "dosbox Properties". Expand the "Configuration Properties" and then the "Linker" category. Then choose "Input". From the properties on the right, you will need to remove some of the "Additional Dependencies". With the setup I have described here, I need to remove '''sdl_net.lib''', '''zlib.lib''', '''libpng.lib''' and '''curses.lib''' (you will also not need the odbc32.lib and odbccp32.lib references, but there is no harm in leaving them). Apply the changes and use the dropdown at the top left to switch to the Release configuration. Repeat the previous step, removing those same references and again apply the changes.
 
=== Configuration setup ===
[[Image:Vce_guide4.png|thumb|Adjusting the config.h file]]
In the Solution Explorer, browse down the solution into "Source files" and then "visualc". Open the file <tt>config.h</tt> listed there and do some editing. Find the line that reads
#define C_SSHOT 1
and change the 1 to a 0. Do the same for the lines mentioning <tt>C_MODEM</tt> and <tt>C_IPX</tt>. The reason we are disabling these options is that they require some extra libraries that we haven’t set up for this tutorial. Also, set <tt>C_CORE_INLINE</tt> to 1 to enable faster CPU emulation.

In the Solution Explorer, in the "Source files", you will find the file <tt>winres.rc</tt>. Right-click on that and choose "View code". ''Remove'' the line at the top that reads
#include "afxres.h"
When you have done this, save the solution ("Save all" from the file menu). This ensures you won’t have to repeat any of the previous steps.
 

== The actual build ==
[[Image:Vce_guide5.png|thumb|Build successfully completed]]
Before building, right click on "Solution 'dosbox'" in the Solution Explorer and go to Properties -> Configuration Properties. Set the Configuration dropdown box to "Release" instead of "Debug". This will cause VC++ to build an optimized binary without extra debug features.

Now that all this is done, press F7 to start the build process. There will be a few warnings, but they are unimportant. The build may take a few minutes depending on the speed of your computer, but if you have followed this tutorial it will complete successfully.

Note that to actually run the executable you have built, you will need the SDL library (<tt>SDL.DLL</tt>) from your regular DOSBox install and place it in the <tt>C:\Development\dosbox-0.74\visualc_net</tt> directory.

Language File

2010-11-02T15:54:56Z

Ykhwong:

== How to create ==
A language file can be generated by [[CONFIG|CONFIG.COM]], which can be found on the internal DOSBox [[ZDrive|Z: drive]] when you start up DOSBox.

CONFIG -writelang filelocation

It writes the current language settings to a file in a specified location. <code>"filelocation"</code> is located on the local drive, not a mounted drive in DOSBox. The language file controls all visible output of the internal commands and the internal DOS.

== How to change ==
Read the language file that you created from the instruction above, and you will hopefully understand how to change it.

== How to use in DOSBox ==
You can setup the filename in the configuration file ([[Dosbox.conf|DOSBox.Conf]]) in the [dosbox] section. There's a <code>language=</code> entry that can be changed with the <code>filelocation</code>.

Alternatively, start DOSBox with the <code>-lang</code> switch to use your new language file.

== See also ==
* [http://www.dosbox.com/download.php?main=1 Language translations]

Building DOSBox with MinGW

2010-11-02T15:51:27Z

Ykhwong: CVS to SVN

== Building your own version of DOSBox ==

Why to do this? 
Because any resource-intensive program can benefit greatly from optimization for your exact processor. 
[[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 MiniGW and MSYS, which can be found at

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

You'll need to download both the latest MiniGW and MSYS. After downloading, install MiniGW and MSYS (in this order). The MSYS-Installer should ask for the installation directory of MiniGW, 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 7.1 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.

Usage

2010-11-02T15:48:14Z

Ykhwong:

== Command Line Parameters ==
<code>dosbox [name] [-exit] [-c command] [-fullscreen] [-userconf] [-conf congfigfilelocation] [-lang languagefilelocation] [-machine machine type] [-noconsole] [-startmapper] [-noautoexec] [-securemode] [-scaler scaler | -forcescaler scaler] [-version] [-socket socket] [-editconf program] [-opencaptures program] [-printconf] [-eraseconf] [-erasemapper]</code>

===Usage===
;<code>name</code>: If <code>name</code> is a directory, DOSBox will mount the specified directory as the C drive. If <code>name</code> is an executable, DOSBox will mount the directory of <code>name</code> as the C drive, and start executing <code>name</code>.

;<code>-exit</code>: DOSBox will close itself when the DOS application "name" ends.

;<code>-c command</code>: Runs the specified command before running <code>name</code>. Multiple commands can be specified. Each command should start with <code>-c</code> though. A command can be: an Internal Program, a DOS command or an executable on a mounted drive.

;<code>-fullscreen</code>: Starts DOSBox in fullscreen mode.

;<code>-userconf</code>: Start DOSBox with the options specified in "configfilelocation". Multiple -conf options may be present.

;<code>-conf configfilelocation</code>: Start DOSBox with the options specified in <code>configfilelocation</code>. Multiple -conf options may be present.

;<code>-lang languagefilelocation</code>: Start DOSBox using the language string specified in <code>languagefilelocation</code>.

;<code>-machine machinetype</code>: Setup DOSBox to emulate a specific type of machine. Valid choices are: hercules, cga, ega, pcjr, tandy, svga_s3 (default) as well as the additional svga chipsets listed in the [[dosbox.conf|DOSBox configuration file]]. The machinetype affects the video card and the available sound cards.

;<code>-noconsole</code> (Windows Only): Start DOSBox without showing the console window, output will be redirected to <code>stdout.txt</code> and <code>stderr.txt</code>. This is useful if DOSBox crashes, since the error messages stored in <code>stdout.txt</code> and <code>stderr.txt</code> may help the developers fixing the problem.

;<code>-startmapper</code>: Enter the [[Mapper|mapper]] directly on startup. Useful for people with keyboard or joystick problems.

;<code>-noautoexec</code>: Skips the [autoexec] section of the loaded configuration file.

;<code>-securemode</code>: Same as -noautoexec, but adds config.com <code>-securemode</code> at the bottom of AUTOEXEC.BAT (which in turn disables any changes to how the drives are mounted inside DOSBox).

;<code>-scaler</code>: Uses the scaler specified by "scaler". See the DOSBox [[dosbox.conf|configuration file]] for the available scalers.

;<code>-forcescaler</code>: Similar to the -scaler parameter, but tries to force usage of the specified scaler even if it might not fit.

;<code>-version</code>: output version information and exit. (see stdout.txt) Useful for frontends.

;<code>-editconf program</code>: calls program with as first parameter the configuration file. You can specify this command more than once. In this case it will move to second program if the first one fails to start.

;<code>-opencaptures program</code>: calls program with as first parameter the location of the captures folder.

;<code>-printconf</code>: prints the location of the default configuration file.

;<code>-resetconf</code>: removes the default configuration file.

;<code>-resetmapper</code>: removes the mapperfile used by the default clean configuration file.

;<code>-socket</code>: passes the socket number to the nullmodem emulation.

===Notes===
*If a <code>name/ command/ configfilelocation/ languagefilelocation</code> contains a space in it, put the whole <code>name/ command/ configfilelocation/ languagefilelocation</code> between quotes ("example").
*In Windows you can also drag directories/files onto the DOSBox executable.

===Example===
dosbox c:\atlantis\atlantis.exe -c "MOUNT D C:\SAVES"

This would mount <code>c:\atlantis</code> as <code>c:\</code> and run <code>atlantis.exe</code>. Before it does that, it would first mount <code>C:\SAVES</code> as the D drive.

Usage

2010-11-02T15:45:58Z

Ykhwong:

== Command Line Parameters ==
<code>dosbox [name] [-exit] [-c command] [-fullscreen] [-userconf] [-conf congfigfilelocation] [-lang languagefilelocation] [-machine machine type] [-noconsole] [-startmapper] [-noautoexec] [-securemode] [-scaler scaler | -forcescaler scaler] [-version] [-socket socket] [-editconf program] [-opencaptures program] [-printconf] [-eraseconf] [-erasemapper]</code>

===Usage===
;<code>name</code>: If <code>name</code> is a directory, DOSBox will mount the specified directory as the C drive. If <code>name</code> is an executable, DOSBox will mount the directory of <code>name</code> as the C drive, and start executing <code>name</code>.

;<code>-exit</code>: DOSBox will close itself when the DOS application "name" ends.

;<code>-c command</code>: Runs the specified command before running <code>name</code>. Multiple commands can be specified. Each command should start with <code>-c</code> though. A command can be: an Internal Program, a DOS command or an executable on a mounted drive.

;<code>-fullscreen</code>: Starts DOSBox in fullscreen mode.

;<code>-userconf</code>: Start DOSBox with the options specified in "configfilelocation". Multiple -conf options may be present.

;<code>-conf configfilelocation</code>: Start DOSBox with the options specified in <code>configfilelocation</code>. Multiple -conf options may be present.

;<code>-lang languagefilelocation</code>: Start DOSBox using the language string specified in <code>languagefilelocation</code>.

;<code>-machine machinetype</code>: Setup DOSBox to emulate a specific type of machine. Valid choices are: hercules, cga, ega, pcjr, tandy, svga_s3 (default) as well as the additional svga chipsets listed in the [[dosbox.conf|DOSBox configuration file]]. The machinetype affects the video card and the available sound cards.

;<code>-noconsole</code> (Windows Only): Start DOSBox without showing the console window, output will be redirected to <code>stdout.txt</code> and <code>stderr.txt</code>. This is useful if DOSBox crashes, since the error messages stored in <code>stdout.txt</code> and <code>stderr.txt</code> may help the developers fixing the problem.

;<code>-startmapper</code>: Enter the [[Mapper|mapper]] directly on startup. Useful for people with keyboard or joystick problems.

;<code>-noautoexec</code>: Skips the [autoexec] section of the loaded configuration file.

;<code>-securemode</code>: Same as -noautoexec, but adds config.com <code>-securemode</code> at the bottom of AUTOEXEC.BAT (which in turn disables any changes to how the drives are mounted inside DOSBox).

;<code>-scaler</code>: Uses the scaler specified by "scaler". See the DOSBox [[dosbox.conf|configuration file]] for the available scalers.

;<code>-forcescaler</code>: Similar to the -scaler parameter, but tries to force usage of the specified scaler even if it might not fit.

;<code>-version</code>: output version information and exit. (see stdout.txt) Useful for frontends.

;<code>-editconf program</code>: calls program with as first parameter the configuration file. You can specify this command more than once. In this case it will move to second program if the first one fails to start.

===Notes===
*If a <code>name/ command/ configfilelocation/ languagefilelocation</code> contains a space in it, put the whole <code>name/ command/ configfilelocation/ languagefilelocation</code> between quotes ("example").
*In Windows you can also drag directories/files onto the DOSBox executable.

===Example===
dosbox c:\atlantis\atlantis.exe -c "MOUNT D C:\SAVES"

This would mount <code>c:\atlantis</code> as <code>c:\</code> and run <code>atlantis.exe</code>. Before it does that, it would first mount <code>C:\SAVES</code> as the D drive.

Usage

2010-11-02T15:43:19Z

Ykhwong:

== Command Line Parameters ==
<code>dosbox [name] [-exit] [-c command] [-fullscreen] [-userconf] [-conf congfigfilelocation] [-lang languagefilelocation] [-machine machine type] [-noconsole] [-startmapper] [-noautoexec] [-securemode] [-scaler scaler | -forcescaler scaler] [-version] [-socket socket] [-editconf program] [-opencaptures program] [-printconf] [-eraseconf] [-erasemapper]</code>

===Usage===
;<code>name</code>: If <code>name</code> is a directory, DOSBox will mount the specified directory as the C drive. If <code>name</code> is an executable, DOSBox will mount the directory of <code>name</code> as the C drive, and start executing <code>name</code>.

;<code>-exit</code>: DOSBox will close itself when the DOS application "name" ends.

;<code>-c command</code>: Runs the specified command before running <code>name</code>. Multiple commands can be specified. Each command should start with <code>-c</code> though. A command can be: an Internal Program, a DOS command or an executable on a mounted drive.

;<code>-fullscreen</code>: Starts DOSBox in fullscreen mode.

;<code>-userconf</code>: Start DOSBox with the options specified in "configfilelocation". Multiple -conf options may be present.

;<code>-conf configfilelocation</code>: Start DOSBox with the options specified in <code>configfilelocation</code>. Multiple -conf options may be present.

;<code>-lang languagefilelocation</code>: Start DOSBox using the language string specified in <code>languagefilelocation</code>.

;<code>-machine machinetype</code>: Setup DOSBox to emulate a specific type of machine. Valid choices are: hercules, cga, ega, pcjr, tandy, svga_s3 (default) as well as the additional svga chipsets listed in the [[dosbox.conf|DOSBox configuration file]]. The machinetype affects the video card and the available sound cards.

;<code>-noconsole</code> (Windows Only): Start DOSBox without showing the console window, output will be redirected to <code>stdout.txt</code> and <code>stderr.txt</code>. This is useful if DOSBox crashes, since the error messages stored in <code>stdout.txt</code> and <code>stderr.txt</code> may help the developers fixing the problem.

;<code>-startmapper</code>: Enter the [[Mapper|mapper]] directly on startup. Useful for people with keyboard or joystick problems.

;<code>-noautoexec</code>: Skips the [autoexec] section of the loaded configuration file.

;<code>-securemode</code>: Same as -noautoexec, but adds config.com <code>-securemode</code> at the bottom of AUTOEXEC.BAT (which in turn disables any changes to how the drives are mounted inside DOSBox).

===Notes===
*If a <code>name/ command/ configfilelocation/ languagefilelocation</code> contains a space in it, put the whole <code>name/ command/ configfilelocation/ languagefilelocation</code> between quotes ("example").
*In Windows you can also drag directories/files onto the DOSBox executable.

===Example===
dosbox c:\atlantis\atlantis.exe -c "MOUNT D C:\SAVES"

This would mount <code>c:\atlantis</code> as <code>c:\</code> and run <code>atlantis.exe</code>. Before it does that, it would first mount <code>C:\SAVES</code> as the D drive.

User:Shibakuma

2010-11-02T15:36:20Z

Ykhwong: removed an unnecessary redirection

KeyMapper

2010-10-27T07:43:00Z

Ykhwong: Redirected page to Mapper

#REDIRECT [[Mapper]]

Special Keys

2010-10-27T07:39:41Z

Ykhwong:

Note: These are the default keybindings. They can be changed using the [[KeyMapper|keymapper]].
{|
|-valign="top"
|width="100px"|'''ALT-ENTER'''||Switch to [[dosbox.conf/render|full-screen]] (and back).
|-valign="top"
|'''ALT-PAUSE'''||Pause emulation.
|-valign="top"
|'''CTRL-F1'''||Show the [[KeyMapper|keymapper]] configuration screen,
|-valign="top"
|'''CTRL-F4'''||Update cached information about mounted drives. Useful if you changed something on a mounted drive outside of DOSBox. Also cycles through disk images mounted using [[IMGMOUNT]].
|-valign="top"
|'''CTRL-F5'''||Save a screenshot (goes to [[SnapsFolder|capture folder]]).
|-valign="top"
|'''CTRL-ALT-F5'''||Start/Stop recording of AVI video. NOTE: You may well have some problems with this, please see [[Recording Video]] for more information.
|-valign="top"
|'''CTRL-F6'''||Start/Stop recording sound output to a wave file (goes to [[SnapsFolder|capture folder]]).
|-valign="top"
|'''CTRL-ALT-F7'''||Start/Stop recording of [[Adlib|OPL]] commands.
|-valign="top"
|'''CTRL-ALT-F8'''||Start/Stop the recording of raw [[MIDI]] commands.
|-valign="top"
|'''CTRL-F7'''||Decreases frameskip.
|-valign="top"
|'''CTRL-F8'''||Increases frameskip.
|-valign="top"
|'''CTRL-F9'''||Kill (close) DOSBox.
|-valign="top"
|'''CTRL-F10'''||Capture/Release the mouse (if you need to use the mouse within DOSBox).
|-valign="top"
|'''CTRL-F11'''||Decrease DOSBox [[Configuration:CPU|cycles]] ([[Performance#CPU Cycles (speed up/slow down)|slows down]] the emulation).
|-valign="top"
|'''CTRL-F12'''||Increase DOSBox [[Configuration:CPU|cycles]] ([[Performance#CPU Cycles (speed up/slow down)|speeds up]] the emulation).
|-valign="top"
|'''ALT-F12'''||Unlock speed (turbo button).
|}

These default bindings are also documented in the README file accompanying the software.

== Language Keys ==
When a [[Keyboard layout|keyboard layout]] is loaded:
{|
|-valign="top"
|width="175px"|'''CTRL+ALT+F2'''||Switch between foreign layout and US layout.
|-valign="top"
|'''LEFT-ALT+RIGHT-SHIFT'''||Activate dual layouts (for some keyboards, e.g. GK codepage 869 and RU codepage 808).
|-valign="top"
|'''LEFT-ALT+LEFT-SHIFT'''||Deactivate dual layouts.
|}
For OS X you have to use additionally + [Applekey] for the same result
For Linux you have to use additionally + [win] for the same result

Mapper

2010-10-27T03:44:50Z

Ykhwong:

== Remapping the keyboard and joystick ==

When you start the mapper (either with CTRL-F1 or -startmapper as a commandline argument to the DOSBox executable) you are presented with a virtual keyboard and a virtual joystick. These virtual devices correspond to the keys and events DOSBox will report to the DOS applications. If you click on a button with your mouse, you can see in the lower left corner with which event it is associated (EVENT) and to what events it is currently bound.
<big>
Event: EVENT
BIND: BIND (the real key/button/axis you push with your finger/hand)

Add Del
mod1 hold Next
mod2
mod3
</big>
* EVENT: The key or joystick axis/button/hat DOSBox will report to DOS applications. (the event that will happen during the game, (eg. shooting/jumping/walking)
* BIND: The key on your real keyboard or the axis/button/hat on your real joystick(s) (as reported by SDL), which is connected to the EVENT.
* mod1,2,3: Modifiers. These are keys you need to have to be pressed while pressing BIND. mod1 = CTRL and mod2 = ALT. These are generally only used when you want to change the special keys of DOSBox.
* Add: Add a new BIND to this EVENT. Basically add a key from your keyboard or an event from the joystick (button press, axis/hat movement) which will produce the EVENT in DOSBox.
* Del: Delete the BIND to this EVENT. If an EVENT has no BINDS, then it is not possible to trigger this event in DOSBox (that is there's no way to type the key or use the respective action of the joystick).
* Next: Go through the list of bindings which map to this EVENT.

== Examples ==

Q1. You want to have the X on your keyboard to type a Z in DOSBox.
: A. Click on the Z on the keyboard mapper. Click "Add". Now press the X key on your keyboard.

Q2. If you click "Next" a couple of times, you will notice that the Z on your keyboard also produces an Z in DOSBox.
: A. Therefore select the Z again, and click "Next" until you have the Z on your keyboard. Now click "Del".

Q3. If you try it out in DOSBox, you will notice that pressing X makes ZX appear.
: A. The X on your keyboard is still mapped to the X as well! Click on the X in the keyboard mapper and search with "Next" until you find the mapped key X. Click "Del".

Examples about remapping the joystick:
:You have a joystick attached, it is working fine under DOSBox and you want to play some keyboard-only game with the joystick (it is assumed that the game is controlled by the arrows on the keyboard):
# Start the mapper, then click on one of the left keyboard arrow. EVENT should be key_left. Now click on Add and move your joystick in the respective direction, this should add an event to the BIND.
# Repeat the above for the missing three directions, additionally the buttons of the joystick can be remapped as well (fire/jump).
# Click on Save, then on Exit and test it with some game.

You want to swap the y-axis of the joystick because some flightsim uses the up/down joystick movement in a way you don't like, and it is not configurable in the game itself:
# Start the mapper and click on Y- in the first joystick field. EVENT should be jaxis_0_1-.
# Click on Del to remove the current binding, then click Add and move your joystick downwards. A new bind should be created.
# Repeat this for Y+, save the layout and finally test it with some game.

If you want to remap anything to your d-pad/hat you will have to change <code>joysticktype=auto</code> to <code>joysticktype=fcs</code> in configuration file. Maybe this will be improved in the next dosbox version.

----

If you change the default mapping, you can save your changes by clicking on "Save". DOSBox will save the mapping to a location specified in the configuration file (the mapperfile= entry). At startup, DOSBox will load your mapperfile, if it is present in the DOSBox configuration file.

Mapper

2010-10-27T03:43:23Z

Ykhwong:

== Mapper ==

When you start the mapper (either with CTRL-F1 or -startmapper as a commandline argument to the DOSBox executable) you are presented with a virtual keyboard and a virtual joystick. These virtual devices correspond to the keys and events DOSBox will report to the DOS applications. If you click on a button with your mouse, you can see in the lower left corner with which event it is associated (EVENT) and to what events it is currently bound.
<big>
Event: EVENT
BIND: BIND (the real key/button/axis you push with your finger/hand)

Add Del
mod1 hold Next
mod2
mod3
</big>
* EVENT: The key or joystick axis/button/hat DOSBox will report to DOS applications. (the event that will happen during the game, (eg. shooting/jumping/walking)
* BIND: The key on your real keyboard or the axis/button/hat on your real joystick(s) (as reported by SDL), which is connected to the EVENT.
* mod1,2,3: Modifiers. These are keys you need to have to be pressed while pressing BIND. mod1 = CTRL and mod2 = ALT. These are generally only used when you want to change the special keys of DOSBox.
* Add: Add a new BIND to this EVENT. Basically add a key from your keyboard or an event from the joystick (button press, axis/hat movement) which will produce the EVENT in DOSBox.
* Del: Delete the BIND to this EVENT. If an EVENT has no BINDS, then it is not possible to trigger this event in DOSBox (that is there's no way to type the key or use the respective action of the joystick).
* Next: Go through the list of bindings which map to this EVENT.

== Examples ==

Q1. You want to have the X on your keyboard to type a Z in DOSBox.
: A. Click on the Z on the keyboard mapper. Click "Add". Now press the X key on your keyboard.

Q2. If you click "Next" a couple of times, you will notice that the Z on your keyboard also produces an Z in DOSBox.
: A. Therefore select the Z again, and click "Next" until you have the Z on your keyboard. Now click "Del".

Q3. If you try it out in DOSBox, you will notice that pressing X makes ZX appear.
: A. The X on your keyboard is still mapped to the X as well! Click on the X in the keyboard mapper and search with "Next" until you find the mapped key X. Click "Del".

Examples about remapping the joystick:
:You have a joystick attached, it is working fine under DOSBox and you want to play some keyboard-only game with the joystick (it is assumed that the game is controlled by the arrows on the keyboard):
# Start the mapper, then click on one of the left keyboard arrow. EVENT should be key_left. Now click on Add and move your joystick in the respective direction, this should add an event to the BIND.
# Repeat the above for the missing three directions, additionally the buttons of the joystick can be remapped as well (fire/jump).
# Click on Save, then on Exit and test it with some game.

You want to swap the y-axis of the joystick because some flightsim uses the up/down joystick movement in a way you don't like, and it is not configurable in the game itself:
# Start the mapper and click on Y- in the first joystick field. EVENT should be jaxis_0_1-.
# Click on Del to remove the current binding, then click Add and move your joystick downwards. A new bind should be created.
# Repeat this for Y+, save the layout and finally test it with some game.

If you want to remap anything to your d-pad/hat you will have to change <code>joysticktype=auto</code> to <code>joysticktype=fcs</code> in configuration file. Maybe this will be improved in the next dosbox version.

----

If you change the default mapping, you can save your changes by clicking on "Save". DOSBox will save the mapping to a location specified in the configuration file (the mapperfile= entry). At startup, DOSBox will load your mapperfile, if it is present in the DOSBox configuration file.

Mapper

2010-10-27T03:40:52Z

Ykhwong:

== Mapper ==

When you start the mapper (either with CTRL-F1 or -startmapper as a commandline argument to the DOSBox executable) you are presented with a virtual keyboard and a virtual joystick. These virtual devices correspond to the keys and events DOSBox will report to the DOS applications. If you click on a button with your mouse, you can see in the lower left corner with which event it is associated (EVENT) and to what events it is currently bound.

* EVENT: The key or joystick axis/button/hat DOSBox will report to DOS applications. (the event that will happen during the game, (eg. shooting/jumping/walking)
* BIND: The key on your real keyboard or the axis/button/hat on your real joystick(s) (as reported by SDL), which is connected to the EVENT.
* mod1,2,3: Modifiers. These are keys you need to have to be pressed while pressing BIND. mod1 = CTRL and mod2 = ALT. These are generally only used when you want to change the special keys of DOSBox.
* Add: Add a new BIND to this EVENT. Basically add a key from your keyboard or an event from the joystick (button press, axis/hat movement) which will produce the EVENT in DOSBox.
* Del: Delete the BIND to this EVENT. If an EVENT has no BINDS, then it is not possible to trigger this event in DOSBox (that is there's no way to type the key or use the respective action of the joystick).
* Next: Go through the list of bindings which map to this EVENT.

== Examples ==

Q1. You want to have the X on your keyboard to type a Z in DOSBox.
: A. Click on the Z on the keyboard mapper. Click "Add". Now press the X key on your keyboard.

Q2. If you click "Next" a couple of times, you will notice that the Z on your keyboard also produces an Z in DOSBox.
: A. Therefore select the Z again, and click "Next" until you have the Z on your keyboard. Now click "Del".

Q3. If you try it out in DOSBox, you will notice that pressing X makes ZX appear.
: A. The X on your keyboard is still mapped to the X as well! Click on the X in the keyboard mapper and search with "Next" until you find the mapped key X. Click "Del".

Examples about remapping the joystick:
:You have a joystick attached, it is working fine under DOSBox and you want to play some keyboard-only game with the joystick (it is assumed that the game is controlled by the arrows on the keyboard):
# Start the mapper, then click on one of the left keyboard arrow. EVENT should be key_left. Now click on Add and move your joystick in the respective direction, this should add an event to the BIND.
# Repeat the above for the missing three directions, additionally the buttons of the joystick can be remapped as well (fire/jump).
# Click on Save, then on Exit and test it with some game.

You want to swap the y-axis of the joystick because some flightsim uses the up/down joystick movement in a way you don't like, and it is not configurable in the game itself:
# Start the mapper and click on Y- in the first joystick field. EVENT should be jaxis_0_1-.
# Click on Del to remove the current binding, then click Add and move your joystick downwards. A new bind should be created.
# Repeat this for Y+, save the layout and finally test it with some game.

If you want to remap anything to your d-pad/hat you will have to change <code>joysticktype=auto</code> to <code>joysticktype=fcs</code> in configuration file. Maybe this will be improved in the next dosbox version.

----

If you change the default mapping, you can save your changes by clicking on "Save". DOSBox will save the mapping to a location specified in the configuration file (the mapperfile= entry). At startup, DOSBox will load your mapperfile, if it is present in the DOSBox configuration file.

Mapper

2010-10-27T03:40:16Z

Ykhwong:

== Mapper ==

When you start the mapper (either with CTRL-F1 or -startmapper as a commandline argument to the DOSBox executable) you are presented with a virtual keyboard and a virtual joystick. These virtual devices correspond to the keys and events DOSBox will report to the DOS applications. If you click on a button with your mouse, you can see in the lower left corner with which event it is associated (EVENT) and to what events it is currently bound.

* EVENT: The key or joystick axis/button/hat DOSBox will report to DOS applications. (the event that will happen during the game, (eg. shooting/jumping/walking)
* BIND: The key on your real keyboard or the axis/button/hat on your real joystick(s) (as reported by SDL), which is connected to the EVENT.
* mod1,2,3: Modifiers. These are keys you need to have to be pressed while pressing BIND. mod1 = CTRL and mod2 = ALT. These are generally only used when you want to change the special keys of DOSBox.
* Add: Add a new BIND to this EVENT. Basically add a key from your keyboard or an event from the joystick (button press, axis/hat movement) which will produce the EVENT in DOSBox.
* Del: Delete the BIND to this EVENT. If an EVENT has no BINDS, then it is not possible to trigger this event in DOSBox (that is there's no way to type the key or use the respective action of the joystick).
* Next: Go through the list of bindings which map to this EVENT.

== Examples ==

Q1. You want to have the X on your keyboard to type a Z in DOSBox.
: A. Click on the Z on the keyboard mapper. Click "Add". Now press the X key on your keyboard.

Q2. If you click "Next" a couple of times, you will notice that the Z on your keyboard also produces an Z in DOSBox.
: A. Therefore select the Z again, and click "Next" until you have the Z on your keyboard. Now click "Del".

Q3. If you try it out in DOSBox, you will notice that pressing X makes ZX appear.
: A. The X on your keyboard is still mapped to the X as well! Click on the X in the keyboard mapper and search with "Next" until you find the mapped key X. Click "Del".

Examples about remapping the joystick:
:You have a joystick attached, it is working fine under DOSBox and you want to play some keyboard-only game with the joystick (it is assumed that the game is controlled by the arrows on the keyboard):
# Start the mapper, then click on one of the left keyboard arrow. EVENT should be key_left. Now click on Add and move your joystick in the respective direction, this should add an event to the BIND.
# Repeat the above for the missing three directions, additionally the buttons of the joystick can be remapped as well (fire/jump).
# Click on Save, then on Exit and test it with some game.

You want to swap the y-axis of the joystick because some flightsim uses the up/down joystick movement in a way you don't like, and it is not configurable in the game itself:
# Start the mapper and click on Y- in the first joystick field. EVENT should be jaxis_0_1-.
# Click on Del to remove the current binding, then click Add and move your joystick downwards. A new bind should be created.
# Repeat this for Y+, save the layout and finally test it with some game.

If you want to remap anything to your d-pad/hat you will have to change <t>joysticktype=auto</t> to <t>joysticktype=fcs</t> in configuration file. Maybe this will be improved in the next dosbox version.

----

If you change the default mapping, you can save your changes by clicking on "Save". DOSBox will save the mapping to a location specified in the configuration file (the mapperfile= entry). At startup, DOSBox will load your mapperfile, if it is present in the DOSBox configuration file.

Keymapper

2010-10-27T03:38:42Z

Ykhwong: moved Keymapper to Mapper

#REDIRECT [[Mapper]]

Mapper

2010-10-27T03:38:42Z

Ykhwong: moved Keymapper to Mapper

Mapper

2010-10-27T03:38:28Z

Ykhwong:

Configuration:DOSBox

2010-10-26T18:45:18Z

Ykhwong:

The '''[dosbox]''' section contains various settings that do not pertain to any other section (e.g. setting the language used in DOSBox help texts, where to store screen captures, etc.)

;language = path-to-language-file
:Select another [[Language File|language file]].
:The default value empty ''(language= )''.
:(since 0.??)

;memsize = nn
:Amount of high memory (in megabytes) available to programs.
:Note: DOSBox always allocates 1 MB of low memory, so the total amount of memory equals 1 MB of low memory, plus whatever is allocated for high memory.
:The default value is 16 ''(memsize=16)''.
:(since 0.??)

;machine = hercules | cga | tandy | cga | tandy | pcjr | ega | vgaonly | svga_s3 | svga_et3000 | svga_et4000 | svga_paradise | vesa_nolfb | vesa_oldvbe
:(since 0.73)
:(previously '''machine = hercules | cga | tandy | vga''')
:The type of machine (specifically the type of graphics hardware) DOSBox tries to emulate.
:The default value is svga_s3 ''(machine=svga_s3)'' (was previously vga)
:Definitions are as follows:
:: vgaonly (previously vga) is ''VGA (Video Graphics Array)'': IBM's graphics system introduced with the PS/2. True VGA supports 16 colors at 640x480 resolution, or 256 colors at 320x200 resolution (and not 256 colors at 640x480, even though many people think it does). VGA colors are chosen from a palette of 262,144 colors (not 16.7 million) because VGA uses 6 bits to specify each color, instead of the 8 that is the standard today. (info taken from http://www.pcguide.com/ref/video/stdVGA-c.html. See also [[wikipedia:Video Graphics Array]] and http://members.chello.at/theodor.lauppert/games/vga.htm)
:: 
::''Tandy'': Refers to the additional graphics modes available on a Tandy 1000 or PCjr, which included 160x100x16, 160x200x16, 320x200x16, and 640x200x4. The Tandy RL/SL/TL series also added a 640x200x16 mode. (info taken from http://www.mobygames.com/attribute/sheet/attributeId,31/)
:: 
::''CGA (Color Graphics Adapter)'': Refers to IBM's first color graphics card. The CGA supports several different modes; the highest quality text mode is 80x25 characters in 16 colors. Graphics modes range from monochrome at 640x200 (which is worse than the Hercules card) to 16 colors at 160x200. However, for gaming, by far the most common mode was 4 colors at 320×200 pixels. These four colors, however, could not be freely chosen from the 16 CGA colors ? there were only two official palettes for this mode:
::*Magenta, cyan, white and background color (black by default). (much more common for gaming)
::*Red, green, brown and background color (black by default). (Can sometimes be selected as an alternate on some games).
::Note that VGA fully supports most CGA modes, so you should be able to leave DosBox in VGA mode and play most CGA games.
::(info taken from [[wikipedia:Color Graphics Adapter]], http://www.pcguide.com/ref/video/stdCGA-c.html, and http://members.chello.at/theodor.lauppert/games/cga.htm)
:: 
::''Hercules'': Refers to a graphics card developed by Hercules Computer Technology as a competitor to CGA for monochrome monitors. Hercules systems generate both high-resolution text and graphics. The resolution is 720 by 348 and only a single color is supported. (info taken from http://www.webopedia.com/TERM/H/Hercules_graphics.html and [[wikipedia:Hercules Graphics Card]])
:(since 0.??)

;captures = path-to-capture-directory
:Directory where things like music (wave and MIDI) and screenshots are captured when special keys CTRL-F5 and CTRL-F6 are used. Screenshots will be captured and saved as (PNG) files with a resolution of 320x200.
:Note: <s>The capture directory will not be created automatically - you must create it before you start capturing music and screenshoots, otherwise nothing will be saved.</s> As of v0.73 (possibly prior) it is created automatically on first use.
:The default value is capture ''(captures=capture)''.
:(since 0.62).

System Requirements

2010-10-26T18:38:44Z

Ykhwong:

Only requirement is a port of [http://www.libsdl.org libsdl] for your system. DOSBox should compile on every system with a decent C++ compiler like GCC.
----

The system requirements for smooth gaming vary depending on the system requirements for the original game, the desired gameplay experience, and the hardware being emulated.

Protected mode games are very resource-demanding. Although they will likely run on a 1 GHz machine, it is unlikely they will run quickly or smoothly. Be sure to read the sections on [[SpecialKeys|special function keys]] used by DOSBox, and how to run [[RunningResourceDemandingGames|resource demanding games]].

=== Rough CPU Equivalency Chart ===
{| border="1" cellspacing="0" style="text-align:center"
! Host Architecture!!Host CPU Speed!!Emulated CPU Class (dynamic core)!!Comments
|-
||x86 (Pentium II)||400 MHz||386||
|-
||x86 (Duron)||800 MHz||486||
|-
||x86 (Pentium III)||1.0 GHz||high-end 486||
|-
||x86 (Pentium M)||1.8 GHz||Pentium II||
|-
||x86 (Athlon XP)||1.8 GHz||Pentium II||
|-
||x86 (Athlon 64)||1.8 GHz||Pentium III||
|-
||x86 (Core 2 Duo)||(any speed)||Pentium III||
|-
||Apple G3||500 MHz||3/486-class||Games tested: Leisure Suit Larry 6, Fuzzy's World of Miniature Space Golf. Extrapolated from ~50% CPU usage on a 1GHz G4.
|-
||Apple G4||1.0 GHz||486-class||Performance adequate for most DOS games. SVGA likely to be too much.
|}

== See also ==
* [[Performance]]

Language File

2010-10-26T18:37:29Z

Ykhwong:

== How to create ==
A language file can be generated by [[CONFIG|CONFIG.COM]], which can be found on the internal DOSBox [[ZDrive|Z: drive]] when you start up DOSBox.

CONFIG -writelang filelocation

It writes the current language settings to a file in a specified location. "filelocation" is located on the local drive, not a mounted drive in DOSBox. The language file controls all visible output of the internal commands and the internal DOS.

== How to change ==
Read the language file that you created from the instruction above, and you will hopefully understand how to change it.

== How to use in DOSBox ==
You can setup the filename in the configuration file ([[Dosbox.conf|DOSBox.Conf]]) in the [dosbox] section. There's a language= entry that can be changed with the filelocation.

Alternatively, start DOSBox with the -lang switch to use your new language file.

== See also ==
* [http://www.dosbox.com/download.php?main=1 Language translations]

DOSBox FAQ

2010-10-26T18:34:08Z

Ykhwong: /* Performance */

Performance

2010-10-26T18:32:53Z

Ykhwong: borrowed from README

* See also [[System Requirements]].
* See also [[FAQ#Performance|Performance]]. (FAQ)

DOSBox emulates the CPU, the sound and graphic cards, and other peripherals of a PC, all at the same time. The speed of an emulated DOS application depends on how many instructions can be emulated, which is adjustable (number of cycles).

== How to speed up/slow down DOSBox ==
=== CPU Cycles (speed up/slow down) ===
By default (cycles=auto) DOSBox tries to detect whether a game needs to be run with as many instructions emulated per time interval as possible (cycles=max, sometimes this results in game working too fast or unstable), or whether to use fixed amount of cycles (cycles=3000, sometimes this results in game working too slow or too fast). But you can always manually force a different setting in the DOSBox's configuration file.

You can force the slow or fast behavior by setting a fixed amount of cycles in the DOSBox's configuration file. If you for example set cycles=10000, then DOSBox window will display a line "Cpu Speed: fixed 10000 cycles" at the top. In this mode you can reduce the amount of cycles even more by hitting CTRL-F11 (you can go as low as you want) or raise it by hitting CTRL-F12 as much as you want, but you will be limited by the power of one core of your computer's CPU.

You can see how much free time your real CPU's cores have by looking at the Task Manager in Windows 2000/XP/Vista/7 and the System Monitor in Windows 95/98/ME. Once 100% of the power of your computer's real CPU's one core is used, there is no further way to speed up DOSBox (it will actually start to slow down), unless you reduce the load generated by the non-CPU parts of DOSBox. DOSBox can use only one core of your CPU, so If you have for example a CPU with 4 cores, DOSBox will not be able to use the power of three other cores.

You can also force the fast behavior by setting cycles=max in the DOSBox configuration file. The DOSBox window will display a line "Cpu Speed: max 100% cycles" at the top then. This time you won't have to care how much free time your real CPU's cores have, because DOSBox will always use 100% of your real CPU's one core. In this mode you can reduce the amount of your real CPU's core usage by CTRL-F11 or raise it with CTRL-F12.

=== CPU Core (speed up) ===
On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails.

It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more). Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!

=== Graphics emulation (speed up) ===
VGA emulation is a demanding part of DOSBox in terms of actual CPU usage. Increase the number of frames skipped (in increments of one) by pressing CTRL-F8. Your CPU usage should decrease when using a fixed cycle setting, and you will be able to increase cycles with CTRL-F12. You can repeat this until the game runs fast enough for you. Please note that this is a trade-off: you lose in fluidity of video what you gain in speed.

=== Sound emulation (speed up) ===
You can also try to disable the sound through the setup utility of the game to reduce load on your CPU further. Setting nosound=true in DOSBox's configuration does NOT disable the emulation of sound devices, just the output of sound will be disabled.

Also try to close every program but DOSBox to reserve as much resources as possible for DOSBox.

=== Advanced cycles configuration ===
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

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

Usage

2010-10-26T18:26:01Z

Ykhwong:

Releases:Current

2010-10-26T18:19:59Z

Ykhwong: Redirected page to Version0.74

#REDIRECT [[Version0.74]]

Version0.74

2010-10-26T18:19:32Z

Ykhwong: Created page with '= This is the current release = (previous release) == Changes == * Several small game specific fixes/hacks/support. (Offensive, Roadhog, GTA instal…'

= This is the current [[Releases|release]] =
([[Version0.73|previous release]])

== Changes ==

* Several small game specific fixes/hacks/support. (Offensive, Roadhog, GTA installer, Kingdom O' Magic soundcard detection, Pirate booter, Armored Fist installer)
* Add the S3-specific 640x480 256 color mode. (fixes regression in "Wooden Ships and Iron Men" and "I Have No Mouth And I Must Scream")
* Fix a stack overflow that could crash DOSBox.
* Add fake microphone input. (fixes Talking Parrot)
* Modify adlib turn off code, so that it doesn't turn off in cases where the same sound is repeated over and over again.
* Several small fixes to the CDROM audio code.(HOMM2, Redneck Rampage and others)
* Several improvements to the CDROM emulation code. (fixes Alpha Storm and GT Racing 97)
* Some small CPU fixes that might fix something.
* Handle opcode 0xff subcode 7 as invalid instruction. (fixes dif-2 & others)
* Some hercules fixes. (Testdrive)
* Improve support for blanked parts that wrap around to the start of the screen. (fixes Magic Circle demo and Sid&Al)
* Remove old OPL cores as the new ones seem to work very nicely.
* Modify movie recording code so that the movies aren't corrupt when you exit dosbox without stopping the movie.
* Change RGB3x scaler to look more pretty.
* Improve initial register values compatility of the GUS.
* Added autodetection for Gameblaster. (games can find it now)
* Change render preferences a bit to be more compatible with Windows 7.
* Add DOS fixes to terminate program. (fixes Fortune Teller)
* Add FFREEP. (fixes Trucks)
* Improve FPU ST80 in C mode when writing zero. (fixes Antigok)
* Add special int10 scanline function. (fixes mz700 and probably lots of games that mess with them)
* Fix scrolling in rarely used video modes. (fixes Orphee)
* Modify game specific hacks a bit so that Kick off 3 works again.
* Lots of fixes to the INT10 video parameter table. (Seven spirits of ra and others)
* Add VGA blanking in machine=vgaonly. (used by Alien Carnage)
* CGA, PCJr, Tandy: Add video blanking, change display start latch timing, sync pulse width correction.
* PCJr, Tandy: implement vertical retrace interrupt.
* PCJr, CGA: line-by-line video emulation.
* PCJr: support on-screen change of color modes 4medium to 16low. (used by Ghostbusters booter)
* Hercules: Add green and amber monochrome support.
* All machines: only update the video timing when needed. (Jungle Hunt, others that synchronize to the video screen might profit)
* Several small DOS fixes.
* Some UMB related fixes. (The Legacy without UMB)
* Fix version number of DSP for SB 1.5. (fixes a few games)
* Several VGA emulation improvements. (Allertone football manager)
* Some Tandy fixes. (Mech Warrior)
* Small improvements and fixes to the OPL emulation.
* Add low level Tandy DAC emulation.
* Some EMS fixes. (fixes Mortal Kombat and others)
* Change SoundBlaster DSP reset mechanism, add sb irq acknowledge logic. (fixes stmik-based applications)
* Some interrupt pointer location modifications. (fixes Tinker Tales)
* Some fixes to the BOOT code. (fixes Last Mission)
* Respect write-only file information. (fixes Champions of Zulala)
* Some RTC fix. (fixes Tully Bodine and others)
* Improve mouse emulation to work better with Water World.
* Hopefully fix the translation of the configuration file.
* Speed up and fixes for the recompiler core. (pitfall2 pcjr)
* Change memory start location. (fixes 7th Guest installer)
* Several fixes to the batch file handling. (Shift and use the typed first %0 instead of the parsed %0)
* Improve file redirection and redirected line ends. (fixes Phantasmagoria 2 DOS installer)
* Fix compilation with new MAC os X version.
* Add 16C550A FIFO support to the serial port emulation.
* Improve modem emulation to get higher speeds.
* Change default samplerates to 44100, blocksize to 1024 and prebuffer to 20, so that hopefully certain soundcards produce more fluent sound playback.
* Add some rarely used, but for some games critical flags to the internal commands.
* Add -userconf flag, so that the userspecific configuration can easily be used together with -conf configfile.
* Improve internal timing with repeating timers (especially with the dynamic core).

Version0.73

2010-10-26T18:17:42Z

Ykhwong:

= This isn't the [[Releases:Current|current]] [[Releases|release]] =
([[Version0.72|previous release]]) | ([[Version0.74|next release]])
== Changes ==
* Support for more graphics modes and cards.
* Improved Vista support.
* New OPL emulation cores.
* Sound fixes and improvements for Mac OS X.
* Lots of compatibility fixes.
* Lots of cdrom detection improvements.
* Lots of memory (EMS/XMS) improvements.
* Various fixes and enhancements for the recompiling core.
* Support for evdev.
* Lots of DOS fixes.
* Slightly faster!
* More stable.

ZDrive

2010-10-26T18:14:08Z

Ykhwong:

When DOSBox loads it automatically creates a Virtual Internal Drive called '''Z:''' which contains various [[Utilities|utilities]] that make a reasonable approximation of a fully setup DOS Compatible environment. This drive is automatically inserted to the front of the [[PATH]] and cannot be modified. This Z: Drive can be largely hidden with some creative modifications to the [[AUTOEXEC|AUTOEXEC.BAT]] for a more complete emulation of MS-DOS.

You can find the following files in Z: drive.
* COMMAND.COM
* AUTOEXEC.BAT
* INTRO.COM
* [[KEYB|KEYB.COM]]
* [[IMGMOUNT|IMGMOUNT.COM]]
* [[BOOT|BOOT.COM]]
* [[RESCAN|RESCAN.COM]]
* [[LOADFIX|LOADFIX.COM]]
* [[MEM|MEM.COM]]
* [[MOUNT|MOUNT.COM]]
* [[MIXER|MIXER.COM]]
* [[CONFIG|CONFIG.COM]]

Language File

2010-10-26T18:01:39Z

Ykhwong:

== How to create ==
A language file can be generated by CONFIG.COM, which can be found on the internal DOSBox Z: drive when you start up DOSBox.

CONFIG -writelang filelocation

It writes the current language settings to a file in a specified location. "filelocation" is located on the local drive, not a mounted drive in DOSBox. The language file controls all visible output of the internal commands and the internal DOS.

== How to change ==
Read the language file that you created from the instruction above, and you will hopefully understand how to change it.

== How to use in DOSBox ==
You can setup the filename in the configuration file (DOSBox.Conf) in the [dosbox] section. There's a language= entry that can be changed with the filelocation.

Alternatively, start DOSBox with the -lang switch to use your new language file.

== See also ==
* [http://www.dosbox.com/download.php?main=1 Language translations]

IMGMOUNT

2010-10-26T17:57:54Z

Ykhwong: /* Loading a CUE image */

A utility to mount hard disk and optical disc images in DOSBox.

'''Note:''' You can use [[TOOLS:Disk Explorer|Disk Explorer]] to '''copy''' files and folders to/from images (but not to '''delete''' them or DOSBox will consider the images corrupted! Read the aforementioned link for more info).

==Command line parameters==

<code>IMGMOUNT DRIVE [imagefile] -t [image_type] -fs [image_format] 
[[#The "-size" parameter (required to to create bootable hard disk images)|-size]] [sectorsbytesize, sectorsperhead, heads, cylinders -u DRIVE]</code>

;DRIVE: Drive name (letter) the image will use
*a for the drive letter a:\ or
*b for the drive letter b:\ etc...

;imagefile: Location of the image files to mount in DOSBox. The location can be on a mounted drive inside DOSBox, or on your real disk. It is possible to mount multiple (e.g. <code>"~/images/CD1.cue ~/images/CD2.cue [...] ~images/CDn.cue"</code>) optical disc images (ISOs or CUE/BIN) as well, if you need CD swapping capabilities specify all images in succession. The CDs can be swapped with CTRL-F4 at any time.

;-t: The following are valid image types:
:;floppy: Specifies a floppy image or images. DOSBox will automatically identify the disk geometry (360K, 1.2MB, 720K, 1.44MB, etc).
:;iso: Specifies an optical disc iso image. The geometry is automatic and set for this size. This can be an iso or a cue/bin.
:;hdd: Specifies a hard disk image. The proper CHS geometry must be set for this to work.

;-fs: The following are valid file system formats:
:;iso: Specifies the ISO 9660 optical disc format.
:;fat: Specifies that the image uses the FAT file system. DOSBox will attempt to mount this image as a drive in DOSBox and make the files available from inside DOSBox.
:;none: DOSBox will make no attempt to read the file system on the disk. This is useful if you need to format it or if you want to boot the disk using the BOOT command. When using the "none" filesystem, you must specify the drive number (2 or 3, where 2=master, 3=slave) rather than a drive letter. For example, to mount a 70MB image as the slave drive device, you would type: <code>"imgmount 3 d:\test.img -size 512,63,16,142 -fs none"</code> (without the quotes). Compare this with a mount to read the drive in DOSBox, which would read as: <code>"imgmount e: d:\test.img -size 512,63,16,142"</code>.

;[[#The "-size" parameter (required to to create bootable hard disk images)|-size]]: The Cylinders, Heads and Sectors specification of the drive. '''Only''' required to to create [[#Bootable hard disk images|bootable hard disk images]]. This means it is '''not''' required for either [[#Loading a regular hard disk image|loading a regular hard disk image]] or [[#optical disc images|optical disc images]].

;-u: unmount an image.
*e.g. if an disk image was mounted to be the disk drive a:\ type:
*<code>"imgmount -u a"</code>

==Optical disc images==
===Loading an ISO image===
====An example in Windows====
<pre>
Z:>mount c "c:\images"
Z:>imgmount d "C:\MyISO.iso" -t iso
Z:>d:
D:>
</pre>

====Other example in Windows (more than one image)====

<pre>
Z:>mount c "c:\images"
Z:>imgmount d c:\mr2_cd1.iso c:\mr2_cd2.iso -t iso
Z:>d:
D:>
</pre>

====An example in Unix====
<pre>
Z:>mount c "/tmp"
Z:>imgmount d "/tmp/MyISO.iso" -t iso
Z:>d:
D:>
</pre>

====Loading more than one image====

It is possible to mount more than one image, and then switch between them using ctrl-f4
Example in Linux:
<pre>
IMGMOUNT.COM d c:\disk1.iso c:\disk2.iso ... -t cdrom
</pre>

===Loading a CUE image===
====An example in Windows====
<pre>
Z:>mount c "c:\images"
Z:>imgmount d "C:\cdimg.cue" -t iso -fs iso
Z:>d:
D:>
</pre>

====An example in Unix====
<pre>
Z:>mount c "/tmp"
Z:>imgmount d "/tmp/cdimg.cue" -t iso -fs iso
Z:>d:
D:>
</pre>

====Note: make sure to use CUE and not BIN for Mixed Mode CDs====
You can mount bin/cue type CD images with the IMGMOUNT command, and it will 'sort of' work if you specify the .bin file as the file to mount. However, it will not mount the audio tracks of the CD correctly if you do this. Specifying the associated .cue file will load all tracks correctly.
====Note: you can mount CUE with an ISO for Mixed Mode CDs====
It is also possible to use a cuescheet in combination with an ISO and [[Cuesheet|compressed audio tracks]] in OGG or MP3 format.

==Hard disk images==
===The "-size" parameter (required to to create [[#Bootable hard disk images|bootable hard disk images]])===
Didn't understand the "512,63,16,142" part?

All you really need to know is that the formula is always:
<pre>-size 512,63,16,X</pre>
'''X''' is the number of "cylinders" in the image. It's based on the image's size. If you create the image through '''Bochs''', then it would tell you the number of cylinders.

If you want to understand a little more, here's a more detailed explanation than the official one on the numbers.

Now, let's say you created a 70M image using the bximage program from '''Bochs'''. You will then get the following details:

<pre>
I:> bximage.exe
========================================================================
bximage
Disk Image Creation Tool for Bochs
$Id: bximage.c,v 1.32 2006/06/16 07:29:33 vruppert Exp $
========================================================================

Do you want to create a floppy disk image or a hard disk image?
Please type hd or fd. [hd]

What kind of image should I create?
Please type flat, sparse or growing. [flat]

Enter the hard disk size in megabytes, between 1 and 129023
[10] 70

I will create a 'flat' hard disk image with
cyl=142
heads=16
sectors per track=63
total sectors=143136
total size=69.89 megabytes

What should I name the image?
[c.img] 70mb.img

Writing: [] Done.

I wrote 73285632 bytes to 70mb.img.
</pre>

You don't actually need to know the total numbers of sectors, other than to calculate the sector size (in bytes):

<pre>
bytes-per-sectors = total-file-size-in-bytes / total-sectors
bytes_per_sectors = 73285632 / 143136
bytes_per_sectors = 512
</pre>
Now you have all you need.

Start the line with 512 and then add the 3 first parts in reverse order. In other words:

<code>imgmount ...... -size 512,63,16,142</code>
* Here's a tip: the first 3 numbers should always be the same. So all you really need is the cyl=X. In other words, it should always be:

<code>imgmount ...... -size 512,63,16,'''X'''</code>
* Only the X changes, according to the size you specify when you create the image.

That wasn't so hard, was it? ;-)

===Loading a regular hard disk image===
====Example====
<pre>
Z:>mount d c:\images
Z:>d:
D:>imgmount c "70mb.img"
</pre>

===Bootable hard disk images===
=====Format the partition with "format"=====
Start DOSBox again and type:
<pre>
Z:>mount d c:\images
Z:>d:
D:>imgmount 2 "70mb.img" -size 512,63,16,142 -t hdd -fs none
D:>boot "msdos622.img"
(Opening and booting from image file: msdos622.img)

...

A:\>format c: /s
</pre>
Exit DOSBox.

The hard disk image is now bootable! See [[#Loading a bootable hard disk image|Loading a bootable hard disk image]].

====Loading a bootable hard disk image====
From now on, whenever you want to boot from drive C:, start DOSBox and type, for example:
<pre>
Z:>mount d c:\images
Z:>d:
D:>imgmount c "70mb.img"
D:>boot -l c
(Opening and directly booting from image file: 70mb.img)
C:>
</pre>

Language File

2010-10-26T17:50:34Z

Ykhwong:

Mapper

2010-10-26T17:43:20Z

Ykhwong: also for a joystick

== KeyMapper ==

When you start the keymapper (either with CTRL-F1 or -startmapper as a commandline argument to the DOSBox executable) you are presented with a virtual keyboard and a virtual joystick. These virtual devices correspond to the keys and events DOSBox will report to the DOS applications. If you click on a button with your mouse, you can see in the lower left corner with which event it is associated (EVENT) and to what events it is currently bound.

* EVENT: The key DOSBox will report to the applications being emulated.
* BIND: The key on your keyboard (as reported by SDL) which is connected to the EVENT.
* mod1,2,3: Modifiers. These are keys you need to have pressed as well, while pressing BIND. mod1 = CTRL and mod2 = ALT. These are generally only used when you want to change the special keys of DOSBox.
* Add: Add a new BIND to this EVENT. Basicly add a key from your keyboard which will produce the key EVENT in DOSBox.
* Del: Delete the BIND to this EVENT. If an EVENT has no BINDS than it's not possible to type this key in DOSBox.
* Next: Cycle through the list of keys(BINDS) which map to this EVENT.

== Examples ==

Q1. You want to have the X on your keyboard to type a Z in DOSBox.
A. With your mouse click on the Z on the keyboard mapper. Click "Add". Now press the X key
on your keyboard.

Q2. If you click "Next" a few times you will notice that the Z on your keyboard also produces a Z in DOSBox.
A. Therefore select the Z again and click "Next" till you have the Z on your keyboard. Now
click "Del".

Q3. If you try it out in DOSBox you will notice that pressing X makes ZX appear.
A. The X on your keyboard is still mapped to the X as well! Click on the X in the keyboard
mapper and search with "Next" till you find the mapped key X. Click "Del".

----

If you change the default mapping you can save your changes by pressing "Save". DOSBox will save the mapping to location specified in the configfile (mapperfile=mapper.txt). At startup DOSBox will load your mapperfile if it's present in the configfile.

DOSBox and Windows Vista and Windows 7

2010-10-26T17:37:34Z

Ykhwong: 0.73 -> 0.74

=== Does it work ? ===
Yes, DOSBox works in both Vista 32 bit and Vista 64 bit. DOSBox also works on Windows 7 32bit and 64bit.

=== CD-ROM support ===

This is currently still in development. 95% of the functions work in 0.74, but if it doesn't work then the best thing you can do is to make an image of your CD-ROM and [[IMGMOUNT]] that.

Releases

2010-10-26T17:34:22Z

Ykhwong:

DOSBox is designed to be cross platform, but variation between each platform make porting all of the code at the same time extremely difficult. Here is a list of the supported platforms and their status.
{{:Releases:All}}

Releases:All

2010-10-26T17:29:55Z

Ykhwong:

:''See also: [[SVN Builds|DOSBox SVN Builds]]''
{| style="font-size: 90%; text-align: left;" cellpadding="3"
|-
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Platform
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Version
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Link
|-
| Microsoft Windows
| [[Version0.74|0.74]]
| [http://sourceforge.net/projects/dosbox/files/dosbox/0.74/DOSBox0.74-win32-installer.exe/download download]
|-
| FreeBSD
| [[Version0.74|0.74]]
| [ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-stable/All/dosbox-0.74.tbz download]
|-
| Fedora Core (Linux)
| [[Version0.74|0.74]]
| [https://admin.fedoraproject.org/pkgdb/applications/Dosbox download]
|-
| Gentoo (Linux)
| [[Version0.74|0.74]]
| [http://packages.gentoo.org/ download]
|-
| Mac OSX
| [[Version0.74|0.74]]
| [http://sourceforge.net/projects/dosbox/files/dosbox/0.74/DOSBox-0.74_Universal.dmg/download download]
|-
| OS/2
| [[Version0.72|0.72]]
| [http://www.joschs-robotics.de/dosbox/ download]
|-
| BeOS
| [[Version0.63|0.63]]
| [http://www.bebits.com/app/3007 download]
|-
| RiscOS
| [[Version0.63|0.63]]
| [http://www.riscos.info/unix/indexes/emulation.html download]
|-
!colspan="3" style="text-align:center;"|Non compiled
|-
| Source Code
| [[Version0.74|0.74]]
| [http://sourceforge.net/projects/dosbox/files/dosbox/0.74/dosbox-0.74.tar.gz/download download]
|-
!colspan="3" style="text-align:center;"|Derivative projects (unsupported)
|-
| WM/PPC 2003
| [[Version0.61|0.61]], [[Version0.63|0.63]]
| [http://n0p.tonych.info/?DOSBox_PPC n0p's DosBox for Pocket PC ]
|-
| WM/PPC 2003
| [[Version0.60|0.60]], [[Version0.63|0.63]]
| [http://pocketdosbox.sourceforge.net/ PocketDosBox]
|-
| WM/PPC 200?
| ???
| [http://pckdos.sourceforge.net/ pckDos]
|}

Releases:All

2010-10-26T17:29:47Z

Ykhwong: updated for 0.74

:''See also: [[SVN Builds|DOSBox SVN Builds]''
{| style="font-size: 90%; text-align: left;" cellpadding="3"
|-
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Platform
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Version
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Link
|-
| Microsoft Windows
| [[Version0.74|0.74]]
| [http://sourceforge.net/projects/dosbox/files/dosbox/0.74/DOSBox0.74-win32-installer.exe/download download]
|-
| FreeBSD
| [[Version0.74|0.74]]
| [ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-stable/All/dosbox-0.74.tbz download]
|-
| Fedora Core (Linux)
| [[Version0.74|0.74]]
| [https://admin.fedoraproject.org/pkgdb/applications/Dosbox download]
|-
| Gentoo (Linux)
| [[Version0.74|0.74]]
| [http://packages.gentoo.org/ download]
|-
| Mac OSX
| [[Version0.74|0.74]]
| [http://sourceforge.net/projects/dosbox/files/dosbox/0.74/DOSBox-0.74_Universal.dmg/download download]
|-
| OS/2
| [[Version0.72|0.72]]
| [http://www.joschs-robotics.de/dosbox/ download]
|-
| BeOS
| [[Version0.63|0.63]]
| [http://www.bebits.com/app/3007 download]
|-
| RiscOS
| [[Version0.63|0.63]]
| [http://www.riscos.info/unix/indexes/emulation.html download]
|-
!colspan="3" style="text-align:center;"|Non compiled
|-
| Source Code
| [[Version0.74|0.74]]
| [http://sourceforge.net/projects/dosbox/files/dosbox/0.74/dosbox-0.74.tar.gz/download download]
|-
!colspan="3" style="text-align:center;"|Derivative projects (unsupported)
|-
| WM/PPC 2003
| [[Version0.61|0.61]], [[Version0.63|0.63]]
| [http://n0p.tonych.info/?DOSBox_PPC n0p's DosBox for Pocket PC ]
|-
| WM/PPC 2003
| [[Version0.60|0.60]], [[Version0.63|0.63]]
| [http://pocketdosbox.sourceforge.net/ PocketDosBox]
|-
| WM/PPC 200?
| ???
| [http://pckdos.sourceforge.net/ pckDos]
|}

SVN Builds

2010-10-26T11:36:24Z

Ykhwong:

This article is a discussion of the general purpose of DOSBox SVN builds, and a list of which known public ones exist and where to get them. The first part is a FAQ covering various questions regarding DOSBox SVN builds; it is followed by a listing, description of and links to known SVN builds, as well as a selection of useful related links.

==SVN Builds FAQ==

===What are SVN builds?===
SVN builds are versions of DOSBox that people have built from the latest version of the DOSBox source code, which is stored on [http://www.sourceforge.net/ sourceforge.net] in something called an SVN repository. SVN builds contain changes that have been made by the DOSBox developers since the latest official release. Some enhanced SVN builds also contain unofficial features and fixes that have been created by enthusiasts in the DOSBox development community.

===Why should I use an SVN build?===
Every so often a new official version of DOSBox is released. However, active development continues between releases, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. If you're having trouble running a game with the current DOSBox release, it's worth trying an SVN build to see if the problem has been addressed since then. You may also want access to the new features or optimizations if you are having compatibility or performance issues.

===Which one should I use?===
That's up to you. Consult the list below to see which features the different builds contain and decide which one you want to try first. If you are interested in trying an SVN build in hopes that it will fix a problem you're having in the latest release version, you should probably start with a "plain" (no-enhancements) SVN build. Also, see replies to this post from the maintainers for additional info on their builds.

===How do I use it?===
Some SVN builds come packaged as a fully-functional DOSBox distribution, so you can simply unpack the archive into an empty folder and run it. Other builds contain only a custom dosbox executable binary (e.g. dosbox.exe) and possibly some supporting libraries, and require that you first install the latest official release of DOSBox and then unpack the SVN build over the top of it - replacing the release versions of the files with the SVN versions. Some developers also recommend regenerating your dosbox.conf configuration file so that you will see any new config options that have been added. Consult [http://vogons.zetafleet.com/viewtopic.php?p=68701#68701 this forum thread] for info on how to regenerate a config file.

===What do I do if I find bugs in an SVN build?===
First, search the DOSBox community forums to see if it's already been reported. If it hasn't, post as much information as possible (see the [http://vogons.zetafleet.com/viewtopic.php?t=2949 help request guidelines]). ''Update:'' Note that bugs in plain SVN builds are probably the only ones of interest to the DOSBox developers. Problem reports for the other builds should be addressed to their respective maintainers, as problems could be caused by experimental patches that aren't part of the official SVN source code.

===Where can I go to talk about SVN builds? (forum thread)===
Please feel free to discuss SVN build-related topics in the [http://vogons.zetafleet.com/viewtopic.php?t=9306 forum thread] where this article originally started.

==List of SVN Builds==

===Plain/vanilla/clean SVN builds===
The following SVN builds are based directly off of the official DOSBox SVN source code. Use these builds to test the latest official SVN changes.

* '''EmuCR'''
** Last updated: April 12, 2010
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated a few times a week. Haven't tried these myself yet; thanks to NoVaTuRiEnT for pointing them out.

* '''Tharos (by XTale)'''
** Last updated: March 28, 2010
** URL: http://builds.tharos-online.de/index.php?dir=&sort=date&order=desc
** Notes: '''Daily builds seem to have stopped as of 3/28/10.'''

===Enhanced SVN builds===
The following SVN builds contain additional fixes and/or features that are not officially part of DOSBox. Many people prefer them due to the included extra features that are not included in in the SVN. Note that if you have problems with these builds, it may be due to the unofficial changes that have been made by their maintainers and not the official DOSBox code itself that is to blame.

* '''ykhwong'''
** Last updated: October 21, 2010
** URL: http://ykhwong.x-y.net/
** URL: http://cafe.daum.net/dosbox
** Description: The Windows build incorporates Direct3D with pixelshaders, OpenglHQ, Innovation, Glide, zip/7z mount, Beep, NE2000 Ethernet, Graphis user interface (menu), Save/Load states, Vertical sync, CPU flags optimization, Various DOS commands (PROMPT, VOL, LABEL, MOUSE, etc) and CONFIG.SYS commands (DEVICE, BUFFERS, FILES, etc), Continuous turbo key, Core-switch key, Show details (from menu bar), Nice DOSBox icon, Font patch (cp437), COPY CON feature, MAKEIMG command, INTRO, Ctrl-break patch, DBCS support patch, Automatic mount, Printer output, MT-32, MP3CUE, Overscan border, Stereo-swap, SDL_Resize, MemSize128, etc.
** OS: Windows, Linux

* '''DOSBox "Mega Build" series (by H-A-L-9000)'''
** Last updated: September 13, 2009
** URL: http://home.arcor.de/h-a-l-9000/
** Description: Builds of DOSBox focused on serial/networking support.

* '''gulikoza'''
** Last Updated: July 9, 2009
** URL: http://www.si-gamer.net/gulikoza/
** Description: Build of DOSBox focused on GLIDE support.

* '''Zirias'''
** Last Updated: May 12, 2010
** URL: http://vogons.zetafleet.com/viewtopic.php?p=186679#186679
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: July 23, 2010
** URL: http://vogons.zetafleet.com/viewtopic.php?p=193022#193022
** Description: All patches from gulikoza's build (coreswitch, direct3d, glide, mt32, openglhq, physfs, NE2000, printer and oplpassthrough). Updated Glide patch by gulikoza to 24.11.2009. SDL_sound support. Some other small fixes (mostly VS2010 compatibility fixes).

===Unofficial ports===
These builds are for other Operating Systems and are not in any way supported by the DOSBox team.

* '''DOSBox 0.72 for AmigaOS 4.0'''
** Last updated: June 14, 2009
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

* '''DOSBox for OS/2'''
** Last updated: September 17, 2010
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://www.os2site.com/sw/emulators/dosbox/index.html

* '''DOSBox v0.60 for Dreamcast'''
** Last Updated: ??? (release dates not currently provided on the linked web site)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

* '''DOSBox for GP2x'''
** Last updated: January 3, 2009
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** URL: http://wiki.gp2x.org/wiki/DosBox

* '''DOSBox for IRIX'''
** Last Updated: ??? (release dates not currently provided on the linked web site)
** URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** Notes: Link seems to now redirect to spam-filter.de. I added a link to a DOSBox on IRIX page on that site, but it doesn't appear to have a binary.

* '''DOSBox for PSP'''
** URL: http://forums.ps2dev.org/viewtopic.php?t=3179&start=60
** URL: http://www.dcemu.co.uk/vbulletin/showthread.php?t=65494

* '''DOSBox for Pocket PC (by n0p)'''
** Last updated: July 6, 2009
** URL: http://n0p.tonych.info/?DOSBox_PPC

* '''DOSBox 0.70 Optimized for PXA270 (iwmmxt)'''
** URL: http://www.oesf.org/forums/index.php?s=1dec7dd003587d385fbec45efb1ffbaa&showtopic=18415&st=270&p=156742&#entry156742

* '''pDOSBox for Pocket PC'''
** URL: http://www.e-lation.net/site/emufor_Pocket_PC.html

* '''aDOSBox 0.73 for Android OS'''
** URL: http://androiddosbox.appspot.com/

===Obsolete SVN/CVS builds===
These builds are no longer maintained and are listed here for historical reference.

* '''DOSBox CVS for Linux (by Moe)'''
** Last updated: December 15, 2006
** URL: http://garni.ch/dosbox/
** Description: Recently Moe has decided to provide a DOSBox Linux (x86, 32-bit, Athlon64-optimized) binary including some useful patches. It is built against latest CVS and includes at least these patches: addkey, adlib optimize, Innovation SSI-2001, Self-Modifying-Code optimizations, SVGA chipsets, CD-Image cycling, Glide emulation, Printer emulation.
** Notes: Moe is also the creator of OPENGL-HQ. OPENGL-HQ is another scaler that is implemented in SDL.dll. Unfortunately it may be some time (or never), until OPENGL-HQ is implemented in the official SDL so until then you'll have to download it from here (or compile it yourself). Neat thing about this is that you can use this SDL.DLL with any SDL program (e.g. DOSBox, SCUMMVM...).

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: August 9, 2008
** URL: http://www.spam-filter.de/bastelstunde#dosbox
** Description: DosBox 0.72 for G3 & DosBox CVS for OSX (G4/G5/i386)

* '''DOSBox with MT-32 emulation (by Canadacow)'''
** Last updated: October 15, 2004
** URL: http://www.artworxinn.com/alex/downloads.htm
** Description: ''This build is no longer useful''; it was made before DOSBox 0.63 came out and contains MT-32 emulation code that is much older than the current Munt releases. Note that more current MT-32 emulation is also included as an unofficial feature of some of the newer SVN builds.

==Useful Links==

===SVN changelog===
The following links list the latest changes to the official DOSBox source code on its sourceforge.net SVN repository:
* URL: http://source.dosbox.com/dosboxsvn.txt (auto-generated changelog provided by Qbix)
* URL: http://dosbox.svn.sourceforge.net/viewvc/dosbox/?view=log (auto-generated changelog created by sourceforge.net)
* URL: http://github.com/Henne/dosbox-svn/commits/master (auto-generated changelog of unofficial git clone of DOSBox SVN)
* URL: http://dosbox.linuxsecured.net/dosboxcvs.txt - '''broken link as of 10/25/10'''
* URL: http://cvscompile.aep-emu.de/cl/dosboxChangeLog.txt - '''broken link as of 10/25/10'''

===SVN build news===
The following link(s) provide news related to DOSBox SVN builds:
* URL: http://www.emucr.com/search/label/DOSBox (EmuCR posts with DOSBox tag, which includes news regarding DOSBox SVN builds, frontends and other DOSBox ports)

===Debugger-enabled builds===
Qbix has a thread on the DOSBox forum containing links to some special DOSBox builds that have a built-in debugger:
* URL: http://vogons.zetafleet.com/viewtopic.php?t=7323

===Making your own SVN build===
The following DOSBoxWiki article discusses the process of making your own SVN build from the official DOSBox SVN source code:
* URL: [[BuildingDOSBox]]

===Snapshot of latest DOSBox SVN source code===
Snapshots of the latest SVN versions of the DOSBox source code are available at the following URL(s) :
* URL: http://source.dosbox.com/dosboxsvn.tgz (auto-generated tarball provided by Qbix)
* URL: http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/?view=tar (auto-generated tarball created by sourceforge.net)
* URL: http://sourceforge.net/scm/?type=svn&group_id=52551 (sourceforge.net instructions for accessing official DOSBox SVN repository)
* URL: http://dosbox.svn.sourceforge.net/viewvc/dosbox/dosbox/trunk/ (sourceforge.net SVN browser for official DOSBox SVN repository)
* URL: http://github.com/Henne/dosbox-svn (unofficial git clone of DOSBox SVN; auto-generated tarballs are also available there)
* URL: http://dosbox.linuxsecured.net/dosboxcvs.tgz - '''broken link as of 10/25/10'''