IndyCar Racing II 
Troubleshooting Guide
for PC's using DOS 5.0 and higher or Windows 95
revised 3/15/96

Sierra Technical Support provides this documentation as a reference to Sierra 
customers using Sierra software products. Sierra Technical Support makes 
reasonable efforts to ensure that the information contained in this
documentation is accurate. However, Sierra makes no warranty, either express
or implied, as to the accuracy, effectiveness, or completeness of the
information contained in this documentation.

SIERRA ON-LINE, INC. DOES NOT WARRANTY OR PROMISE THAT 
THE INFORMATION HEREIN WILL WORK WITH ANY OR ALL 
COMPUTER SYSTEMS. SIERRA DOES NOT ASSUME ANY LIABILITY, 
EITHER INCIDENTAL OR CONSEQUENTIAL, FOR THE USE OF THE 
INFORMATION HEREIN, INCLUDING ANY AND ALL DAMAGE TO OR 
LOST USE OF COMPUTER HARDWARE OR SOFTWARE PRODUCTS, 
LOSS OF WARRANTIES, OR LOST DATA BY THE CUSTOMER OR ANY 
THIRD PARTY. NO ORAL OR WRITTEN INFORMATION OR ADVICE 
GIVEN BY SIERRA, ITS EMPLOYEES, DISTRIBUTORS, DEALER OR 
AGENTS SHALL CHANGE THE RESTRICTION OF LIABILITY OR 
CREATE ANY NEW WARRANTIES. IN NO CASE SHALL SIERRA'S 
LIABILITY EXCEED THE PURCHASE PRICE OF THE SIERRA 
SOFTWARE PRODUCT.


TABLE OF CONTENTS

SECTION 1 - HARDWARE REQUIREMENTS
SECTION 2 - INSTALLATION PROCEDURES
SECTION 3 - COMMON INSTALLATION PROBLEMS
SECTION 4 - COMMON GAME PROBLEMS
SECTION 5 - COMMON SOUND PROBLEMS
SECTION 6 - DOS BOOT DISK INSTRUCTIONS 
SECTION 7 - WINDOWS 95 BOOT DISK INSTRUCTIONS
SECTION 8 - IF YOU STILL HAVE PROBLEMS
SECTION 9 - SOUND CARD DRIVER INFORMATION


SECTION 1 - HARDWARE REQUIREMENTS

REQUIRED
486DX33 with 8 MB RAM
2X Speed CD ROM drive
9 MB hard drive space (18 MB compressed)
MS-DOS 5.0 or higher
VGA
Mouse (PaintKit only)
RECOMMENDED FOR BEST PERFORMANCE
Pentium with 10 MB RAM
47 MB hard drive space (94 MB compressed)
Sound Blaster or 100% compatible
SVGA (640x480x256)
Joystick or Driving Wheel/Pedal Combo

SECTION 2 - INSTALLATION PROCEDURES 

DOS Installation
1. Before installing the game, make sure that your computer is turned 
on and that the MS-DOS prompt is showing. The prompt should 
look like this C> or like this C:\> (the letter may be different if you 
are installing to a different drive). Exit completely out of any other 
program you may have running such as Windows or DOS Shell.
2. Insert the IndyCar Racing II CD into your CD-ROM drive. Change 
to your CD-ROM drive by typing the letter of your CD-ROM drive 
followed by a colon, and then press <ENTER>. For example, if “D” 
is your CD-ROM drive, type D: and press <ENTER>.
3. Type INSTALL and press <ENTER>. Follow the on-screen 
instructions to complete the installation.
4. By default, the installation program will create a directory on your 
C: drive called ICR2 and place all game files in that directory.
5. The game will prompt you for sound configurations. This will only 
occur when you have newly installed the game. You must run each 
setup before you can play IndyCar Racing II. 
6. To play IndyCar Racing II after you have installed the program, 
change to the ICR2 directory on your hard drive by typing CD\ICR2 
and pressing <ENTER>.
7. From the game directory, type INDYCAR (for VGA) and press 
<ENTER> or INDYCAR -H (for SVGA) to begin the game.
 
You may reconfigure your sound setup after you have installed the 
game. To do so, change to your IndyCar Racing II game directory, as 
explained in Step 5 above, type SETUP and press <ENTER>. Then 
follow the on-screen instructions.

Windows 95 Installation
1. Insert the IndyCar Racing II CD into your CD-ROM drive. After a 
few seconds, a window will automatically appear on your Desktop 
and ask you if you would like to install IndyCar Racing II.
2. Choose "Yes, please" and follow the on-screen instructions.

To play IndyCar Racing II from Windows 95 after installation, insert the 
CD in your CD-ROM drive. It will ask you if you want to play IndyCar 
Racing II. Click on "yes".

NOTE: IndyCar Racing II may not play properly if any other programs 
are running in Windows 95. Make sure no other programs are running, 
including screen savers and virus scanners BEFORE you start IndyCar 
Racing II.

If no window appears after putting the CD in the drive, you may have 
Autoplay disabled in Windows 95. To enable it, click on your Start 
button, go to Settings, then Control Panel. From Control Panel, double-
click on the System icon. Choose the Device Manager tab, then find the 
section labeled "CD-ROM". Click the plus (+) next to CD-ROM, then 
click the name of the CD-ROM beneath it. Then click the "Properties" 
button. When the Properties window comes up, choose the "Settings" 
tab. In the "Options" section, put a check mark next to "Auto insert 
notification". Then click "Apply" and "OK". Follow the on-screen 
directions (you may need to restart Windows 95). Now when you insert 
the IndyCar Racing II CD, a window should automatically appear.

If you have trouble installing IndyCar Racing II under Windows 95, we 
recommend booting your system in MS-DOS mode and installing the 
game following the instructions below.

SECTION 3 - COMMON INSTALLATION PROBLEMS

PROBLEM: In Windows 95, when you insert the CD, you don't get the 
message "Do you want to play IndyCar II?"
SOLUTION: You need to enable the Autoplay feature of Windows 95. 
Click on your Start button, go to Settings, then Control Panel. From 
Control Panel, double-click on the System icon. Choose the Device 
Manager tab, then find the section labeled "CD-ROM". Click the plus 
(+) next to CD-ROM, then click the name of the CD-ROM beneath it. 
Then click the "Properties" button. When the properties window comes 
up, choose the "Settings" tab. In the "Options" section, put a check mark 
next to "Auto insert notification". Then click "Apply" and "OK". Follow 
the on-screen directions (you may need to restart Windows 95). Now 
when you insert the IndyCar Racing II CD, a window should 
automatically appear.


