DOSBoxWiki - User contributions [en]

GAMES:Archon: The Light and the Dark

2017-10-09T21:16:04Z

Lwc: Unneeded section

{{Infobox Game
|title=Archon: The Light and the Dark
|id=771
|image=[[Image:GAME_Archon_Title.png|320px]]
|caption=Title Screen
|developer=Free Fall Associates
|publisher=Electronic Arts
|released=1983
|version=[[Version0.73|0.73]]
|status=Supported
|executable='''ARCHON.COM'''
|setup=}}

'''Archon: The Light and the Dark''' is a strategic board game with some similarities to chess. It was remade a decade later as [[GAMES:Archon Ultra|Archon Ultra]].

== Making it work ==

If you require support for general issues, see the [[Performance|performance guide]] and [[DOSBox_FAQ|FAQ]].

== External links ==

*[http://www.mobygames.com/game/pc-booter/archon-the-light-and-the-dark Archon: The Light and the Dark] at MobyGames

[[Category:Strategy games]]

GAMES:Archon Ultra

2017-10-09T21:09:37Z

Lwc: Created page with "{{Infobox Game |title=Archon Ultra |id=1835 |image=320px |caption=Title Screen |developer=Free Fall Associates |publisher=Strategic Simulations..."

{{Infobox Game
|title=Archon Ultra
|id=1835
|image=[[Image:GAME_Archon_Ultra.jpg|320px]]
|caption=Title Screen
|developer=Free Fall Associates
|publisher=Strategic Simulations
|released=1994
|version=[[Version0.74|0.74]]
|gversion=1.1a
|status=Supported
|executable='''ARCHON.EXE'''
|dos4gw=Internally
|dos32a=Yes
}}

'''Archon Ultra''' is a remake of the strategic board game [[GAMES:Archon: The Light and the Dark|Archon: The Light and the Dark]].

== Netplay ==

This game offers modem multiplayer, which DOSBox can convert to netplay. You can enable it by creating the following files in the game's folder:

'''dosbox.conf'''
<pre>
[serial]
serial1=modem
serial2=dummy
serial3=disabled
serial4=disabled
</pre>

'''modem.bat'''
<pre>
@echo off
SET ARCHON_MODEM_COMPORT=2
SET ARCHON_MODEM_COMADDR=2f8
SET ARCHON_MODEM_COMINT=3
archon
</pre>

Then use DOSBox to launch the second file instead of the game's executable.

[[Category:Action games]]
[[Category:Strategy games]]

File:GAME Archon Ultra.jpg

2017-10-09T20:50:12Z

Lwc:

GAMES:Archon: The Light and the Dark

2017-10-09T20:48:26Z

Lwc: 3, not 4

{{Infobox Game
|title=Archon: The Light and the Dark
|id=771
|image=[[Image:GAME_Archon_Title.png|320px]]
|caption=Title Screen
|developer=Free Fall Associates
|publisher=Electronic Arts
|released=1983
|version=[[Version0.73|0.73]]
|status=Supported
|executable='''ARCHON.COM'''
|setup=}}

'''Archon: The Light and the Dark''' is a strategic board game with some similarities to chess. It was remade a decade later as [[GAMES:Archon Ultra|Archon Ultra]].

== Making it work ==

If you require support for general issues, see the [[Performance|performance guide]] and [[DOSBox_FAQ|FAQ]].

== Testing ==

*14 January 2011 by [[User:Rtalaman|Rtalaman]]:
:Works fine with Dosbox.

== External links ==

*[http://www.mobygames.com/game/pc-booter/archon-the-light-and-the-dark Archon: The Light and the Dark] at MobyGames

[[Category:Strategy games]]

GAMES:Archon: The Light and the Dark

2017-10-09T20:39:13Z

Lwc: Remade

{{Infobox Game
|title=Archon: The Light and the Dark
|id=771
|image=[[Image:GAME_Archon_Title.png|320px]]
|caption=Title Screen
|developer=Free Fall Associates
|publisher=Electronic Arts
|released=1984
|version=[[Version0.73|0.73]]
|status=Supported
|executable='''ARCHON.COM'''
|setup=}}

'''Archon: The Light and the Dark''' is a strategic board game with some similarities to chess. It was remade a decade later as [[GAMES:Archon Ultra|Archon Ultra]].

== Making it work ==

If you require support for general issues, see the [[Performance|performance guide]] and [[DOSBox_FAQ|FAQ]].

== Testing ==

*14 January 2011 by [[User:Rtalaman|Rtalaman]]:
:Works fine with Dosbox.

== External links ==

*[http://www.mobygames.com/game/pc-booter/archon-the-light-and-the-dark Archon: The Light and the Dark] at MobyGames

[[Category:Strategy games]]

GAMES:Amazon: Guardians of Eden

2017-05-06T08:17:27Z

Lwc: Added a section, improved the category

{{Infobox Game
|title=Amazon: Guardians of Eden
|image=[[Image:GAME_Amazon_Guardians_of_Eden_Title.png|320px]]
|caption=Title Screen
|developer=Access Software
|publisher=Access Software
|released=1992
|version=[[Version0.72|0.72]]
|status=Slow and small but works
|executable='''AMAZON.EXE'''
|installer='''INSTALL.EXE'''
|setup='''AMAZON.EXE''' (when AM.CFG is deleted)
}}

'''Amazon: Guardians of Eden''' is a point-and-click adventure with a special SVGA mode and occasional speeches.

== Making it work in ScummVM ==
Amazon: Guardians of Eden is supported by [[TOOLS:ScummVM|ScummVM]] which may be preferable to emulating through DOSBox. ScummVM needs a folder containing the following files:
* *.AP
* *.BLK
* *.DAT
* *.LZ
* *.MAP

== Making it work in DOSBox ==
It is suggested to make a bigger screen, for example by using this [[dosbox.conf]]:
<pre>[render]
scaler=normal3x</pre>

===Notes===
* Hold the mouse's right click button without releasing to skip intros.
* The game's GUI offers no quit button, but ctrl+q or ctrl+alt+esc do the trick.
* SVGA mode is disabled by default. It can only be enabled (except during intros) by clicking alt+v, but that makes the screen too small to play even in fullscreen.
* SVGA mode allows clicking and watching previous levels' intros.

== External links ==

*[http://www.mobygames.com/game/dos/amazon-guardians-of-eden Amazon: Guardians of Eden] at MobyGames

[[Category:Action-adventure games]]

GAMES:Sam & Max Hit the Road

2017-05-06T08:14:22Z

Lwc: /* Making it work in ScummVM */ Used internal link

{{Infobox Game
|title=Sam & Max Hit the Road
|id=1443
|image=[[Image:GAME_Sam_and_Max_Hit_the_Road.png|320px]]
|caption=
|developer=LucasArts
|publisher=LucasArts
|released=1993
|version=[[Version0.72|0.72]]
|status=Supported}}

'''Sam & Max Hit the Road''' is a graphic adventure video game.

== Making it work in ScummVM ==

Sam & Max is supported by [[TOOLS:ScummVM|ScummVM]] which may be preferable to emulating through DOSBox. ScummVM needs a folder containing the following folders and files copied from the disc:
* MONSTER.SOU
* SAMNMAX.000
* SAMNMAX.001

== Making it work in DOSBox ==

If you require support for general issues, see the [[Performance|performance guide]] and [[DOSBox_FAQ|FAQ]].

== External links ==

*[http://www.mobygames.com/game/dos/sam-max-hit-the-road Sam & Max Hit the Road] at MobyGames

[[Category:Adventure games]]

GAMES:Leisure Suit Larry 6: Shape Up or Slip Out!

2017-05-06T07:57:40Z

Lwc: /* Making it work without the CD */ Fixed grammar

{{Infobox Game
|title=Leisure Suit Larry 6: Shape Up or Slip Out!
|image=[[Image:Larry 6 Jewel Case.jpg]]
|caption=Jewel Case
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1993
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Seems fine, but haven't fully tested
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}

'''Leisure Suit Larry 6: Shape Up or Slip Out!''' is a lighthearted quest in which 40-something Larry Laffer finds himself in a health spa hotel populated by women whom he tries to romanticize.

==The floppy version==
This version is supported by [[TOOLS:ScummVM|ScummVM]] which may be preferable to emulating through DOSBox.

==The CD-ROM hi-res version==
This version is supported by [[TOOLS:ScummVM|ScummVM]], but only in an early beta testing.

===Making it work without the CD===
Even if you choose full installation, the game still demands you to insert the CD every time you want to play. Luckily, it just does a simple file check. So here's how to bypass that check:
# Run the (obviously '''full''') installation. For this example, let's assume you installed the game to C:\SIERRA\LSL6CD
# Copy the AUD folder from the CD to C:\SIERRA\LSL6CD
# Copy the SFX folder from the CD to C:\SIERRA\LSL6CD
# Copy the hires\patches sub-folder from the CD to C:\SIERRA\LSL6CD
# Edit c:\SIERRA\LSL6CD\RESOURCE.CFG in Notepad and search and replace (in this order and assuming the CD was installed from D):
## C:\SIERRA\LSL6CD to \
## \SIERRA\LSL6CD to \
## D:\hires\ to \
## D:\ to \
##* The "\" assumes you'll always run the game directly from its folder.

From then on, '''ignore''' any BAT files and just run SIERRA.EXE directly.

[[Category:Adventure games]]

GAMES:Leisure Suit Larry: Love for Sail!

2017-05-05T16:07:37Z

Lwc: Added intro

{{Infobox Game
|title=Leisure Suit Larry: Love for Sail!
|image=[[Image:Larry 7 Cover Art.png]]
|caption=Cover Art
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1996
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Untested
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}

'''Leisure Suit Larry: Love for Sail!''' is the last game in the original Leisure Suit Larry series.

The plot revolves around 40-something Larry Laffer trying to win various action games in order to gain another week on a cruise ship to be shared in the captain's cabin.

It should be noted this game is not supported by [[TOOLS:ScummVM|ScummVM]] due to its rare usage of Sierra's newest SCI engine.

 

==The 1-level-only demo==
{{Infobox Game
|title=Leisure Suit Larry: Love for Sail! (Freeware Demo)
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1996
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Perfect
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}
This is a freeware demo that lets you play only 1 action game - Strip-Liars-Dice - with Dewmi Moore (parody of actress Demi Moore).

===Making it work without the CD===
The demo demands you to insert the CD every time you want to play. Luckily, it just does a simple file check. So here's how to bypass that check:
# Run the installation. For this example, let's assume you installed the game to C:\SIERRA\LSL7CD
# Copy all *.000 files from the CD to C:\SIERRA\LSL7CD
# Copy all *.AUD files from the CD (including the *.AUD files in the 22M8\ sub-folder) to C:\SIERRA\LSL7CD
# Copy all *.SFX files from the CD to C:\SIERRA\LSL7CD
# Edit c:\SIERRA\LSL7CD\RESOURCE.CFG in Notepad and search and replace (in this order and assuming the CD was installed from D):
## C:\SIERRA\LSL7CD to \
## \SIERRA\LSL7CD to \
## D:\ to \
##* The "\" assumes you'll always run the game directly from its folder.
# Edit the main BAT file and remove (or prefix with the word "rem" - without the quotes) the call to the CD checker
Now you can play the game without the CD!

[[Category:Action-adventure games]]

GAMES:Leisure Suit Larry: Love for Sail!

2017-05-05T16:06:47Z

Lwc: Linebreak

{{Infobox Game
|title=Leisure Suit Larry: Love for Sail!
|image=[[Image:Larry 7 Cover Art.png]]
|caption=Cover Art
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1996
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Untested
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}

'''Leisure Suit Larry: Love for Sail!''' is the last game in the original Leisure Suit Larry series.

The plot revolves around 40-something Larry Laffer trying to win various action games in order to gain another week on a cruise ship to be shared in the captain's cabin.

This game is not supported by [[TOOLS:ScummVM|ScummVM]] due to its rare usage of Sierra's newest SCI engine.

 

==The 1-level-only demo==
{{Infobox Game
|title=Leisure Suit Larry: Love for Sail! (Freeware Demo)
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1996
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Perfect
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}
This is a freeware demo that lets you play only 1 action game - Strip-Liars-Dice - with Dewmi Moore (parody of actress Demi Moore).

===Making it work without the CD===
The demo demands you to insert the CD every time you want to play. Luckily, it just does a simple file check. So here's how to bypass that check:
# Run the installation. For this example, let's assume you installed the game to C:\SIERRA\LSL7CD
# Copy all *.000 files from the CD to C:\SIERRA\LSL7CD
# Copy all *.AUD files from the CD (including the *.AUD files in the 22M8\ sub-folder) to C:\SIERRA\LSL7CD
# Copy all *.SFX files from the CD to C:\SIERRA\LSL7CD
# Edit c:\SIERRA\LSL7CD\RESOURCE.CFG in Notepad and search and replace (in this order and assuming the CD was installed from D):
## C:\SIERRA\LSL7CD to \
## \SIERRA\LSL7CD to \
## D:\ to \
##* The "\" assumes you'll always run the game directly from its folder.
# Edit the main BAT file and remove (or prefix with the word "rem" - without the quotes) the call to the CD checker
Now you can play the game without the CD!

[[Category:Action-adventure games]]

GAMES:Leisure Suit Larry: Love for Sail!

2017-05-05T16:06:02Z

Lwc: Created page with "{{Infobox Game |title=Leisure Suit Larry: Love for Sail! |image=Image:Larry 7 Cover Art.png |caption=Cover Art |developer=Sierra On-Line |publisher=Sierra On-Line |release..."

{{Infobox Game
|title=Leisure Suit Larry: Love for Sail!
|image=[[Image:Larry 7 Cover Art.png]]
|caption=Cover Art
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1996
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Untested
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}

'''Leisure Suit Larry: Love for Sail!''' is the last game in the original Leisure Suit Larry series. The plot revolves around 40-something Larry Laffer trying to win various action games in order to gain another week on a cruise ship to be shared in the captain's cabin.

This game is not supported by [[TOOLS:ScummVM|ScummVM]] due to its rare usage of Sierra's newest SCI engine.

 

==The 1-level-only demo==
{{Infobox Game
|title=Leisure Suit Larry: Love for Sail! (Freeware Demo)
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1996
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Perfect
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}
This is a freeware demo that lets you play only 1 action game - Strip-Liars-Dice - with Dewmi Moore (parody of actress Demi Moore).

===Making it work without the CD===
The demo demands you to insert the CD every time you want to play. Luckily, it just does a simple file check. So here's how to bypass that check:
# Run the installation. For this example, let's assume you installed the game to C:\SIERRA\LSL7CD
# Copy all *.000 files from the CD to C:\SIERRA\LSL7CD
# Copy all *.AUD files from the CD (including the *.AUD files in the 22M8\ sub-folder) to C:\SIERRA\LSL7CD
# Copy all *.SFX files from the CD to C:\SIERRA\LSL7CD
# Edit c:\SIERRA\LSL7CD\RESOURCE.CFG in Notepad and search and replace (in this order and assuming the CD was installed from D):
## C:\SIERRA\LSL7CD to \
## \SIERRA\LSL7CD to \
## D:\ to \
##* The "\" assumes you'll always run the game directly from its folder.
# Edit the main BAT file and remove (or prefix with the word "rem" - without the quotes) the call to the CD checker
Now you can play the game without the CD!

[[Category:Action-adventure games]]

File:Larry 7 Cover Art.png

2017-05-05T15:46:44Z

Lwc:

GAMES:Leisure Suit Larry 6: Shape Up or Slip Out!

2017-05-05T15:37:48Z

Lwc: Created page with "{{Infobox Game |title=Leisure Suit Larry 6: Shape Up or Slip Out! |image=Image:Larry 6 Jewel Case.jpg |caption=Jewel Case |developer=Sierra On-Line |publisher=Sierra On-Li..."

{{Infobox Game
|title=Leisure Suit Larry 6: Shape Up or Slip Out!
|image=[[Image:Larry 6 Jewel Case.jpg]]
|caption=Jewel Case
|developer=Sierra On-Line
|publisher=Sierra On-Line
|released=1993
|version=[[Version0.74|0.74]]
|gversion=1.000
|status=Seems fine, but haven't fully tested
|executable='''SIERRA.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''
}}

'''Leisure Suit Larry 6: Shape Up or Slip Out!''' is a lighthearted quest in which 40-something Larry Laffer finds himself in a health spa hotel populated by women whom he tries to romanticize.

==The floppy version==
This version is supported by [[TOOLS:ScummVM|ScummVM]] which may be preferable to emulating through DOSBox.

==The CD-ROM hi-res version==
This version is supported by [[TOOLS:ScummVM|ScummVM]], but only in an early beta testing.

===Making it work without the CD===
Even if you choose full installation, the game still demands you to insert the CD every time you want to play. Luckily, it just does a simple file check. So here's how to bypass that check:
# Run the (obviously '''full''') installation. For this example, let's assume you installed the game to C:\SIERRA\LSL6CD
# Copy the AUD folder from the CD to C:\SIERRA\LSL6CD
# Copy the SFX folder from the CD to C:\SIERRA\LSL6CD
# Copy the hires\patches sub-folder from the CD to C:\SIERRA\LSL6CD
# Edit c:\SIERRA\LSL6CD\RESOURCE.CFG in Notepad and search and replace (in this order and assuming the CD was installed from D):
## C:\SIERRA\LSL6CD to \
## \SIERRA\LSL6CD to \
## D:\hires\ to \
## D:\ to \
##* The "\" assumes you'll always run the game directly from its folder.

From then on, '''ignore''' and BAT files and just run SIERRA.EXE directly.

[[Category:Adventure games]]

File:Larry 6 Jewel Case.jpg

2017-05-05T14:47:36Z

Lwc:

SVN Builds

2017-05-05T14:15:49Z

Lwc: Reverted edits by Lwc (talk) to last revision by Wengier

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. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release (0.74) is several years old, and is therefore missing a significant amount of work performed by the developers. 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://www.vogons.org/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://www.vogons.org/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://www.vogons.org/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''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===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:

* '''DOSBox SVN-lfn''' (DOSBox with Long File Name (LFN) and mouse copy/paste support) by Wengier
** Last updated: 2017-02-26
** SVN base version: r4006
** URL: http://www.wpdos.org/dosbox-vdos-lfn.html (introduction + source + Windows binary + links to forum discussions)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** URL: http://bit.ly/1laDvGX (alternative Windows binary compiled with MinGW instead of Visual Studio, zipped)
** Description: This is an enhanced build of DOSBox based on its SVN version that adds Windows-style Long File Name (LFN) as well as mouse copy/paste support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). It now also includes features such as automatic drive mounting, APM power off, direct parallel port passthrough used for printing, DOS APIs that communicate with the Windows clipboard, and DBCS support for displaying CJK (East Asian) characters. Windows binaries are provided, but sources should work on other platforms such as Linux and macOS/OS X too (pdcurses might be required for the cross-platform clipboard copy/paste feature). Please see README.TXT file inside the binary package for more information.

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** 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. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

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

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/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.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/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: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

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

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

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** 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: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** 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: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** 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://sourceforge.net/p/dosbox/code-0/4006/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2017-02-26'''

===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://www.vogons.org/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]]

===Unofficial ports===
The following DOSBoxWiki article discusses unofficial ports for other operating systems, which are not in any way supported by the DOSBox team.
* [[Unofficial ports]]

===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)

SVN Builds

2017-05-05T14:14:48Z

Lwc: Reverted edits by Wengier (talk) to last revision by WikiSysop

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. Active development continues between releases, however, with new features and fixes continuously added to DOSBox's SVN repository that eventually result in the next release. At the time of this writing, the last official release is several years old, and is therefore missing a significant amount of work performed by the developers. 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://www.vogons.org/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://www.vogons.org/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://www.vogons.org/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''' for Windows
** URL: http://www.emucr.com/search/label/DOSBox
** Notes: Updated daily, although there are reports that it may lag behind if multiple changes are checked in by the DOSBox developers on the same day followed by no changes for some time after.
** Compiled '''without''' screenshot, video recording and IPX support.

* '''Dominus''' for OS X 10.4 - 10.7 (ppc/intel)
** URL: http://dl.dropbox.com/u/7737184/Dosbox/Dosbox-Snapshot.dmg
** Notes: Automatically updated on changes to SVN.

===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:

* '''DOSBox with Long File Name (LFN) and mouse copy/paste support''' by Wengier
** Last updated: 2014-12-25
** SVN base version: r3876
** URL: http://www.vogons.org/viewtopic.php?t=40610 (discussion + source + Windows binary)
** URL: http://www.vogons.org/viewtopic.php?t=41179 (discussion + source + Windows binary)
** URL: http://bit.ly/12jANWF (latest Windows binary + required DLLs, zipped)
** Description: This is a build of DOSBox based on its SVN version that adds Long File Name (LFN) and mouse copy/past support. With this both the DOSBox shell commands and many native LFN-aware DOS programs should now be able to use LFN in DOSBox, and users can also use the right mouse button to select, copy and paste text from and to DOSBox (when the mouse is not locked). Windows binaries are provided, but sources should work on other platforms too (pdcurses is required for the cross-platform clipboard copy/paste feature).

* '''DOSBox SVN Daum''' by ykhwong for Windows, OSX, and Linux
** Last updated: 2015-01-25
** SVN base version: r3894
** URL: http://ykhwong.x-y.net/ (Windows binary, Linux x86 source)
** 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. Recent versions include DOSBox-X branch changes as well.

* '''dosbox-patched''' for Ubuntu Linux (Oneiric and newer)
** Last updated: 2014-01-12
** SVN base version: ?
** URL: https://code.launchpad.net/~i30817/+archive/dosbox-patched
** Description: "Daily build of dosbox trunk with mt32 patch (roms go into ~/.dosbox)". Automatically-built PPA packages built from DOSBox SVN trunk with Munt MT-32 emulation patch.

* '''DOSBox-X''' by TheGreatCodeholio
** Last updated: It is constantly updated
** URL: http://www.vogons.org/viewtopic.php?t=31881 (discussion + links)
** URL: https://github.com/joncampbell123/dosbox-x/releases
** Description: "This is a branch of DOSBox 0.74 that I have been working on and off for the past 8 months. I've been modifying a lot in the source to make the emulation more accurate, to fix other parts of the emulation, and to widen the kind of hardware DOSBox emulates. I call it "DOSBox-x" for lack of a better name."

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

* '''"Mega Build" series (by H-A-L-9000)'''
** Last updated: 2010-11-18
** SVN base version: r3661
** URL: http://home.arcor.de/h-a-l-9000/ (Windows binary, Linux source, Intel Mac OS X port by thedoctor45)
** URL: http://www.vogons.org/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.

* '''"UBER BUILD" (by Virusek)'''
** Last Updated: 2010-07-23
** SVN base version: r3623
** URL: http://www.vogons.org/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: 2010-05-12
** URL: http://www.vogons.org/viewtopic.php?p=186679#186679 (Debian i386 + amd64 binary & source packages)
** Description: Debian Linux APT packaged version of DOSBox with Glide support.

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

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

* '''DOSBox for Mac OSX (by rhoenie/Marcus Herbert)'''
** Last updated: 2008-08-09
** 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: 2006-12-15
** <s>URL: http://garni.ch/dosbox/</s>
** 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: 2004-10-15
** <s>URL: http://www.artworxinn.com/alex/downloads.htm</s>
** 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://sourceforge.net/p/dosbox/code-0/3852/log/?path=/dosbox (sourceforge.net SVN log) - '''fixed on 2014-01-01'''

===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://www.vogons.org/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)

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

===Android===
* '''AnDOSBox''' (ver. 0.74, v1.2.8, 2012-10-18)
** URL: http://sites.google.com/site/andosbox/

* '''DosBox Turbo''' (ver. 0.74 SVN, v2.1.20, 2015-02-25)
** URL: http://sites.google.com/site/dosboxturbo/

* '''Magic Dosbox''' (ver. 0.74, v1.0.29, 2015-06-30)
** URL: http://magicbox.imejl.sk

* '''aDOSBox''' (ver. 0.73, v0.2.5, 2011-05-16)
** URL: http://play.google.com/store/apps/details?id=org.hystudio.android.dosbox

===iOS===
* '''DOSPad''' (ver. 0.74, v1.96, 2011-01)
** URL: http://www.litchie.com/?page_id=123

===PSP===
* '''DOSBox PSP''' (ver. 0.71, 2008-08-03)
** <s>URL: http://www.qj.net/tag/crazyc-gaming-news.html</s>
** URL: http://www.pspdosbox.co.uk
** <s>URL: http://forums.ps2dev.org/viewtopic.php?t=9564</s>

===Symbian===
* '''Symbian DOSBox''' (ver. 0.73, 2009-12-07)
** URL: http://sourceforge.net/projects/s60dosbox/

===Pocket PC / Windows Mobile===
* '''DosBox PPC''' (ver. 0.73, 2009-07-06)
** URL: http://n0p.8bit.fm

===Wii===
* '''DOSBox for Wii''' (ver. 0.74, v1.7, 2012-06-30)
** URL: http://code.google.com/p/dosbox-wii/

===Dreamcast===
* '''DOSBox for Dreamcast''' (ver. 0.60, 2005?)
** URL: http://gpf.dcemu.co.uk/dcdoxbox.shtml

===GP2x===
* '''DOSBox for GP2x''' (ver. 0.72, 2009-01-03)
** URL: http://dl.openhandhelds.org/cgi-bin/gp2x.cgi?0,0,0,0,72,2534
** <s>URL: http://wiki.gp2x.org/wiki/DosBox</s>

* '''DOSBox for GP2x Wiz''' (ver. 0.72, 2009-08-27)
** URL: http://dl.openhandhelds.org/cgi-bin/wiz.cgi?0,0,0,0,72,198

* '''DOSBox for GP2x Caanoo''' (ver. 0.74, 2012-01-14)
** URL: http://dl.openhandhelds.org/cgi-bin/caanoo.cgi?0,0,0,0,72,826

===Dingoo A320===
* '''DOSBox for Dingoo A320''' (ver. 0.74, 2013-03-11)
** URL: http://www.slaanesh.net/2013/03/dosbox-074-open-dingux.html

===OS/2===
* '''DOSBox/2''' (ver. 0.74 SVN, 2015-06-05)
** URL: http://www.joschs-robotics.de/dosbox/
** URL: http://wiki.netlabs.org/index.php/DOSBox_Port

===AmigaOS 4.0===
* '''DOSBox for AmigaOS 4.0''' (ver. 0.72, 2009-06-14)
** URL: http://www.os4depot.net/share/emulation/computer/dosbox.lha
** URL: http://www.os4depot.net/index.php?function=browse&cat=emulation/computer

===Java===
* '''jDosbox''' (ver. v0.74, v0.74.28, 2013-02-27)
** URL: http://jdosbox.sourceforge.net

===JavaScript===
* '''JsDOSBox''' (ver. 0.74, v3.2, 2015-02-14)
** URL: http://sourceforge.net/projects/jsdosbox/

===IRIX===
* '''DOSBox for IRIX''' (ver. 0.71, 2007?)
** URL: http://www.spam-filter.de/dosbox/dosbox_on_irix
** <s>URL: http://www.enosnusnu.de/index.php?/archives/98-DOSBox-on-IRIX.html</s>
** 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.

===PXA270===
* '''DOSBox "Optimized" for PXA270 (by wellswang & kkazakov)''' (ver. 0.70, 2007-03-19)
** <s>URL: http://www.oesf.org/forum/index.php?showtopic=18415&st=270&p=156742&#entry156742</s>
** 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

GAMES:Star Wars: Dark Forces

2012-10-20T19:06:43Z

Lwc: Undo revision 4469 by Lwc (talk)

GAMES:Star Wars: Dark Forces

2012-10-20T19:05:08Z

Lwc: Reverted edits by Lwc (talk) to last revision by PoultryInMotion

{{Infobox Game
|title=Star Wars: Dark Forces
|image=[[Image:Dark Forces Box Cover.jpg]]
|caption=Box art for Dark Forces
|developer=LucasArts
|publisher=LucasArts
|released=1995
|version=[[Version0.72|0.72]]
|gversion=1.0 (Build 2)
|status=Perfect
|executable='''DARK.EXE'''
|installer='''INSTALL.EXE'''
|setup='''SETUP.EXE'''
|dos4gw=Externally
|dos32a=Yes
}}

'''Star Wars: Dark Forces''' is first-person shooter (single person only - no multiplay) that is halfway between the basic playability of [[GAMES:Doom|Doom]] and the advanced playability of [[GAMES:Duke Nukem 3D|Duke Nukem 3D]].

==Making it work without the CD==
Even if you choose full installation, the game still demands you to insert the CD every time you want to play. Luckily, it just does a simple file check. So here's how to bypass that check:
# Run the (obviously '''full''') installation. For this example, let's assume you installed the game to c:\games\DARK\
# Copy D:\CD.ID to the root of the DOSBox drive that you are running from (e.g. c:\games\ which you are mounting as drive C in DOSBox)
# Edit DRIVE.CD (e.g. c:\games\DARK\DRIVE.CD) and change ''X'' to C (or whatever your hard drive is).
#* DRIVE.ID doesn't support more than one letter. If it's a problem for you, you can leave the original DRIVE.ID alone (assuming it contains the letter D), and alternatively put this [[dosbox.conf]] file in c:\games\DARK\ :
#** ''[autoexec]''
#** ''mount d .''
Now you can play the game without the CD!

==Optimum configuration==

(Note: The below was tested and confirmed to work using DOSBox v0.74) 

Once you have the game installed, you may find that it runs at a very low (mostly unplayable) framerate even on a modern system. To get the game running it’s best, edit the following entries in the [[dosbox.conf]] file (note: change the “<code>fullresolution</code>” setting below to match your monitor’s native resolution): 

<pre>

[sdl]

fullscreen=true
fullresolution=1280x800
output=openglnb
sensitivity=250

[render]

aspect=true
scaler=none

[cpu]

cycles=max

[dos]

xms=false
ems=false
umb=false

</pre>

The most important of the above entries is “<code>output=openglnb</code>”. This tells DOSBox to use the OpenGL renderer. (note: the “nb” in “<code>openglnb</code>” means “'''n'''o '''b'''i-linear” filtering. This keeps the pixels looking “pixelated” and more true to the original game). This setting utilizes the power of your hardware accelerated graphics card to render the display and increases the frame rate from “slideshow” speed, to a silky-smooth hundreds of frames per second. For more information on output settings, see [[Configuration:SDL]]. 

Also, make sure to use the “<code>xms=false, ems=false, umb=false</code>” settings as shown above, since this game runs in “DOS/4GW Protected Mode” and therefore has it’s own memory management system. Activating Extended (XMS) or Expanded (EMS) memory managers will interfere with the game’s memory manager and possibly cause memory corruption and undesirable gameplay effects. For more information on DOS/4GW DOS memory extenders and helpful hints on using them with Protected Mode games, see these external sites: 

[http://www.tenberry.com/dos4g/index.html Tenberry Software - DOS4G] (Original creators of DOS/4G and DOS/4GW) 
[http://http://dos32a.narechk.net/index_en.html Narech Kontcell - DOS/32] (A free and more memory efficient drop-in replacement for DOS/4G and DOS/4GW) 
[http://dos32a.narechk.net/manual/html/user/3.htm DOS/32 - How to use with games] (Specific information on how to use the DOS/32 DOS extender EXE in place of the memory inefficient DOS/4GW EXE that came with your favorite games--and more!) 

Also see [[TOOLS:DOS32A]] 

Additionally, also see personal suggestions in the [[{{TALKPAGENAME}}|talk page]]. 

==The 3-level-only demo==

{{Infobox Game
|title=Star Wars: Dark Forces SE (Freeware Demo)
|image=
|caption=
|developer=LucasArts
|publisher=LucasArts
|released=1995
|version=[[Version0.72|0.72]]
|gversion=1.0L (Build 1)
|status=Perfect
|executable='''DARK.EXE'''
|installer='''D:\DARKSE\INSTALL.EXE'''
|setup='''SETUP.EXE'''
|dos4gw=Externally
|dos32a=Yes
}}

This is a freeware demo that lets you play only the first 3 levels. Once you complete level 3, the "next mission" button is just treated like the exit button (both display an ad for the full game before exiting).

===Installation requirement===
'''D:\DARKSE\INSTALL.EXE''' has a special requirement. You must [[MOUNT]] the '''entire''' CD-ROM drive and only then "[[Commands#CD|CD]]" your way into it (in other words: you can't just directly mount '''DARKSE''' itself). Here is how to do it:
<pre>
Z:\>mount d d:\
Z:\>d:
D:\>cd DARKSE
D:\DARKSE>install
</pre>

=== Making it work ===
The game will run quite well in DOSBox, but there are two points to note:

* Run SETUP.EXE (it will also run automatically after a successful completion of the installation) and choose your settings.
* While the game has no CD protection per se, there is no choice for a full installation. Therefore, most of the game is played directly from the CD-ROM. Use this [[dosbox.conf]] file to support that behavior:
<pre>
[autoexec]
mount d d:\ -t cdrom
</pre>
(assuming your CD-ROM drive is D, of course)

===Making it work without the CD===
Since the game has no CD protection, but also no choice for a full installation, here is a way to copy just the needed files from the CD-ROM and thus simulate a CD-free full installation:
# Install the game. For this example, let's assume you installed it to c:\games\DARKSE\
# Create c:\games\DARKSE\'''CD'''
# Copy D:\CD.ID to c:\games\DARKSE\CD\
# Create c:\games\DARKSE\CD\'''DARKSE'''
# Create c:\games\DARKSE\CD\DARKSE\'''DARK'''
# Copy every '''GOB''' file that '''doesn't already exist''' in c:\games\DARKSE\ to c:\games\DARKSE\CD\DARKSE\DARK\
# Create c:\games\DARKSE\CD\DARKSE\DARK\'''LFD'''
# Copy every '''LFD''' file that '''doesn't already exist''' in c:\games\DARKSE\LFD\ to c:\games\DARKSE\CD\DARKSE\DARK\LFD\
# Put this [[dosbox.conf]] file in c:\games\DARKSE\ :
<pre>
[autoexec]
mount d cd -t cdrom
</pre>
Now you can play the game without the CD!

===Tip for those who eventually move from the demo to the full game===
The demo version and the full version share the same save-file (DARKPILO.CFG). Therefore, if you like the demo and end up getting the full game, just copy over DARKPILO.CFG from the demo to the full game, and you'll be able to start playing directly in level 4 with your saved player from the demo.

GAMES:Star Wars: Dark Forces

2012-10-20T19:04:40Z

Lwc: /* The 3-level-only demo */ Added line break between templates

Talk:GAMES:Star Wars: Dark Forces

2012-10-20T19:01:20Z

Lwc: /* Optimum configuration */ Moved from article

== Optimum configuration ==

Use DOSBOX to run the setup program. You can use every music card except for AWE32 MIDI, Soundscape Synth, and Gravis Ultrasound. Using these for music card either produce no music, or crash the game.

For Digital Sound, you can use all excepr Sound Blaster, Sound Blaster Pro, AWE32, Pro AudioSpectrum, and SoundScape Audio.

The rest of the options work fine, however using Gravis gives tne sound a considerable delay before playing. SB2.0 can lag if a few sounds are playing at once, so use Sound Blaster 16 for the best performance.

Now, go to your DOSBOX config, and change prebuffer to 0 under the sound area. This will remove some delay before sounds. Also, it may help to change rate to 11025, this will decrease lag and cause no problems in sound quality.

You shouldn't use fulldouble, this causes lots of render errors and other things that you don't want. It runs graphically fine at any resolution, but the sound may become delayed at higher ones.

If you want to remove the letterboxing without making it look terrible, change output to ddraw, and set aspect to true.

If you want to use the mouse for horizontal aiming, you may want to crank up the resolution. Nope, you should keep Dark Forces' sensitivity the same, for some reason it only affects turning left.

Now, set sensitivity in the DOSBOX configuration to 250. Note that this will also increase the mouse speed in the menus, so be warned.

* Note from another user: You can change the mouse sensitivity in the game. When setting it to the max, you will see no difference at first. However, if you close and re-run the game it should handle properly, without changing the DOSBOX configuration sensitivity.

That's it! Dark Forces should now look and play it's best.

—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:65.33.18.92|65.33.18.92]] ([[User talk:65.33.18.92|talk]] • [[Special:Contributions/65.33.18.92|contribs]]) 02:51, 7 August 2008

:(Note: The below was tested and confirmed to work using DOSBox v0.74) 

:Once you have the game installed, you may find that it runs at a very low (mostly unplayable) framerate even on a modern system. To get the game running it’s best, edit the following entries in the [[dosbox.conf]] file (note: change the “<code>fullresolution</code>” setting below to match your monitor’s native resolution): 

<pre>

[sdl]

fullscreen=true
fullresolution=1280x800
output=openglnb
sensitivity=250

[render]

aspect=true
scaler=none

[cpu]

cycles=max

[dos]

xms=false
ems=false
umb=false

</pre>

:The most important of the above entries is “<code>output=openglnb</code>”. This tells DOSBox to use the OpenGL renderer. (note: the “nb” in “<code>openglnb</code>” means “'''n'''o '''b'''i-linear” filtering. This keeps the pixels looking “pixelated” and more true to the original game). This setting utilizes the power of your hardware accelerated graphics card to render the display and increases the frame rate from “slideshow” speed, to a silky-smooth hundreds of frames per second. For more information on output settings, see [[Configuration:SDL]]. 

:Also, make sure to use the “<code>xms=false, ems=false, umb=false</code>” settings as shown above, since this game runs in “DOS/4GW Protected Mode” and therefore has it’s own memory management system. Activating Extended (XMS) or Expanded (EMS) memory managers will interfere with the game’s memory manager and possibly cause memory corruption and undesirable gameplay effects. For more information on DOS/4GW DOS memory extenders and helpful hints on using them with Protected Mode games, see these external sites: 

:—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:PoultryInMotion|PoultryInMotion ]] ([[User talk:PoultryInMotion |talk]] • [[Special:Contributions/PoultryInMotion |contribs]]) 00:05, 23 July 2012

GAMES:Star Wars: Dark Forces

2012-10-20T18:56:12Z

Lwc: Removed vandalism

TOOLS:Disk Explorer

2012-04-28T16:13:45Z

Lwc: Elaborated and solved the bug

{{Infobox Tool
|title=Disk Explorer
|license=Freeware
|homepage=[http://hp.vector.co.jp/authors/VA013937/editdisk/index_e.html hp.vector.co.jp]
}}

'''Disk Explorer''' is a small portable software that can be used to copy and delete files and folders to/from images. This provides an easy way to modify the images which DOSBox uses through its [[IMGMOUNT]] command.

==Note==
In older Disk Explorer versions, '''deleting''' files and folders from images ruined the modified images (at least as far as DOSBox was concerned). The solution back then was settling on deleting images' files and folders from within DOSBox itself.

==Conclusion==
* Use this tool to copy and delete files and folders to/from images.

Talk:Main Page

2012-04-28T15:29:07Z

Lwc: Replaced forum questions with a discussion

==FAQ==
As it requires admin rights, please fix the main page's link to the FAQ (to avoid a clash with MediaWiki:FAQ), thanks! -[[User:Lwc|Lwc]] 15:29, 28 April 2012 (UTC)

Performance

2012-04-28T15:26:04Z

Lwc: Fixed link

* See also [[System Requirements]].
* See also [[DOSBox 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

Template:Infobox Tool

2012-04-28T15:23:10Z

Lwc: Fixed link

{| class="infobox bordered vevent" style="float: {{{align|right}}}; font-size: 90%; text-align: left;" cellpadding="3"
|-
! colspan="2" style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | ''{{{title|{{PAGENAME}}}}}''
|-
| colspan="2" style="text-align: center;" | {{{image|}}}<div>{{{caption|}}}</div>
|-
| style="background-color: #ccccff; width: 70px;" | Homepage
| {{{homepage|''Unknown''}}}
|-
| style="background-color: #ccccff; width: 70px;" | License
| {{{license|''Free''}}}
|-
| style="background-color: #ccccff; width: 70px;" | [[DOSBox FAQ#What is Abandonware?|Abandonware]]
| {{{abandonware|''Yes''}}}
|}

Talk:FAQ

2012-04-28T15:21:40Z

Lwc: moved Talk:FAQ to Talk:DOSBox FAQ: Avoiding a clash with Mediawiki:FAQ

#REDIRECT [[Talk:DOSBox FAQ]]

Talk:DOSBox FAQ

2012-04-28T15:21:40Z

Lwc: moved Talk:FAQ to Talk:DOSBox FAQ: Avoiding a clash with Mediawiki:FAQ

== Core=dynamic ==

Setting '''core=dynamic''' gave a significant performance boost in Wolfenstein 3D.
What does this actually do, and why isn't it default?

And whats the difference between the '''cputype'''s?

FAQ

2012-04-28T15:21:40Z

Lwc: moved FAQ to DOSBox FAQ: Avoiding a clash with Mediawiki:FAQ

#REDIRECT [[DOSBox FAQ]]

DOSBox FAQ

2012-04-28T15:21:40Z

Lwc: moved FAQ to DOSBox FAQ: Avoiding a clash with Mediawiki:FAQ

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.

TOOLS:FreeDOS

2012-04-28T15:15:50Z

Lwc: No longer abandonware, hooray!

{{Infobox Tool
|title=FreeDOS
|homepage=http://www.freedos.org
|abandonware=No
}}

'''FreeDOS''' is a GPL-licensed re-implementation of the DOS operating system intended for old computers and x86 emulators which don't provide their own internal DOS.

Most of the utilities it provides work perfectly well in DOSBox and it is an excellent source for useful commands like MORE which DOSBox doesn't provide.

==Conclusion==
* Use utilities like MORE.EXE from FreeDOS as replacements for MS-DOS utilities like MORE.COM.
* Install FreeDOS to C:\DOS to provide a more complete DOS experience.

User talk:WikiSysop

2010-11-04T23:50:24Z

Lwc: /* Questionable deletion */ Please keep the discussion in once place

== Questionable deletion ==

Can you explain why you censored [http://www.dosbox.com/wiki/index.php?title=TOOLS:ScummVM&diff=next&oldid=3635 this section]? You didn't even include any edit summary. -[[User:Lwc|Lwc]] 18:42, 17 October 2010 (UTC)
:ah yes.
:The scummvm people used that piece of information as proof that we prefer scummvm over dosbox for games that scummvm supports.
:Which is not true.
:Especially the last part of that section is totally not true. —Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:WikiSysop|WikiSysop]] ([[User talk:WikiSysop|talk]] • [[Special:Contributions/WikiSysop|contribs]]) 08:49, 18 October 2010
::If they "use" unofficial wiki information, it's their problem. But who said the last part is totally not true? It sounds true enough for me. -[[User:Lwc|Lwc]] 23:50, 4 November 2010 (UTC)

User talk:Lwc

2010-11-04T23:49:18Z

Lwc: Please keep the discussion where it started

==Questionable deletion==
[[User talk:WikiSysop#Questionable deletion]]

User talk:WikiSysop

2010-10-17T18:42:38Z

Lwc: Questionable deletion

Sound

2010-07-09T16:50:42Z

Lwc: /* Roland */ config=midiconfig

DOSBox is capable of emulating several sound devices. By emulating the hardware the user can utilize whatever audio device they have installed in their PC, while the DOS [[GAMES|Game]] or [[Software|Application]] believes it is running on the emulated hardware.

Sound was sometimes difficult to set up in the DOS era. Unlike Windows, DOS did not keep a list of the system's sound devices, nor did it expose generic drivers for them. Software had to include separate support for each sound device it wanted to give the users the option of using. If a game did not support a user's audio hardware, no sound was possible. And the game had to be configured with the memory addresses of the hardware by hand. Also, different devices supported different features, resulting in games that could sound very different (maybe high-quality music on one card, but voice-acting on another) depending on the hardware available. Thankfully, DOSBox can emulate all the most popular sound systems of the DOS era, so one can usually find something that sounds good.

Most of the sound devices are capable of existing inside the same computer at the same time, so when configuring DOSBox sound you need to think of them as separate devices that can be enabled or disabled. Sound devices that are not in use do not use many resources, so you don't gain much in the way of performance by reducing the number of sound devices enabled. A game will likely only use a single device at a time anyway. (The one notable exception being routing music and sound effects through different devices, which was common for people with both a Sound Blaster and a separate MIDI device.) DOSBox also makes sure the appropriate environment variables are defined for each device, so game audio device auto-detection usually works, if the game attempts it.

DOSBox's output to your real computer's sound system is configured under the '''<tt>mixer</tt>''' category. Each emulatable device has its own configuration section. Note that almost all sound devices have a configuration setting to enable or disable them, as well as one for the sample rate of the emulation. The sample rate of a device must never exceed the '''<tt>rate</tt>''' setting under the '''<tt>mixer</tt>''' heading, as this will cause undefined behavior.

DOSBox can emulate the following devices. Although the sound quality you will get depends heavily on your configuration and what the software you are running supports, they are listed here in roughly ascending order of audio processing power.

==PC Speaker==

The most ubiquitous audio device of all time. Built into every personal computer to this very day, the PC Speaker acts as diagnostic device during the initial booting up of a computer. (to inform the user, in a series of beeps, if there is any low level hardware issue) Early game developers utilized the PC Speaker to generate music and sound effects - to good effect. Later, some developers invented ways to generate complex audio through the PC Speaker, even reproducing voice. Very few games utilized the PC Speaker in this way, as the CPU requirements were high and the quality was severely limited. However, a Windows driver was written that allowed Windows games to utilize the PC Speaker in this manner, which was useful if the user had no other sound device.

The PC Speaker is configured under the '''<tt>speaker</tt>''' category. There are no special options to configure for the PC Speaker. If enabled, it just does what it does.

==Tandy 1000 Speaker==

The Tandy 1000 was based on the IBM PCjr and like the PCjr it included not only the standard PC speaker but also the TI-SN76496 sound chip which provided three square wave tone generators and one white noise generator. This made for much higher quality sound effects and music than the standard PC Speaker. The Tandy 1000 TL and SL added an 8-bit DAC for realistic sound effects.

The Tandy 1000 Speaker is configured under the '''<tt>speaker</tt>''' category. The setting for controlling whether Tandy emulation is enabled is worth mentioning. It can be set to '''<tt>on</tt>''' or '''<tt>off</tt>''', but it can also be set to '''<tt>auto</tt>''', in which case it will be turned on if the system type (near the top of the configuration file) is set to '''<tt>tandy</tt>''' and off otherwise.

Some people have reported needing to turn on Sound Blaster emulation in order to support the Tandy 1000 TL/SL DAC.

==Disney Sound Source==

The Disney Sound Source was an external audio device that connected to a PC via a Parallel Port, also known as the Printer Port. An enhanced version of the Covox Speech Accelerator with "Mickey Mouse" ears on top, the device was surprisingly capable of producing polyphonic audio and voice. The sound quality is distinctive and tinny, though by no means high quality. One notable game that supported the device was Sierra's [[GAMES:King's Quest 6|King's Quest 6]] which managed to provide an audio experience similar to the Sound Blaster audio card.

The Disney Sound Source became popular due to its brand name and ease of configuration: There are no Base Address, IRQ, or DMA settings because it connects to any available Parallel Port. However, applications that utilize a printer might lock up if they try to talk to this device by mistake, so if you are having parallel port trouble and are not using this device for audio, you may want to consider disabling it.

A Windows driver exists (as with the PC Speaker) that can let the device work as an audio device in Windows 3.11.

The Disney Sound System is configured under the '''<tt>speaker</tt>''' category. As mentioned before, it has no special configuration. (And does not even have a rate setting.)

==Sound Blaster==

The Sound Blaster is widely considered the most popular audio device standard. In the DOS era of games, it came in several editions. In most cases '''<tt>sb16</tt>''' is the best option for DOSBox, though many older games that were produced before the SB16 was manufactured might have some issues with working with the otherwise backwards-compatible device. Here is a list of the different capabilities of the various Sound Blaster cards.

{| style="font-size: 90%; text-align: left;" cellpadding="3"
|-
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Device
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Name
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Bits
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Top Sample Rate
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Stereo
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Synthesizer
|-
| none
| Sound Blaster Emulation disabled
| ''n/a''
| ''n/a''
| ''n/a''
| ''n/a''
|-
| sb1
| Sound Blaster 1.0
| 8
| 22 KHz
| No
| CMS / OPL-2
|-
| sb2
| Sound Blaster 2.0
| 8
| 44.1 KHz
| No
| OPL-2
|-
| sbpro1
| Sound Blaster Pro 1.0
| 8
| 44.1 KHz
| Yes
| Dual OPL-2
|-
| sbpro2
| Sound Blaster Pro 2.0
| 8
| 44.1 KHz
| Yes
| OPL-3
|-
| sb16
| Sound Blaster 16
| 16
| 44.1 KHz
| Yes
| OPL-3
|}

Due to its advanced features, competitive price point, and backwards-compatibility with AdLib cards, Soundblaster became considered the "standard" for special effects reproduction in many applications and games. (Sadly, once they drove all the competition out of business, the "competitive price point" went away.) Although they have internal synthesizers, Sound Blaster cards are not MPU-401 compatible, and were therefore often coupled with a MIDI card for enhanced music emulation.

The Sound Blaster is configured under the '''<tt>sblaster</tt>''' category. There are several options for configuring this device, which are explained in the comments in that category.

===AdLib===

DOSBox does not emulate the AdLib Music Synthesizer Card directly. However, it does emulate Sound Blaster cards that feature AdLib support in their synthesizers.

The AdLib/synthesizer support of the Sound Blaster is configured separately from the rest of the card, with the '''<tt>oplmode</tt>''' and '''<tt>oplrate</tt>''' settings. The OPL Mode controls what synthesizer is emulated. The following settings are available:

{| style="font-size: 90%; text-align: left;" cellpadding="3"
|-
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Device
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Name
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Number of Channels
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Stereo
! style="font-size:110%; text-align: center; background-color: #ccccff;" class="summary" | Notes
|-
| auto
| Auto-Select Synthesizer
| ''n/a''
| ''n/a''
| This will pick whichever synthesizer was actually present on the model of Sound Blaster you are trying to emulate. Note that it will always pick AdLib-compatible settings, never '''<tt>cms</tt>'''.
|-
| cms
| Creative Music System / GameBlaster
| 6
| Yes
| Supported stereo, but fewer channels than AdLib cards. Never gained popularity due to its poor audio quality. Note that turning this on in DOSBox will disable AdLib support, as CMS is the one option that is not AdLib-compatible.
|-
| opl2
| AdLib / OPL-2 / Yamaha 3812
| 9
| No
| The gold standard of PC synthesis for many years.
|-
| dualopl2
| Dual OPL-2
| 9
| Yes
| The Sound Blaster Pro 1.0 used two OPL-2s in tandem to support stereo sound.
|-
| opl3
| AdLib Gold / OPL-3 / Yamaha YMF262
| 18
| Yes
| Became the new gold standard after AdLib. Supported by the ubiquitous Sound Blaster 16.
|}

==Gravis Ultrasound==

The Gravis Ultrasound was an advanced synthesizer released by an unlikely manufacturer: Canadian joystick company Advanced Gravis. Its audio was far ahead of any other consumer device of the time, supporting wave-table synthesis, stereo sound, 14-channel playback at 44.1 KHz or a ''whopping'' 32 channels of playback at 19.2 KHz.

However, the Ultrasound eschewed any attempt at backwards-compatibility with AdLib or Soundblaster cards. Programs had to be written to specifically take advantage of its capabilities. Many DOS users kept a Sound Blaster in their PC in addition to an Ultrasound, in case they needed to run a program that did not support the more advanced card. (And in DOSBox, this can be imitated by turning on both devices in your configuration file, which is recommended.)

One quirk of the Ultrasound is that, unlike most synthesizers, it did not come with any voices pre-installed on the card. All voices had to be installed from disk either at driver load time or by the application. Because of this, a set of drivers and "patch files" is needed in order to use the Ultrasound in DOSBox. Due to incompatibilities between the license of the patch files and DOSBox's GPL license, these files cannot be distributed with DOSBox, so you will need to download them from another website:

'''HuggyBaby's Ready-To-Use DOSBox Ultrasound Folders (featuring the original GUS 4.11 set and the enhanced Pro Patches Lite 1.61 set)'''

http://www.dosgames.com/forum/about10574.html

'''GUS Install Disk Set Version 4.11'''

http://ftp.isu.edu.tw/pub/Hardware/multimedia/Gravis/gus411/index-e.htm

More sites with patch files can be found on the [[Wikipedia:Gravis Ultrasound#External links|Gravis Ultrasound page on Wikipedia]]. The patch files must be unzipped to a folder that can be accessed from DOSBox's command line. It is common practice to put these in a folder called "ULTRASND" under whatever folder you will mount as your C: drive.

The Gravis Ultrasound is configured under the '''<tt>gus</tt>''' category. It has several options, which are explained in the comments in the configuration file. Of particular note is the '''<tt>ultradir</tt>''' option, which must be set to the path to the patch files ''inside'' DOSBox. (Which is likely not the same as the path on your real hard drive.)

An Example:

If you have a folder called "Games" on your C: drive that you mount as X: in DOSBox, and then you install the patch files to C:\Games\ULTRASND\, the config entry will be

ultradir=X:\ULTRASND\

==General MIDI (MPU-401)==

General MIDI isn't a specific piece of hardware so much as a standard that has been supported by various sound cards (and other devices such as mixers, instruments, lighting control panels, etc...) throughout computing history. DOSBox is able to emulate MIDI in either regular or uart modes.

Since MIDI support is still common on computers, DOSBox passes MIDI data along to any MIDI synthesizer installed on your system rather than trying to emulate a particular device. General MIDI in DOSBox sounds exactly like any other program on your host computer that plays MIDI files because it is generating its output through the same device. You can think of the General MIDI as more a pass-though interface than a piece of emulated hardware.

General MIDI is configured under the '''<tt>midi</tt>''' category. There are several options, which are explained briefly in the comments in the configuration file and at greater length in the README file. Owners of Yamaha MIDI Synthesizers and other external synthesizers may find [[Using Yamaha MIDI synthesizers|this guide]] useful.

===Roland===

The Roland synthesizers, particularly the MT-32, are worth mentioning separately. Many DOS games included separate support for the MT-32 (or the MT-100, LAPC-I, CM-32L, or CM-64) in addition to basic General MIDI support. People who have a real Roland MT-32 or a software synthesizer that emulates one can take advantage of this support. Since DOSBox only passes along MIDI data to your synthesizer without looking at it, simply route DOSBox's General MIDI to your Roland and configure your DOS software to use Roland mode.

A Roland MT-32 can be connected to the PC using a USB to MIDI adapter. The MT-32 output can be connected to the line-in on a sound card. Dosbox can be configured to use the MT-32 for music when it is connected this way. At the Dosbox command prompt, type '''mixer /listmidi''' to get a list of the midi devices attached to the machine. Locate the USB midi adapter in the list and note the number that it is associated with. Change [[Dosbox.conf#midiconfig = id of MIDI device|Dosbox.conf's midiconfig = id of MIDI device]] to the ID of the USB midi device (e.g. midiconfig=0) Once that is done, the MT-32 should operate.

==External Links==

* A comprehensive overview of DOS-era sound systems and DOSBox's support (or lack thereof) for them: http://ipggi.wordpress.com/2008/04/26/dosbox-sound-emulation/

TOOLS:ScummVM

2010-04-04T11:24:57Z

Lwc: Undo revision 3433 by 24.99.111.221 (Talk)

{{Infobox Tool
|title=ScummVM
|homepage=http://www.scummvm.org
|abandonware=No
}}

'''ScummVM''' is a free and open source software that allows you to run certain classic graphical point-and-click adventure games, assuming you have their data files. In other words, it replaces the original executables of the games, allowing you to play the games directly (without DOSBox like emulation) on new systems.

Unlike DOSBox, ScummVM provides custom emulation for each game and not for DOS itself. Of course, this means ScummVM emulates games in an opt-in fashion. That is, the developers choose which games would be supported, as opposed to DOSBox in which you can (at least try to) run anything that runs under DOS.

==Conclusion==
Since ScummVM uses the same license as DOSBox, is almost as unintrusive in its installation (the general configuration file must be put in one of Windows' special folders), and is just as cross-platformed, once a game is within the limited range of games supported by ScummVM, it is pointless to run it in DOSBox anymore.

TOOLS:DOS32A

2010-04-04T11:19:39Z

Lwc: Fixed English

{{Infobox Tool
|title=DOS32A
|homepage=http://dos32a.narechk.net
}}

'''DOS32A''' (DOS/32 Advanced DOS Extender) is a free and open source software that can be used to replace the DOS4GW.EXE DOS Extender file that many DOS games use.

Once a game uses this (although [[#Note|see note]]), it is expected to run faster and better in DOSBox.

==Usage==
===Externally===
It is much easier if games just call DOS4GW.EXE externally. If the game is launched by a .BAT file, you can edit it to call DOS32A instead of DOS4GW. This way, you do not need to back up and rename the executables.

If not, all you have to do is in this case is:
# (Optional) Back up DOS4GW.EXE in the game folder. For example, '''rename''' it to DOS4GW.BAK
# Copy over dos32a\binw\dos32a.exe to the game's folder in which DOS4GW.EXE was located
# Rename that local copy of dos32a.exe to DOS4GW.EXE
That's it! The game will run it instead. If something goes wrong, just rename DOS4GW.BAK back to DOS4GW.EXE.

There's no need to do this through the command prompt, but it may make the above instructions easier to understand:
<pre>
C:\>cd\games\mygame
C:\games\mygame>ren DOS4GW.EXE DOS4GW.BAK
C:\games\mygame>copy "c:\program files\dosbox\dos32a\binw\dos32a.exe" DOS4GW.EXE
</pre>

Then if the game complains, you can easily undo everything:

<pre>
C:\>cd\games\mygame
C:\games\mygame>del DOS4GW.EXE
C:\games\mygame>ren DOS4GW.BAK DOS4GW.EXE
</pre>

===Internally===
Some games embed DOS4GW.EXE inside the game's own EXE file (e.g. mygame.exe). It is a little more complicated in this case to make the game use DOS32A instead, but it is still well worth it. What you need to do in this case is:
# (Optional) Back up the file that has DOS4GW.exe embedded in it. This usually means the game's main EXE. For example, '''copy''' mygame.exe to mygame.old (make sure you use copy and '''not''' rename).
# You must now "set" a path ("8dot3" style!) for DOS32A (e.g. '''set dos32a=c:\progra~1\dosbox\dos32a''')
# Run c:\progra~1\dosbox\dos32a\binw\sb /r mygame.exe
That's it! DOS32A is now embedded in the game's EXE file instead of DOS4GW.EXE! If something goes wrong, just rename mygame.old to mygame.exe.

Due to the requirement to "set" a path, it's best to do all of this through the command prompt:
<pre>
C:\>cd\games\mygame
C:\games\mygame>copy mygame.exe mygame.old
C:\games\mygame>set dos32a=c:\progra~1\dosbox\dos32a
C:\games\mygame>%dos32a%\binw\sb /r mygame.exe
</pre>

mygame.exe now uses DOS32A internally.

Then if the game complains when you run mygame.exe, you can easily undo everything:

<pre>
C:\>cd\games\mygame
C:\games\mygame>del mygame.exe
C:\games\mygame>ren mygame.old mygame.exe
</pre>

==Note==
Some games do not work with DOS32A at all. For example, Shadowcaster is incompatible with it because RAVEN.EXE run with DOS32A is unable to find the A32SBDG.DLL file that is in the same directory, while with DOS4GW it can.

==Conclusion==
* If a game uses DOS4GW.EXE, be sure to try using DOS32A instead, but always back up the original file first.

DOSBox FAQ

2010-04-04T11:19:13Z

Lwc: /* Gibberish */ fixed link

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.

===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 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.''' Apple updated the video drivers for certain NVidia cards in 10.5.4. This update also disabled 256 color mode support resulting in many graphical errors in programs that run in that mode. The only known solution is to downgrade your video drivers to the pre-10.5.4 release. Instructions for doing so are available in this thread: http://forums.macrumors.com/showthread.php?t=490676 . Alternatively an installer package has been made to automate the process; this package is available from: http://70.181.80.166:82/blog/archives/2008/07/mac-os-10531054-nvidia-256-colors.html

===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.

Connectivity

2010-04-04T11:09:30Z

Lwc: /* Start client(s) */ fixed English

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).

== IPX emulation ==
First, [[Dosbox.conf#%5Bipx%5D|enable IPX]].

=== Start IPX server ===

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.

On the server machine, execute the following command:

ipxnet startserver [UDP port]

See screenshot below:

[[Image:dosbox_lan_02.png]]

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:
ipxnet startserver 19900

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.

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)'''.

=== Start client(s) ===

On each one of the clients, run the following command to connect to the server:

ipxnet connect <IP> [UDP port]

For example:

ipxnet connect 192.168.2.100

See screenshot below:

[[Image:dosbox_lan_03.png]]

Port is optional. The same rules apply as in [[#Start IPX server]]. For example:
ipxnet connect 192.168.2.100 19900

You now have the network running. You can confirm it by typing:
IPXNET STATUS
If you want to check the speed and/or see the list of server and all clients, type:
IPXNET PING

'''Start your game'''

If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:
IPXNET DISCONNECT
and only after all clients disconnect (or you'll risk locking them up), the server can type:
IPXNET STOPSERVER

== Modem emulation==
First, define [[Configuration:SerialPort]].

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.

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)'''.

===The game's modem options===
You must enter the game's modem options and:
* 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.
* Choose the highest modem's speed the game allows.
* ''For [[#Emulating making a call|clients only]]'' 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.
* The game's other modem options don't matter in DOSBox.

Exit the settings, enter the game itself and find the call/answer menu entry.

====Emulating answering a call====
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.

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).

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".

====Emulating making a call====
The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.

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:
ATDT1.2.3.4
or "ATDT<HOST>". For example, in the case of "hosty":
ATDThosty

== How to obtain computer's IP address==
===The quick and advanced way===
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".

===The long but user friendly way===

Go to "My Network Place"

Click on "View My Network Connections"

[[Image:Network_settings1.png]]

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.

[[Image:Network_settings2.png]]

==External links==
* [http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html dedoimedo.com] (the original article plus screenshots from actual multiplayer games)

Connectivity

2010-04-04T11:08:31Z

Lwc: /* Start client(s) */ "my" case

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).

== IPX emulation ==
First, [[Dosbox.conf#%5Bipx%5D|enable IPX]].

=== Start IPX server ===

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.

On the server machine, execute the following command:

ipxnet startserver [UDP port]

See screenshot below:

[[Image:dosbox_lan_02.png]]

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:
ipxnet startserver 19900

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.

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)'''.

=== Start client(s) ===

On each one of the clients, run the following command to connect to the server:

ipxnet connect <IP> [UDP port]

For example:

ipxnet connect 192.168.2.100

See screenshot below:

[[Image:dosbox_lan_03.png]]

Port is optional. The same rules apply as in [[#Start IPX server]]. For example:
ipxnet connect 192.168.2.100 19900

You now have the network running. You can confirm it by:
IPXNET STATUS
If you want to check the speed and/or see the list of server and all clients, type:
IPXNET PING

'''Start your game'''

If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:
IPXNET DISCONNECT
and only after all clients disconnect (or you'll risk locking them up), the server can type:
IPXNET STOPSERVER

== Modem emulation==
First, define [[Configuration:SerialPort]].

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.

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)'''.

===The game's modem options===
You must enter the game's modem options and:
* 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.
* Choose the highest modem's speed the game allows.
* ''For [[#Emulating making a call|clients only]]'' 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.
* The game's other modem options don't matter in DOSBox.

Exit the settings, enter the game itself and find the call/answer menu entry.

====Emulating answering a call====
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.

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).

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".

====Emulating making a call====
The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.

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:
ATDT1.2.3.4
or "ATDT<HOST>". For example, in the case of "hosty":
ATDThosty

== How to obtain computer's IP address==
===The quick and advanced way===
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".

===The long but user friendly way===

Go to "My Network Place"

Click on "View My Network Connections"

[[Image:Network_settings1.png]]

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.

[[Image:Network_settings2.png]]

==External links==
* [http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html dedoimedo.com] (the original article plus screenshots from actual multiplayer games)

Connectivity

2010-04-04T11:03:53Z

Lwc: /* Emulating making a call */ ATDT<HOST>

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).

== IPX emulation ==
First, [[Dosbox.conf#%5Bipx%5D|enable IPX]].

=== Start IPX server ===

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.

On the server machine, execute the following command:

ipxnet startserver [UDP port]

See screenshot below:

[[Image:dosbox_lan_02.png]]

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:
ipxnet startserver 19900

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.

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)'''.

=== Start client(s) ===

On each one of the clients, run the following command to connect to the server:

ipxnet connect <IP> [UDP port]

Specifically, in my case:

ipxnet connect 192.168.2.100

See screenshot below:

[[Image:dosbox_lan_03.png]]

Port is optional. The same rules apply as in [[#Start IPX server]]. For example:
ipxnet connect 192.168.2.100 19900

You now have the network running. You can confirm it by:
IPXNET STATUS
If you want to check the speed and/or see the list of server and all clients, type:
IPXNET PING

'''Start your game'''

If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:
IPXNET DISCONNECT
and only after all clients disconnect (or you'll risk locking them up), the server can type:
IPXNET STOPSERVER

== Modem emulation==
First, define [[Configuration:SerialPort]].

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.

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)'''.

===The game's modem options===
You must enter the game's modem options and:
* 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.
* Choose the highest modem's speed the game allows.
* ''For [[#Emulating making a call|clients only]]'' 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.
* The game's other modem options don't matter in DOSBox.

Exit the settings, enter the game itself and find the call/answer menu entry.

====Emulating answering a call====
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.

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).

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".

====Emulating making a call====
The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.

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:
ATDT1.2.3.4
or "ATDT<HOST>". For example, in the case of "hosty":
ATDThosty

== How to obtain computer's IP address==
===The quick and advanced way===
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".

===The long but user friendly way===

Go to "My Network Place"

Click on "View My Network Connections"

[[Image:Network_settings1.png]]

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.

[[Image:Network_settings2.png]]

==External links==
* [http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html dedoimedo.com] (the original article plus screenshots from actual multiplayer games)

Connectivity

2010-04-04T11:01:41Z

Lwc: Fixed sections and English

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).

== IPX emulation ==
First, [[Dosbox.conf#%5Bipx%5D|enable IPX]].

=== Start IPX server ===

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.

On the server machine, execute the following command:

ipxnet startserver [UDP port]

See screenshot below:

[[Image:dosbox_lan_02.png]]

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:
ipxnet startserver 19900

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.

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)'''.

=== Start client(s) ===

On each one of the clients, run the following command to connect to the server:

ipxnet connect <IP> [UDP port]

Specifically, in my case:

ipxnet connect 192.168.2.100

See screenshot below:

[[Image:dosbox_lan_03.png]]

Port is optional. The same rules apply as in [[#Start IPX server]]. For example:
ipxnet connect 192.168.2.100 19900

You now have the network running. You can confirm it by:
IPXNET STATUS
If you want to check the speed and/or see the list of server and all clients, type:
IPXNET PING

'''Start your game'''

If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:
IPXNET DISCONNECT
and only after all clients disconnect (or you'll risk locking them up), the server can type:
IPXNET STOPSERVER

== Modem emulation==
First, define [[Configuration:SerialPort]].

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.

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)'''.

===The game's modem options===
You must enter the game's modem options and:
* 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.
* Choose the highest modem's speed the game allows.
* ''For [[#Emulating making a call|clients only]]'' 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.
* The game's other modem options don't matter in DOSBox.

Exit the settings, enter the game itself and find the call/answer menu entry.

====Emulating answering a call====
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.

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).

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".

====Emulating making a call====
The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.

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:
ATDT1.2.3.4
or
ATDThosty

== How to obtain computer's IP address==
===The quick and advanced way===
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".

===The long but user friendly way===

Go to "My Network Place"

Click on "View My Network Connections"

[[Image:Network_settings1.png]]

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.

[[Image:Network_settings2.png]]

==External links==
* [http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html dedoimedo.com] (the original article plus screenshots from actual multiplayer games)

Dosbox.conf

2009-12-23T13:10:18Z

Lwc: /* Creation and Location */ Moved info from Connectivity

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

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

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

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

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

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

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

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

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

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

== Sections ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Recommendations==

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

User profile folder

2009-12-23T13:07:59Z

Lwc: No need to analyze the EXE

The '''user profile folder''' or '''Home Folder''' is a place where DOSBox will look for the [[Dosbox.conf]] file for the user that executes dosbox.exe. The location of this folder varies depending on the host Operating System.

Connectivity

2009-12-23T13:02:25Z

Lwc: /* IPX emulation */ Moved info

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).

== IPX emulation ==
First, [[Dosbox.conf#%5Bipx%5D|enable IPX]].

=== Start IPX server ===

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.

On the server machine, execute the following command:

ipxnet startserver [UDP port]

See screenshot below:

[[Image:dosbox_lan_02.png]]

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:
ipxnet startserver 19900

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.

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)'''.

=== Start client(s) ===

On each one of the clients, run the following command to connect to the server:

ipxnet connect <IP> [UDP port]

Specifically, in my case:

ipxnet connect 192.168.2.100

See screenshot below:

[[Image:dosbox_lan_03.png]]

Port is optional. The same rules apply as in [[#Start IPX server]]. For example:
ipxnet connect 192.168.2.100 19900

You now have the network running. You can confirm it by:
IPXNET STATUS
If you want to check the speed and/or see the list of server and all clients, type:
IPXNET PING

'''Start your game'''

If you're done, but want to remain in DOSBox, the clients can optionally use the following commands:
IPXNET DISCONNECT
and only after all clients disconnect (or you'll risk locking them up), the server can type:
IPXNET STOPSERVER

== Modem emulation==
First, define [[Configuration:SerialPort]].

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.

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)'''.

==The game's modem options==
You must enter the game's modem options and:
* 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.
* Choose the highest modem's speed the game allows.
* ''For [[#Emulating making a call|clients only]]'' 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.
* The other game's modem options don't matter in DOSBox.

Exit the settings, enter the game itself and find the call/answer menu entry.

===Emulating answering a call===
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.

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).

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".

===Emulating making a call===
The client should choose the "make a call" option in their game. Then supply the server's hostname or IP address.

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:
ATDT1.2.3.4
or
ATDThosty

== How to obtain computer's IP address==
===The quick and advanced way===
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".

===The long but user friendly way===

Go to "My Network Place"

Click on "View My Network Connections"

[[Image:Network_settings1.png]]

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.

[[Image:Network_settings2.png]]

==External links==
* [http://www.dedoimedo.com/games/reviving/dosbox_multiplayer.html dedoimedo.com] (the original article plus screenshots from actual multiplayer games)

Configuration

2009-12-23T12:56:39Z

Lwc: Fixed

#Redirect [[Dosbox.conf]]

Configuration:IPX

2009-12-23T12:55:02Z

Lwc: Fixed

;ipx=true/false: default "false"

See [[Connectivity]] on how to use IPX once it's enabled.

Dosbox.conf

2009-12-23T12:52:32Z

Lwc: /* [ipx] */ Removed double info

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

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

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

=== Windows Vista ===
Dosbox.conf is created automatically in the Windows [[user profile folder]] (e.g. ''{system drive}'':\Users\''{username}''\AppData\Local\DOSBox\. For version 0.73 it is named ''dosbox-0.73.conf''. The location is indicated by the DOSBox Status Window upon startup.

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

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

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

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

== Sections ==

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Recommendations==

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

Ipxnet

2009-12-23T12:50:48Z

Lwc: Fixed

#Redirect [[Connectivity]]

How To:Networking with DOSBox

2009-12-23T12:49:50Z

Lwc: Fixed

#Redirect [[Connectivity]]

IPX

2009-12-23T12:49:46Z

Lwc: Fixed

#Redirect [[Connectivity]]