http://www.dosbox.com/wiki/api.php?action=feedcontributions&user=Mutagen&feedformat=atomDOSBoxWiki - User contributions [en]2024-03-29T11:19:58ZUser contributionsMediaWiki 1.34.1http://www.dosbox.com/wiki/index.php?title=Configuration:CPU&diff=4216Configuration:CPU2010-11-15T07:49:17Z<p>Mutagen: Undo revision 4198 by Ihezosiva (Talk) spam</p>
<hr />
<div>The CPU section controls how DOSBox tries to emulate the CPU, how fast the emulation should be, and to adjust it. DOSBox offers 4 different methods of [[/cpu/core/Intro|CPU emulation]].<br />
<br />
==== core = [[/cpu/core/simple|simple]] | [[/cpu/core/normal|normal]]| [[/cpu/core/dynamic|dynamic]] | auto ====<br />
[[/cpu/core/Intro|CPU core]] used in emulation. The choices result in a different efficency of DOSBox and in very rare cases have an effect on stability.<br />
<br />
:{| class="wikitable"<br />
|-<br />
| '''normal''' || The program is interpreted instruction by instruction. This approach is a lot more CPU demanding than dynamic core but allows for a more fine-grained time emulation and is needed on platforms for which DOSBox doesn't have a dynamic core.<br />
|-<br />
| '''simple''' || Basically the same as normal, but optimized for real-mode (older) games. In case a protected-mode game is started, it automatically switches back to normal core.<br />
|-<br />
| '''dynamic''' || The program instructions are, in blocks, translated to host processor instructions that execute directly. See also [http://en.wikipedia.org/wiki/Just-in-time_compilation ]. In the most cases this approach is more efficent than interpretation, except for programs that employ massive self-modifying code. This option is not present on all host platforms.<br />
|-<br />
| '''auto''' || Real-mode programs are run with the normal core. For protected mode programs it switches to dynamic core, if available.<br />
|-<br />
| '''full''' || Deprecated. <br />
|}<br />
<br />
Default is '''auto'''.<br />
<br />
==== cputype = auto | 386 | 386_slow | 486_slow | pentium_slow | 386_prefetch ====<br />
CPU Type used in emulation. '''auto''' is the fastest choice.<br />
<br />
:(since 0.73)<br />
<br />
Default is '''auto'''.<br />
<br />
==== cycles = fixed ''nnnn'' | max [''default''%] [limit ''cycle limit''] | auto [''realmode default''] [''protected mode default''%] [limit "cycle limit"] ====<br />
Amount of instructions DOSBox tries to emulate each millisecond. Set to '''max''' to automatically run as many cycles as possible. '''auto''' setting switches to '''max''' if appropriate.<br />
<br />
:{| class="wikitable"<br />
|-<br />
| '''fixed ''nnnn'' ''' || Sets the emulated CPU speed to a fixed amount of cycles (''nnnn''). A value of 3000 equates 3 MIPS. If this value is too high some games will run too fast or crash. How high you can go depends on the power of your host CPU and on the selected core (above). If the value is too high for your CPU the emulation will slow down and the sound starts to skip.<br />
|-<br />
| '''max''' || Automatically sets the cycles so approximately the (optional) ''default''%-value of your host CPU is used. If the value is not specified it defaults to 100%. The optional ''limit'' parameter limits the maximum speed to the specified value.<br />
|-<br />
| '''auto''' || For realmode games, this option switches to ''realmode default'' number of cycles or 3000 if not specified. When switching to protected mode, cycles is internally switched to '''max''' using the remaining optional parameters.<br />
|}<br />
<br />
Default is '''auto'''.<br />
====== Examples: ======<br />
* ''cycles=fixed 5000'', ''cycles=5000'' - All games you start are run with a fixed speed of ~5 MIPS. Useful for speed sensitive games or games that need a continuous CPU speed. You can change the actual value with Ctrl+F11 and Ctrl+F12 ([[SpecialKeys|keycombo]]) while DOSBox runs.<br />
* ''cycles=max'' - All games you start run at the maximum speed your CPU permits. Use Ctrl+F11 and Ctrl+F12 to change the percentage of your CPU to be used.<br />
* ''cycles=max limit 50000'' - All games you start run at up to 50000 cycles, depending on the power of your CPU.<br />
* ''cycles=max 50%'' - About 50% of your CPU power will be used.<br />
* ''cycles=auto'' - Realmode games will run at 3000 cycles. Protected mode games run with ''cycles=max''.<br />
* ''cycles=auto 5000 50% limit 50000'' - Realmode games run with 5000 fixed cycles, protected mode games with ''cycles=max 50% limit 50000''.<br />
<br />
==== cycleup = ''nnn'' ====<br />
Amount of cycles to increase with [[SpecialKeys|keycombo]].<br />
<br />
Default is '''10'''. Setting it lower than 100 will be a percentage of the current value.<br />
<br />
==== cycledown = ''nnn'' ====<br />
Amount of cycles to decrease with [[SpecialKeys|keycombo]].<br />
<br />
Default is '''20'''. Setting it lower than 100 will be a percentage of the current value.</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=Basic_Setup_and_Installation_of_DosBox&diff=4215Basic Setup and Installation of DosBox2010-11-15T07:48:31Z<p>Mutagen: </p>
<hr />
<div>>== Basic Concepts ==<br />
<br />
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.<br />
<br />
* [[MOUNT|Mount a Drive]]<br />
* [[Drives]]<br />
* [[Sound]]<br />
* [[Display]]<br />
* [[Input]]<br />
* [[Connectivity]] (Modems/Networking)<br />
<br />
== Installation ==<br />
<br />
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'''.<br />
<br />
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:<br />
<br />
[[Image:DOSBox-Folders.jpg]]<br />
<br />
== Running a game ==<br />
<br />
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:<br />
Z:\>'''MOUNT C C:\OLDGAMES'''<br />
Drive C mounted as local directory C:\OLDGAMES\<br />
<br />
To dissect the above:<br />
*'''[[MOUNT]]''': Tells the program to [[MOUNT|mount]] a directory<br />
*'''C''': Tells the program what you want your new drive to be called (leaving it as C: is fine)<br />
*'''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.<br />
<br />
''(Note: If you want to [[MOUNT|mount]] a CD-ROM instead of a folder, type this:''<br />
Z:\>'''MOUNT D D:\ -t cdrom'''<br />
MSCDEX installed.<br />
Drive D is mounted as CDRom D:\<br />
<br />
''(Note: '''"cdrom"''' is case sensitive and must be lowercase!)''<br />
<br />
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).''<br />
<br />
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:<br />
<br />
Z:\>'''C:'''<br />
<br />
C:\><br />
<br />
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:<br />
<br />
C:\>'''CD TESTDRIV'''<br />
<br />
C:\TESTDRIV><br />
<br />
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.<br />
<br />
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:<br />
<br />
C:\TESTDRIV>'''TDCGA.EXE'''<br />
<br />
That's it! Here's a picture of all of the commands I've written about in Step 2: <br />
<br />
[[Image:Dosbox2.jpg]]<br />
<br />
== Alternate methods for running a game ==<br />
<br />
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.<br />
<br />
*[[DOSBoxFrontends|Using Frontends]]<br />
*[[DOSBoxShortcuts|Creating desktop shortcuts]]<br />
**[[DOSBoxShortcuts#Windows|in Microsoft Windows]]<br />
**[[DOSBoxShortcuts#OSX|in Apple OSX]]<br />
**[[DOSBoxShortcuts#GNOME|in Linux GNOME]]<br />
<br />
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.<br />
<br />
If you have other errors, please search the [http://vogons.zetafleet.com forums] first before posting a question.<br />
<br />
== Performance ==<br />
Yay, you've gotten your game to run! But maybe you're experiencing slowdown? How do you fix this? With the following commands:<br />
<br />
'''<tt>CTRL+F7</tt>''' = Decreases frameskip<br/><br />
'''<tt>CTRL+F8</tt>''' = Increases Frameskip<br/><br />
'''<tt>CTRL+F11</tt>''' = Slows down the game<br/><br />
'''<tt>CTRL+F12</tt>''' = Speeds up the game<br/><br />
<br />
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.'''''<br />
<br />
[[Image:Dosbox3.jpg]]<br />
<br />
== Other Useful features ==<br />
<br />
=== Quick start ===<br />
<br />
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. <br />
<br />
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:<br />
<br />
<code><pre>MOUNT C C:\OLDGAMES<br />
C:</pre></code><br />
<br />
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): <br />
<br />
[[Image:Dosbox4.jpg]]<br />
<br />
=== Full Screen ===<br />
<br />
Just press '''<tt>ALT+ENTER</tt>''' to go into and out of full screen.<br />
<br />
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.</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=Basic_Setup_and_Installation_of_DosBox&diff=4214Basic Setup and Installation of DosBox2010-11-15T07:44:13Z<p>Mutagen: Reverted edits by Mutagen (Talk) to last revision by Isomequf</p>
<hr />
<div>>== Basic Concepts ==<br />
<br />
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.<br />
<br />
* [[MOUNT|Mount a Drive]]<br />
* [[Drives]]<br />
* [[Sound]]<br />
* [[Display]]<br />
* [[Input]]<br />
* [[Connectivity]] (Modems/Networking)<br />
<br />
----<br />
<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;"><br />
----<br />
=[http://irutubaj.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=<br />
----<br />
=[http://irutubaj.co.cc CLICK HERE]=<br />
----<br />
</div><br />
<br />
== Installation ==<br />
<br />
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'''.<br />
<br />
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:<br />
<br />
[[Image:DOSBox-Folders.jpg]]<br />
<br />
== Running a game ==<br />
<br />
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:<br />
Z:\>'''MOUNT C C:\OLDGAMES'''<br />
Drive C mounted as local directory C:\OLDGAMES\<br />
<br />
To dissect the above:<br />
*'''[[MOUNT]]''': Tells the program to [[MOUNT|mount]] a directory<br />
*'''C''': Tells the program what you want your new drive to be called (leaving it as C: is fine)<br />
*'''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.<br />
<br />
''(Note: If you want to [[MOUNT|mount]] a CD-ROM instead of a folder, type this:''<br />
Z:\>'''MOUNT D D:\ -t cdrom'''<br />
MSCDEX installed.<br />
Drive D is mounted as CDRom D:\<br />
<br />
''(Note: '''"cdrom"''' is case sensitive and must be lowercase!)''<br />
<br />
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).''<br />
<br />
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:<br />
<br />
Z:\>'''C:'''<br />
<br />
C:\><br />
<br />
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:<br />
<br />
C:\>'''CD TESTDRIV'''<br />
<br />
C:\TESTDRIV><br />
<br />
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.<br />
<br />
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:<br />
<br />
C:\TESTDRIV>'''TDCGA.EXE'''<br />
<br />
That's it! Here's a picture of all of the commands I've written about in Step 2: <br />
<br />
[[Image:Dosbox2.jpg]]<br />
<br />
== Alternate methods for running a game ==<br />
<br />
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.<br />
<br />
*[[DOSBoxFrontends|Using Frontends]]<br />
*[[DOSBoxShortcuts|Creating desktop shortcuts]]<br />
**[[DOSBoxShortcuts#Windows|in Microsoft Windows]]<br />
**[[DOSBoxShortcuts#OSX|in Apple OSX]]<br />
**[[DOSBoxShortcuts#GNOME|in Linux GNOME]]<br />
<br />
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.<br />
<br />
If you have other errors, please search the [http://vogons.zetafleet.com forums] first before posting a question.<br />
<br />
== Performance ==<br />
Yay, you've gotten your game to run! But maybe you're experiencing slowdown? How do you fix this? With the following commands:<br />
<br />
'''<tt>CTRL+F7</tt>''' = Decreases frameskip<br/><br />
'''<tt>CTRL+F8</tt>''' = Increases Frameskip<br/><br />
'''<tt>CTRL+F11</tt>''' = Slows down the game<br/><br />
'''<tt>CTRL+F12</tt>''' = Speeds up the game<br/><br />
<br />
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.'''''<br />
<br />
[[Image:Dosbox3.jpg]]<br />
<br />
== Other Useful features ==<br />
<br />
=== Quick start ===<br />
<br />
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. <br />
<br />
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:<br />
<br />
<code><pre>MOUNT C C:\OLDGAMES<br />
C:</pre></code><br />
<br />
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): <br />
<br />
[[Image:Dosbox4.jpg]]<br />
<br />
=== Full Screen ===<br />
<br />
Just press '''<tt>ALT+ENTER</tt>''' to go into and out of full screen.<br />
<br />
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.</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=Commands&diff=4213Commands2010-11-15T07:44:01Z<p>Mutagen: Reverted edits by Ihezosiva (Talk) to last revision by Lwc</p>
<hr />
<div>== CD (Change Directory) ==<br />
:Allows you to move up and down a directory tree. '''CD''' is simple to use, just type <br />
<br />
CD [Directory-Name]<br />
<br />
: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<br />
<br />
C:\>'''CD SIERRA\KQ5'''<br />
C:\SIERRA\KQ5><br />
<br />
:There are also 3 special directories that are available inside every directory which help you simply move around. They are<br />
<br />
. which refers to the current directory <br />
<br />
.. which refers to the directory directly above the current directory<br />
<br />
/ which refers to the root directory<br />
<br />
:Once you have moved into a sub directory, you can move back by typing<br />
<br />
C:\SIERRA\KQ5>'''CD ..'''<br />
C:\SIERRA><br />
<br />
:And like all other directories you can string them together<br />
<br />
C:\SIERRA\KQ5>'''CD ..\..'''<br />
C:\><br />
<br />
:If you ever need to move back to the root directory you can use the '''\''' alias.<br />
<br />
C:\SIERRA\KQ5>'''CD \'''<br />
C:\><br />
<br />
== CLS ==<br />
:Clears the screen of all input and returns just the current prompt in the upper left hand corner.<br />
<br />
== COPY ==<br />
:Copy a file<br />
:Syntax is COPY <Orignal Filename> <New Filename><br />
<br />
COPY Document.txt CopyOfDocument.TXT<br />
<br />
== DIR ==<br />
: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)<br />
<br />
== DEL ==<br />
:Remove one or more files.<br />
<br />
== EXIT ==<br />
:Exit from DOSBox<br />
<br />
== MD ==<br />
:Makes a directory.<br />
<br />
== MOVE (unsupported) ==<br />
:DOSBox has no MOVE command. Use the REN command to move files.<br />
<br />
== RD ==<br />
:Removes a directory.<br />
<br />
== TYPE ==<br />
:Display the contents of a text-file.<br />
<br />
== REN ==<br />
:Renames one or more files.<br />
:Note: Unlike MS-DOS, DOSBox doesn't require the source and target filenames to be in the same folder.<br />
<br />
== LOADFIX ==<br />
:Loads a program above the first 64K of memory.<br />
<br />
== LOADHIGH ==<br />
:Loads a program into upper memory (requires xms=true,umb=true)<br />
<br />
== CHOICE ==<br />
:Waits for a keypress and sets ERRORLEVEL. Displays the given prompt followed by [Y,N]? for yes or no respones.<br />
:Used for batch scripts in most cases.<br />
<br />
CHOICE "Text to ask"<br />
<br />
== VER ==<br />
:View and set the reported DOS version. Also displays the running DOSBox version.<br />
:To set the reported DOS version use the following:<br />
<br />
VER SET <MAJOR> [MINOR]<br />
<br />
:where MAJOR is the number before the period, and MINOR is what comes after.<br />
: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)</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=Scaler&diff=4212Scaler2010-11-15T07:43:51Z<p>Mutagen: Reverted edits by Ihezosiva (Talk) to last revision by 192.35.35.34</p>
<hr />
<div>Back in the original days of DOS, games ran on specific resolutions on CRT monitors (and occasionally televisions). Limited hardware required these games to run on what is today considered extremely low resolutions. A Scaler is like a filter, that reprocesses the emulated screen before it is drawn on the physical monitor, and enables old games to take on a slightly updated look (or stylized look).<br />
<br />
The scaler used can be changed in the [[dosbox.conf]] file; it can also be changed in DosBox session by using the ''scaler [name]'' command. The ''scaler'' command by itself will display the name of the active scaler. <br />
<br />
== Examples ==<br />
These screen shots (of [[GAMES:Doom|Doom]]) represent a small section of the full game screen, and have been blown up 200% to better show how the image is being altered. Some effects are more subtle or visible depending on the range of colors displayed on the screen at individual moments.<br />
<br />
{|<br />
|-<br />
|style="vertical-align: top;padding-left:30px"|<br />
<br />
{|<br />
|-<br />
!Scaler<br />
!Example<br />
|-<br />
|style="vertical-align: top;"|normal2x<br />
normal3x<br />
|[[Image:Scaler-normal2x.png]]<br />
|-<br />
|style="vertical-align: top;"|advmame2x<br />
advmame3x<br />
|[[Image:Scaler-advmame2x.png]]<br />
|-<br />
|style="vertical-align: top;"|hq2x<br />
hq3x<br />
|[[Image:Scaler-hq2x.png]]<br />
|}<br />
<br />
|style="vertical-align: top;padding-left:30px"|<br />
<br />
{|<br />
|-<br />
!Scaler<br />
!Example<br />
|-<br />
|style="vertical-align: top;"|2xsai<br />
|[[Image:Scaler-2xsai.png]]<br />
|-<br />
|style="vertical-align: top;"|super2xsai<br />
|[[Image:Scaler-super2xsai.png]]<br />
|-<br />
|style="vertical-align: top;"|advinterp2x<br />
advinterp3x<br />
|[[Image:Scaler-advinterp2x.png]]<br />
|}<br />
<br />
|style="vertical-align: top;padding-left:30px"|<br />
<br />
{|<br />
|-<br />
!Scaler<br />
!Example<br />
|-<br />
|style="vertical-align: top;"|tv2x<br />
tv3x<br />
|[[Image:Scaler-tv2x.png]]<br />
|-<br />
|style="vertical-align: top;"|rgb2x<br />
rgb3x<br />
|[[Image:Scaler-rgb2x.png]]<br />
|-<br />
|style="vertical-align: top;"|scan2x<br />
scan3x<br />
|[[Image:Scaler-scan2x.png]]<br />
|}<br />
<br />
|}</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=Connectivity&diff=4211Connectivity2010-11-15T07:43:41Z<p>Mutagen: Reverted edits by Ihezosiva (Talk) to last revision by Lwc</p>
<hr />
<div>DOSBox networking works in a client-server architecture, where one machine acts as a server and all the others connect to it as its clients. DOSBox emulates outdated protocols and actually routes them to Internet's own IP protocol (TCP/IP for serial/modem emulation and the even better UDP/IP for IPX emulation).<br />
<br />
== IPX emulation ==<br />
First, [[Dosbox.conf#%5Bipx%5D|enable IPX]].<br />
<br />
=== Start IPX server ===<br />
<br />
Power on DOSBox on all the computers that you want to participate in the LAN games. One of these computers will have to act as a server. The rest will be clients.<br />
<br />
On the server machine, execute the following command:<br />
<br />
ipxnet startserver [UDP port]<br />
<br />
See screenshot below:<br />
<br />
[[Image:dosbox_lan_02.png]]<br />
<br />
UDP port is optional. Otherwise it defaults to 213 (the assigned IANA port for IPX tunnelling). If you want another port, for example, port 19900, type:<br />
ipxnet startserver 19900<br />
<br />
If you change the default, it's customary to choose something above 1024 as anything below is considered reserved. In Linux specifically, only root (or superuser) can use port numbers lower than 1024.<br />
<br />
Whatever UDP port is chosen (including the default), '''it must be forwarded and open to the outside network if a server is hidden behind a router (NAT)'''.<br />
<br />
=== Start client(s) ===<br />
<br />
On each one of the clients, run the following command to connect to the server:<br />
<br />
ipxnet connect <IP> [UDP port]<br />
<br />
For example:<br />
<br />
ipxnet connect 192.168.2.100 <br />
<br />
See screenshot below:<br />
<br />
[[Image:dosbox_lan_03.png]]<br />
<br />
Port is optional. The same rules apply as in [[#Start IPX server]]. For example:<br />
ipxnet connect 192.168.2.100 19900<br />
<br />
You now have the network running. You can confirm it by typing:<br />
IPXNET STATUS<br />
If you want to check the speed and/or see the list of server and all clients, type:<br />
IPXNET PING<br />
<br />
'''Start your game''' <br />
<br />
If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:<br />
IPXNET DISCONNECT <br />
and only after all clients disconnect (or you'll risk locking them up), the server can type:<br />
IPXNET STOPSERVER<br />
<br />
== Modem emulation==<br />
First, define [[Configuration:SerialPort]].<br />
<br />
If you change the default TCP port, it's customary to choose something above 1024 as anything below is considered reserved. In Linux specifically, only root (or superuser) can use port numbers lower than 1024.<br />
<br />
Whatever TCP port is chosen (including the default 5000), '''it must be forwarded and open to the outside network if a server is hidden behind a router (NAT)'''.<br />
<br />
===The game's modem options===<br />
You must enter the game's modem options and:<br />
* Define the same COM number as you chose in DOSBox. If the game is hardcoded to a certain COM number, this must be the one you choose in DOSBox.<br />
* Choose the highest modem's speed the game allows.<br />
* <sup>''For [[#Emulating making a call|clients only]]''</sup> If there's an address book, you can define the server in advance. Actually, some games might refuse to call anyone that's not listed in advance in the address book.<br />
* The game's other modem options don't matter in DOSBox.<br />
<br />
Exit the settings, enter the game itself and find the call/answer menu entry.<br />
<br />
====Emulating answering a call====<br />
Some games may want you to define an auto-answer command in advance, while others may want you to answer manually when the call comes in. Some may allow both modes.<br />
<br />
In the first mode, the server should choose the "wait for calls" option in their game. If the game wants you to type a manual command, use "ATS0=1" (answer on first call).<br />
<br />
In the second mode, the server should choose the "answer call" option when the game announces a call is coming in. If the game wants you to type a manual command, use "ATA".<br />
<br />
====Emulating making a call====<br />
The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.<br />
<br />
If the game wants you to type a manual command, use "ATDT<IP>". For example, if the server is "hosty" <1.2.3.4>, type:<br />
ATDT1.2.3.4<br />
or "ATDT<HOST>". For example, in the case of "hosty":<br />
ATDThosty<br />
<br />
== How to obtain computer's IP address==<br />
===The quick and advanced way===<br />
If you're not afraid of the command prompt (surely if you use DOSBox without a frontend), browse to '''Start > All Programs > Accessories > Command Prompt'''. Once there, type "ipconfig".<br />
<br />
===The long but user friendly way===<br />
<br />
Go to "My Network Place"<br />
<br />
Click on "View My Network Connections"<br />
<br />
[[Image:Network_settings1.png]]<br />
<br />
Right Click the Network that you are using and choose "Status", then, you will be able to obtain the computer's IP address in a local network.<br />
<br />
[[Image:Network_settings2.png]]<br />
<br />
==External links==<br />
* [http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html dedoimedo.com] (the original article plus screenshots from actual multiplayer games)</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=Mapper&diff=4210Mapper2010-11-15T07:42:56Z<p>Mutagen: Reverted edits by Ihezosiva (Talk) to last revision by Ykhwong</p>
<hr />
<div>== Remapping the keyboard and joystick ==<br />
<br />
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.<br />
<big><br />
Event: EVENT<br />
BIND: BIND (the real key/button/axis you push with your finger/hand)<br />
<br />
Add Del<br />
mod1 hold Next<br />
mod2<br />
mod3<br />
</big><br />
* 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)<br />
* 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.<br />
* 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.<br />
* 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.<br />
* 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).<br />
* Next: Go through the list of bindings which map to this EVENT.<br />
<br />
== Examples ==<br />
<br />
Q1. You want to have the X on your keyboard to type a Z in DOSBox.<br />
: A. Click on the Z on the keyboard mapper. Click "Add". Now press the X key on your keyboard.<br />
<br />
Q2. If you click "Next" a couple of times, you will notice that the Z on your keyboard also produces an Z in DOSBox.<br />
: A. Therefore select the Z again, and click "Next" until you have the Z on your keyboard. Now click "Del".<br />
<br />
Q3. If you try it out in DOSBox, you will notice that pressing X makes ZX appear.<br />
: 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".<br />
<br />
<br />
Examples about remapping the joystick:<br />
: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):<br />
# 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.<br />
# Repeat the above for the missing three directions, additionally the buttons of the joystick can be remapped as well (fire/jump).<br />
# Click on Save, then on Exit and test it with some game.<br />
<br />
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:<br />
# Start the mapper and click on Y- in the first joystick field. EVENT should be jaxis_0_1-.<br />
# Click on Del to remove the current binding, then click Add and move your joystick downwards. A new bind should be created.<br />
# Repeat this for Y+, save the layout and finally test it with some game.<br />
<br />
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.<br />
<br />
----<br />
<br />
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.</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=DOSBox_FAQ&diff=4209DOSBox FAQ2010-11-15T07:42:45Z<p>Mutagen: Reverted edits by Ihezosiva (Talk) to last revision by Ykhwong</p>
<hr />
<div>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.<br />
<br />
== Performance ==<br />
<br />
===Slow games/applications===<br />
'''Q.''' My game/application runs slowly, how do I improve speed?<br />
<br />
'''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.<br />
Also be sure to check the compatibility section of this FAQ as some game/applications are more trouble (or resource hogs) than others.<br />
<br />
* See also [[Performance#How to speed up/slow down DOSBox|How to speed up/slow down DOSBox]]<br />
<br />
===Problems in sound/music===<br />
'''Q.''' The Sound/Music for my DOS game/application sounds terrible what can I do?<br />
<br />
'''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.<br />
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)<br />
<br />
===Increasing memory size===<br />
'''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)?<br />
<br />
'''A.''' See the memsize option detailed in [[Configuration:DOSBox]].<br />
<br />
== Usage ==<br />
<br />
===Problems with colors and fullscreen drawing in Mac OS X===<br />
'''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?<br />
<br />
<br />
'''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.<br />
<br />
===No backslash key===<br />
'''Q.''' My backslash key is mapped to ']' with DOSBox on Windows. Is there a workaround?<br />
<br />
'''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]<br />
<br />
''' - Driver fix on Windows XP'''<br />
<br />
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.<br />
<br />
''' - Driver fix on Windows Vista'''<br />
<br />
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.<br />
<br />
''' - Workaround using DosBox Keymapper'''<br />
<br />
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.<br />
<br />
<br />
===Trapped mouse cursor===<br />
'''Q.''' My cursor is trapped within the DOSBox window when I click inside. How do I get the cursor out?<br />
<br />
'''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.<br />
<br />
<br />
=== Gnome scripting ===<br />
'''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?<br />
<br />
<br />
'''A.''' With -exit as commandline parameter for DOSBox.<br />
<br />
===Hard drive/CDROM access===<br />
'''Q.''' How do I access my hard drive/cdrom in DOSBox?<br />
<br />
'''A.''' See the information on the [[MOUNT]] command, or type <tt>intro mount</tt> or <tt>intro cdrom</tt> in DOSBox for the basics.<br />
<br />
<br />
=== Accessing ISO images===<br />
'''Q.''' I have an ISO image I made of files for backup purposes. How do I access it in DOSBox?<br />
<br />
'''A.''' See the information on the [[IMGMOUNT]] command<br />
<br />
=== Swapping CD images===<br />
'''Q.''' How do I unmount or change images? I need to swap CD images in the drive.<br />
<br />
'''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.<br />
<br />
===CD Audio tracks===<br />
'''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.<br />
<br />
'''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]].<br />
<br />
===Gibberish===<br />
'''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?<br />
<br />
'''A.''' Use the [[KEYB]] command to change your [[KEYB#Layout codes|Keyboard layout]].<br />
<br />
===No ":" symbol===<br />
'''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.<br />
<br />
'''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.<br />
<br />
===Scrolling up/down===<br />
'''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.<br />
<br />
'''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:<br />
# 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])<br />
# Put it in C:\C<br />
# Edit C:\Program Files\Dosbox\dosbox.conf in Notepad<br />
# Go to the bottom of the file, where it reads <tt>[autoexec]</tt>. Add to it or change it to read:<br><tt>[autoexec]<br> MOUNT C C:\C<br> PATH=%PATH%;C:\</tt><br><br><br />
# Save it, close DOSBox and then re-open DOSbox.<br />
# Now, say you wanted to use this command:<br> <tt>C:\> type readme.txt</tt><br><br>Instead type this:<br> <tt>C:\> type readme.txt | more</tt><br />
<br />
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)<br />
<br />
== Misc ==<br />
<br />
===The main site's image===<br />
'''Q.''' What is the picture in the dosbox www site in the title bar?<br />
<br />
'''A.''' [[GAMES:Dune 2|Dune 2]].<br />
<br />
=== What is DOS?===<br />
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.<br />
<br />
=== What is Abandonware?===<br />
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.</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=GAMES:Dungeon_Keeper&diff=4208GAMES:Dungeon Keeper2010-11-15T07:41:54Z<p>Mutagen: Reverted edits by Isomequf (Talk) to last revision by NaSH</p>
<hr />
<div>{{Infobox Game<br />
|title=Dungeon Keeper<br />
|id=758<br />
|image=<br />
|caption=<br />
|developer=Bullfrog Productions<br />
|publisher=Electronic Arts<br />
|released=07/1997<br />
|version=<br />
|status=<br />
|executable='''KEEPER.EXE'''<br />
|installer=<br />
|setup=<br />
|dos4gw=yes<br />
|dos32a}}<br />
<br />
''Dungeon Keeper'' is a strategy video game released for the PC in which the player attempts to build and manage a dungeon or lair while protecting it from (computer-controlled) 'hero' characters intent on stealing the user's accumulated treasures and killing various monsters. <br />
<br />
== Tested ==<br />
* Dungeon Keeper works perfectly fine (including intro video and sound)<br />
* Tested with the German version, DOSBox 0.72 and openSUSE 11.0<br />
* 30 May 2010 by [[User:NaSH|NaSH]]: <br />
:Tested on Ubuntu 10.04, with DOSBox 0.74 compiled from source (make & checkinstall)</div>Mutagenhttp://www.dosbox.com/wiki/index.php?title=Basic_Setup_and_Installation_of_DosBox&diff=4206Basic Setup and Installation of DosBox2010-11-15T07:11:21Z<p>Mutagen: Reverted edits by Isomequf (Talk) to last revision by WikiSysop</p>
<hr />
<div>== Basic Concepts ==<br />
<br />
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.<br />
<br />
* [[MOUNT|Mount a Drive]]<br />
* [[Drives]]<br />
* [[Sound]]<br />
* [[Display]]<br />
* [[Input]]<br />
* [[Connectivity]] (Modems/Networking)<br />
<br />
== Installation ==<br />
<br />
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'''.<br />
<br />
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:<br />
<br />
[[Image:DOSBox-Folders.jpg]]<br />
<br />
== Running a game ==<br />
<br />
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:<br />
Z:\>'''MOUNT C C:\OLDGAMES'''<br />
Drive C mounted as local directory C:\OLDGAMES\<br />
<br />
To dissect the above:<br />
*'''[[MOUNT]]''': Tells the program to [[MOUNT|mount]] a directory<br />
*'''C''': Tells the program what you want your new drive to be called (leaving it as C: is fine)<br />
*'''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.<br />
<br />
''(Note: If you want to [[MOUNT|mount]] a CD-ROM instead of a folder, type this:''<br />
Z:\>'''MOUNT D D:\ -t cdrom'''<br />
MSCDEX installed.<br />
Drive D is mounted as CDRom D:\<br />
<br />
''(Note: '''"cdrom"''' is case sensitive and must be lowercase!)''<br />
<br />
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).''<br />
<br />
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:<br />
<br />
Z:\>'''C:'''<br />
<br />
C:\><br />
<br />
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:<br />
<br />
C:\>'''CD TESTDRIV'''<br />
<br />
C:\TESTDRIV><br />
<br />
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.<br />
<br />
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:<br />
<br />
C:\TESTDRIV>'''TDCGA.EXE'''<br />
<br />
That's it! Here's a picture of all of the commands I've written about in Step 2: <br />
<br />
[[Image:Dosbox2.jpg]]<br />
<br />
== Alternate methods for running a game ==<br />
<br />
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.<br />
<br />
*[[DOSBoxFrontends|Using Frontends]]<br />
*[[DOSBoxShortcuts|Creating desktop shortcuts]]<br />
**[[DOSBoxShortcuts#Windows|in Microsoft Windows]]<br />
**[[DOSBoxShortcuts#OSX|in Apple OSX]]<br />
**[[DOSBoxShortcuts#GNOME|in Linux GNOME]]<br />
<br />
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.<br />
<br />
If you have other errors, please search the [http://vogons.zetafleet.com forums] first before posting a question.<br />
<br />
== Performance ==<br />
Yay, you've gotten your game to run! But maybe you're experiencing slowdown? How do you fix this? With the following commands:<br />
<br />
'''<tt>CTRL+F7</tt>''' = Decreases frameskip<br/><br />
'''<tt>CTRL+F8</tt>''' = Increases Frameskip<br/><br />
'''<tt>CTRL+F11</tt>''' = Slows down the game<br/><br />
'''<tt>CTRL+F12</tt>''' = Speeds up the game<br/><br />
<br />
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.'''''<br />
<br />
[[Image:Dosbox3.jpg]]<br />
<br />
== Other Useful features ==<br />
<br />
=== Quick start ===<br />
<br />
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. <br />
<br />
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:<br />
<br />
<code><pre>MOUNT C C:\OLDGAMES<br />
C:</pre></code><br />
<br />
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): <br />
<br />
[[Image:Dosbox4.jpg]]<br />
<br />
=== Full Screen ===<br />
<br />
Just press '''<tt>ALT+ENTER</tt>''' to go into and out of full screen.<br />
<br />
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.</div>Mutagen