The Wii versions should have version numbers of the form #.##.##, with the original DOSBox version first, followed by the version of the Wii port. In this case 0.72.01. Also the README now includes wii-specific information.

This commit is contained in:
Carl.Kenner 2009-05-10 10:32:50 +00:00
parent f75d73a75f
commit a142aa3d65
3 changed files with 216 additions and 265 deletions

477
README
View File

@ -1,5 +1,37 @@
DOSBox v0.72
DOSBox v0.72.01 (Wii port)
====
WII:
====
Report bugs at: http://code.google.com/p/dosbox-wii/issues/list
You can also view and download the source code from there.
To run homebrew applications, such as this one, on your Wii,
please see http://www.wiibrew.org/wiki/Main_Page
See the wiki for more information:
http://www.wiibrew.org/wiki/DOSBox_Wii
You currently need a USB keyboard to use DOSBox.
The Wii Remote can be used as a mouse by pointing and using the A
and B buttons. The Wii Remote, Nunchuk, Classic Controller and
Gamecube Controller can also be used as a joystick.
HOME will exit back to the homebrew channel, as will the RESET
button on the console.
The C: drive will automatically be mounted to sd:/DOSBox/
The Z: driver is a virtual drive that is part of DOSBox.
Other drives can be mounted using the MOUNT command.
sd: means the SD card, usb: means a USB drive,
carda: and cardb: mean the Gamecube memory cards.
The Wii's DVD drive, and shared folders on the network, can't be
mounted yet in this version.
The configuration is loaded from sd:/DOSBox/dosbox.conf
This file will be created automatically after you start DOSBox.
Please edit it with a text editor to choose settings appropriate
for each game.
=====
NOTE:
@ -40,7 +72,7 @@ INDEX:
Type INTRO in DOSBox for a quick tour.
It is essential that you get familiar with the idea of mounting,
DOSBox does not automatically make any drive (or a part of it)
DOSBox does not automatically make any drive (or parts of it)
accessible to the emulation.
See the FAQ entry "I've got a Z instead of a C at the prompt" as
well as the description of the MOUNT command (section 4).
@ -57,15 +89,14 @@ Q: I've got a Z instead of a C at the prompt.
Q: Do I always have to type these commands? Automation?
Q: How do I change to fullscreen?
Q: My CD-ROM doesn't work.
Q: The game/application can't find its CD-ROM.
Q: The mouse doesn't work.
Q: There is no sound.
Q: The sound stutters or sounds stretched/weird.
Q: I can't type \ or : in DOSBox.
Q: The keyboard lags.
Q: The cursor always moves into one direction!
Q: The game/application can't find its CD-ROM.
Q: The game/application runs much too slow!
Q: The game/application does not run at all/crashes!
Q: Can DOSBox harm my computer?
Q: I would like to change the memory size/cpu speed/ems/soundblaster IRQ.
Q: What sound hardware does DOSBox presently emulate?
@ -103,43 +134,18 @@ Q: My CD-ROM doesn't work.
A: To mount your CD-ROM in DOSBox you have to specify some additional options
when mounting the CD-ROM.
To enable CD-ROM support (includes MSCDEX):
- mount d f:\ -t cdrom (windows)
- mount d /media/cdrom -t cdrom (linux)
In some cases you might want to use a different CD-ROM interface,
for example if CD audio does not work:
To enable SDL-support (does not include low-level CD access!):
- mount d f:\ -t cdrom -usecd 0 -noioctl
To enable ioctl access using digital audio extraction for CD audio
(windows-only, useful for Vista):
- mount d f:\ -t cdrom -ioctl_dx
To enable ioctl access using MCI for CD audio (windows-only):
- mount d f:\ -t cdrom -ioctl_mci
To force ioctl-only access (windows-only):
- mount d f:\ -t cdrom -ioctl_dio
To enable low-level aspi-support (win98 with aspi-layer installed):
- mount d f:\ -t cdrom -aspi
- mount d f:\ -t cdrom
To enable low-level CD-ROM-support (uses ioctl if possible):
- mount d f:\ -t cdrom -usecd 0
To enable low-level SDL-support:
- mount d f:\ -t cdrom -usecd 0 -noioctl
To enable low-level aspi-support (win98 with aspi-layer installed):
- mount d f:\ -t cdrom -usecd 0 -aspi
In the commands: - d driveletter you will get in DOSBox
- f:\ location of CD-ROM on your PC.
- 0 The number of the CD-ROM drive, reported by "mount -cd"
(note that this value is only needed when using SDL
for CD audio, otherwise it is ignored)
See also the next question: The game/application can't find its CD-ROM.
Q: The game/application can't find its CD-ROM.
A: Be sure to mount the CD-ROM with -t cdrom switch, this will enable the
MSCDEX interface required by DOS games to interface with CD-ROMs.
Also try adding the correct label (-label LABEL) to the mount command,
where LABEL is the CD-label (volume ID) of the CD-ROM.
Under Windows you can specify -ioctl, -aspi or -noioctl. Look at the
description of the mount command in Section 4 for their meaning and the
additional audio-CD related options -ioctl_dx, ioctl_mci, ioctl_dio.
Try creating a CD-ROM image (preferably CUE/BIN pair) and use the
DOSBox-internal IMGMOUNT tool to mount the image (the CUE sheet).
This enables very good low-level CD-ROM support on any operating system.
- 0 The number of the CD-ROM drive, reported by mount -cd
See also the question: The game/application can't find its CD-ROM.
Q: The mouse doesn't work.
@ -161,9 +167,6 @@ A: Be sure that the sound is correctly configured in the game. This might be
If you still don't get any sound set the core to normal and use some lower
fixed cycles value (like cycles=2000). Also assure that your host operating
sound does provide sound.
In certain cases it might be useful to use a different emulated sound device
like a soundblaster pro (sbtype=sbpro1 in the DOSBox configuration file) or
the gravis ultrasound (gus=true).
Q: The sound stutters or sounds stretched/weird.
@ -171,41 +174,52 @@ A: You're using too much CPU power to keep DOSBox running at the current speed.
You can lower the cycles, skip frames, reduce the sampling rate of
the respective sound device (see the DOSBox configuration file) or
the mixer device. You can also increase the prebuffer in the configfile.
If you are using cycles=max or =auto, then make sure that there is no
If you are using cycles=max or =auto, then make sure that there no
background processes interfering! (especially if they access the harddisk)
Q: I can't type \ or : in DOSBox.
A: This can happen in various cases, like your host keyboard layout does not
have a matching DOS layout representation (or it was not correctly detected),
or the key mapping is wrong.
A: This is a known problem. It only occurs if your keyboard layout isn't US.
Some possible fixes:
1. Use / instead, or ALT-58 for : and ALT-92 for \.
2. Change the DOS keyboard layout (see Section 7: Keyboard Layout).
3. Add the commands you want to execute to the [autoexec]-section
of the DOSBox configuration file.
4. Open the DOSBox configuration file and change the usescancodes entry.
5. Switch the keyboard layout of your operating system.
Note that if the host layout can not be identified, or keyboardlayout is set
to none in the DOSBox configuration file, the standard US layout is used.
In this configuration try the keys around "enter" for the key \ (backslash),
and for the key : (colon) use shift and the keys between "enter" and "l".
1. Switch the keyboard layout of your operating system.
2. Use / instead.
3. Open dosbox.conf and change usescancodes=false to usescancodes=true.
4. Add the commands you want to execute to the "configfile".
5. Change the DOS keyboard layout (see Section 7 Keyboard Layout).
6. Use ALT-58 for : and ALT-92 for \.
7. for \ try the keys around "enter". For ":" try shift and the keys
between "enter" and "l" (US keyboard layout).
8. Try keyb.com from FreeDOS (http://projects.freedos.net/keyb/).
Look for keyb2.0 pre4 as older and newer versions are known to
have a bug in the loader routines.
Q: The keyboard lags.
A: Lower the priority setting in the DOSBox configuration file, for example
set "priority=normal,normal". You might also want to try lowering the cycles
(use a fixed cycle count to start with, like cycles=10000).
A: Lower the priority setting in the DOSBox configuration file
like set "priority=normal,normal". You might also want to
try lowering the cycles.
Q: The cursor always moves into one direction!
A: See if it still happens if you disable the joystick emulation,
set joysticktype=none in the [joystick] section of your DOSBox
configuration file. Maybe also try unplugging any joystick/gamepad.
configuration file. Maybe also try unplugging any joystick.
If you want to use the joystick in the game, try setting timed=false
and be sure to calibrate the joystick (both in your OS as well as
in the game or the game's setup program).
in the game or the game's setup).
Q: The game/application can't find its CD-ROM.
A: Be sure to mount the CD-ROM with -t cdrom switch, this will enable the
MSCDEX interface required by DOS games to interface with CD-ROMs.
Also try adding the correct label (-label LABEL). To enable lower-level
CD-ROM support, add the following switch to mount: -usecd #, where # is
the number of your CD-ROM drive reported by mount -cd. Under Windows you
can specify -ioctl, -aspi or -noioctl. Look at the description elsewhere
in this document for their meaning.
Try creating a CD-ROM image (preferably CUE/BIN pair) and use the
DOSBox-internal IMGMOUNT tool to mount the image. This enables very
good low-level CD-ROM support on any operating system.
Q: The game/application runs much too slow!
@ -213,10 +227,6 @@ A: Look at the section "How to run resource-demanding games" for more
information.
Q: The game/application does not run at all/crashes!
A: Look at Section 10: Troubleshooting
Q: Can DOSBox harm my computer?
A: DOSBox can not harm your computer more than any other resource demanding
program. Increasing the cycles does not overclock your real CPU.
@ -228,7 +238,6 @@ Q: I would like to change the memory size/cpu speed/ems/soundblaster IRQ.
A: This is possible! Just create a config file: config -writeconf configfile.
Start your favourite editor and look through the settings. To start DOSBox
with your new settings: dosbox -conf configfile
See the description of the config command in Section 4 for more details.
Q: What sound hardware does DOSBox presently emulate?
@ -251,7 +260,7 @@ A: DOSBox emulates several legacy sound devices:
- Adlib
Borrowed from MAME, this emulation is almost perfect and includes the
Adlib's ability to almost play digitized sound.
- SoundBlaster 16 / SoundBlaster Pro I & II / SoundBlaster I & II
- SoundBlaster 16/ SoundBlaster Pro I & II /SoundBlaster I & II
By default DOSBox provides Soundblaster 16 level 16-bit stereo sound.
You can select a different SoundBlaster version in the configfile of
DOSBox (See Internal Commands: CONFIG).
@ -275,12 +284,12 @@ Q: Great README, but I still don't get it.
A: A look at "The Newbie's pictorial guide to DOSBox" located at
http://vogons.zetafleet.com/viewforum.php?f=39 might help you.
Also try the wiki of DOSBox:
http://www.dosbox.com/wiki/
http://dosbox.sourceforge.net/wiki/
For more questions read the remainder of this README and/or check
the site/forum:
http://www.dosbox.com
http://dosbox.sourceforge.net
@ -288,17 +297,17 @@ http://www.dosbox.com
3. Usage:
=========
NOTE: Currently it is not possible to use command line options on the Wii.
An overview of the command line options you can give to DOSBox.
Windows Users must open cmd.exe or command.com or edit the shortcut to
dosbox.exe for this.
DOSBox.exe for this.
The options are valid for all operating systems unless noted in the option
description:
dosbox [name] [-exit] [-c command] [-fullscreen] [-conf congfigfile]
[-lang languagefile] [-machine machinetype] [-noconsole]
[-startmapper] [-noautoexec] [-securemode]
[-scaler scaler | -forcescaler scaler]
[-version]
[-startmapper] [-noautoexec] [-scaler scaler | -forcescaler scaler]
dosbox -version
@ -312,7 +321,7 @@ dosbox -version
-c command
Runs the specified command before running "name". Multiple commands
can be specified. Each command should start with "-c" though.
can be specified. Each command should start with "-c", though.
A command can be: an Internal Program, a DOS command or an executable
on a mounted drive.
@ -322,20 +331,15 @@ dosbox -version
-conf configfile
Start DOSBox with the options specified in "configfile".
Multiple -conf options may be present.
See Section 11 for more details.
See Chapter 10 for more details.
-lang languagefile
Start DOSBox using the language specified in "languagefile".
-machine machinetype
Setup DOSBox to emulate a specific type of machine. Valid choices are:
hercules, cga, pcjr, tandy, svga_s3 (default) as well as the additional
svga chipsets listed in the help of the DOSBox configuration file.
svga_s3 enables vesa emulation as well.
For some special vga effects the machinetype vgaonly can be used,
note that this disables svga capabilites and might be (considerably)
slower due to the much higher emulation precision.
The machinetype affects both the videocard and the available soundcards.
hercules, cga, pcjr, tandy, vga (default). The machinetype affects
both the videocard and the available soundcards.
-noconsole (Windows Only)
Start DOSBox without showing the console window. Output will
@ -348,11 +352,6 @@ dosbox -version
-noautoexec
Skips the [autoexec] section of the loaded configuration file.
-securemode
Same as -noautoexec, but adds config.com -securemode at the
bottom of AUTOEXEC.BAT (which in turn disables any changes to how
the drives are mounted inside DOSBox).
-scaler scaler
Uses the scaler specified by "scaler". See the DOSBox configuration
file for the available scalers.
@ -367,14 +366,14 @@ dosbox -version
Note: If a name/command/configfile/languagefile contains a space, put
the whole name/command/configfile/languagefile between quotes
("command or file name"). If you need to use quotes within quotes
(most likely with -c and mount):
(most likely with -c and mount).
Windows and OS/2 users can use single quotes inside the double quotes.
Other people should be able to use escaped double quotes inside the
double quotes.
Windows: -c "mount c 'c:\program files\'"
Linux: -c "mount c \"/tmp/name with space\""
win -c "mount c 'c:\program files\'"
linux -c "mount c \"/tmp/name with space\""
For example (Windows):
For example:
dosbox c:\atlantis\atlantis.exe -c "MOUNT D C:\SAVES"
This mounts c:\atlantis as c:\ and runs atlantis.exe.
@ -428,11 +427,11 @@ MOUNT -u "Emulated Drive letter"
-label drivelabel
Sets the name of the drive to "drivelabel". Needed on some
systems if the CD-ROM label isn't read correctly (useful when a
program can't find its CD-ROM). If you don't specify a label and no
systems if the cd label isn't read correctly. Useful when a
program can't find its CD-ROM. If you don't specify a label and no
lowlevel support is selected (that is omitting the -usecd # and/or
-aspi parameters, or specifying -noioctl):
For Windows: label is extracted from "Real Drive".
-aspi parameters or specifying -noioctl):
For win32: label is extracted from "Real Drive".
For Linux: label is set to NO_LABEL.
If you do specify a label, this label will be kept as long as the drive
@ -442,29 +441,19 @@ MOUNT -u "Emulated Drive letter"
Forces use of the aspi layer. Only valid if mounting a CD-ROM under
Windows systems with an ASPI-Layer.
-ioctl (automatic selection of the CD audio interface)
-ioctl_dx (digital audio extraction used for CD audio)
-ioctl_dio (ioctl calls used for CD audio)
-ioctl_mci (MCI used for CD audio)
-ioctl
Forces use of ioctl commands. Only valid if mounting a CD-ROM under
a Windows OS which support them (Win2000/XP/NT).
The various choices only differ in the way CD audio is handled,
preferrably -ioctl_dio is used (lowest workload), but this might not
work on all systems so -ioctl_dx (or -ioctl_mci) can be used.
-noioctl
-noioctl
Forces use of the SDL CD-ROM layer. Valid on all systems.
-usecd number
Valid on all systems, under windows the -noioctl switch has to be
present to make use of the -usecd switch.
Enables to select the drive that should be used by SDL. Use this if
the wrong or no CD-ROM drive is mounted while using the SDL CD-ROM
interface. "number" can be found by "MOUNT -cd".
Forces use of SDL CD-ROM support for drive number.
Number can be found by -cd. Valid on all systems.
-cd
Displays all CD-ROM drives detected by SDL, and their numbers.
See the information at the -usecd entry above.
Displays all detected CD-ROM drives and their numbers. Use with -usecd.
-u
Removes the mount. Doesn't work for Z:\.
@ -474,7 +463,7 @@ MOUNT -u "Emulated Drive letter"
Basically MOUNT allows you to connect real hardware to DOSBox's emulated PC.
So MOUNT C C:\GAMES tells DOSBox to use your C:\GAMES directory as drive C:
in DOSBox. It also allows you to change the drive letter identification
in DOSBox. It also allows you to change the drive's letter identification
for programs that demand specific drive letters.
For example: Touche: Adventures of The Fifth Musketeer must be run on your C:
@ -486,52 +475,41 @@ MOUNT -u "Emulated Drive letter"
Mounting your entire C drive with MOUNT C C:\ is NOT recommended! The same
is true for mounting the root of any other drive, except for CD-ROMs (due to
their read-only nature). Otherwise if you or DOSBox make a mistake you may
lose all your files.
loose all your files.
It is recommended to put all your applications/games into a subdirectory
and mount that.
General MOUNT Examples:
1. To mount c:\DirX as a floppy :
mount a c:\DirX -t floppy
2. To mount system CD-ROM drive E as CD-ROM drive D in DOSBox:
mount d e:\ -t cdrom
3. To mount system CD-ROM drive at mountpoint /media/cdrom as CD-ROM drive D
in DOSBox:
mount d /media/cdrom -t cdrom -usecd 0
4. To mount a drive with ~870 mb free diskspace (simple version):
mount c d:\ -freesize 870
5. To mount a drive with ~870 mb free diskspace (experts only, full control):
mount c d:\ -size 512,127,16513,13500
6. To mount /home/user/dirY as drive C in DOSBox:
mount c /home/user/dirY
7. To mount the directory where DOSBox was started as D in DOSBox:
mount d .
(note the . which represents the directory where DOSBox was started)
1. To mount c:\DirX as a floppy :
mount a c:\DirX -t floppy
2. To mount system CD-ROM drive E as CD-ROM drive D in DOSBox:
mount d e:\ -t cdrom
3. To mount system CD-ROM drive at mountpoint /media/cdrom as CD-ROM drive D
in DOSBox:
mount d /media/cdrom -t cdrom -usecd 0
4. To mount a drive with ~870 mb free diskspace (simple version):
mount c d:\ -freesize 870
5. To mount a drive with ~870 mb free diskspace (experts only, full control):
mount c d:\ -size 512,127,16513,13500
6. To mount /home/user/dirY as drive C in DOSBox:
mount c /home/user/dirY
7. To mount the directory where DOSBox was started as D in DOSBox:
mount d .
MEM
Program to display the amount of free memory.
VER
VER set major_version [minor_version]
Display the current DOSBox version and reported DOS version
(parameterless usage).
Change the reported DOS version with the "set" parameter,
for example: "VER set 6 22" to have DOSBox report DOS 6.22
as version number.
CONFIG -writeconf localfile
CONFIG -writelang localfile
CONFIG -securemode
CONFIG -set "section property=value"
CONFIG -get "section property"
CONFIG can be used to change or query various settings of DOSBox
during runtime. It can save the current settings and language strings to
disk. Information about all possible sections and properties can
be found in Section 11 (The Config File).
be found in section 11 (The Config File).
-writeconf localfile
Write the current configuration settings to file. "localfile" is
@ -539,7 +517,7 @@ CONFIG -get "section property"
The configuration file controls various settings of DOSBox:
the amount of emulated memory, the emulated soundcards and many more
things. It allows access to AUTOEXEC.BAT as well.
See Section 11 (The Config File) for more information.
See section 11 (The Config File) for more information.
-writelang localfile
Write the current language settings to file. "localfile" is
@ -547,14 +525,8 @@ CONFIG -get "section property"
The language file controls all visible output of the internal commands
and the internal DOS.
-securemode
Switches DOSBox to a more secure mode. In this mode the internal
commands MOUNT, IMGMOUNT and BOOT won't work. It's not possible either
to create a new configfile or languagefile in this mode.
(Warning: you can only undo this mode by restarting DOSBox.)
-set "section property=value"
CONFIG will attempt to set the property to new value. Currently
CONFIG will attempt to set the property to new value. At this moment
CONFIG can not report whether the command succeeded or not.
-get "section property"
@ -566,20 +538,20 @@ CONFIG -get "section property"
own preferences for each game.
Examples:
1. To create a configfile in your current directory:
config -writeconf dosbox.conf
2. To set the cpu cycles to 10000:
config -set "cpu cycles=10000"
3. To turn ems memory emulation off:
config -set "dos ems=off"
4. To check which cpu core is being used.
config -get "cpu core"
1. To create a configfile in your current directory:
config -writeconf dosbox.conf
2. To set the cpu cycles to 10000:
config -set "cpu cycles=10000"
3. To turn ems memory emulation off:
config -set "dos ems=off"
4. To check which cpu core is being used.
config -get "cpu core"
LOADFIX [-size] [program] [program-parameters]
LOADFIX -f
Program to reduce the amount of available conventional memory.
Useful for old programs which don't expect much memory to be free.
Program to reduce the amount of memory available. Useful for old programs
which don't expect much memory to be free.
-size
number of kilobytes to "eat up", default = 64kb
@ -587,14 +559,14 @@ LOADFIX -f
-f
frees all previously allocated memory
Examples:
1. To start mm2.exe and allocate 64kb memory
(mm2 will have 64 kb less available) :
loadfix mm2
2. To start mm2.exe and allocate 32kb memory :
loadfix -32 mm2
3. To free previous allocated memory :
loadfix -f
Examples:
1. To start mm2.exe and allocate 64kb memory
(mm2 will have 64 kb less available) :
loadfix mm2
2. To start mm2.exe and allocate 32kb memory :
loadfix -32 mm2
3. To free previous allocated memory :
loadfix -f
RESCAN
@ -609,13 +581,11 @@ MIXER
mixer channel left:right [/NOSHOW] [/LISTMIDI]
channel
Can be one of the following: MASTER, DISNEY, SPKR, GUS, SB, FM [, CDAUDIO].
CDAUDIO is only available if a CD-ROM interface with volume control is
enabled (CD image, ioctl_dx).
Can be one of the following: MASTER, DISNEY, SPKR, GUS, SB, FM.
left:right
The volume levels in percentages. If you put a D in front it will be
in decibel (Example: mixer gus d-10).
in decibel (example mixer gus d-10).
/NOSHOW
Prevents DOSBox from showing the result if you set one
@ -633,31 +603,20 @@ IMGMOUNT
IMGMOUNT DRIVE [imagefile] -t [image_type] -fs [image_format]
-size [sectorsbytesize, sectorsperhead, heads, cylinders]
IMGMOUNT DRIVE [imagefile1, .. ,imagefileN] -t iso -fs iso
imagefile
Location of the image file to mount in DOSBox. The location can
Location of the image files to mount in DOSBox. The location can
be on a mounted drive inside DOSBox, or on your real disk. It is
possible to mount CD-ROM images (ISOs or CUE/BIN) as well, if you
need CD swapping capabilities specify all images in succession
(see the next entry).
CUE/BIN pairs are the preferred CD-ROM image type as they can
store audio tracks compared to ISOs (which are data-only). For
the CUE/BIN mounting always specify the CUE sheet.
imagefile1, .. ,imagefileN
Location of the image files to mount in DOSBox. Specifying a number
of image files is only allowed for CD-ROM images. The CD's can be
swapped with CTRL-F4 at any time. This is required for games which
use multiple CD-ROMs and require the CD to be switched during the
gameplay at some point.
need CD swapping capabilities specify all images in succession.
The CDs can be swapped with CTRL-F4 at any time.
-t
The following are valid image types:
floppy: Specifies a floppy image. DOSBox will automatically identify
the disk geometry (360K, 1.2MB, 720K, 1.44MB, etc).
iso: Specifies a CD-ROM iso image. The geometry is automatic and
set for this size. This can be an iso or a cue/bin pair.
floppy: Specifies a floppy image or images. DOSBox will automatically
identify the disk geometry ( 360K, 1.2MB, 720K, 1.44MB, etc).
iso: Specifies a CD-ROM iso image. The geometry is automatic and
set for this size. This can be an iso or a cue/bin.
hdd: Specifies a harddrive image. The proper CHS geometry
must be set for this to work.
@ -669,18 +628,18 @@ IMGMOUNT
available from inside DOSBox.
none: DOSBox will make no attempt to read the file system on the disk.
This is useful if you need to format it or if you want to boot
the disk using the BOOT command. When using the "none"
the disk using the BOOT command. When using the "none"
filesystem, you must specify the drive number (2 or 3,
where 2 = master, 3 = slave) rather than a drive letter.
For example, to mount a 70MB image as the slave drive device,
you would type (without the quotes):
you would type:
"imgmount 3 d:\test.img -size 512,63,16,142 -fs none"
Compare this with a mount to be able to access the drive
within DOSBox, which would read as:
(without the quotes) Compare this with a mount to read the
drive in DOSBox, which would read as:
"imgmount e: d:\test.img -size 512,63,16,142"
-size
The Cylinders, Heads and Sectors of the drive.
The Cylinders, Heads and Sectors specification of the drive.
Required to mount hard drive images.
An example how to mount CD-ROM images:
@ -709,7 +668,7 @@ BOOT
[-l driveletter]
This parameter allows you to specify the drive to boot from.
The default is the A drive, the floppy drive. You can also boot
The default is the A drive, the floppy drive. You can also boot
a hard drive image mounted as master by specifying "-l C"
without the quotes, or the drive as slave by specifying "-l D"
@ -729,12 +688,12 @@ IPX
With regard to actually setting up a network, one system needs to be
the server. To set this up, type "IPXNET STARTSERVER" (without the quotes)
in a DOSBox session. The server DOSBox session will automatically add
itself to the virtual IPX network. For every additional computer that
should be part of the virtual IPX network, you'll need to type
"IPXNET CONNECT <computer host name or IP>".
For example, if your server is at bob.dosbox.com, you would type
"IPXNET CONNECT bob.dosbox.com" on every non-server system.
in a DOSBox session. The server DOSBox session will
automatically add itself to the virtual IPX network. For every
additional computer that should be part of the virtual IPX network,
you'll need to type "IPXNET CONNECT <computer host name or IP>".
For example, if your server is at bob.dosbox.com,
you would type "IPXNET CONNECT bob.dosbox.com" on every non-server system.
To play games that need Netbios a file named NETBIOS.EXE from Novell is
needed. Establish the IPX connection as explained above, then run
@ -824,19 +783,17 @@ KEYB [languagecode [codepage [codepagefile]]]
Examples:
1. To load the german keyboard layout (automatically uses codepage 858):
keyb gr
2. To load the russian keyboard layout with codepage 866:
keyb ru 866
In order to type russian characters press ALT+RIGHT-SHIFT.
3. To load the french keyboard layout with codepage 850 (where the
codepage is defined in EGACPI.DAT):
keyb fr 850 EGACPI.DAT
4. To load codepage 858 (without a keyboard layout):
keyb none 858
This can be used to change the codepage for the FreeDOS keyb2 utility.
5. To display the current codepage and, if loaded, the keyboard layout:
keyb
1) To load the german keyboard layout (automatically uses codepage 858):
keyb gr
2) To load the russian keyboard layout with codepage 866:
keyb ru 866
In order to type russian characters press ALT+RIGHT-SHIFT.
3) To load the french keyboard layout with codepage 850 (where the
codepage is defined in EGACPI.DAT):
keyb fr 850 EGACPI.DAT
4) To load codepage 858 (without a keyboard layout):
keyb none 858
This can be used to change the codepage for the freedos keyb2 utility.
@ -849,13 +806,13 @@ For more information use the /? command line switch with the programs.
================
ALT-ENTER Switch to full screen and back.
ALT-PAUSE Pause emulation (hit ALT-PAUSE again to continue).
ALT-PAUSE Pause emulation.
CTRL-F1 Start the keymapper.
CTRL-F4 Change between mounted disk-images. Update directory cache for all drives!
CTRL-ALT-F5 Start/Stop creating a movie of the screen. (avi video capturing)
CTRL-F5 Save a screenshot. (PNG format)
CTRL-F5 Save a screenshot. (png)
CTRL-F6 Start/Stop recording sound output to a wave file.
CTRL-ALT-F7 Start/Stop recording of OPL commands. (DRO format)
CTRL-ALT-F7 Start/Stop recording of OPL commands.
CTRL-ALT-F8 Start/Stop the recording of raw MIDI commands.
CTRL-F7 Decrease frameskip.
CTRL-F8 Increase frameskip.
@ -865,20 +822,19 @@ CTRL-F11 Slow down emulation (Decrease DOSBox Cycles).
CTRL-F12 Speed up emulation (Increase DOSBox Cycles).
ALT-F12 Unlock speed (turbo button).
(NOTE: Once you increase your DOSBox cycles beyond your computer's maximum
capacity, it will produce the same effect as slowing down the emulation.
This maximum will vary from computer to computer.)
These are the default keybindings. They can be changed in the keymapper
(see Section 6: Mapper).
These are the default keybindings. They can be changed in the keymapper.
Saved/recorded files can be found in current_directory/capture
(this can be changed in the DOSBox configuration file).
(can be changed in the configfile).
The directory has to exist prior to starting DOSBox, otherwise nothing
gets saved/recorded !
NOTE: Once you increase your DOSBox cycles beyond your computer's maximum
capacity, it will produce the same effect as slowing down the emulation.
This maximum will vary from computer to computer.
==========
6. Mapper:
@ -888,10 +844,10 @@ When you start the DOSBox mapper (either with CTRL-F1 or -startmapper as
a command line argument to the DOSBox executable) you are presented with
a virtual keyboard and a virtual joystick.
These virtual devices correspond to the keys and events DOSBox will
report to the DOS applications. If you click on a button with your mouse,
you can see in the lower left corner with which event it is associated
(EVENT) and to what events it is currently bound.
These virtual devices correspond to the keys DOSBox will report to the
DOS applications. If you click on a key with your mouse, you can see in
the lower left corner with which event it is associated (EVENT) and to
what events it is currently bound.
Event: EVENT
BIND: BIND
@ -943,32 +899,32 @@ Examples about remapping the joystick:
You have a joystick attached, it is working fine under DOSBox and you
want to play some keyboard-only game with the joystick (it is assumed
that the game is controlled by the arrows on the keyboard):
1. Start the mapper, then click on one of the arrows in the middle
1) Start the mapper, then click on one of the arrows in the middle
of the left part of the screen (right above the Mod1/Mod2 buttons).
EVENT should be key_left. Now click on Add and move your joystick
in the respective direction, this should add an event to the BIND.
2. Repeat the above for the missing three directions, additionally
2) Repeat the above for the missing three directions, additionally
the buttons of the joystick can be remapped as well (fire/jump).
3. Click on Save, then on Exit and test it with some game.
3) Click on Save, then on Exit and test it with some game.
You want to swap the y-axis of the joystick because some flightsim uses
the up/down joystick movement in a way you don't like, and it is not
configurable in the game itself:
1. Start the mapper and click on Y- in the upper joystick field (this
1) Start the mapper and click on Y- in the upper joystick field (this
is for the first joystick if you have two joysticks attached) or the
lower joystick field (second joystick or, if you have only one
joystick attached, the second axes cross).
EVENT should be jaxis_0_1- (or jaxis_1_1-).
2. Click on Del to remove the current binding, then click Add and move
2) Click on Del to remove the current binding, then click Add and move
your joystick downwards. A new bind should be created.
3. Repeat this for Y+, save the layout and finally test it with some game.
3) Repeat this for Y+, save the layout and finally test it with some game.
If you change the default mapping, you can save your changes by clicking on
"Save". DOSBox will save the mapping to a location specified in the configuration
file (the mapperfile= entry). At startup, DOSBox will load your mapperfile,
if it is present in the DOSBox configuration file.
"Save". DOSBox will save the mapping to a location specified in the configfile
(mapperfile=mapper.txt). At startup, DOSBox will load your mapperfile, if it
is present in the configfile.
@ -977,43 +933,39 @@ if it is present in the DOSBox configuration file.
===================
To switch to a different keyboard layout, either the entry "keyboardlayout"
in the [dos] section of the DOSBox configuration file can be used, or the
internal DOSBox program keyb.com. Both accept DOS conforming language codes
(see below), but only by using keyb.com a custom codepage can be specified.
The default keyboardlayout=auto currently works under windows only, the
layout is chosen according to the OS layout.
in the [dos] section in dosbox.conf can be used, or the internal DOSBox
program keyb.com. Both accept DOS conforming language codes (see below), but
only by using keyb.com a custom codepage can be specified.
Layout switching
DOSBox supports a number of keyboard layouts and codepages by default,
in this case just the layout identifier needs to be specified (like
keyboardlayout=sv in the DOSBox configuration file, or using "keyb sv"
at the DOSBox command prompt).
keyboardlayout=sv in the DOSBox config file, or using "keyb sv" at
the DOSBox command prompt).
Some keyboard layouts (for example layout GK codepage 869 and layout RU
codepage 808) have support for dual layouts that can be activated by
pressing LEFT-ALT+RIGHT-SHIFT and deactivated by LEFT-ALT+LEFT-SHIFT.
Supported external files
The FreeDOS .kl files are supported (FreeDOS keyb2 keyboard layoutfiles) as
well as the FreeDOS keyboard.sys/keybrd2.sys/keybrd3.sys libraries which
The freedos .kl files are supported (freedos keyb2 keyboard layoutfiles) as
well as the freedos keyboard.sys/keybrd2.sys/keybrd3.sys libraries which
consist of all available .kl files.
See http://projects.freedos.net/keyb/ for precompiled keyboard layouts if
the DOSBox-integrated layouts don't work for some reason, or if updated or
the DOSBox-integrated layouts don't work for some reason, or updated or
new layouts become available.
Both .CPI (MS-DOS and compatible codepage files) and .CPX (FreeDOS
UPX-compressed codepage files) can be used. Some codepages are compiled
into DOSBox, so it is mostly not needed to care about external codepage
files. If you need a different (or custom) codepage file, copy it into
the directory of the DOSBox configuration file so it is accessible for
DOSBox.
Both .CPI (MSDOS/compatible codepage files) and .CPX (freedos UPX-compressed
codepage files) can be used. Some codepages are compiled into DOSBox, so it
is mostly not needed to care about external codepage files. If you need
a different (or custom) codepage file, copy it into the directory of the
DOSBox configuration file so it is accessible for DOSBox.
Additional layouts can be added by copying the corresponding .kl file into
the directory of the DOSBox configuration file and using the first part of
the filename as language code.
the directory of dosbox.conf and using the first part of the filename as
language code.
Example: For the file UZ.KL (keyboard layout for Uzbekistan) specify
"keyboardlayout=uz" in the DOSBox configuration file.
"keyboardlayout=uz" in dosbox.conf.
The integration of keyboard layout packages (like keybrd2.sys) works similar.
@ -1092,7 +1044,7 @@ CPU Cycles
in the DOSBox configuration file specify for example cycles=30000. When
running some DOS application you can raise the cycles with CTRL-F12 even
more, but you will be limited by the power of your actual CPU. You can see
how much free time your real CPU has by looking at the Task Manager in
how much free time your true CPU has by looking at the Task Manager in
Windows 2000/XP and the System Monitor in Windows 95/98/ME. Once 100% of
your real CPU time is used there is no further way to speed up DOSBox
unless you reduce the load generated by the non-CPU parts of DOSBox.
@ -1116,7 +1068,7 @@ Graphics emulation
Sound emulation
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 does NOT disable
the emulation of sound devices, just the output of sound will be disabled.
the emulation of sound devices, just the sound output will be disabled.
Also try to close every program but DOSBox to reserve as much resources
as possible for DOSBox.
@ -1185,15 +1137,14 @@ You can edit the generated configfile to customize DOSBox.
The file is divided into several sections (the names have [] around it).
Some sections have options you can set.
# and % indicate comment-lines.
The DOSBox configuration file contains the current settings. You can
alter them and start DOSBox with the -conf switch to load the file and
use these settings.
The generated configfile contains the current settings. You can alter them and
start DOSBox with the -conf switch to load the file and use these settings.
DOSBox will first parse the settings in ~/.dosboxrc (Linux),
~\dosbox.conf (Win32) or "~/Library/Preferences/DOSBox Preferences"
(MACOSX). Afterwards DOSBox will parse all configfiles specified with the
-conf switch. If no configfile is specified with the -conf switch, DOSBox will
look in the current directory for the DOSBox configuration file.
look in the current directory for dosbox.conf.
@ -1230,5 +1181,5 @@ See the THANKS file.
============
See the site:
http://www.dosbox.com
http://dosbox.sourceforge.net
for an email address (The Crew-page).

File diff suppressed because one or more lines are too long

View File

@ -1,4 +1,4 @@
#define VERSION "0.72"
#define VERSION "0.72.01"
/* Define to 1 to enable internal debugger, requires libcurses */
#define C_DEBUG 0