SECTION 4 - COMMON GAME PROBLEMS

PROBLEM: You receive a message: "ERROR: Initializing Mouse Could 
Not Find Mouse on System"
SOLUTION: There is no mouse driver installed in DOS. A mouse driver 
must be installed before the game will run. Check your mouse 
documentation for loading instructions.

PROBLEM: When you start the game, the program crashes with a 
DOS/4GW Professional fatal error (1307): not enough memory.
SOLUTION: This is caused by a memory conflict, usually with a memory 
manager such as EMM386 or QEMM. Running the game from a boot 
disk will usually correct this problem. Use the game's INSTALL 
program to create a boot disk. If you experience problems, create a boot 
disk using the appropriate instructions in Sections 6 or 7. 

PROBLEM: You get an "Error reading Drive D" or "Unable to read drive 
D" message. (Drive letter will vary depending on your CD drive letter). 
The error may occur at the beginning of the game or randomly 
throughout the program.
SOLUTION: The most common reason for a "read error" is a dirty or 
scratched CD. You should check the CD to make sure that there are no 
smudges, fingerprints, scratches or cracks on it. If you see any smudges 
on the CD, clean it off with a soft cloth and try it again. 

If this doesn't work, the problem may lie with the CD ROM drivers. You 
should make sure that you are using the latest version (v2.23) of 
MSCDEX in your AUTOEXEC.BAT. If you're using DOS 6.2 or higher, 
use the MSCDEX in your C:\DOS directory; this one is version 2.23. If 
you're using Windows 95 and running the game in MS-DOS mode, you 
should be using the MSCDEX in your C:\WINDOWS\COMMAND 
directory; this one is version 2.25. You should also check with the CD 
ROM drive manufacturer to make sure that you have the latest version 
of their CD drivers. Outdated or incompatible drivers can also cause this 
type of problem.

This error can also be caused by a defective CD. The easiest way to get a 
new CD is to exchange it at the store where you bought the game. If they 
are unable to exchange the game, Sierra will replace it for you. Please 
see your game documentation for information CD replacement.

PROBLEM: You experience random lockups during the game, or your 
computer reboots during the middle of game play. Sometimes you 
receive memory errors or other problems when playing IndyCar Racing 
II. 
SOLUTION: This is caused by a memory conflict. Running the game from 
a boot disk will usually correct this problem. Use the game's SETUP 
program to create a boot disk. If you experience problems, please see the 
boot disk instructions in Sections 6 or 7.

PROBLEM: The graphics in the game are in low resolution or are 
distorted.
SOLUTION: Make sure you are typing INDYCAR -H to start the game in 
high resolution SVGA mode. If this doesn't help then your video card 
may be using an incompatible VESA driver. Make sure that you are 
using the VESA driver appropriate for your video card. Check your 
video card documentation for details. The game does include a universal 
vesa driver that can be installed by typing SETUP from the ICR2 
directory. In addition, graphics distortion can be caused by an 
incompatible mouse driver. Some DOS mouse drivers don't handle 
VESA (SVGA-resolution) applications well. Try switching to a 
Microsoft or Logitech mouse driver. Sierra recommends Microsoft 8.20 
or higher, or Logitech 6.1 or higher. If you are running the game in 
Windows 95, be sure that no other programs are running.

PROBLEM: The highlighted menu is scrolling uncontrollably.
SOLUTION: This problem is caused by a joystick (or other steering device) 
that is out of calibration. To stop the scrolling, press the "J" key at the 
Main Menu. This will turn off the joystick. Then, follow the steps below 
to calibrate the joystick:

1. Select OPTIONS from the Main Menu and press <ENTER>
2. Select CONTROLS and press <ENTER>
3. Select CALIBRATE JOYSTICK 1 and press <ENTER>
4. Push the joystick left, right, up and down and to all four corners. 
(NoteOn some wheels or yokes, you may only be able to "steer" 
left and right to calibrate.)
5. Press <ENTER>

Once the joystick is re-calibrated, return to the Main Menu and press the 
"J" key again to turn the joystick back on. For wheels and yokes with no 
Y-axis, it is not necessary to turn the joystick back on in the menus by 
pressing "J". The wheel will still function in driving mode.

PROBLEM: The replay is extremely short.
SOLUTION: The length of the replay is affected by the amount of available 
memory: the more available memory you have, the longer the replay 
will be. To increase the amount of free memory, create a boot disk using 
the automatic boot disk maker in the game's SETUP program or the 
appropriate instructions in Sections 6 and 7.

PROBLEM: The video is choppy.
SOLUTION: There are several steps you can take to improve the frame rate 
of IndyCar Racing II. These include:
 
1. Turning graphic options off. We usually suggest that people start 
by turning off road and grass textures. Next, turn off wall textures 
and possibly grandstands. Next, continue to turn off graphic 
options (car textures, horizon, etc.) until the frame rate improves to 
an acceptable level.
2. Reducing the number of opponents. Another way to improve frame 
rate is to reduce the number of opponents that you compete 
against. Reducing opponents from the default of 31 down to 15-20 
can have a dramatic effect on frame rates.
3. Reducing the drawing of opponents in front and behind. A third 
option to improve frame rate is to reduce the number of opponents 
that are being drawn in front and behind the user's car. Reducing 
these numbers to 5-6 in front and 1-2 behind can also have a great 
effect on frame rate.
4. Reduce the number of opponents that can be heard. Reducing the 
number of opponents that you can hear simultaneously to 2-3. This 
will reduce the strain on the processor and sound improve frame 
rate slightly.
5. Use FM sound. Yet another option is to use FM sound instead of 
digital sound. To do this, type INDYCAR -F from the ICR2 
prompt and press <ENTER>. The sound quality will not be as high 
as the digital sound, but it is much less memory intensive and can 
improve frame rate.
6. Run in standard VGA. If you are running the game in SVGA 
(HiRes), you need at least a 486DX2/66 with 8 MB RAM. This is 
the MINIMUM requirement for SVGA and you may have to 
reduce graphic detail and opponents significantly in order to get an 
acceptable frame rate. If lowering these options does not improve 
the frame rate enough, you're only option is a faster computer or to 
run the game in VGA.
 
PROBLEM: The joystick is calibrated but it doesn't appear to control the 
car properly.
SOLUTION: In order to play the game using a joystick, steering wheel 
device, or flight yoke, you have set up the controls in addition to 
performing a joystick calibration. To do this:

