site map

Running Score on Windows Vista using DOSBox

editor: Gordon J. Callon

[ Method  |  To adjust "dosbox.conf" manually  |  Sample dosbox.conf file  |  Sample dosbox.conf file: plain text version  |  Recommended directory setups (and plain text versions: 1 or 2  |  Further advice ]

Conditions of Use

Andrew Parker:

Back Score Links
Download the latest version of DOSBox from At the date of writing this is version 0.72.

Go direct to the download page at

You need to get just the Win32 installer version (at the top of the list).

These notes relate to setting it up so that it runs straight into Scor4 and out again.

This was done as an "ordinary unprivileged user" on Vista, so that any strange messages about security will be encountered.

The main thing is that DOSBox doesn't know about Vista Program Files folders having reduced accessibility as compared to XP,

so you need to change the permissions (giving the admin password, if asked) and allow full control of the DOSBox-0.72 folder in

Program Files, and also set a couple of folders NOT to be read only.



You can now either adjust the dosbox..conf file, as detailed below, or you may like to try a sample one which is optimised for

running Score. But note, if you elect to use the pre-configured file, you may still need to edit the path information at the end of

the file which controls the virtual directories mounted when DOSBox runs.

Top Top
Back Score Links

To adjust "dosbox.conf" manually, I suggest the following changes:

in the first block:







in the final block – this assumes that c to be your Vista drive:


# Lines in this section will be run at startup.

mount c c:\


cd \scor4



Save this new version of the dosbox.conf.

Create a shortcut to DOSBox.exe as desired.

Top Top
Back Score Links

When you run DOSBox, you will now get Score in a window. When you exit Score, the DOSBox will close.

To get similar DOSBoxes for other Score fullscreen utilities, just start DOSBox with a different config file on the

command line. For example, the alternative config files can have the autoexec parameters to mount the Vista

drive and run the utility directly. Alternatively, you can have a config file with no autoexec parameters (apart

from the mount command, perhaps) and then use the command line normally.

To capture the mouse inside the DOSBox, just place your mouse over the area

and click. To free the mouse, either do an alt-tab switch to another

window or press Ctrl-F10.

You will need the normal XP-type pref.scr with the mouse interrupt set to

irq 5, and so on.

Andrew Parker

31 March 2008

Top Top
Back Score Links

Sample dosbox.conf file:


# fullscreen -- Start dosbox directly in fullscreen.

# fulldouble -- Use double buffering in fullscreen.

# fullresolution -- What resolution to use for fullscreen: original or fixed size (e.g. 1024x768).

# windowresolution -- Scale the window to this size IF the output device supports hardware scaling.

# output -- What to use for output: surface,overlay,opengl,openglnb,ddraw.

# autolock -- Mouse will automatically lock, if you click on the screen.

# sensitivity -- Mouse sensitivity.

# waitonerror -- Wait before closing the console if dosbox has an error.

# priority -- Priority levels for dosbox: lowest,lower,normal,higher,highest,pause (when not focussed).

# Second entry behind the comma is for when dosbox is not focused/minimized.

# mapperfile -- File used to load/save the key/event mappings from.

# usescancodes -- Avoid usage of symkeys, might not work on all operating systems.
















# language -- Select another language file.

# memsize -- Amount of memory dosbox has in megabytes.

# machine -- The type of machine tries to emulate:hercules,cga,tandy,pcjr,vga.

# captures -- Directory where things like wave,midi,screenshot get captured.






# frameskip -- How many frames dosbox skips before drawing one.

# aspect -- Do aspect correction, if your output method doesn't support scaling this can slow things down!

# scaler -- Scaler used to enlarge/enhance low resolution modes.

# Supported are none,normal2x,normal3x,advmame2x,advmame3x,hq2x,hq3x,

# 2xsai,super2xsai,supereagle,advinterp2x,advinterp3x,

# tv2x,tv3x,rgb2x,rgb3x,scan2x,scan3x.





# core -- CPU Core used in emulation: normal,simple,dynamic,auto.

# auto switches from normal to dynamic if appropriate.

# cycles -- Number of instructions dosbox tries to emulate each millisecond.

# Setting this value too high results in sound dropouts and lags.

# You can also let DOSBox guess the correct value by setting it to max.

# The default setting (auto) switches to max if appropriate.

# cycleup -- Number of cycles to increase/decrease with keycombo.

# cycledown Setting it lower than 100 will be a percentage.






# nosound -- Enable silent mode, sound is still emulated though.

# rate -- Mixer sample rate, setting any devices higher than this will

# probably lower their sound quality.

# blocksize -- Mixer block size, larger blocks might help sound stuttering

# but sound will also be more lagged.

# prebuffer -- How many milliseconds of data to keep on top of the blocksize.






# mpu401 -- Type of MPU-401 to emulate: none, uart or intelligent.

# device -- Device that will receive the MIDI data from MPU-401.

# This can be default,alsa,oss,win32,coreaudio,none.

# config -- Special configuration options for the device. In Windows put

# the id of the device you want to use. See README for details.





# sbtype -- Type of sblaster to emulate:none,sb1,sb2,sbpro1,sbpro2,sb16.

# sbbase,irq,dma,hdma -- The IO/IRQ/DMA/High DMA address of the soundblaster.

# mixer -- Allow the soundblaster mixer to modify the dosbox mixer.

# oplmode -- Type of OPL emulation: auto,cms,opl2,dualopl2,opl3.

# On auto the mode is determined by sblaster type.

# All OPL modes are 'Adlib', except for CMS.

# oplrate -- Sample rate of OPL music emulation.










# gus -- Enable the Gravis Ultrasound emulation.

# gusbase,irq1,irq2,dma1,dma2 -- The IO/IRQ/DMA addresses of the

# Gravis Ultrasound. (Same IRQ's and DMA's are OK.)

# gusrate -- Sample rate of Ultrasound emulation.

# ultradir -- Path to Ultrasound directory. In this directory

# there should be a MIDI directory that contains

# the patch files for GUS playback. Patch sets used

# with Timidity should work fine.










# pcspeaker -- Enable PC-Speaker emulation.

# pcrate -- Sample rate of the PC-Speaker sound generation.

# tandy -- Enable Tandy Sound System emulation (off,on,auto).

# For auto Tandysound emulation is present only if machine is set to tandy.

# tandyrate -- Sample rate of the Tandy 3-Voice generation.

# disney -- Enable Disney Sound Source emulation.







# joysticktype -- Type of joystick to emulate: auto (default), none,

# 2axis (supports two joysticks), 4axis,

# fcs (Thrustmaster), ch (CH Flightstick).

# none disables joystick emulation.

# auto chooses emulation depending on real joystick(s).

# timed -- enable timed intervals for axis. (false is old style behaviour).

# autofire -- continuously fires as long as you keep the button pressed.

# swap34 -- swap the 3rd and the 4th axis. can be useful for certain joysticks.

# buttonwrap -- enable button wrapping at the number of emulated buttons.







# serial1-4 -- set type of device connected to com port.

# Can be disabled, dummy, modem, nullmodem, directserial.

# Additional parameters must be in the same line in the form of

# parameter:value. Parameter for all types is irq.

# for directserial: realport (required), rxdelay (optional).

# for modem: listenport (optional).

# for nullmodem: server, rxdelay, txdelay, telnet, usedtr,

# transparent, port, inhsocket (all optional).

# Example: serial1=modem listenport:5000






# xms -- Enable XMS support.

# ems -- Enable EMS support.

# umb -- Enable UMB support.

# keyboardlayout -- Language code of the keyboard layout (or none).






# ipx -- Enable ipx over UDP/IP emulation.



# Lines in this section will be run at startup.

mount c c:\


cd \scor4



Top Top
Back Score Links

Two alternate recommended subdirectory [folder] setups:

DOSBox may show an error if setup to operate in the root directory of the C:\ drive. DOSBox is better mounted in a subdirectory (secondary folder). If Score is installed in its default configuration, in C:\Score with the Preference files and Library files in C:\LIB, with DOSBox mounted in a subdirectory, then Score is unable to find the Preference files and Library files and will not function.

Andrew Parker recommends the following directory (folder) setup to correct this problem:

Make a subdirectory in your real C: drive, and call it "scoredb" for Score DosBox. In realworld C:\SCOREDB you now need to have at least two directories: LIB and SCORE. So you just move your files from realworld C:\LIB to C:\SCOREDB\LIB and your programs from C:\SCORE to C:\SCOREDB\SCORE. (You will need to move the HLP files, too.)

Now you mount C:\SCOREDB in DosBox to be the new C: in the DosBox world.

When DosBox mounts that, Score sees C:\LIB and is happy. The fact that this is the realworld C:\SCOREDB\LIB is never known to Score!

Score data files must be included in the SCOREDB subdirectory [folder] as well.

Thomas Weber suggests (tested with Score 4):

Have a small partition "D" that is reserved for Score (version 4). [Weber uses both DosBox (from Windows XP and occasionally from Linux) and the XP DOS emulation (Command Prompt).] This makes things much easier because the real D drive can be mounted to a virtual D drive in DosBox. This means that Score and the user always find the files at the same place, regardless of the environment.

The separate fat16 D drive also has another advantage: If Windows on drive C gets damaged for some reason, the user simply can format C: without losing Score on drive D. In theory, in Windows XP, the user also could boot plain DOS and have access to Score because it's a fat16 drive.

[The editor, Gordon J. Callon, is very interested to learn of any who have tried either of these suggestions and of the results.]

Some more advice:

Anthony Maydwell suggests (tested with Score 4):

The simplest way to address the issue of directories is to have Score in the D: drive (for reasons suggested above).

One advantage: The user can shift the entire directory onto another platform without "installation".

Problems with Score locating its path maybe as simple as forgetting to apply the 8:3 rule to directories (i.e., remember to name directories with no more than eight characters and file names with a maximum of eight characters [dot] three characters) - see the CD line below.

This may be clarified with a sample dosbox.conf file's mount and directory lines:

CD \Docume~1\Research\Sibeli~1\MUS0835

Top Top
Back Score Links

[This is one of several possibilities. Obviously, the CD line will vary with each user. The last line refers to Score version 4; this will be different for other versions of Score.]

Note that the working directory is defined so it is not necessary to CD [change directory] from the root every time Score is started.

site map
Copyright © 2008 by Gordon J. Callon. All rights reserved. e-mail: gordon.callon @
Last updated: 22 October 2008.