Usage

SVN-specific manuals | Main | Usage | MB6 Patches
Official manuals | README | Video Instructions

USAGE
Refer to the official manual for more information.

CONTENTS

1. GENERAL USAGE
2. SPECIAL KEYS
3. PARAMETERS
4. DOS COMMANDS
5. SAVE STATES
6. USER INTERFACE
7. GLIDE EMULATION
8. DIRECT3D
9. OPENGL-HQ
10. DONGLE SUPPORT
11. DOSBOX-X BRANCH

GENERAL USAGE
For Windows users:
DOSBox SVN-Daum for Windows can be installed by using the installer or by unzipping files from an archive.
Using the installer (setup.exe) is recommended. After the installer has copied files or the files are unzipped, run DOSBox SVN-Daum.
On the Main menu, click Quick Launch and select any executable(*.exe, *.com or *.bat) to run.
To drag and drop the executable onto the main window is also supported.

For Linux users:
DOSBox SVN-Daum for Linux was confirmed to work on Ubuntu and can be installed by unzipping files from an archive.
After the files are unzipped, double click "dosbox" or enter "./dosbox" in Terminal. (Check the file execute permission)

For OS X users:
DOSBox SVN-Daum for OS X was confirmed to work on OS X Mavericks and can be installed by unzipping files from an archive.
After the files are unzipped, double click "dosbox" or type "./dosbox" in Terminal. (Check the file execute permission)

For all users:
Additional configuration may be required for specific games to properly work. (e.g, CD-ROM drive support or the removal of EMS memory manager)
This operation can be performed on the GUI or commandline in advance. For details, refer to the Troubleshooting section from the official manual.
In order to disable the automatic mount, open the configuration file and set automount=false under [dos] section.

Tools:
Some tools are provided in the TOOLS directory. Currently only for Windows.

- Run DOSBox configuration.bat : Open the configuration file with Notepad. If the file cannot be found, a new configuration file is autoatically created.
- Reset DOSBox configuration.bat : Remove the existing configuration file and create a new configuration file with default settings.
- Reset DOSBox mapper.bat : Remove the existing mapper file and create a new mapper file with default settings.
- Read manuals.bat : View DOSBox manuals.
- Install movie codec.bat : Install/uninstall ZMBV movie codec to allow users to edit and watch movies captured by DOSBox.
- Run DOSBox without GUI.bat : Run DOSBox without GUI.
- Run DOSBox with DirectX driver.bat : Run DOSBox with DirectX driver. Can help to solve hardware or software compatibilty problems.
- Run DOSBox (noconsole).bat : Run DOSBox without console. (not recommended)
- Run DOSBox with Secondary Display.bat : Enable secondary display with color mode selection. (amber, green or white)
- Open Screenshots & Recordings.bat : Open CAPTURE folder for screenshots and recordings.
- Open Saves.bat : Open SAVE folder for saved slots.

General notes:

- Using a configuration file created with an older version of DOSBox may cause unexpected behavior.
- Switching the video output too frequently can make DOSBox unstable. (Windows only)
- Hardware scalers(hardware_none, hardware2x, hardware3x, hardware4x, and hardware5x) do not work with output=surface.
- If DOSBox throws an error saying "DirectX initialization failed.", update the video card driver to the most recent version. (Windows only)
- Disney must be disabled in order to enable the printer emulation. (printer=true, disney=false)
- Disney must be disabled in order to enable the MIDI. (MB6)
- Dongle must be disabled in order to use disney sound. (dongle=false, disney=true, printer=false)
- To enable the MT-32 (MUNT) emulation, any group of the following ROM files are required.
  1) CM32L_CONTROL.ROM, CM32L_PCM.ROM
  2) MT32_Control.ROM, MT32_PCM.ROM
- If DOSBox shows any graphical issues, try to change the settings for linewise, char9, and multiscan. Some utilities such as UNIVBE or S3VBE20 can help to solve the problems.
- If DOSBox throws an error saying "Warning: file creation failed: LPT1", set parallel1=file in the configuration file.
- In order to enable overscan, set the video output to surface.
- The amount of memory that DOSBox can have is up to 512MB. (memsize=512 or memsizekb=524288)
  However, the maximum memory size for saving or loading states is 200MB.