1. Start the game and get to the Main Menu
2. Highlight OPTIONS and press <ENTER>
3. Highlight CONTROLS and press <ENTER>
4. Highlight SET CONTROLS and press <ENTER>
5. Highlight each specific control (STEERING, ACCELERATION, 
etc.) and press <ENTER> then press the joystick button, keyboard 
key, or joystick direction that you want to use for each specific 
function. (NOTE: If you use the same key for two different 
controls, you will receive a "Conflicting Controls" error message 
when you try to exit the SET CONTROLS menu. You will need to 
make sure that all controls are set to different keys.)

PROBLEM: While using a steering wheel or yoke the car is steering in the 
opposite direction.
SOLUTION: Go into the OPTIONS/CONTROLS/SET CONTROLS menu. 
Choose STEERING and press <ENTER>. Slowly steer to the LEFT 
until you are sent back to the SET CONTROLS menu and release the 
yoke. The line next to steering shoud read: JOYSTICK 1 X-AXIS < >.

Once you see this, the joystick's steering should be set up properly. Set 
the other controls as necessary.

PROBLEM: The multiplayer mode won't work.
SOLUTION: (NOTE: For general information about modem play, see the 
section in the IndyCar Racing II manual starting on page 46.)

The most common problem with the multiplayer (modem play) feature 
is an incorrect modem initialization string. Several initialization strings 
for specific modems are included in the game. If your modem is not 
among those already in the game (or if the string does not work), you 
will need to construct the string manually. Specifically, the modem 
initialization string needs to do three (or four) things:

- Turn off data compression (hardware)
- Turn off error detection
- Turn off error corrections
- Set the modem to 9600 baud (recommended for any modem not 
listed in the game)

Information on how to construct an initialization string for your 
particular modem can be found in your modem manual. The string 
should follow the following format:

AT&F^M~~~AT______________^M

Enter the codes from the modem manual for the above functions into 
the blank line in the sample string.

ADDITIONAL MODEM STRINGS FOR INDYCAR RACING II:

Modem Name				Recommended Initialization 
String
----------				---------------------------------
Gateway Telepath II (550)		atz^m
Practical Peripherals 14.4		at&f&c0&k0&q6s95=44^m
USRobotics Sportster External           at&f^m~~~at&c1&d2&k0&m0&n6&a0^m
ViVa 14.4				at&f0&d2%cob8\n0^m (see note below)


If you don't see your question listed in this document: Most 
difficulties with IndyCar Racing II, including lockups and Fatal or Panic 
errors can be resolved by simply running the game with a boot disk. 
Please see Sections 6 and 7 for detailed boot disk instructions. 
Incompatible or outdated sound card and VESA drivers can also cause 
lockups and errors. You should make sure that you are using the latest 
versions of your sound card and video drivers. Contact your sound and 
video card manufacturers to obtain the latest drivers. If you are 
experiencing problems in Windows 95, restart the computer in DOS 
mode and run the game in that environment.


SECTION 4 - COMMON SOUND PROBLEMS

PROBLEM: The game locks up with the last information displayed being 
sound card settings.
SOLUTION: This lockup is caused by an incorrect sound card choice or one 
of it's settings. Run SETUP from the \ICR2 directory to change the 
settings. Please consult your sound card documentation for the correct 
sound card setup. Otherwise, go to the Setup Sound Card – Manual 
and select Change Digital Sound Card. Choose None from the choices 
and the game will play.

PROBLEM: When running the game, you get no sound and/or music.
SOLUTION: This is usually caused by either incorrect sound settings in the 
program or insufficient free memory. First, check your sound settings 
for the game. If you're running under Windows 95, consult your 
Windows 95 documentation on how to change and configure sound 
drivers. If you're running under DOS, run the SETUP program from the 
\ICR2 directory. Select Setup Sound Card - Manual and follow the on 
screen instructions. If the Sound Blaster setting doesn't work, check 
your sound card documentation to see if your card can emulate the 
Microsoft Sound System, then set the card up for that mode and re-run 
the SETUP program. If you're sure that all of your settings are correct in 
SETUP, you may not have enough available memory to run the game 
with full music and sound effects under your current configuration. 
Running the game from a boot disk should correct this problem. Use the 
game's SETUP program to create a boot disk or use the boot disk 
instructions in Sections 6 and 7.

NOTE: NOTE: Some sound drivers do not support sound correctly 
when running DOS applications under Windows 95. This usually occurs 
when the sound card is not directly supported by Windows 95, which 
forces you to use the Windows 3.1 drivers for the sound card. Common 
symptoms of this are lockups or simply no sound. You should be able to 
get around this by restarting your computer in MS-DOS mode (with a 
boot disk, if necessary) and running the game from DOS. If you 
continue to experience problems with sound after booting from a boot 
disk, check your sound card documentation to make sure that you have 
all of the necessary lines in the CONFIG.SYS and AUTOEXEC.BAT 
files, or contact your sound card manufacturer for details or information 
on updated Windows 95 drivers.

PROBLEM: While playing the game, the sound slows down or drops out, 
or the video display becomes choppy and slow.
SOLUTION: This is often caused by insufficient available memory. 
Running the game from a boot disk should correct this problem. Use the 
Install program to create a boot disk or use the boot disk instructions in 
Sections 6 or 7. If you are running in Windows 95 make sure no other 
applications are running. This includes screen savers, virus scanners and 
anything using sound..


SECTION 6 - INDYCAR RACING II BOOT DISK INSTRUCTIONS FOR DOS

IndyCar Racing II can make a boot disk for you. In order to do this 
insert a blank disk in your A: Drive. Then change to the directory for the 
game (i.e. \ICR2). Then at the prompt type SETUP <Enter>. Then 
follow the instructions as they appear on the screen. This should work to 
make a boot disk, however, if it doesn't you can follow the steps below 
to make a boot disk manually.

STEP 1 - FORMATTING THE DISK
To make a boot disk, you must system format a high density diskette in 
the A: drive. This procedure will transfer the "system files" to the disk 
and allow the computer to boot up correctly. The disk must be in the A: 
drive; the computer will not boot from the B: drive. At a DOS prompt, 
type the FORMAT command as follows:

FORMAT A: /S <ENTER>
If you get a "Bad command or file name" error message, type: 

PATH=C:\DOS <ENTER>

Then retype the FORMAT command above. If you receive the error 
again, the MS-DOS FORMAT command may not be on your system, or 
it may have been renamed. Programs such as PC Tools and Norton Disk 
Utilities sometimes rename the FORMAT command to prevent 
accidental loss of data. If you are using a program of this type, check 
your documentation to find out how to format a SYSTEM DISK, then 
proceed to Step 2. 

