DOSBoxWiki - User contributions [en]

Configuration:CPU

2018-10-02T01:14:02Z

Collector: /* cycles = fixed nnnn | max [default%] [limit cycle limit] | auto [realmode default] [protected mode default%] [limit "cycle limit"] */

The CPU section controls how DOSBox tries to emulate the CPU, how fast the emulation should be, and to adjust it. DOSBox offers 4 different methods of [[/cpu/core/Intro|CPU emulation]].

<div id="core"></div>
==== core = [[/cpu/core/simple|simple]] | [[/cpu/core/normal|normal]]| [[/cpu/core/dynamic|dynamic]] | auto ====
[[/cpu/core/Intro|CPU core]] used in emulation. The choices result in a different efficency of DOSBox and in very rare cases have an effect on stability.

:{| class="wikitable"
|-
|<div id="normal"></div> '''normal''' || The program is interpreted instruction by instruction. This approach is a lot more CPU demanding than dynamic core but allows for a more fine-grained time emulation and is needed on platforms for which DOSBox doesn't have a dynamic core.
|-
|<div id="simple"></div> '''simple''' || Basically the same as normal, but optimized for real-mode (older) games. In case a protected-mode game is started, it automatically switches back to normal core.
|-
|<div id="dynamic"></div> '''dynamic''' || The program instructions are, in blocks, translated to host processor instructions that execute directly. See also [http://en.wikipedia.org/wiki/Just-in-time_compilation ]. In the most cases this approach is more efficent than interpretation, except for programs that employ massive self-modifying code. This option is not present on all host platforms.
|-
|<div id="auto"></div> '''auto''' || Real-mode programs are run with the normal core. For protected mode programs it switches to dynamic core, if available.
|-
|<div id="full"></div> '''full''' || Deprecated.
|}

Default is '''auto'''.

<div id="cputype"></div>

==== cputype = auto | 386 | 386_slow | 486_slow | pentium_slow | 386_prefetch ====
CPU Type used in emulation. '''auto''' is the fastest choice.

:(since 0.73)

Default is '''auto'''.

<div id="cycles"></div>
==== cycles = fixed ''nnnn'' | max [''default''%] [limit ''cycle limit''] | auto [''realmode default''] [''protected mode default''%] [limit "cycle limit"] ====
Amount of instructions DOSBox tries to emulate each millisecond. Set to '''max''' to automatically run as many cycles as possible. '''auto''' setting switches to '''max''' if appropriate.

:{| class="wikitable"
|-
|<div id="fixed"></div>'''fixed ''nnnn'' ''' || Sets the emulated CPU speed to a fixed amount of cycles (''nnnn''). A value of 3000 equates 3 MIPS. If this value is too high some games will run too fast or crash. How high you can go depends on the power of your host CPU and on the selected core (above). If the value is too high for your CPU the emulation will slow down and the sound starts to skip.
|-
|<div id="max"></div> '''max''' || Automatically sets the cycles so approximately the (optional) ''default''%-value of your host CPU is used. If the value is not specified it defaults to 100%. The optional ''limit'' parameter limits the maximum speed to the specified value.
|-
|<div id="auto"></div> '''auto''' || For realmode games, this option switches to ''realmode default'' number of cycles or 3000 if not specified. When switching to protected mode, cycles is internally switched to '''max''' using the remaining optional parameters.
|}

Default is '''auto'''.
====== Examples: ======
* ''cycles=fixed 5000'', ''cycles=5000'' - All games you start are run with a fixed speed of ~5 MIPS. Useful for speed sensitive games or games that need a continuous CPU speed. You can change the actual value with Ctrl+F11 and Ctrl+F12 ([[SpecialKeys|keycombo]]) while DOSBox runs.
* ''cycles=max'' - All games you start run at the maximum speed your CPU permits. Use Ctrl+F11 and Ctrl+F12 to change the percentage of your CPU to be used.
* ''cycles=max limit 50000'' - All games you start run at up to 50000 cycles, depending on the power of your CPU.
* ''cycles=max 50%'' - About 50% of your CPU power will be used.
* ''cycles=auto'' - Realmode games will run at 3000 cycles. Protected mode games run with ''cycles=max''.
* ''cycles=auto 5000 50% limit 50000'' - Realmode games run with 5000 fixed cycles, protected mode games with ''cycles=max 50% limit 50000''.

<div id="cycleup"></div>

==== cycleup = ''nnn'' ====
Amount of cycles to increase with [[SpecialKeys|keycombo]].

Default is '''10'''. Setting it lower than 100 will be a percentage of the current value.

<div id="cycledown"></div>
==== cycledown = ''nnn'' ====
Amount of cycles to decrease with [[SpecialKeys|keycombo]].

Default is '''20'''. Setting it lower than 100 will be a percentage of the current value.

Configuration:CPU

2018-10-02T00:36:39Z

Collector: /* core = simple | normal| dynamic | auto */

The CPU section controls how DOSBox tries to emulate the CPU, how fast the emulation should be, and to adjust it. DOSBox offers 4 different methods of [[/cpu/core/Intro|CPU emulation]].

<div id="core"></div>
==== core = [[/cpu/core/simple|simple]] | [[/cpu/core/normal|normal]]| [[/cpu/core/dynamic|dynamic]] | auto ====
[[/cpu/core/Intro|CPU core]] used in emulation. The choices result in a different efficency of DOSBox and in very rare cases have an effect on stability.

:{| class="wikitable"
|-
|<div id="normal"></div> '''normal''' || The program is interpreted instruction by instruction. This approach is a lot more CPU demanding than dynamic core but allows for a more fine-grained time emulation and is needed on platforms for which DOSBox doesn't have a dynamic core.
|-
|<div id="simple"></div> '''simple''' || Basically the same as normal, but optimized for real-mode (older) games. In case a protected-mode game is started, it automatically switches back to normal core.
|-
|<div id="dynamic"></div> '''dynamic''' || The program instructions are, in blocks, translated to host processor instructions that execute directly. See also [http://en.wikipedia.org/wiki/Just-in-time_compilation ]. In the most cases this approach is more efficent than interpretation, except for programs that employ massive self-modifying code. This option is not present on all host platforms.
|-
|<div id="auto"></div> '''auto''' || Real-mode programs are run with the normal core. For protected mode programs it switches to dynamic core, if available.
|-
|<div id="full"></div> '''full''' || Deprecated.
|}

Default is '''auto'''.

<div id="cputype"></div>

==== cputype = auto | 386 | 386_slow | 486_slow | pentium_slow | 386_prefetch ====
CPU Type used in emulation. '''auto''' is the fastest choice.

:(since 0.73)

Default is '''auto'''.

<div id="cycles"></div>
==== cycles = fixed ''nnnn'' | max [''default''%] [limit ''cycle limit''] | auto [''realmode default''] [''protected mode default''%] [limit "cycle limit"] ====
Amount of instructions DOSBox tries to emulate each millisecond. Set to '''max''' to automatically run as many cycles as possible. '''auto''' setting switches to '''max''' if appropriate.

:{| class="wikitable"
|-
| '''fixed ''nnnn'' ''' || Sets the emulated CPU speed to a fixed amount of cycles (''nnnn''). A value of 3000 equates 3 MIPS. If this value is too high some games will run too fast or crash. How high you can go depends on the power of your host CPU and on the selected core (above). If the value is too high for your CPU the emulation will slow down and the sound starts to skip.
|-
| '''max''' || Automatically sets the cycles so approximately the (optional) ''default''%-value of your host CPU is used. If the value is not specified it defaults to 100%. The optional ''limit'' parameter limits the maximum speed to the specified value.
|-
| '''auto''' || For realmode games, this option switches to ''realmode default'' number of cycles or 3000 if not specified. When switching to protected mode, cycles is internally switched to '''max''' using the remaining optional parameters.
|}

Default is '''auto'''.
====== Examples: ======
* ''cycles=fixed 5000'', ''cycles=5000'' - All games you start are run with a fixed speed of ~5 MIPS. Useful for speed sensitive games or games that need a continuous CPU speed. You can change the actual value with Ctrl+F11 and Ctrl+F12 ([[SpecialKeys|keycombo]]) while DOSBox runs.
* ''cycles=max'' - All games you start run at the maximum speed your CPU permits. Use Ctrl+F11 and Ctrl+F12 to change the percentage of your CPU to be used.
* ''cycles=max limit 50000'' - All games you start run at up to 50000 cycles, depending on the power of your CPU.
* ''cycles=max 50%'' - About 50% of your CPU power will be used.
* ''cycles=auto'' - Realmode games will run at 3000 cycles. Protected mode games run with ''cycles=max''.
* ''cycles=auto 5000 50% limit 50000'' - Realmode games run with 5000 fixed cycles, protected mode games with ''cycles=max 50% limit 50000''.

<div id="cycleup"></div>
==== cycleup = ''nnn'' ====
Amount of cycles to increase with [[SpecialKeys|keycombo]].

Default is '''10'''. Setting it lower than 100 will be a percentage of the current value.

<div id="cycledown"></div>
==== cycledown = ''nnn'' ====
Amount of cycles to decrease with [[SpecialKeys|keycombo]].

Default is '''20'''. Setting it lower than 100 will be a percentage of the current value.

Configuration:CPU

2018-10-02T00:34:21Z

Collector:

The CPU section controls how DOSBox tries to emulate the CPU, how fast the emulation should be, and to adjust it. DOSBox offers 4 different methods of [[/cpu/core/Intro|CPU emulation]].

<div id="core"></div>
==== core = [[/cpu/core/simple|simple]] | [[/cpu/core/normal|normal]]| [[/cpu/core/dynamic|dynamic]] | auto ====
[[/cpu/core/Intro|CPU core]] used in emulation. The choices result in a different efficency of DOSBox and in very rare cases have an effect on stability.

:{| class="wikitable"
|-
| '''normal''' || The program is interpreted instruction by instruction. This approach is a lot more CPU demanding than dynamic core but allows for a more fine-grained time emulation and is needed on platforms for which DOSBox doesn't have a dynamic core.
|-
| '''simple''' || Basically the same as normal, but optimized for real-mode (older) games. In case a protected-mode game is started, it automatically switches back to normal core.
|-
| '''dynamic''' || The program instructions are, in blocks, translated to host processor instructions that execute directly. See also [http://en.wikipedia.org/wiki/Just-in-time_compilation ]. In the most cases this approach is more efficent than interpretation, except for programs that employ massive self-modifying code. This option is not present on all host platforms.
|-
| '''auto''' || Real-mode programs are run with the normal core. For protected mode programs it switches to dynamic core, if available.
|-
| '''full''' || Deprecated.
|}

Default is '''auto'''.

<div id="cputype"></div>
==== cputype = auto | 386 | 386_slow | 486_slow | pentium_slow | 386_prefetch ====
CPU Type used in emulation. '''auto''' is the fastest choice.

:(since 0.73)

Default is '''auto'''.

<div id="cycles"></div>
==== cycles = fixed ''nnnn'' | max [''default''%] [limit ''cycle limit''] | auto [''realmode default''] [''protected mode default''%] [limit "cycle limit"] ====
Amount of instructions DOSBox tries to emulate each millisecond. Set to '''max''' to automatically run as many cycles as possible. '''auto''' setting switches to '''max''' if appropriate.

:{| class="wikitable"
|-
| '''fixed ''nnnn'' ''' || Sets the emulated CPU speed to a fixed amount of cycles (''nnnn''). A value of 3000 equates 3 MIPS. If this value is too high some games will run too fast or crash. How high you can go depends on the power of your host CPU and on the selected core (above). If the value is too high for your CPU the emulation will slow down and the sound starts to skip.
|-
| '''max''' || Automatically sets the cycles so approximately the (optional) ''default''%-value of your host CPU is used. If the value is not specified it defaults to 100%. The optional ''limit'' parameter limits the maximum speed to the specified value.
|-
| '''auto''' || For realmode games, this option switches to ''realmode default'' number of cycles or 3000 if not specified. When switching to protected mode, cycles is internally switched to '''max''' using the remaining optional parameters.
|}

Default is '''auto'''.
====== Examples: ======
* ''cycles=fixed 5000'', ''cycles=5000'' - All games you start are run with a fixed speed of ~5 MIPS. Useful for speed sensitive games or games that need a continuous CPU speed. You can change the actual value with Ctrl+F11 and Ctrl+F12 ([[SpecialKeys|keycombo]]) while DOSBox runs.
* ''cycles=max'' - All games you start run at the maximum speed your CPU permits. Use Ctrl+F11 and Ctrl+F12 to change the percentage of your CPU to be used.
* ''cycles=max limit 50000'' - All games you start run at up to 50000 cycles, depending on the power of your CPU.
* ''cycles=max 50%'' - About 50% of your CPU power will be used.
* ''cycles=auto'' - Realmode games will run at 3000 cycles. Protected mode games run with ''cycles=max''.
* ''cycles=auto 5000 50% limit 50000'' - Realmode games run with 5000 fixed cycles, protected mode games with ''cycles=max 50% limit 50000''.

<div id="cycleup"></div>
==== cycleup = ''nnn'' ====
Amount of cycles to increase with [[SpecialKeys|keycombo]].

Default is '''10'''. Setting it lower than 100 will be a percentage of the current value.

<div id="cycledown"></div>
==== cycledown = ''nnn'' ====
Amount of cycles to decrease with [[SpecialKeys|keycombo]].

Default is '''20'''. Setting it lower than 100 will be a percentage of the current value.

Configuration:RENDER

2018-10-02T00:32:04Z

Collector:

The rendering (drawing) section controls methods that DOSBox uses to improve the speed and quality of the graphics displayed on the screen. E.g. it can "forget" (skip) the every 3rd screen update (which will save time), or it can try to smooth out some of the coarse low-resolution graphics that was used on old displays, but which looks bad when shown on a modern, high-resolution screen.

<div id="frameskip"></div>
==== frameskip = ''nnn'' ====
How many frames DOSBox skips before drawing one.

Default is '''0'''.

<div id="aspect"></div>
==== aspect = true | '''false''' ====
Do [[/render/aspect|aspect correction]]. It only affects non-square pixel modes like VGA Mode 13h, which has a resolution of 320x200 pixels and is used by many DOS games (DOOM, etc). Recommended as such games were designed for 4:3 displays, and without aspect correction will look distorted and not as the developer intended.

Default is '''false'''.

<div id="scaler"></div>
==== scaler = none | normal2x | normal3x | tv2x | tv3x | rgb2x | rgb3x | scan2x | scan3x | advmame2x | advmame3x | advinterp2x | advinterp3x | 2xsai | super2xsai | supereagle | hq2x | hq3x ====

Specifies which scaler is used to enlarge and enhance low resolution modes, BEFORE any additional scaling done according to the Fullresolution and Windowresolution settings under [sdl]. To see comparisons between the different scalers, see [[Scaler]].
:none: no scaling is performed.
:normal: nearest-neighbour scaling (big square pixels).
:scan: like 'normal', but with horizontal black lines.
:tv: like 'scan', but with darkened versions of the data instead of black lines.
:rgb: simulates the phosphors on a dot trio CRT.
:advmame: smooths corners and removes jaggies from diagonal lines.
:advinterp: identical to 'advmame'.
:sai: similar to 'advmame' but with much softer color gradients and edges.
:supersai: similar to 'sai' but sharper.
:hq: a 'high quality' scaler which delivers a cleaner and sharper image than 'advmame' or 'sai' scalers.

Default is '''normal2x'''.

Supported scalers which still need descriptions: supereagle

Configuration:DOSBox

2018-10-02T00:30:24Z

Collector:

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

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

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

<div id="machine"></div>
;machine = hercules | cga | tandy | cga | tandy | pcjr | ega | vgaonly | svga_s3 | svga_et3000 | svga_et4000 | svga_paradise | vesa_nolfb | vesa_oldvbe
:(since 0.73)
:(previously '''machine = hercules | cga | tandy | vga''')
:The type of machine (specifically the type of graphics hardware) DOSBox tries to emulate.
:The default value is svga_s3 ''(machine=svga_s3)'' (was previously vga)
:Definitions are as follows:

<div id="svga_s3"></div>
::'''svga_s3''' ('''vga''' on DOSBox 0.71 and 0.72) is ''SVGA (Super Video Graphics Array)'': A loose standard designed to allow graphics modes superior to that of VGA. This option emulates an S3 Trio64, one of the most compatible SVGA cards, supporting 256 colors at up to 1600x1200 and full (32- or 24-bit) color at up to 1024x768. It is nearly 100% backwards compatible with VGA, and thus is backwards compatible with EGA and CGA (except 16-color composite mode). It is not backwards compatible with special Tandy, PCjr or Hercules Monochrome graphics modes.
::<small>(info taken from http://ipggi.wordpress.com/2008/03/16/dosbox-graphic-and-machine-emulation-cga-vga-tandy-pcjr-hercules/ and http://www.datasheetarchive.com/S3%20TRIO%2064-datasheet.html)</small>
::<br/>
<div id="vgaonly"></div>
:: '''vgaonly''' ('''vga''' on DOSBox 0.70 and previous) is ''VGA (Video Graphics Array)'': IBM's graphics system introduced with the PS/2. True VGA supports 16 colors at 640x480 resolution, or 256 colors at 320x200 resolution (and not 256 colors at 640x480, even though many people think it does). VGA colors are chosen from a palette of 262,144 colors (not 16.7 million) because VGA uses 6 bits to specify each color, instead of the 8 that is the standard today.
::<small>(info taken from http://www.pcguide.com/ref/video/stdVGA-c.html. See also [[wikipedia:Video Graphics Array]] and http://members.chello.at/theodor.lauppert/games/vga.htm)</small>
::<br/>
<div id="CGA"></div>
::'''CGA''' (''Color Graphics Adapter''): Refers to IBM's first color graphics card. The CGA supports several different modes; the highest quality text mode is 80x25 characters in 16 colors. Graphics modes range from monochrome at 640x200 (which is worse than the Hercules card) to 16 colors at 160x200 in composite mode. However, for gaming, by far the most common mode was 4 colors at 320×200 pixels. While various hacks allowed substitution of one of the 16 colors above, there were only two official palettes for this mode:
::*Magenta, cyan, white and background color (black by default). (much more common for gaming)
::*Red, green, brown and background color (black by default). (Can sometimes be selected as an alternate on some games).
::Note that SVGA fully supports most CGA modes (except the 16-color composite mode), so you should be able to leave DosBox in SVGA mode and play most CGA games.
::<small>(info taken from [[wikipedia:Color Graphics Adapter]], http://www.pcguide.com/ref/video/stdCGA-c.html, and http://members.chello.at/theodor.lauppert/games/cga.htm)</small>
::<br/>
<div id="Tandy"></div>
::'''Tandy''': Refers to the additional graphics modes available on a Tandy 1000 or PCjr, which included 160x100x16, 160x200x16, 320x200x16, and 640x200x4. The Tandy RL/SL/TL series also added a 640x200x16 mode. Also backwards compatible with CGA, except for 16-color composite mode.
::<small>(info taken from http://www.mobygames.com/attribute/sheet/attributeId,31/)</small>
::<br/>
<div id="PCjr"></div>
::'''PCjr''': Refers not to a graphics mode but an entire system developed by IBM, and the company's first attempt at a home computer. Its graphics modes are identical to that of the Tandy, but it is not 100% compatible with any other IBM computer. Allows the user to boot cartridge files specifically designed for this system (.jrc).
::<small>(infofrom [[wikipedia:IBM PCjr]] and www.dosbox.com/DOSBoxManual.html)</small><br/>
<div id="Hercules"></div>
::'''Hercules''': Refers to a graphics card developed by Hercules Computer Technology as a competitor to CGA for monochrome monitors. Hercules systems generate both high-resolution text and graphics. The resolution is 720 by 348 and only a two colors (foreground and background) are supported.
::<small>(info taken from http://www.webopedia.com/TERM/H/Hercules_graphics.html and [[wikipedia:Hercules Graphics Card]])</small>
::<br/>
<div id="EGA"></div>
::'''EGA''' (''Enhanced Graphics Adapter''): Refers to a graphics card developed by IBM between the CGA and VGA, and thus has capabilities between the two. It supports 16 colors at a time from a set of 64 possible in resolutions up to 640x350. It also supports all the color modes of CGA except 16-color composite mode. This mode is rarely needed as VGA and SVGA can handle all the same modes.
::<small>(info taken from [[wikipedia:Enhanced Graphics Adapter]])</small>
::<br/>
::Aditional SVGA modes (only necessary if '''svga_s3''' doesn't work.)
<div id="vesa_oldvbe"></div>
::*'''vesa_oldvbe''' the same as svga_s3, but uses a lower version of VESA (1.3), the code used to interface with SVGA cards. This is necessary for some older SVGA programs.
<div id="vesa_nolfb"></div>
::*'''vesa_nolfb''' the same as svga_s3 introduces a no-line frame buffer hack. Sometimes runs faster than plain svga_s3. Only needed in a few games due to either a bug in DOSBox or the line-frame buffer mode of the game.
<div id="svga_paradise"></div>
::*'''svga_paradise''' emulates the Paradise PVGA1A and is only capable of the SVGA resolutions of 256 colors at 640×480 and 16 colors at 800×600. Like all SVGA modes, it is nearly 100% backwards compatible with VGA.
<div id="svga_et3000"></div>
::*'''svga_et3000''' emulates the Tseng Labs ET3000, which can handle everything the Paradise card can plus 256 colors at 800×600 and 16 colors at 1024×768.
<div id="svga_et4000"></div>
::*'''svga_et4000''' emulates the Tseng Labs ET4000, which is the same as the ET3000 except it can also handle 256 colors at 1024×768.
::<small>(info taken from http://ipggi.wordpress.com/2008/03/16/dosbox-graphic-and-machine-emulation-cga-vga-tandy-pcjr-hercules/)</small>

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

Configuration:DOSBox

2018-10-02T00:27:25Z

Collector:

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

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

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

<div id="machine"></div>
;machine = hercules | cga | tandy | cga | tandy | pcjr | ega | vgaonly | svga_s3 | svga_et3000 | svga_et4000 | svga_paradise | vesa_nolfb | vesa_oldvbe
:(since 0.73)
:(previously '''machine = hercules | cga | tandy | vga''')
:The type of machine (specifically the type of graphics hardware) DOSBox tries to emulate.
:The default value is svga_s3 ''(machine=svga_s3)'' (was previously vga)
:Definitions are as follows:

<div id="svga_s3"></div>
::'''svga_s3''' ('''vga''' on DOSBox 0.71 and 0.72) is ''SVGA (Super Video Graphics Array)'': A loose standard designed to allow graphics modes superior to that of VGA. This option emulates an S3 Trio64, one of the most compatible SVGA cards, supporting 256 colors at up to 1600x1200 and full (32- or 24-bit) color at up to 1024x768. It is nearly 100% backwards compatible with VGA, and thus is backwards compatible with EGA and CGA (except 16-color composite mode). It is not backwards compatible with special Tandy, PCjr or Hercules Monochrome graphics modes.
::<small>(info taken from http://ipggi.wordpress.com/2008/03/16/dosbox-graphic-and-machine-emulation-cga-vga-tandy-pcjr-hercules/ and http://www.datasheetarchive.com/S3%20TRIO%2064-datasheet.html)</small>
::<br/>
<div id="vgaonly"></div>
:: '''vgaonly''' ('''vga''' on DOSBox 0.70 and previous) is ''VGA (Video Graphics Array)'': IBM's graphics system introduced with the PS/2. True VGA supports 16 colors at 640x480 resolution, or 256 colors at 320x200 resolution (and not 256 colors at 640x480, even though many people think it does). VGA colors are chosen from a palette of 262,144 colors (not 16.7 million) because VGA uses 6 bits to specify each color, instead of the 8 that is the standard today.
::<small>(info taken from http://www.pcguide.com/ref/video/stdVGA-c.html. See also [[wikipedia:Video Graphics Array]] and http://members.chello.at/theodor.lauppert/games/vga.htm)</small>
::<br/>
<div id="CGA"></div>
::'''CGA''' (''Color Graphics Adapter''): Refers to IBM's first color graphics card. The CGA supports several different modes; the highest quality text mode is 80x25 characters in 16 colors. Graphics modes range from monochrome at 640x200 (which is worse than the Hercules card) to 16 colors at 160x200 in composite mode. However, for gaming, by far the most common mode was 4 colors at 320×200 pixels. While various hacks allowed substitution of one of the 16 colors above, there were only two official palettes for this mode:
::*Magenta, cyan, white and background color (black by default). (much more common for gaming)
::*Red, green, brown and background color (black by default). (Can sometimes be selected as an alternate on some games).
::Note that SVGA fully supports most CGA modes (except the 16-color composite mode), so you should be able to leave DosBox in SVGA mode and play most CGA games.
::<small>(info taken from [[wikipedia:Color Graphics Adapter]], http://www.pcguide.com/ref/video/stdCGA-c.html, and http://members.chello.at/theodor.lauppert/games/cga.htm)</small>
::<br/>
<div id="Tandy"></div>
::'''Tandy''': Refers to the additional graphics modes available on a Tandy 1000 or PCjr, which included 160x100x16, 160x200x16, 320x200x16, and 640x200x4. The Tandy RL/SL/TL series also added a 640x200x16 mode. Also backwards compatible with CGA, except for 16-color composite mode.
::<small>(info taken from http://www.mobygames.com/attribute/sheet/attributeId,31/)</small>
::<br/>
<div id="PCjr"></div>
::'''PCjr''': Refers not to a graphics mode but an entire system developed by IBM, and the company's first attempt at a home computer. Its graphics modes are identical to that of the Tandy, but it is not 100% compatible with any other IBM computer. Allows the user to boot cartridge files specifically designed for this system (.jrc).
::<small>(infofrom [[wikipedia:IBM PCjr]] and www.dosbox.com/DOSBoxManual.html)</small><br/>
<div id="Hercules"></div>
::'''Hercules''': Refers to a graphics card developed by Hercules Computer Technology as a competitor to CGA for monochrome monitors. Hercules systems generate both high-resolution text and graphics. The resolution is 720 by 348 and only a two colors (foreground and background) are supported.
::<small>(info taken from http://www.webopedia.com/TERM/H/Hercules_graphics.html and [[wikipedia:Hercules Graphics Card]])</small>
::<br/>
<div id="EGA"></div>
::'''EGA''' (''Enhanced Graphics Adapter''): Refers to a graphics card developed by IBM between the CGA and VGA, and thus has capabilities between the two. It supports 16 colors at a time from a set of 64 possible in resolutions up to 640x350. It also supports all the color modes of CGA except 16-color composite mode. This mode is rarely needed as VGA and SVGA can handle all the same modes.
::<small>(info taken from [[wikipedia:Enhanced Graphics Adapter]])</small>
::<br/>
::Aditional SVGA modes (only necessary if '''svga_s3''' doesn't work.)
::*'''vesa_oldvbe''' the same as svga_s3, but uses a lower version of VESA (1.3), the code used to interface with SVGA cards. This is necessary for some older SVGA programs.
::*'''vesa_nolfb''' the same as svga_s3 introduces a no-line frame buffer hack. Sometimes runs faster than plain svga_s3. Only needed in a few games due to either a bug in DOSBox or the line-frame buffer mode of the game.
::*'''svga_paradise''' emulates the Paradise PVGA1A and is only capable of the SVGA resolutions of 256 colors at 640×480 and 16 colors at 800×600. Like all SVGA modes, it is nearly 100% backwards compatible with VGA.
::*'''svga_et3000''' emulates the Tseng Labs ET3000, which can handle everything the Paradise card can plus 256 colors at 800×600 and 16 colors at 1024×768.
::*'''svga_et4000''' emulates the Tseng Labs ET4000, which is the same as the ET3000 except it can also handle 256 colors at 1024×768.
::<small>(info taken from http://ipggi.wordpress.com/2008/03/16/dosbox-graphic-and-machine-emulation-cga-vga-tandy-pcjr-hercules/)</small>

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

Configuration:DOSBox

2018-10-02T00:24:16Z

Collector:

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

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

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

<div id="machine"></div>
;machine = hercules | cga | tandy | cga | tandy | pcjr | ega | vgaonly | svga_s3 | svga_et3000 | svga_et4000 | svga_paradise | vesa_nolfb | vesa_oldvbe
:(since 0.73)
:(previously '''machine = hercules | cga | tandy | vga''')
:The type of machine (specifically the type of graphics hardware) DOSBox tries to emulate.
:The default value is svga_s3 ''(machine=svga_s3)'' (was previously vga)
:Definitions are as follows:

::'''svga_s3''' ('''vga''' on DOSBox 0.71 and 0.72) is ''SVGA (Super Video Graphics Array)'': A loose standard designed to allow graphics modes superior to that of VGA. This option emulates an S3 Trio64, one of the most compatible SVGA cards, supporting 256 colors at up to 1600x1200 and full (32- or 24-bit) color at up to 1024x768. It is nearly 100% backwards compatible with VGA, and thus is backwards compatible with EGA and CGA (except 16-color composite mode). It is not backwards compatible with special Tandy, PCjr or Hercules Monochrome graphics modes.
::<small>(info taken from http://ipggi.wordpress.com/2008/03/16/dosbox-graphic-and-machine-emulation-cga-vga-tandy-pcjr-hercules/ and http://www.datasheetarchive.com/S3%20TRIO%2064-datasheet.html)</small>
::<br/>
:: '''vgaonly''' ('''vga''' on DOSBox 0.70 and previous) is ''VGA (Video Graphics Array)'': IBM's graphics system introduced with the PS/2. True VGA supports 16 colors at 640x480 resolution, or 256 colors at 320x200 resolution (and not 256 colors at 640x480, even though many people think it does). VGA colors are chosen from a palette of 262,144 colors (not 16.7 million) because VGA uses 6 bits to specify each color, instead of the 8 that is the standard today.
::<small>(info taken from http://www.pcguide.com/ref/video/stdVGA-c.html. See also [[wikipedia:Video Graphics Array]] and http://members.chello.at/theodor.lauppert/games/vga.htm)</small>
::<br/>
::'''CGA''' (''Color Graphics Adapter''): Refers to IBM's first color graphics card. The CGA supports several different modes; the highest quality text mode is 80x25 characters in 16 colors. Graphics modes range from monochrome at 640x200 (which is worse than the Hercules card) to 16 colors at 160x200 in composite mode. However, for gaming, by far the most common mode was 4 colors at 320×200 pixels. While various hacks allowed substitution of one of the 16 colors above, there were only two official palettes for this mode:
::*Magenta, cyan, white and background color (black by default). (much more common for gaming)
::*Red, green, brown and background color (black by default). (Can sometimes be selected as an alternate on some games).
::Note that SVGA fully supports most CGA modes (except the 16-color composite mode), so you should be able to leave DosBox in SVGA mode and play most CGA games.
::<small>(info taken from [[wikipedia:Color Graphics Adapter]], http://www.pcguide.com/ref/video/stdCGA-c.html, and http://members.chello.at/theodor.lauppert/games/cga.htm)</small>
::<br/>
::'''Tandy''': Refers to the additional graphics modes available on a Tandy 1000 or PCjr, which included 160x100x16, 160x200x16, 320x200x16, and 640x200x4. The Tandy RL/SL/TL series also added a 640x200x16 mode. Also backwards compatible with CGA, except for 16-color composite mode.
::<small>(info taken from http://www.mobygames.com/attribute/sheet/attributeId,31/)</small>
::<br/>
::'''PCjr''': Refers not to a graphics mode but an entire system developed by IBM, and the company's first attempt at a home computer. Its graphics modes are identical to that of the Tandy, but it is not 100% compatible with any other IBM computer. Allows the user to boot cartridge files specifically designed for this system (.jrc).
::<small>(infofrom [[wikipedia:IBM PCjr]] and www.dosbox.com/DOSBoxManual.html)</small>
::'''Hercules''': Refers to a graphics card developed by Hercules Computer Technology as a competitor to CGA for monochrome monitors. Hercules systems generate both high-resolution text and graphics. The resolution is 720 by 348 and only a two colors (foreground and background) are supported.
::<small>(info taken from http://www.webopedia.com/TERM/H/Hercules_graphics.html and [[wikipedia:Hercules Graphics Card]])</small>
::<br/>
::'''EGA''' (''Enhanced Graphics Adapter''): Refers to a graphics card developed by IBM between the CGA and VGA, and thus has capabilities between the two. It supports 16 colors at a time from a set of 64 possible in resolutions up to 640x350. It also supports all the color modes of CGA except 16-color composite mode. This mode is rarely needed as VGA and SVGA can handle all the same modes.
::<small>(info taken from [[wikipedia:Enhanced Graphics Adapter]])</small>
::<br/>
::Aditional SVGA modes (only necessary if '''svga_s3''' doesn't work.)
::*'''vesa_oldvbe''' the same as svga_s3, but uses a lower version of VESA (1.3), the code used to interface with SVGA cards. This is necessary for some older SVGA programs.
::*'''vesa_nolfb''' the same as svga_s3 introduces a no-line frame buffer hack. Sometimes runs faster than plain svga_s3. Only needed in a few games due to either a bug in DOSBox or the line-frame buffer mode of the game.
::*'''svga_paradise''' emulates the Paradise PVGA1A and is only capable of the SVGA resolutions of 256 colors at 640×480 and 16 colors at 800×600. Like all SVGA modes, it is nearly 100% backwards compatible with VGA.
::*'''svga_et3000''' emulates the Tseng Labs ET3000, which can handle everything the Paradise card can plus 256 colors at 800×600 and 16 colors at 1024×768.
::*'''svga_et4000''' emulates the Tseng Labs ET4000, which is the same as the ET3000 except it can also handle 256 colors at 1024×768.
::<small>(info taken from http://ipggi.wordpress.com/2008/03/16/dosbox-graphic-and-machine-emulation-cga-vga-tandy-pcjr-hercules/)</small>

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

Configuration:SDL

2018-10-02T00:22:35Z

Collector:

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

<div id="fullscreen"></div>
;fullscreen = true | false
:Start DOSBox directly in fullscreen.
:Default is false.

<div id="fulldouble"></div>
;fulldouble = true | false
:Use double buffering in fullscreen. See [http://en.wikipedia.org/wiki/Multiple_buffering]
:Default is false.

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

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

;output = surface | overlay | opengl | openglnb | ddraw
:What to use for output. Surface does not support scaling or aspect correction. More information here: [http://www.vogons.org/viewtopic.php?=&p=102291]
:Default is surface.
<div id="autolock"></div>
;autolock = true | false
:Mouse will automatically lock, if you click on the screen.
:Default is true.
<div id="sensitivity></div>
;sensitivity = 1..1000
:Mouse sensitivity.
:Default is 100.

<div id="waitonerror"></div>
;waitonerror = true | false
:Wait before closing the console if DOSBox has an error.
:Default is true.

<div id="priority"></div>
;priority = ''when-focused'',''when-minimzed''
:Priority levels for DOSBox. Second entry behind the comma is for when DOSBox is not focused/minimized. Valid priorities are: lowest, lower, normal, higher, highest, and pause.
:Default is higher,normal.

<div id="mapperfile"></div>
;mapperfile = ''path-to-mapper-file''
:File used to load/save the key/event mappings from.
:Default is mapper-<version>.txt.

<div id="usescancodes"></div>
;usescancodes = true | false
:Avoid usage of symkeys, might not work on all operating systems.
:Default is true.

Configuration:SDL

2018-10-02T00:21:07Z

Collector:

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

<div id="fullscreen"></div>
;fullscreen = true | false
:Start DOSBox directly in fullscreen.
:Default is false.

<div id="fulldouble"></div>
;fulldouble = true | false
:Use double buffering in fullscreen. See [http://en.wikipedia.org/wiki/Multiple_buffering]
:Default is false.

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

<div id="windowresolution"></div>
;windowresolution = ''width'' x ''height'' | original | desktop
:Scale the window to this size IF the output device supports hardware scaling (i.e. any output other than surface). Original is the game's default or chosen (through setup.exe or in-game menu) resolution. Note: the scaler setting under [render] is also able to scale up the original resolution to some degree. Those changes are performed before any scaling done with windowresolution setting.
:Default is original.
<div id="output"></div>
;output = surface | overlay | opengl | openglnb | ddraw
:What to use for output. Surface does not support scaling or aspect correction. More information here: [http://www.vogons.org/viewtopic.php?=&p=102291]
:Default is surface.
<div id="autolock">
;</div>autolock = true | false
:Mouse will automatically lock, if you click on the screen.
:Default is true.
<div id="sensitivity></div>
;sensitivity = 1..1000
:Mouse sensitivity.
:Default is 100.

<div id="waitonerror"></div>
;waitonerror = true | false
:Wait before closing the console if DOSBox has an error.
:Default is true.

<div id="priority"></div>
;priority = ''when-focused'',''when-minimzed''
:Priority levels for DOSBox. Second entry behind the comma is for when DOSBox is not focused/minimized. Valid priorities are: lowest, lower, normal, higher, highest, and pause.
:Default is higher,normal.

<div id="mapperfile"></div>
;mapperfile = ''path-to-mapper-file''
:File used to load/save the key/event mappings from.
:Default is mapper-<version>.txt.

<div id="usescancodes"></div>
;usescancodes = true | false
:Avoid usage of symkeys, might not work on all operating systems.
:Default is true.

Configuration:SDL

2018-10-02T00:19:05Z

Collector:

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

<div id="fullscreen"></div>
;fullscreen = true | false
:Start DOSBox directly in fullscreen.
:Default is false.

<div id="fulldouble></div>
;fulldouble = true | false
:Use double buffering in fullscreen. See [http://en.wikipedia.org/wiki/Multiple_buffering]
:Default is false.

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

<div id="windowresolution></div>
;windowresolution = ''width'' x ''height'' | original | desktop
:Scale the window to this size IF the output device supports hardware scaling (i.e. any output other than surface). Original is the game's default or chosen (through setup.exe or in-game menu) resolution. Note: the scaler setting under [render] is also able to scale up the original resolution to some degree. Those changes are performed before any scaling done with windowresolution setting.
:Default is original.
<div id="output"></div>
;output = surface | overlay | opengl | openglnb | ddraw
:What to use for output. Surface does not support scaling or aspect correction. More information here: [http://www.vogons.org/viewtopic.php?=&p=102291]
:Default is surface.
<div id="autolock">
;</div>autolock = true | false
:Mouse will automatically lock, if you click on the screen.
:Default is true.
<div id="sensitivity></div>
;sensitivity = 1..1000
:Mouse sensitivity.
:Default is 100.

<div id="waitonerror></div>
;waitonerror = true | false
:Wait before closing the console if DOSBox has an error.
:Default is true.

<div id="priority></div>
;priority = ''when-focused'',''when-minimzed''
:Priority levels for DOSBox. Second entry behind the comma is for when DOSBox is not focused/minimized. Valid priorities are: lowest, lower, normal, higher, highest, and pause.
:Default is higher,normal.

<div id="mapperfile></div>
;mapperfile = ''path-to-mapper-file''
:File used to load/save the key/event mappings from.
:Default is mapper-<version>.txt.

<div id="usescancodes></div>
;usescancodes = true | false
:Avoid usage of symkeys, might not work on all operating systems.
:Default is true.

User:Collector

2018-07-16T18:50:18Z

Collector: Created page with "I am Andrew Branscom, owner and creator of [http://sierrahelp.com/ The Sierra Help Pages], the largest Sierra On-Line tech site on the net. I am known as Collector in the Sier..."

I am Andrew Branscom, owner and creator of [http://sierrahelp.com/ The Sierra Help Pages], the largest Sierra On-Line tech site on the net. I am known as Collector in the Sierra and gaming communities.

GAMES:Robin Hood: Conquests of the Longbow

2012-04-08T06:43:28Z

Collector:

{{Infobox Game
|title=Robin Hood: Conquests of the Longbow
|developer=Sierra On-Line, Inc.
|publisher=Sierra On-Line, Inc.
|released=1991
|status=Perfect
|executable='''SCIDHUV.EXE'''
|installer='''INSTALL.EXE'''
|setup='''INSTALL.EXE'''}}

Sierra's ''Robin Hood: Conquests of the Longbow'' works perfectly on DOSBox 0.72 running on Windows Vista Home Premium.

GAMES:Robin Hood: Conquests of the Longbow

2012-04-08T06:41:24Z

Collector:

{{Infobox Game
|title=Robin Hood: Conquests of the Longbow
|developer=Sierra On-Line, Inc.
|publisher=Sierra On-Line, Inc.
|released=1991
|status=Perfect
|executable='''SCIDHUV.EXE or ROBIN.BAT or SIERRA.bat, the .bat files simply executes SCIDHUV.EXE'''
|installer='''INSTALL.EXE'''
|Setup='''INSTALL.EXE'''}}

Sierra's ''Robin Hood: Conquests of the Longbow'' works perfectly on DOSBox 0.72 running on Windows Vista Home Premium.

GAMES:Lords of the Realm II

2012-04-08T06:34:34Z

Collector:

Lords of the Realms II, a strategic game combinig (fantastic!) turn-based strategic organization of the realm and real-time battles and sieges (here one notices the age of the game...), works perfectly with DOSBox 0.70, with sounds, music and speech. Just perfect!

To play without CD, install the game through DOSBox, copy the FILES folder from the CD to the installed folder and edit the cdpath= entry in the LORDS2.INI to cdpath=C:\FILES (if you have the game's folder mounted as C:. To force the game to use the high resolution versions of the SMK cut scenes, replace the contents of the SMK_LOW folder with that of the SMK_HIGH.

GAMES:Laura Bow 2: The Dagger of Amon Ra

2012-04-08T06:19:29Z

Collector:

Found to function both on Windows Vista (x64) and Mac OS X.

Be sure to setup the correct audio hardware with INSTALL.EXE or manually edit the RESOURCE.CFG.

Talk:GAMES:Laura Bow 2: The Dagger of Amon Ra

2012-04-08T06:17:12Z

Collector: Created page with ""On Windows 7, there appears to be an issue with MIDI playback, where the incorrect MIDI patches are played (tubular bells where there should be a brass ensemble, for example)..."

"On Windows 7, there appears to be an issue with MIDI playback, where the incorrect MIDI patches are played (tubular bells where there should be a brass ensemble, for example)."

This would be because the wrong sound driver was was specified in the RESOURCE.CFG file, probably the MT-32 driver (the default) was selected without an MT-32 unit.

GAMES:King's Quest V: Absence Makes the Heart Go Yonder!

2012-04-08T06:12:11Z

Collector:

Works in DOSBox 0.73.

Note that if there is not an absolute path set for the RESOURCE.CFG in the autoexec section or batch file, the game will complain that there is no room for save games, i.e., if the game's folder is mounted as C:\ then start the game with:

SIERRA.EXE C:\RESOURCE.CFG

GAMES:King's Quest: Quest for the Crown

2012-04-08T06:03:40Z

Collector:

'''King's Quest''' (both the original version and the enhanced remake) works fine under DOSBox 0.72, but you can get enhanced sound from the original version by changing your dosbox.conf file to emulate a Tandy computer.

The 1987 version and enhanced remake (1990) was compatible with DOS:
[dosbox]
machine=tandy

The 1984 version was distributed with a PC Booter disk that overrode the operating system:
[dosbox]
machine=cga

[autoexec]
mount c C:\KQ1
boot KQ.img

GAMES:Jones in the Fast Lane

2012-04-08T05:59:36Z

Collector:

Both floppy and CD-ROM versions work in DOSBox 0.74. Some extra steps are required to get the digital audio on the CD-ROM version to work.

The SoundBlaster driver from the CD-ROM version of the game will not initialize if a CD-ROM drive has not been mounted with low level support. Also, the GOSiERRA SoundBlaster patcher will not work with this driver. The SB driver from ''Mixed-up Mother Goose'' SCI1 Enhanced CD-ROM (not the later SCI32 version ''Mixed-up Mother Goose Deluxe''), AUDBLASX.DRV, can be exchanged for the AUDBLAST.DRV that shipped with the Jones CD. Either rename the driver or adjust it in the RESOURCE.CFG. The GOSiERRA SoundBlaster patcher does not work with this driver, either, so the game will have to be started with no more than 5000 to 6000 cycles, normal core.

The SHP installer allows for full hard drive instillation and includes a manually patched SB driver that does not require the CD to be mounted nor does it have to have the cycles set so low. It works with both floppy and CD versions.

http://sierrahelp.com/Patches-Updates/NewSierraInstallers.html#J

GAMES:Jones in the Fast Lane

2012-04-08T04:27:44Z

Collector: Created page with "Both floppy and CD-ROM versions work in DOSBox 0.74. Some extra steps are required to get the digital audio on the CD-ROM version to work. The SoundBlaster driver from the CD..."

Both floppy and CD-ROM versions work in DOSBox 0.74. Some extra steps are required to get the digital audio on the CD-ROM version to work.

The SoundBlaster driver from the CD-ROM version of the game will not initialize if a CD-ROM drive has not been mounted with low level support. Also, the GOSiERRA SoundBlaster patcher will not work with this driver. The SB driver from ''Mixed-up Mother Goose'' SCI1.1 Enhanced CD-ROM (not the later SCI32 version ''Mixed-up Mother Goose Deluxe''), AUDBLASX.DRV, can be exchanged for the AUDBLAST.DRV that shipped with the Jones CD. Either rename the driver or adjust it in the RESOURCE.CFG. The GOSiERRA SoundBlaster patcher does not work with this driver, either, so the game will have to be started with no more than 5000 to 6000 cycles, normal core.

The SHP installer allows for full hard drive instillation and includes a manually patched SB driver that does not require the CD to be mounted nor does it have to have the cycles set so low. It works with both floppy and CD versions.

http://sierrahelp.com/Patches-Updates/NewSierraInstallers.html#J

GAMES:Gold Rush!

2012-04-08T03:49:48Z

Collector:

Video works. Audio does not begin until after the intro starts. This is normal.

GAMES:Gold Rush!

2012-04-08T03:49:16Z

Collector:

Video works. Audio does not begin until after the intro starts.

GAMES:Black Cauldron

2012-04-08T03:41:58Z

Collector:

'''Black Cauldron''' works fine under DOSBox 0.72, but you can get enhanced sound from the original version by changing your dosbox.conf file to emulate a Tandy computer.

The 1987 version was compatible with DOS:
[dosbox]
machine=tandy

The 1985 version was distributed with a PC Booter disk that overrode the operating system:
[dosbox]
machine=cga

[autoexec]
echo PRESS CTRL F4 TO CHANGE FLOPPIES
boot BC-1.img BC-2.img

Building DOSBox with MinGW

2010-11-29T22:24:27Z

Collector: /* Example for Building DosBOX 7.1 on OpenSUSE 10.2 Linux */

== Building your own version of DOSBox ==

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

=== 1. Grab the source ===

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

Download it and extract it to a separate directory.

=== 2. SDL ===

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

: http://www.libsdl.org/

and extract to a separate directory.

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

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

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

=== 3. Compiling environment ===

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

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

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

=== 4. Compiling SDL ===

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

./configure
make
make install

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

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

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

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

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

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

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

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

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

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

=== 5. Compiling DOSBox ===

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

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

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

./configure
make

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

=== 6. Running ===

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

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

-Remove the existing DOSBox version if you have it.

-Obtain and extract the DOSBox source code.

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

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

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

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

GAMES:EcoQuest: The Search for Cetus

2010-11-16T05:45:20Z

Collector: Corrected information about MPC version of game.

Ecoquest: The Search for Cetus is an educational adventure game produced by Sierra Entertainment. It is definitely kid-friendly and runs quite well on DOSbox. The CD-ROM version needs to have the correct path to the game's resources in the RESOURCE.CFG for the speech to be heard. Install the game within DOSBox with both a C: drive and a CD-ROM drive mounted or manually edit the RESOURCE.CFG to point to the correct path. You can also use the new installer to set it up automatically http://sierrahelp.com/Patches-Updates/NewSierraInstallers.html#EcoQ1