- To enable the xBRZ scaler, the following configuration is required:
  scaler=xbrz, output=surface, fullscreen=true
  This scaler is processed by the Intel TBB which does not support Windows 2000.
- Once DOSBox exposes the following compatibilty issues on Windows, disable the WINDIB driver by running "Run DOSBox with DirectX driver.bat" in TOOLS directory. (Alternatively, on the Video menu, click Driver->Reset DOSBox with DirectX driver forced)
  - Simultaneous shift keys not working
  - Any other issues including unknown crash
  However, the following problems can be expected:
  - Low performance.
  - Frequent blinking.
  - Incapable of using the openglide wrapper.
  - Incapable of unmaximizing the maximized DOSBox window in Direct3D.
  - Incapable of switching the video output between DirectDraw and OpenGL.
- DOSBox debugger is for debugging. For details, refer to a guide to the DOSBox debugger. NOT for the average DOSBox user.
- Installing Windows 95 / 98 as a guest OS inside DOSBox is available while the support for Windows 9x is limited.
  Recommended settings:
  core=dynamic
  cputype=pentium
  glide=emu
  voodoo=auto
  machine=svga_s3
  vmemsize=4
  For more information, refer to the following guides.
  Guide - Windows 95 on DOSBox 0.74 (VOGONS Forum)
  Guide - Windows 98 SE on DOSBox 0.74 (VOGONS Forum)
  NOTE: Please refer to the win9x-drv directory for installing S3 video driver.

Technical details (Windows):

- As for the 64bit build, dynamic core will not be properly supported and OpenGlide wrapper may not be working properly.
- Unlike the official DOSBox versions, DOSBox SVN-Daum for Windows enables the WINDIB driver for several reasons. (Refer to the above general notes section) However, DirectDraw does not work properly with the WINDIB driver. To resolve the issue, DOSBox will automatically set the SDL video driver to DirectX when setting the video output to DirectDraw.
- Microsoft Visual Studio 2013 Update 1 is used for compilation. This build was confirmed to work under Windows 8.1. Added some assember hacks to support Windows 2000.
- This build may not work properly without SSE2 support. Please check the following list.
  List of CPUs with SSE2 support
  - AMD K8-based CPUs (Athlon 64, Sempron 64, Turion 64, etc.)
  - AMD Phenom CPUs
  - Intel NetBurst-based CPUs (Pentium 4, Xeon, Celeron, Celeron D, etc.)
  - Intel Pentium M and Celeron M
  - Intel Core family (including Intel Core 2, Intel Core i5, Intel Core i7)
  - Intel Atom
  - Transmeta Efficeon
  - VIA C7
  - VIA Nano

SPECIAL KEYS
Several experimental patches provide the following additional special keys.

CPU Core-switch (from gulikoza)

- Ctrl - 1 : Normal core
- Ctrl - 2 : Full core
- Ctrl - 3 : Dynamic core
- Ctrl - 4 : Simple core
- Ctrl - = : Maximize the CPU cycles

SVN-Daum features

- Ctrl - Alt - Enter : Show/Hide the menu bar (Windows)
- Alt - F11 : Continuous turbo mode

Save / Load states (from ZenJu)

- Alt - F5 : Save States
- Alt - F6 : Prev Slot
- Alt - F7 : Next Slot
- Alt - F9 : Load States

Redraw Screen (from truth)

- Ctrl - F3 : Redraw DOSBox screen.

Internal UI (from Moe)

- Alt - F10 : Start the internal UI

For the other special keys, refer to the official manual.

PARAMETERS
Several experimental patches provide the following additional parameters.

Usage
dosbox [-nomenu] [-nogui] [-startui] [-nolog] [-showcycles] [-opensaves program] [-display2 (option)] [-disable_numlock_check] [-savedir (path)] [-date_host_forced] [-disable_vga_comp] [-vgmlog] [-disable_share]