STEP 2 - LOCATING THE MOUSE DRIVER 
If you are playing a game that uses a mouse, the Microsoft compatible 
mouse driver must be loaded into memory with the boot disk. There are 
two kinds of mouse drivers available: those that load in the 
CONFIG.SYS file and those that load in the AUTOEXEC.BAT file. 
CONFIG.SYS mouse drivers have an extension of .SYS (MOUSE.SYS) 
and 
AUTOEXEC.BAT drivers have either a .COM or .EXE extension 
(MOUSE.COM, MOUSE.EXE). You must load at least one of these 
drivers, but it is not necessary to load them all. 


If you do not know where the mouse drivers are located on your system, 
the command below should help you locate them. Type the following at 
the C:\ prompt:

DIR MOUSE* /S <ENTER>

This command will cause the system to search all subdirectories for a 
file called MOUSE. If the system locates a MOUSE file, it will display 
the path where the file is located. For example, if the MOUSE.COM file 
is located in a C:\MOUSE directory, the system will display:

Directory of C:\MOUSE
	MOUSE.SYS			55160 	03-10-92	3:10a
	MOUSE.COM			56408	03-10-03	6:00a

If this procedure does not locate a MOUSE file, your mouse driver may 
have a different name; some common names for mouse drivers are 
IMOUSE, GMOUSE and HPMOUSE. Your should check your mouse 
documentation for the exact file names and how to install them. 

Once you have located the mouse driver, you must copy it to the boot 
disk. The following example assumes that the mouse drivers are located 
in the C:\MOUSE directory as shown above. To copy the MOUSE files 
to the boot disk, type:

COPY C:\MOUSE\MOUSE.* A: <ENTER>

Substitute the appropriate path and file names for your mouse drivers in 
the command above. After you press ENTER, you should see a message 
indicating that some files were copied.

STEP 3 - LOCATING THE CD ROM DEVICE DRIVER
The CD ROM drive requires a device driver loaded in the CONFIG.SYS 
file. This driver must be loaded correctly or you will be unable to access 
your CD ROM drive. To make sure that the device driver loads correctly 
on the boot disk, look at the CONFIG.SYS on the hard drive and copy 
the driver line from there. To display the CONFIG.SYS, type the 
following at a DOS prompt:

CD\ <ENTER>
EDIT CONFIG.SYS <ENTER>

The CONFIG.SYS file will display on the screen. Look for the line that 
loads the CD ROM device driver. The line should look something like 
this:

DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
DEVICEHIGH=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
DEVICEHIGH /L:14652 =C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220

The device driver in your CONFIG.SYS may differ slightly from those 
listed above. Carefully write down the line for use in your boot disk.

To exit the CONFIG.SYS, press the <ALT>, <F>, then <X> keys.

If you have a SCSI CD ROM drive, there may be an additional driver in 
your CONFIG.SYS that must be loaded for the CD ROM device drivers 
to load correctly. Check your CD drive documentation for more 
information. 

NOTE: If you cannot locate the driver in your CONFIG.SYS file, check 
your CD-ROM drive documentation, or contact the drive's 
manufacturer.

STEP 4 - LOCATING THE MSCDEX CD ROM EXTENSION
In addition to the CD ROM device driver in the CONFIG.SYS, your CD 
ROM drive requires MSCDEX, the Microsoft extension for CD ROM 
drives. If this extension is not loaded correctly in the AUTOEXEC.BAT, 
you will be unable to access your CD ROM drive. To display the 
AUTOEXEC.BAT, type the following at a DOS prompt:

CD\ <ENTER>
EDIT AUTOEXEC.BAT <ENTER>

The AUTOEXEC.BAT file will display on the screen. Look for the line 
that loads MSCDEX. It should look something like this:

C:\DOS\MSCDEX /D:MSCD001
LH C:\DOS\MSCDEX /D:MSCD001 
LOADHIGH /L:14429 C:\DOS\MSCDEX /D:MSCD001

The MSCDEX line in your AUTOEXEC.BAT may differ slightly from 
the ones above. Carefully write down the line for use in your boot disk. 
Add "LH" or "LOADHIGH" commands to the front of the line if it is 
not already there.

To exit the AUTOEXEC.BAT, press the <ALT>, <F>, then <X> keys.

STEP 5 - LOCATING THE SOUND CARD DRIVERS
Many sound cards have drivers or initialization lines that must be loaded 
in the AUTOEXEC.BAT or CONFIG.SYS. Some sound cards that 
require these drivers or initialization routines are the SoundBlaster 16, 
MAD16 and the Aria 16.

At the end of these Boot Disk Instructions, you will find a section 
labeled "Sound Cards". These tables contain the sound card lines for 
many common sound cards. Check to see if your sound card is on the 
list. If it is, you will need to add the appropriate lines to the 
AUTOEXEC.BAT and/or CONFIG.SYS on your boot disk. If your 
sound card is not listed, you should check your documentation for 
information on what needs to load in the AUTOEXEC.BAT and 
CONFIG.SYS. 

STEP 6 - CREATING THE CONFIG.SYS FILE
To create the CONFIG.SYS file on the boot disk, type the following at a 
DOS prompt:

A: <ENTER>
CD\ <ENTER>
EDIT CONFIG.SYS <ENTER>

This will display the blank (usually blue) screen of the DOS Editor. 
Enter the following lines:

DEVICE=C:\DOS\HIMEM.SYS 
DOS=HIGH,UMB 
FILES=30
BUFFERS=20 

If you're using MOUSE.SYS to load your mouse, add the following 
line:

DEVICE=A:\MOUSE.SYS 

Add the CD ROM device driver as you wrote it down in the "Locating 
the CD ROM Device Driver" section. The device driver should look 
something like this:

DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220 

If you need to load any sound card drivers, copy them from the "Sound 
Cards" section now. The following example lines are for the 
SoundBlaster 16:

DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5 
DEVICE=C:\SB16\DRV\CTMMSYS.SYS

Save the file by pressing <ALT>, <F>, then <S>. Exit the file by 
pressing <ALT>, <F>, then <X>.

STEP 7 - CREATING THE AUTOEXEC.BAT FILE
To create the AUTOEXEC.BAT file on the boot disk, type the following 
at a DOS prompt:

A: <ENTER>
CD\ <ENTER>
EDIT AUTOEXEC.BAT <ENTER>

This will display the blank (usually blue) screen of the DOS Editor. 
Enter the following lines:

@ECHO OFF
C:\ 
SET COMSPEC=C:\COMMAND.COM 
PROMPT SIERRA BOOT DISK $_$P$G 
PATH=C:\;C:\DOS;C:\SIERRA 

If you are using the MOUSE.COM or MOUSE.EXE file to load your 
mouse, add the appropriate line:

A:\MOUSE.COM

Add the MSCDEX line as you write it down in the "Locating the 
MSCDEX CD ROM Extension" section. For example:

C:\DOS\MSCDEX /D:MSCD001 

If you need to run any sound card initialization programs or load any 
drivers, copy them from the "Sound Cards" section now. The following 
example lines are for the SoundBlaster 16:

SET BLASTER=A220 I5 D1 H5 T6 
SET SOUND=C:\SB16
SET MIDI=SYNTH:1 MAP:E 
C:\SB16\SB16SET /M:220 /VOC:220 /CD:220 /MIDI:220 /LINE:220 
C:\SB16\DIAGNOSE /S 

Save the file by pressing <ALT>, <F>, then <S>. Exit the file by 
pressing <ALT>, <F>, then <X>.

STEP 8 - REBOOT THE COMPUTER AND START THE GAME
Reboot your system by pressing the <RESET> button on your computer 
or by using the <CTRL> <ALT> <DELETE> key sequence on your 
keyboard. Follow the instructions in the game manual to start the game.


SECTION 7 - WINDOWS 95 BOOT DISK INSTRUCTIONS 

IMPORTANT NOTE: Please read all instructions before beginning 
this procedure. SECTION 7a will help you make a boot disk that will 
start Windows 95, SECTION 7b will help you create a boot disk which 
boots the computer to MS-DOS mode.

SECTION 7a - TRY THIS FIRST!

The following instructions will work for most systems. If this procedure 
doesn't allow you to start IndyCar Racing II please follow the steps 
outlined in SECTION 7b.

To make a boot disk, you must system format a high density diskette in 
the A: drive. This procedure will transfer the "system files" to the disk 
and allow the computer to boot up correctly. The disk must be in the A: 
drive; the computer will not boot from the B: drive. 

To format a disk in Windows 95, put the disk in the drive, open My 
Computer, then right click on the A: icon. From the pop-up menu, 
select Format. Under "Format type" select Full; under "Other options", 
choose Copy system files. Click on Start. 

After the disk is formatted, you must copy the MSDOS.SYS file from 
the hard drive to the floppy disk. To do this, leave the floppy disk in the 
drive, open Windows Explorer and find the MSDOS.SYS file in the 
root of the C: drive. Right click on the file, then select Send to from the 
pop-up menu. Send the file to the A: drive and replace the existing file.

NOTE: If you don't see the MSDOS.SYS file in Explorer, the file is 
hidden. To make the file visible, select View, Options, then Show all 
files. If you do not wish the hidden files to remain visible, you can hide 
them again after you've made the boot disk by choosing View, Options, 
Hide files of this type.

Now that you have the boot disk created, go to the START button and 
select SHUT DOWN then select RESTART THE COMPUTER. When 
the system restarts you should have a configuration that will work to run 
IndyCar Racing II. If you still experience problems starting the game, 
use the instructions in SECTION 7b to make a boot disk.


SECTION 7b

STEP 1 - FORMATTING THE DISK
To make a boot disk, you must system format a high density diskette in 
the A: drive. This procedure will transfer the "system files" to the disk 
and allow the computer to boot up correctly. The disk must be in the A: 
drive; the computer will not boot from the B: drive. 

To format a disk in Windows 95, put the disk in the drive, open My 
Computer, then right click on the A: icon. From the pop-up menu, 
select Format. Under "Format type" select Full; under "Other options", 
choose Copy system files. Click on Start. 

STEP 2 - LOCATING THE MOUSE DRIVER 
If you are playing a game that uses a mouse, the Microsoft compatible 
mouse driver must be loaded into memory with the boot disk. There are 
two kinds of mouse drivers available: those that load in the 
CONFIG.SYS file and those that load in the AUTOEXEC.BAT file. 
CONFIG.SYS mouse drivers have an extension of .SYS (MOUSE.SYS) 
and 
AUTOEXEC.BAT drivers have either a .COM or .EXE extension 
(MOUSE.COM, MOUSE.EXE). You must load at least one of these 
drivers, but it is not necessary to load them all. 

If you do not know where the mouse drivers are located on your system, 
the command below should help you locate them. Type the following at 
the C:\ prompt:

DIR MOUSE* /S <ENTER>

This command will cause the system to search all subdirectories for a 
file called MOUSE. If the system locates a MOUSE file, it will display 
the path where the file is located. For example, if the MOUSE.COM file 
is located in a C:\MOUSE directory, the system will display:

Directory of C:\MOUSE
	MOUSE.SYS			55160 	03-10-92	3:10a
	MOUSE.COM			56408	03-10-03	6:00a

If this procedure does not locate a MOUSE file, your mouse driver may 
have a different name; some common names for mouse drivers are 
IMOUSE, GMOUSE and HPMOUSE. Your should check your mouse 
documentation for the exact file names and how to install them. 

Once you have located the mouse driver, you must copy it to the boot 
disk. The following example assumes that the mouse drivers are located 
in the C:\MOUSE directory as shown above. To copy the MOUSE files 
to the boot disk, type:

COPY C:\MOUSE\MOUSE.* A: <ENTER>

Substitute the appropriate path and file names for your mouse drivers in 
the command above. After you press ENTER, you should see a message 
indicating that some files were copied.

STEP 3 - LOCATING THE CD ROM DEVICE DRIVER
The CD ROM drive requires a device driver loaded in the CONFIG.SYS 
file. This driver must be loaded correctly or you will be unable to access 
your CD ROM drive. To make sure that the device driver loads correctly 
on the boot disk, look at the CONFIG.SYS on the hard drive and copy 
the driver line from there. To display the CONFIG.SYS, click on the 
Start button, then choose Run. In the command line, type SYSEDIT. 
The SYSEDIT window will appear. Click on the CONFIG.SYS title bar 
to display the CONFIG.SYS file. Look for the line that loads the CD 
ROM device driver. The line should look something like this:

DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
DEVICE /L:14652 =C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220

The device driver in your CONFIG.SYS may differ slightly from those 
listed above. Carefully write down the line for use in your boot disk. 

If you have a SCSI CD ROM drive, there may be an additional driver in 
your CONFIG.SYS that must be loaded for the CD ROM device drivers 
to load correctly. Check your CD drive documentation for more 
information. 