- -nomenu
  Hide the menu bar at startup. (Windows only) To show the hidden menu on the fly, press the Ctrl-Alt-Enter.
- -nogui
  Disable the graphical user interface. (Windows only)
- -startui
  Start the internal UI at startup.
- -nolog
  Disable the file logging.
- -showcycles
  Show information about DOSBox's current CPU cycles and FPS on the title bar.
- -opensaves program
  Call program with as first parameter the location of the SAVE folder. (e.g, -opensaves explorer.exe)
- -display2 (option)
  Enable the dual display. The supported color modes are: -display2 "amber", -display2 "green", -display2 "white"
  The dual display is supported by very few software. (e.g., Mah Jongg)
- -disable_numlock_check
  Do not check the status of number lock at startup. (Windows only, useful for DirectX driver)
- -savedir (path)
  Set the default save location for DOSBox state slots. (e.g, -savedir "c:\game\pre2\savedir")
- -date_host_forced
  Force to synchronize the date and time in the guest operating system with the time in the host operating system. Setting the internal date is not allowed during runtime.
- -disable_vga_comp
  Disable the VGA compatibility mode. For example, disable the forced double buffering in the OpenglHQ and allow the OpenGL renderer to enable the pixel_buffer_object. This option can break the video output depending on the type of video card.
- -vgmlog
  Enables DRO logging. (http://vgmrips.net/forum/viewtopic.php?t=410)
- -disable_share
  Disables SHARE feature.

A way to access the above parameters readily is to create a shortcut or to use a script. For other DOSBox parameters, refer to the official manual.

DOS COMMANDS
The following additional commands are provided from a patch called "More parameters support in internal commands" and FreeDOS, and some other patches provided by Moe and h-a-l-9000. These commands are unofficial part of DOSBox.

External commands

- 50.COM, 28.COM : Changes the number of line displayed on shell.
- EDIT.COM : Opens FreeDOS file editor.
- APPEND.EXE : Similar to PATH command.
- COPY.EXE : COPY command with more parameters.
- XCOPY.EXE : Advanced COPY command.
- MOUSE.COM : Enables/disables DOSBox mouse driver. To uninstall it, type "mouse /u". For y-axis reverse, type "mouse /v" (They also can be found in GUI)
- IMGMAKE.COM : Creates a floppy/harddisk (.img) image. (h-a-l-9000) Just type IMGMAKE for more information.
- MOVE.COM : Moves a file or directory to another location
- TREE.EXE : Graphically displays the directory structure of a drive/path.
- FIND.EXE : Print lines of a file that contains a string
- DOS32A.EXE, DOS4GW.EXE : DOS Extenders

Internal commands

- ADDKEY : Generates artifical keypresses. (Moe) [How to use]
  "normal", "simple", "dynamic" and "full" also can be used for switching CPU core. (only supports delay)
- VOL : Views the volume name of disk.
- LABEL : Sets the volume name of disk.
- MORE : Displays output one screen at a time.
- PROMPT : Shows/Changes command prompt. Supports special characters including escape codes.

CONFIG.SYS commands

- LASTDRIV.COM
- FCBS.COM
- DEVICE.COM
- BUFFERS.COM
- FILES can be set in the DOSBox configuration. (h-a-l-9000)

The following commands are official part of DOSBox but include some unofficial changes.

- INTRO command shows the DOSBox introduction that allows users to select one of the help items with arrow keys.
- DIR displays a list of files and subdirectories in a directory with volume label and serial number.
- MEM command is available with some parameters like /C and /P.
- COPY command is provided as a command file in Z drive.

For more information about DOS commands, type "HELP" on prompt.

SAVE STATES

A patch for saving states to memory was provided by ZenJu. For more information, refer to http://vogons.zetafleet.com/viewtopic.php?t=25274.
Saving, loading or removing the states can be performed on the Main menu or with shortcut keys. For the shortcut keys, refer to the section "Special keys" above.
More enhancements have been implemented. (Thanks to tikalat)

USER INTERFACE
Two types of GUI are available in the SVN-Daum build.
Win32 GUI menu
A small GUI menu bar has been integrated for the Windows users.

- Main
- Cpu
- Video
- Sound
- Dos
- Capture
- Drive

Provides basic capabilities for mounting images. Use IMGMOUNT command for more advanced size options with cylinders, heads and sectors specification of the drive. The options are useful for the bootable hard disk images.

Internal UI
The internal user interface is cross-platform compatible and was implemented by Moe. The interface can be started by pressing the Alt-F10 during runtime or by using -startui parameter.
Limitations:
1) Paused mode while in the UI.
2) Does not support any mounting method.

GLIDE EMULATION

Any of the following files must not be in the game directory: glide2x.ovl, glide2x.dll, libglide2x.so or libglide2x.dylib

A couple of options are provided to enable the glide emulation: Glide wrapper and Internal 3dfx Voodoo chipset emulation

- Glide wrapper (glide=true)
  The OpenGlide wrapper patch for DOSBox is maintained by Gulikoza.
  Set glide=true in the configuration file for the glide games.
  On Linux: libglide2x.so is an OpenGlide library required to run the glide games.
  On OS X: libglide2x.dylib is required to run the glide games.
  On Windows: glide2x.dll is required. This file can be manually replaced with another glide wrapper library. On the other hand, some glide wrappers like nGlide automatically put glide2x.dll into the system directory during installation. DOSBox first searches the system directory for the glide wrapper.
  In order to allow the OpenGlide to enable FULLSCREEN for the glide games:
  1. Hit the Alt-Enter to switch the current video mode to fullscreen. Alternatively, set fullscreen=true in the dosbox configuration file.
  2. Run the glide game.
  In order to solve problems using non-OpenGlide wrapper on Windows, follow the below instruction.
  1. Do not replace the existing glide2x.ovl with another.
  2. Hit the Alt-Enter to switch the current mode to fullscreen. Alternatively, set fullscreen=true in the dosbox configuration file.
  3. Run the glide game.

- 3dfx Voodoo chip emulation (glide=emu)
  Kekko's description:
  - higher compatibility with titles (even those with integrated .ovl)
  - portability
  - integration with dosbox internal renderer: full-screen, different output modes and video capture would be supported
  - no need of external libs
  - d3d support for win9x games
  Under [pci] section, specify the mode of the internal voodoo emulation. (voodoo=auto is default)
  voodoo = false | software | auto | opengl
  How to enable the emulation:
  Set glide=emu in the configuration file. The kekko's emulation may result in poor performance because everything is emulated in the software mode by default.
  This is an internal emulation which does not require external glide2x library but only requires glide2x_emu.ovl.
  The support for hardware acceleration is avaiable by setting the video output to OpenGL. (Set voodoo=auto/opengl with output=opengl/openglnb)
  For more information, visit http://vogons.zetafleet.com/viewtopic.php?t=25606

DIRECT3D

Written by gulikoza

New options:
Direct3D output now supports the use of custom pixel shaders for picture scaling.
To use it your card has to support PS2.0 (Radeon >=9500, GeForce >=FX5200) or PS1.4 for scale2x_ps14.fx (Radeon >= 8500).

** These shaders are currently available :
1) General

- point.fx - normal (nearest neighbor) resize
- pilinear.fx - bilinear resize (slightly blurry)
- scale2x.fx - advmame2x resize
- scale2x_ps14.fx - advmame2x resize (PS1.4 version)
- 2xSaI.fx - 2xSaI resize
- 2xSaI_sRGB.fx - 2xSai (Gamma Corrected) resize

2) The following are all modifications of the GLSL shaders for OGL2 PSX plugin. Ported to .fx format by guest(r).
Some of the shaders also have settings you can modify by editing the .fx file.

- GS2x.fx
- GS4x.fx
- GS4xColorFilter.fx
- GS4xFilter.fx
- GS4xScale.fx

3) Other shaders...