NOTE: If you cannot find your CD ROM driver in the CONFIG.SYS 
file, you may need to look in the CONFIG.DOS file. To access this file, 
choose Start, Run, then type NOTEPAD C:\CONFIG.DOS. If you 
still cannot locate the driver, check your CD ROM drive documentation 
or contact the drive's manufacturer. 

STEP 4 - LOCATING THE MSCDEX CD ROM EXTENSION
In addition to the CD ROM device driver in the CONFIG.SYS, your CD 
ROM drive requires MSCDEX, the Microsoft extension for CD ROM 
drives. If this extension is not loaded correctly in the AUTOEXEC.BAT, 
you will be unable to access your CD ROM drive. To make sure that 
MSCDEX loads correctly on the boot disk, use SYSEDIT to look at the 
AUTOEXEC.BAT on your C: drive and copy the MSCDEX line from 
there. It should look something like this:

C:\DOS\MSCDEX /D:MSCD001
LH C:\DOS\MSCDEX /D:MSCD001 
LOADHIGH /L:14429 C:\WINDOWS\COMMAND\MSCDEX /D:MSCD001

The MSCDEX line in your AUTOEXEC.BAT may differ slightly from 
the ones above. Carefully write down the line for use in your boot disk. 
Add "LH" or "LOADHIGH" commands to the front of the line if it is 
not already there.

STEP 5 - CREATING THE CONFIG.SYS FILE
To create the CONFIG.SYS file on the boot disk, choose Start, Run, 
then type NOTEPAD A:\CONFIG.SYS in the command line field. This 
will start the Windows Notepad program. In the new Notepad screen, 
enter the following lines:

DEVICE=C:\WINDOWS\HIMEM.SYS 
DOS=HIGH,UMB 
FILES=30
BUFFERS=20 

If you're using MOUSE.SYS to load your mouse, add the following 
line:

DEVICE=A:\MOUSE.SYS 

Add the CD ROM device driver as you wrote it down in the "Locating 
the CD ROM Device Driver" section. The device driver should look 
something like this:

DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220 

Save the file by clicking on File, Save. Close Notepad by clicking on 
File, Exit.

STEP 6 - CREATING THE AUTOEXEC.BAT FILE
To create the AUTOEXEC.BAT file on the boot disk, choose Start, 
Run, then type NOTEPAD A:\AUTOEXEC.BAT in the command line 
field. This will start the Windows Notepad program. In the new Notepad 
screen, enter the following lines:

@ECHO OFF
C:\ 
SET COMSPEC=C:\COMMAND.COM 
PROMPT SIERRA BOOT DISK $_$P$G 
PATH=C:\;C:\DOS;C:\SIERRA 

If you are using the MOUSE.COM or MOUSE.EXE file to load your 
mouse, add the appropriate line:

A:\MOUSE.COM

If your CD ROM drive requires the MSCDEX CD-ROM extension, add 
the line loading MSCDEX that you wrote down in Step 3.

Save the file by clicking on File, Save. Close Notepad by clicking on 
File, Exit.

STEP 7 - REBOOT THE COMPUTER AND RUN THE GAME
Leave the disk in the drive and restart the computer by clicking on Start, 
Shut Down., then Restart the computer. The computer will now re-
boot with the boot disk. When you get to the C:\ prompt, start IndyCar 
Racing II.

SECTION 8 - IF YOU STILL HAVE PROBLEMS
If you continue to experience problems, or if you have any questions 
concerning any of the above steps, Sierra Technical Support will be 
happy to assist you. You can reach Technical Support at (206) 644-4343 
between 8:15 am and 4:45 pm, Monday through Friday. We can also be 
reached by fax at (206) 644-7697 or by mail at the following address:

Sierra On-Line Technical Support
PO Box 85006
Bellevue, WA 98015-8506

In Europe, please contact our office in England. The Customer Service 
number is (44) 1734-303171, between 
9:00 am and 5:00 pm, Monday through Friday. The BBS number is (44) 
1734-304227 and the fax number 
is (44) 1734-303201. Customer Service can also be reached at the 
following address:

Sierra On-Line Limited
4 Brewery Court
The Old Brewery
Theale, Reading, Berkshire
RG7 5AJ UNITED KINGDOM

You can also contact our Technical Support Team on one of the 
following services:

Sierra BBS		(206) 644-0112 
CompuServe		GO SIERRA
America Online		KEYWORD SIERRA
Internet			http://www.sierra.com
			support@sierra.com

If you decide to write or fax, please provide the following information so
that Sierra Technical Support can assist you as efficiently as possible:

Name:
Fax number:
Phone number:
Address:

Game name, version number and S/N number (from disk #1 or CD hub): 

What problem are you having?  Be VERY specific.  Is there an 
error message?  What is it?  Where does it occur? Does it happen 
the same way each time?





Floppy or CD?

Are you playing in Windows or DOS?

Type of computer (386, 486, etc.)

Brand of video card (Trident, Diamond, etc.)

Amount of RAM (4 meg, 8 meg, etc.)

DOS version (MS-DOS 6.0, PC-DOS 6.2, etc.)

Windows version (3.1, WFWG, Win95, etc.)

Brand of sound card and sound card settings (SoundBlaster Pro, 
Forte16, Mozart, etc.  Please be VERY specific with the brand 
name. Sound card settings include DMA, IRQ and I/" values.)

Any disk compression?  What kind? (Doublespace, Stacker, etc.)

Any third-part memory manager?  What kind?  (QEMM, 386MAX, 
etc.)

Largest executable program size or bytes free after booting with the 
boot disk. (Type MEM to find out.) 

What have you tried so far?  (Boot disk, no sound, etc.)



Please attach copies of your CONFIG.SYS and AUTOEXEC.BAT 
from your hard drive and the boot disk.




SOUND CARD DRIVER INFORMATION 

NOTE:  The sound card drivers and initialization lines in this section are
the default settings for these devices.  You should check your AUTOEXEC.BAT
and CONFIG.SYS on your hard drive to see if you are using any non-default
settings.


ADLIB
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE

This is a MIDI card only and will not play most sound 
effects.


ARIA 16 - Common on IBMs
        AUTOEXEC.BAT
        SET ARIA=C:\ARIA
        SET BLASTER=A220 I5 D1 T5
        C:\DOS\SOUNDCLT.COM*

        CONFIG.SYS
        DEVICE=C:\ARIA\BIN\SOUNDCFG.SYS
        DEVICE=C:\ARIA\BIN\SNDSAVER.SYS
        
*This line is not always present.


ATI STEREO FXCD
        AUTOEXEC.BAT
        SET ATI_SND=C:\SFXCD

        CONFIG.SYS
        NONE


AUDIO ROCK IT 16
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE


AUDIO 16 BY AZTECH
        AUTOEXEC.BAT
        C:\GB2KAUDIO\UTILITY\GWBVOL
        SET BLASTER=*
        SET SOUND=*

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for
the SET BLASTER and SET SOUND parameters.


BOCA SOUND EXPRESS
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 T5

        CONFIG.SYS
        DEVICE=C:\SE1440\CSACMOD1.EXE


BREVE TECHNOLOGIES
        AUTOEXEC.BAT
        C:\BRV16F\DOSDRV\INIT16
        C:\BRV16F\DOSDRV\MIXER

        CONFIG.SYS
        NONE


CRYSTAL CLEAR WAVE TABLE BY CRYSTAL LAKE
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 T5
        C:\CCLEAR\CSACMAX1.COM*
        C:\CCLEAR\CSACHMX1.COM**

        CONFIG.SYS
        DEVICE=C:\CCLEAR\CSAMOD1.EXE -S***

*Enables Soundblaster compatibility.
**Add /ON to enable Soundblaster compatibility, /OFF to disable it.
***Use -S for Soundblaster mode and -W for Windows Sound System mode.


DIAMOND
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND16=C:\DIAMOND
        C:\DIAMOND\SNDINIT /B**

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.
**Use /C for Soundblaster mode and /B for Microsoft Sound System mode.


DIAMOND LX
        AUTOEXEC.BAT
        SET SOUND=C:\SONIC
        SET BLASTER=A220 I5 D1 T5
        C:\SONIC\MZTVOL.EXE
        C:\SONIC\MZTINIT WSS*
        C:\SONIC\MTZINIT.SYS

        CONFIG.SYS
        NONE

*Use WSS for Windows Sound System mode and SB for Soundblaster mode.


DSP16
        AUTOEXEC.BAT
        SET BLASTER=*

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.


ENSONIQ SOUNDSCAPE - Common on Gateways
Driver version 1.10 dated 11/31/94
        AUTOEXEC.BAT
        SET BLASTER=A220 Ixx Dx
        SET SNDSCAPE=C:\SNDSCAPE
        C:\SNDSCAPE\SSINIT FM*
        C:\SNDSCAPE\VSB_EMM.COM**

        CONFIG.SYS
        DEVICE=C:\DOS\EMM386.EXE***

*Use FM for FM synth, GM for General MIDI and MT32 for Roland MT32 emulation.
**Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT


ENSOMIQ SOUNDSCAPE - Common on Gateways
Driver version 1.20.02 dated 12/19/94
        AUTOEXEC.BAT
        SET BLASTER=A220 Ixx Dx
        SET SNDSCAPE=C:\SNDSCAPE
        C:\SNDSCAPE\SSINIT /I*
        C:\SNDSCAPE\VSB_EMM.COM**

        CONFIG.SYS
        DEVICE=C:\DOS\EMM386.EXE***

*/I enables FM synth and General MIDI emulation.
Run MT32.EXE to enable Roland MT32 emulation.
**Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT


ESS AUDIO DRIVE - Common on Compaqs
        AUTOEXEC.BAT            
        NONE     

        CONFIG.SYS
        DEVICE=C:\CPQDOS\VOLCTRL.EXE*
        DEVICE=C:\PCAUDIO\VOLCTRL.EXE**

*Loads the DOS mixer. <Ctrl/Right Shift> turns up the volume, <Ctrl/Left Shift>
turns it down.
**Necessary to load Windows mixer.


FORTE 16 - Common on Packard Bells
        AUTOEXEC.BAT
        SET BLASTER=*
        SET GALAXY=*
        SET SOUND=C:\FORTE16
        C:\FORTE16\UTILITY\EMUTSR

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for these settings.
**Enables the Soundblaster emulation.


FUSION 16
        AUTOEXEC.BAT
        SET BLASTER=*

        CONFIG.SYS
        DEVICE=C:\SPECTRUM\MVSOUND.SYS D: Q:**

*Check the AUTOEXEC.BAT on your hard drive for these settings.
**D: is the DMA channel and Q: is the IRQ setting


GALANT
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE


GALAXY - See Multi-Media Pro 16


GATEWAY 2000 AUDIO DRIVE
        AUTOEXEC.BAT
        C:\G2KAUDIO\UTILITY\GWBVOL
        SET BLASTER=A220 I5 D1 T5
        SET SOUND=C:\G2KAUDIO

        CONFIG.SYS
        NONE

This sound card will autoconfigure itself to Soundblaster or Microsoft
Sound System mode.


GOLDEN SOUND BY TOPEK
        AUTOEXEC.BAT
        C:\GS16\GS-ENV PC:\GS16ES

        CONFIG.SYS
        NONE


GRAVIS ULTRASOUND OR GRAVIS ACE
        AUTOEXEC.BAT
        SET ULTRASND=*
        SET ULTRADIR=*
        C:\ULTRASND\ULTRINIT
        SBOS.BAT**
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for complete SET lines for the GUS.
**The SBOS.BAT line must be loaded to enable the card's Soundblaster
emulation. This line is not needed for the ACE.


IBM PS/1
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE


ISP 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET ISP16=C:\ISP16
        C:\ISP16\ISPINIT /B/M*

        CONFIG.SYS
        NONE
*Use /B switch for SB mode
*Use /M switch for  Microsoft Sound System mode



JAZZ 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\JAZZ\JAZZ.SYS D:* Q:*

*D:  DMA CHANNEL.
*Q:  IRQ SETTING.
Specific values and directories may change



MAD 16
        AUTOEXEC.BAT
        SET MAD16=C:\MAD16
        SET BLASTER=A220 I5 D1 
        C:\MAD16\M16INIT /B /M*

        CONFIG.SYS
        NONE

*Use /B switch for Soundblaster  mode.  Use /M switch for Microsoft Sound
System Mode



MAGIC S20 - Common on Acers
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND16=C:\MAGICS20
        C:\MAGICS20\SNDINIT /B /M*

        CONFIG.SYS
        NONE

*Use /B switch for Soundblaster  mode.  Use /M switch for  Microsoft Sound
System Mode



MAGITEC GREEN 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE



MEDIA CONCEPT
        AUTOEXEC.BAT
        SET MC=C:\MC

        CONFIG.SYS
        NONE



MEDIA VISION DELUXE
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\MEDVSN\VBEAI.COM

        CONFIG.SYS
        DEVICE=C:\MEDVSN\PROS.SYS



MEDIA VISION PREMIUM 3D SCSI2
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\MEDVSN\PA3D.SYS
        DEVICE=MINI406A.SYS



MMCD16W
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=C:\MMCD16W
        SET GALAXY=*

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT for the SET BLASTER and SET GALAXY parameters



MONTE CARLO BY TURTLE BEACH
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\MCARLO\MCHKMIX

        CONFIG.SYS
        DEVICE=C:\MCARLO\MCMODE -S -W*

*Use -S switch for SB mode
*Use -W switch for  Microsoft Sound System Mode



MOZART SOUND CARD Common on Canons
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\MOZART
        C:\MOZART\MTZVOL.EXE

        CONFIG.SYS
        DEVICE=C:\MOZART\MZTINIT.SYS WSS /530*

*WSS /530 Puts the card into WSS mode port 530



MULTI-MEDIA PRO 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        SET SOUND=C:\MMP16P

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the full SET GALAXY line.



MW WAVE - Common on IBM Thinkpads
        AUTOEXEC.BAT
        SET BLASTER=
        SET MWPATH=C:\MWD\MANAGER;C:\MWD\MWGAMES*
        SET MWROOT=C:\MWD
        MWGAMES=ON**

        CONFIG.SYS
        NONE

*This is all one line.
**ON turns on Soundblaster emulation and OFF turns it off.



ORCHID GAMEWAVE
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=*
        C:\GW32\GW32.EXE

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
SET BLASTER lines.



ORCHID SOUNDWAVE
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=*
        C:\SW32\SW32.EXE

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
SET BLASTER lines.



PHILLIPS
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE



PRO AUDIO SPECTRUM 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\SPECTRUM\MVSOUND.SYS D:*Q:*

*D:  DMA CHANNEL.      Q:  IRQ SETTING.
<DIR> may be PROAUDIO on older drivers.



PRO SONIC
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\PROSONIC\PROSYS.SYS



SC400
        AUTOEXEC.BAT
        SET SOUND=C:\SC400
        SET BLASTER=A220 I5 D1
        C:\SC400\UTILITY\SNDINIT /B

        CONFIG.SYS
        NONE



SGBAS16
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=C:\SGBAS16
        SET GALAXY=*

        CONFIG.SYS
        DEVICE=C:\SGBAS16\DRIVERS\EEPRO.SYS

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY and
SET BLASTER lines.



SOUNDBLASTER AWE 32 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\SB16
        C:\SB16\SB16SET /P/Q
        C:\SB16\DIAGNOSE /S*
        C:\SB16\AWEUTIL /S

        CONFIG.SYS
        DEVICE=C:\SB16\DRV\CTSB16.SYS   /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
        DEVICE=C:\SB16\DRV\CTMMSYS.SYS**

*May be SBCONFIG on older cards.
**This line is only required to enable the sound card's CD-ROM interface.



SOUNDBLASTER PRO
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\SBPRO*
        C:\SBPRO\SBP_SET*

        CONFIG.SYS
        NONE

*On newer cards the drivers and such may look like 
the SB16 except loading out of a different directory.



SOUNDBLASTER 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 H5 T6
        SET SOUND=C:\SB16
        SET MIDI=SYNTH:1 MAP:E
        C:\SB16\SB16SET*
        C:\SB16\DIAGNOSE /S**

        CONFIG.SYS
        DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
        DEVICE=C:\SB16\DRV\CTMMSYS.SYS***

*Check the AUTOEXEC.BAT on your hard drive for the complete SB16SET line.




SOUND EXPRESSION BY BOCA
        AUTOEXEC.BAT
        SET BLASTER=
        C:\CE1440\CSACMAX1.COM*
        C:\CE1440\CSACHMX1.COM**

        CONFIG.SYS
        DEVICE=C:\SE1440\CSACMOD1.EXE -S -W***

*Enables Soundblaster compatibility.
**/ON turns on Soundblaster compatibility, /OFF turns it off.
***-S for Soundblaster mode and -W for Windows Sound System mode.




SOUND EZ - See Mad 16



SOUND FX PLUS
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SOUND=C:\MMSUP

        CONFIG.SYS
        NONE




SOUNDMAND BY LOGITECH
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\SOUNDMAN\MVSOUND.SYS




SOUND 16A - Common on Packard Bells 1 OF 2**
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        C:\SOUND16A\UTILITY\SETMODE /MSS**
        SET SOUND16=C:\SOUND16A

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /SB switch for SB mode. Use /MSS switch for Microsoft Sound System Mode.




SOUND 16A - Common on Packard Bells 2 OF 2**
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        C:\AUDIO\SNDINIT.EXE /B**
        SET SOUND16=C:\AUDIO

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /B switch for SB mode
**Use /M switch for  Microsoft Sound System Mode




SOUND 144 - Common on Packard Bells
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        SET SOUND=SOUND144
        C:\SOUND144\UTILITY\SETMODE /SBP**

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.




STRAUSS
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE





TROPEZ BY TURTLE BEACH 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\TROPEZ\DOSAPPS\SETUPSND*
        C:\TROPEZ\DOSAPPS\TZMODE -S*

        CONFIG.SYS
        DEVICE=C:\TROPEZ\DOSAPPS\TZMODE**

*Windows will disable these lines, so they will need to be run again
if Windows is started and shut down.  Use -S for Soundblaster mode and -W
for Windows Sound System mode on the TZMODE line.
**This line is necessary if the sound card is also 
acting as the CD-ROM controller.




VIBRA 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 H5 T6
        SET SOUND=C:\VIBRA16
        SET MIDI=*
        C:\VIBRA16\DIAGNOSE /S**
        C:\VIBRA16\MIXERSET /P/Q

        CONFIG.SYS
        DEVICE=C:\VIBRA16\DRV\VIBRA16.SYS
        DEVICE=C:\VIBRA16\DRV\CTMMSYS.SYS

*Check the AUTOEXEC.BAT on your hard drive for the complete SET MIDI line.
**Older cards may use SBCONFIG instead of DIAGNOSE.




VOYETRA SOUND
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET ISP16=ISP16*
        C:\ISP16\ISPINIT /B

        CONFIG.SYS
        NONE

*May be SET ISP16=VOYETRA




WAVERIDER BY AZTECH
        AUTOEXEC.BAT
        SET BLASTER=
        SET SOUND=C:\WAVRIDER
        SET GALAXY=
        C:\WAVRIDER\DRIVERS\WAVERIDE.EXE
        C:\WAVRIDER\SETMODE /SBP*

        CONFIG.SYS
        NONE

*Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.