** How to enable pixelshader
1. Open dosbox.conf with notepad.
2. Set 'output=direct3d' to enable Direct3D. Follow one of these options.

1. Set 'scaler=hardware2x', 'scaler=hardware3x', 'scaler=hardware4x', or 'scaler=hardware5x'
2. Set 'scaler=none'. Set the values like 640x480 in fullresolution and windowresolution.

3. Then set 'pixelshader=' option to one of the shaders.
When pixel shader is active DOSBox will report it in the console: D3D:Pixel shader output enabled
If you don't get this line then pixel shader effects are not in use.

OPENGL-HQ

Written by Moe

This readme documents version 2012-10-19 of OpenGL-HQ, if you got a later version there's a slim chance I forgot to update this :) The current version and screenshots can be downloaded from http://www.syntax-k.de/projekte/sdl-opengl-hq/

OpenGL-HQ is a video "driver" for SDL that uses your graphics hardware to scale the output to any size you want. It was originally written for 2D games/emulators like dosbox, scummvm or exult.

WARNING:
This is beta quality software. While it works nicely for me and several other people, expect bugs to be present. If something doesn't work, first check for a new version. Please mail me if you encounter anything that's not yet listed in the README.

Features:

- uses your hardware to get fast scaling
- scales any 2D SDL program
- scales with any scaling factor, even fractional ones
- switches back to the native driver if an app tries to use OpenGL
- portable
- configurable like SDL
- see the screenshots at the URL above, really

Requirements:
- a Radeon 9600, GeForce 5700 or higher with current driver; OpenGL extension ARB_fragment_program must be hardware accelerated, EXT_framebuffer_object is recommended
-- Note: Since 2012, the fragment programs may no longer be compatible with an acutal 9600. In case of problems use an older version of *_pass3.fp
- OpenGL-support for your OS in SDL (which means Windows, Linux/X11 or MacOS X)

Limitations:
- may show bad performance with programs that already provide high-resolution output or with high-quality driver settings (Radeon 9600-9800 class chips are driven at their limits)
- might not work with FSAA enabled
- MacOS X untested (but should work)
- it has become very unlikely, but it is still possible that desktop resolution is not autodetected correctly; use SDL_OPENGLHQ_FULLRES in that case
- untested on non-x86 processors/non-mainstream graphics cards, notably embedded/mobile platforms

Bugs unlikely to be fixed, or of unknown origin:
- ATI's Triple-Buffering feature interferes with some apps; if you see lockups or similar, try setting SDL_OPENGLHQ_DOUBLEBUF as shown below
-- needs to be confirmed against current drivers

Bugs to be fixed: none known

If you see any problems, CHECK THE TROUBLESHOOTING SECTION BELOW. If your problem is not solved there, please write as detailed as you can: Tell me what you did (exactly!), what you expected to happen, what happened instead, and include screen shots of the problem. Include any relevant config files as well (dosbox.conf for dosxbox, for example).

How to use (Quickstart):
This is a windows quickstart guide. Other systems adjust as needed.

1) Copy SDL.DLL into the application's directory, overwriting the shipped version
2) Create a batch file (using Notepad) with these contents:

> set SDL_VIDEODRIVER=openglhq
> set SDL_OPENGLHQ_WINRES=800x600
> <name of your application>.exe

3) Save the file as <name of your application>.bat in the same directory as the EXE file is
4) Double-click this batch file to start the application; Create a shortcut or adjust existing shortcuts to use this batch file

Configuration:
Configuration is done via environment variables (just like the rest of SDL). It is recommended to set these options in a batch file (see previous section).

- SDL_VIDEODRIVER - set it to openglhq to use OpenGL-HQ
- SDL_OPENGLHQ_WINRES
- SDL_OPENGLHQ_FULLRES - set to a resolution like "960x720" to set the windowed/fullscreen size in all windowed/fullscreen modes; you may add a bit depth as in "960x720-16"; alternatively, you can specify a fixed scaling factor (like "2.5")
  default: windowed: "1", fullscreen: your desktop resolution
- SDL_OPENGLHQ_VIDEODRIVER - set to the name of your SDL video device (the one you'd normally use for SDL_VIDEODRIVER)
- SDL_OPENGLHQ_DOUBLEBUF - override application's choice of doublebuffering; if set to 1, doublebuffering is always on, if set to 0, doublebuffering is always off; if unset, the application's choice is respected
- SDL_OPENGLHQ_STATIC
- SDL_OPENGLHQ_DYNAMIC - two parameters which tweak the HQ calculation; the defaults (static 10, dynamic 33) are fine in most cases; to optimize rendering, play with these values (static 0-255, dynamic 0-100)
- SDL_OPENGLHQ_SHOWFPS - print average FPS to the console every ten seconds; this only counts frames actually rendered. See FAQ below.
- SDL_OPENGLHQ_DATA - a directory with data files for OpenGL-HQ; You can use this to load your own fragment programs or edge detect table. Currently, you will have to read the source code for details.

You must set SDL_VIDEODRIVER to get any effect at all. If you want windowed applications to be scaled, set SDL_OPENGLHQ_WINRES. Everything else is usually not neccessary, the settings are autodetected.

If you want to set options for ALL SDL apps, you can do so:
Windows: Control Panel -> System Properties -> Advanced -> Environment Variables
Unix-like systems: add "export <name of evironment var>=<value>" to ~/.profile

Performance:
To put it short: Absolutely great. On hardware barely meeting the minimal requirements, running a demanding protected-mode high-resolution SVGA program in DOSBox with frameskip 0 and scaling by a factor of 2, performance drops by just 20%. At frameskip 4, performance difference is at 5-10%.
At VGA resolution scaling by 4, the difference is reduced even more: 12% performance loss at frameskip 0. Software scaling is far worse: Normal2x costs about 20%, advmame2x is at 25%, hq2x (not my optimized version, but the slower HiEnd3D version) about 40%.
Above measurements done on a single-core Athlon 3700+. On a dual-core processor, there is no noticeable speed impact, since OpenGL-HQ uses a second core if available.

Troubleshooting:
Q: Something doesn't work or looks weird.
A: Check that you are running the latest official video drivers. It has not been tested with hacked drivers, and old drivers are known to fail.

Q: DosBox crashes.
A: DosBox has bad error handling at video initialization. Until that's fixed, a crash most probably means your hardware doesn't support OpenGL-HQ.

Q: DosBox locks up when trying to go fullscreen
A: ATI driver issue. Set "fulldouble=false" in your dosbox.conf, or set SDL_OPENGLHQ_DOUBLEBUF

Q: Performance is terrible!
A: You've probably set forced vsync-waiting in Catalsyst Control Center and your app wants double buffering (like "fulldouble=true" in DosBox). On a Radeon 9600-9800 class chip, that's simply too much at higher resolutions. These first fully programmable chips are used to their limits, so that's barely surprising.

Q: It works partly, but some video modes look exactly like before.
Q: Output looks much worse than in your screenshots, blurry and not sharp at all.
Q: WTF? I did everything as shown, and nothing changed?
A: Disable all software scaling in your program. Many emulators default to some kind of scaling, but OpenglHQ can only work with x1 (no) scaling. Moreover, if the program's output is larger than the selected window size, the output is scaled down using traditional bilinear filtering.

Q: My mouse is slow! How can I speed it up?
A: This should mostly be fixed in the last release, but your backend video driver might change acceleration setting when grabbing the mouse. At least the x11 driver does that, and you can configure it using environment variables.

Q: I only get 8 FPS! What crap is this software?
A: The screen is not continuously rendered like in native 3D programs. If the emulator/emulated program only updates the screen 8 times per second, OpenGL-HQ will show just 8 FPS. If you want to test how fast OpenGL-HQ can go on your machine, use a program that does frequent screen updates.

For more help, contact me at info@syntax-k.de. Please DO NOT mail Sam Lantinga or the SDL team about this, they aren't involved in this
in any way at all.

License:
SDL - Simple DirectMedia Layer OpenGL-HQ scaling
Copyright (C) 2005, 2006 2012 Jorg Walter <info@syntax-k.de>

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details.

You should have received a copy of the GNU Library General Public License along with this library; if not, write to the Free Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

The SDL patch uses code published on the SDL mailing list in January 2005 for desktop resolution autodetect.

Credits:
Many thanks to all VOGONS users who assited in testing and providing windows builds. Even more thanks to gulikoza from the VOGONS forums for porting the code to EXT_framebuffer_object.

History:
2012-10-19 fix 15-bit mode; it never worked, which shows how rarely it is used
2012-10-17 (b) fix problems with odd video mode widths
2012-10-17 fix/improve math precision for modern screen resolutions, fix partial screen update bug in (default) fast mode, add optional FPS output
2006-12-15 fix a subtle mouse movemement bug mainly observable in fullscreen apps, improve API compatibility, reduce needless pixel copying, working MacOS X support
2006-11-22 fix 16-bit video modes on ATI cards, improve compilation sequence, improve rendering accuracy and speed by reducing complexity
2006-11-21 use EXT_framebuffer_object extension for rendering, fix threading issues, improve performance, port to SDL-1.2, make 64-bit-clean

DONGLE SUPPORT
This is DosBox handler of 93c46 copy-protection dongle connected to LPT port.
At least Rainbow Sentinel Cplus and MicroPhar are 93c46-based dongles.

93c46 memory chip contain 64*16 words. More on it:
http://www.atmel.com/dyn/resources/prod_documents/doc0172.pdf

Few notes:

* It is unable to detect dongle presence on software side, so, software usually reading some cell (often 0x3F) and check magic value.
* Wiring scheme may differ from dongle to dongle, but usually, DI (data input), SK (clock), CS (chip select) and power lines are taken from D0..D7 in some order.
* DO (data output) may be connected to ACK or BUSY printer lines.

More information: http://blogs.conus.info/node/56

-- dennis@conus.info

DOSBOX-X BRANCH
TheGreatCodeholio provided the following features with his own DOSBox-X branch.

- Accurate PS/2 keyboard emulation, support for scan code sets 1, 2, and 3, emulation and response to LED commands, reset commands, mode changes, and obscure commands
- Gravis Ultrasound panning register fixes
- PS/2 AUX port emulation.
- CGA snow emulation. If you set machine=cga and enable the option, video memory I/O is slowed down to CGA speeds and writes will trigger "snow", just like an actual CGA.
- Sound Blaster "Goldplay" support.
- ISA Plug & Play emulation.
- Serial mouse emulation.
- Higher memory limit to 512MB.
- Finer-grained memory sizes. (kb)
- Refresh rate control.

IDE support
This is basic IDE emulation for both ATA (hard disk) and ATAPI (CD-ROM).
Open the configuration file (e.g., dosbox.conf) to find the following ide sections:

[ide, primary]
[ide, secondary]
[ide, tertiary]
[ide, quaternary]
[ide, quinternary]
[ide, sexternary]
[ide, septernary]
[ide, octernary]

Set enable to true in order to enable each IDE interface.
IMGMOUNT provides the following parameters ("-ide").
-ide 1m - Attach to primary IDE controller as master
-ide 1s - Attach to primary IDE controller as slave
-ide 2m - Attach to secondary IDE controller as master
-ide 2s - Attach to secondary IDE controller as slave
-ide auto - Attach to unused slot (default)
-ide none - Do not attach to IDE port

Also, [autoexec] section in the configuration file can be look like this:
[autoexec]
# C: drive for Win95
imgmount 2 "path_to_hdd_image\hdd.img" -size 512,63,32,512 -t hdd -fs none -ide 1m
# D: drive with Windows 95 install CD-ROM
imgmount D "path_to_cd_image\cd.iso" -t iso -fs iso -ide 2m
# Now start Win95
boot -l c

For more information, visit http://vogons.zetafleet.com/viewtopic.php?t=31881.

SVN-specific manuals | Main | Usage | MB6 Patches
Official manuals | README | Video Instructions