 
	
Sierra Technical Support	America Online:  Keyword SIERRA
PO Box 85006		       	Compuserve:  Go SIERRA
Bellevue, WA  98015-8506	Email:  support@sierra.com 
Phone:   (206) 644-4343		WWW:  http://www.sierra.com
Fax:     (206) 644-7697


IndyCar Racing Troubleshooting Guide
Revised 3/19/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 - SOUND ISSUES
SECTION 6 - GAME PLAY TIPS
SECTION 7 - OBTAINING A SIERRA PATCH DISK
SECTION 8 - INDYCAR RACING BOOT DISK INSTRUCTIONS FOR DOS
SECTION 9 - IF YOU STILL HAVE PROBLEMS...
SECTION 10 - ON-LINE DOCUMENTATION
SECTION 11 - CONTACTING SIERRA FOR FURTHER ASSISTANCE

SECTION 1 - HARDWARE REQUIREMENTS

REQUIRED:
386DX 25
6 MB RAM (Small Install)
5 MB Hard Drive Space (Small Install)
MS-DOS 5.0 or higher
Double Speed CD ROM Drive
VGA
RECOMMENDED FOR BEST PERFORMANCE:
486DX 33 or greater
8 MB RAM
Sound Blaster/Adlib Compatible
Joystick or driving wheel/pedal combo
SECTION 2 - INSTALLATION PROCEDURES

If you are in Windows 3.1, close Windows completely and exit to a DOS prompt. Insert the CD and switch to the CD drive by typing the drive letter followed by a colon. Ex: D:. Then type INSTALL to begin the installation program. Follow the on-screen prompts to complete the installation. 

If you are in Windows 95, insert the CD and click on your START button, then select RUN. In the box, type your CD ROM drive letter followed by a colon, then a backslash, and "INSTALL". 
Ex: D:\INSTALL. Finally hit <ENTER>.

SECTION 3 - COMMON INSTALLATION PROBLEMS

Problem: IndyCar Racing SE (Special Edition) CD will not install or will not run once installed on a Packard Bell computer with twin CD-ROM drives.
Solution: When this occurs, the game must be manually installed.
Follow these steps to manually install IndyCar Racing:

STEP 1 - Copying the files to the hard drive
1. Insert the IndyCar Racing SE CD into the CD-ROM drive
2. Type C: and press <ENTER>
3. Type XCOPY /S D:\*.* and press <ENTER>
4. Type INSTALL and press <ENTER>
5. Choose C for the drive to which to install the game and press <ENTER>
6. Choose /INDY for the directory to which to install the game and press <ENTER>
7. Once the installation is complete, press <ENTER>
8. Choose SETUP SOUND CARD and enter the requested information
9. Choose EXIT TO DOS

STEP 2 - Edit the configuration file to recognize the CD-ROM drive
1. From the DOS prompt, type C: and press <ENTER>
2. Type CD\INDY and press <ENTER>
3. Type EDIT LIB.CFG and press <ENTER>
4. Find the line that reads C:\INDYCAR and change in to read D:\INDYCAR
5. Exit the editor and save the file by pressing ALT, F, X, and Y.

STEP 3 - Delete the extraneous installation files
1. From the DOS prompt, type C: and press <ENTER>
2. Type CD\ and press <ENTER>
3. Type DELTREE INDYCAR and press <ENTER>
4. Type Y to confirm the deletion
5. Type DELTREE INSTALL and press <ENTER>
6. Type Y to confirm the deletion
7. Type DEL INSTALL.EXE and press <ENTER>

STEP 4 - Play IndyCar
1. From the DOS prompt, type C: and press <ENTER>
2. Type CD\INDY and press <ENTER>
3. Type INDYCAR and press <ENTER>

NOTE: This procedure will not autodetect your sound card; you must set up the sound card manually. Run the SETUP program in the C:\INDY directory to set up your sound card.



SECTION 4 - COMMON GAME PROBLEMS

Problem: Copy Protection appears when starting game.  Printed documentation is not provided.
Solution:  The copy protection has been disabled in this version of Indy Car II.  To bypass this screen, hit the <ESC> key.  The game should continue as normal.

Problem: When starting the game in Windows 95, you receive an error message stating, "DOS /4G error 2501: exception 0Eh (page fault) at XXX:XXXXXXXX --- Crash Address (unrelocated) 
Solution: This game will not run under Windows 95; you must restart your computer in MS-DOS mode and run the game in DOS. 

Problem: When starting the game you receive the following error messages: "DOS /4G error 2506: NOT ENOUGH PHYSICAL MEM (PHYSMIN) --- DOS/4G FATAL ERROR (1011):VMM INITIALIZATION ERROR (1)"
Solution: The game requires 3000K of physical extended memory available and 430K of conventional. Create a boot disk to free up more memory for the game. See Sections 8 and 9 for detailed boot disk instructions.

Problem: The picture gets very "jumpy" or the game plays slowly.
Solution: Turn the graphic options off. 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.

The minimum and maximum frame rate settings in the OPTIONS\GRAPHICS menu do not affect the number of frames per second in the game. These options only have an effect on the graphics options that 
are set to AUTO. If the FPS settings are too high, all the graphics options will go off and most likely not come back again. If the numbers are too low or too close together, the graphics options will flash on and off repeatedly during the game and make frame rate very inconsistent. (NOTE: The maximum frame rate is only 15 FPS)

Problem: When you try to select a menu item, the item goes gray but nothing happens.
Solution: IndyCar Racing has problems when multiple (two or more) game ports are active at the same time. To correct this problem, make sure that only one of the game ports is active. This usually
involves either a hardware or software setting that disables the port - you should check with your hardware manufacturer to make sure. Game ports can be on sound cards, game cards, or hard-wired
to the motherboard. Instructions for disabling the game port may be found in the manuals for the sound card, game card, or computer manual or by contacting the manufacturer of the hardware.

Other problems may occur if there is an inactive game port with something plugged in. Often people have questions about why their joystick/wheel/yoke is not working. Often, the problem is either related to the fact that the joystick/wheel/yoke has not been calibrated and the controls have not been set or that the game port that the device is plugged in to is not active.

Problem: Occasionally the car seems to steer incorrectly or is drifting to the left or right.
Solution: In most cases, this problem occurs because the joystick has gone out of calibration. This is easily solved by following these steps:

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. (NOTE: On some wheels or yokes, you may only be able to steer left and right to calibrate.)
5. Press <ENTER>

The joystick should now be calibrated. If you have a Thrustmaster with floor pedals, you may also have follow the above steps and choose CALIBRATE JOYSTICK 2.

If you've already set up your controls, the game should be ready to play. If you haven't set up the controls, follow these steps:

1. Highlight SET CONTROLS (from the OPTIONS/CONTROLS menu and press <ENTER>
2. 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.

After setting up all the controls, return to the Main Menu and enter a race to make sure that the controls are set to your liking. If they're not, or your preferences change, you can always return to the SET CONTROLS menu and change them again.

Problem: The joystick won't calibrate or loses calibration during the game.
Solution: If you have a joystick calibration program from the joystick manufacturer, run it and calibrate your joystick in DOS, using that program. Then, go back into IndyCar and calibrate the joystick within the game. This usually corrects the problem. 

If the above steps don't help, the problem may stem from the fact that your joystick port cannot keep up with polling requests from the game. If you have a 486 or a Pentium computer and you are using a generic game card or the built-in joystick port, the card/port may not be able to handle the combination of the speed of the machine and the rate of the joystick polling requests that the game uses. Polling the joystick port at a high rate insures the smoothest possible joystick control. 

Sierra and most major joystick manufacturers recommend a dedicated joystick card that can be calibrated to the speed of your computer. CH Products, Thrustmaster and Gravis all make excellent speed-adjustable joystick cards. You can find these cards at your local software or hardware dealer. Dedicated joystick cards are relatively inexpensive ($20-$40) and will usually solve this kind of problem. 

If you use a dedicated joystick card already, you should make sure that all other joystick ports are disabled. Other joystick ports can be found on your sound card, game port or multi-I/O card. Check your hardware documentation for more information on disabling joystick ports. 

Problem: The yellow flag remains active throughout the race if it comes out after an accident.
Solution: Three of the IndyCar expansion tracks (Detroit, Indianapolis, and Mid Ohio) have incorrect information in their .TXT files. This causes the yellow flag to remain active throughout the whole race if it comes out after an accident. To solve this problem, you must edit the individual tracks .TXT file and correct the GFLAG entry. 
To do this:

1. Type CD\INDYCAR and press <ENTER>
2. Type CD [track name] (substitute INDY, MIDOHIO, DETROIT for the appropriate track).
3. type EDIT [track name].TXT (substitute INDY, MIDOHIO, DETROIT for the appropriate track).
4. Change the number in the GFLAG line to correspond to the one of the following.

	Detroit: 		64698698
	Indianapolis:	64198652
	Mid Ohio: 	66789081

5. Save and exit.

The changes will take effect the next time you race at the specific track.

Problem: You're having trouble getting modem play to work. 
Solution: (NOTE: You must be using v1.04 or later in order for modem play to work properly.) 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 (required for IndyCar)

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


Modem Name				Recommended Initialization String
----------        			---------------------------------
Gateway Telepath			at&f^m~~~atn0s37=9&c1&d2&k0&q0%c0^m
Intel 144/144e				at&f^m~~~at&c1&d2%c0-j0^m
Practical Peripherals PM14400FXMT	at&f^m~~~atn0s37=9&q6^m
SupraFAXModem				at&f^m~~~atn0s37=9&c1&d2&k0&q0%c0^m
USRobotics Sportster			at&f^m~~~at&c1&d2&k0&m0&n6^m
Zoom/FaxModem				at&f^m~~~atn0s37=9&c1&d2&k0%c0^m
Zoom 14.4				at&f^m~~~at&k0q0&d2e1v1x4s37=9n0^m
Zoom 28.8				at&f^m~~~at&k0q0&d2e1v1x4s37=9n0^m


Problem: How do you install the IndyCar Racing v1.04 Patch? (3.5 disk version only)
Solution: Here are the instructions for installing the v1.04 patch from diskette:

1. Insert the diskette in drive A:
2. Type A: and press <ENTER>
3. Type INSTALL and press <ENTER>
4. Enter the drive and directory to which IndyCar is installed and the installer will update your IndyCar program to version 1.04.

Here are the instructions for installing the v1.04 patch if it has been downloaded from our BBS or an on-line service. When downloaded, the patch file should be called ICR104.ZIP. The .ZIP extension means that the file is compressed and requires PKUNZIP or another decompression utility. Here are the steps to take:

1. Go to the directory where the ICR104.ZIP file is located
2. Type COPY ICR104.ZIP C:\INDYCAR and press <ENTER>
3. Type CD\INDYCAR and press <ENTER>
4. Type PKUNZIP INDYCAR.ZIP and press <ENTER>

This command will "unzip" or decompress the file and make it usable. You should make a backup copy of the ICR104.ZIP file in case you ever need to reinstall the game. If you save this file to a diskette, you will be able to update the program again after reinstallation.

Problem: When installing the IndyCar Circuits Track Pack, the installation program returns an error message of "Wrong Disk in Drive" after Disk #2 is inserted. 
Solution: This problem is easily corrected by booting with a boot disk and reinstalling the game. See Sections 8 and 9 for detailed boot disk instructions. 

General Troubleshooting Steps
If you do not see your specific problem listed above, these standard troubleshooting procedures correct most problems running IndyCar Racing. 

Step 1 - Run the program from a minimal boot disk.
A boot disk is a tool that can be used to resolve most conflicts. Boot disks will free up more system resources and memory for your games. The boot disk also creates an environment that is "cleaner" or free of extra TSR and utilities that can sometimes cause conflicts. Boot disk instructions are included in Sections 8 and 9 of this document.

Step 2 - Check for corrupted files. 
Run CHKDSK /F or SCANDISK to detect and correct any hard drive errors and corrupted files. If you find any errors such as cross-linked or truncated files or lost allocation units, correct them, then delete and reinstall IndyCar Racing.

Step 3 - Check for sound card conflicts.
Many lockups in games can be traced to sound card configuration. To determine if you have a sound card lockup, run the SETUP program and change the setting to NONE. If the game works with this setting, but locks up with a sound card selection; you will know there is some sort of sound card conflict. See your sound card's documentation for help resolving sound card conflicts. Also reference Section 5 for help with sound problems.

Step 4 - Reinstall the game in a clean boot environment.
Lockups and other technical problems can be caused by corrupted game files. No program will run correctly if the data or executable files are corrupted. These corruptions will occur during the installation of the game and are usually due to conflicts with TSRs or other utilities running in DOS during the installation. Reinstalling the game in the same DOS environment will usually result in the same corrupted data. You should install the game in a "clean" boot environment.

Step 5 - Check your drivers! Outdated or incompatible video or sound drivers can also cause lockups and errors in Windows. Sierra recommends you check with your sound and video card manufacturers to make sure you have the latest versions of these drivers. Some manufacturers update their drivers several times a year, so it's easy to get behind.


SECTION 5 - SOUND ISSUES

IndyCar Racing supports a variety of different sound cards. The game's sound and music configuration is set up through a program called SETUP in the \INDYCAR directory. The SETUP program is run automatically when you first install the game, but you can run it again at any time to change the sound card configuration.. 

Problem: No sound through the PC speaker.
Solution: The sound effects in IndyCar are too complicated for the PC speaker to produce. Therefore, there will be no sound through the PC speaker if you do not have a sound card. The game should run fine without a sound card, just silently. 

SECTION 6 - GAME PLAY TIPS

Technical Support has limited information on IndyCar Racing strategy and game-play hints. This section contains answers to some frequently-asked questions. For additional game-play information, Sierra recommends the IndyCar manual and on-line forums that address sports simulations. CompuServe and America On-Line have active forums where you can obtain valuable information from your fellow racing fans!
 
Question: When the driver crashes during a race or is otherwise eliminated (disqualification, etc.), is there a way the complete the race more quickly?
Answer: IndyCar Racing Version 1.04 has an "accelerated time" feature that allows you to speed up the race if you're eliminated from contention (either through crash or disqualification). If you do not have Version 1.04, see Section 7 on how to obtain a sierra patch disk.

1. Press the ESC key to go to the Standings Screen
2. Press the A key to begin accelerated time.

You will receive a DNF (Did Not Finish) for the race and the computer will simulate the rest of the race.


SECTION 7 - OBTAINING A SIERRA PATCH DISK
There is currently one patch available for IndyCar Racing 3.5", ICR104.EXE.

The fastest way to obtain a Sierra patch disk is to download it from one of the following on-line services: the Sierra BBS (206-644-0112), CompuServe (GO SIERRA) or America OnLine (KEYWORD SIERRA). The file name is ICR104.EXE. You can also request a patch disk be mailed to you by writing to Sierra Technical Support, PO Box 85006, Bellevue, WA 98015-8506. 

When you receive the patch, please view the README file for complete details about what the patch addresses.

SECTION 8 - DOS BOOT DISK INSTRUCTIONS

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 CD ROM DEVICE DRIVER (Skip if not playing the CD version of IndyCar.)
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 3 - LOCATING THE MSCDEX CD ROM EXTENSION (Skip if not playing the CD version.)
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 4 - 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 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 5 - 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 
FILES=30
BUFFERS=20 

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

DEVICE=A:\MOUSE.SYS 

If necessary, add the CD ROM device driver. For example: 

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

If necessary, add the sound card drivers. 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 6 - 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

If necessary, add the MSCDEX line as you wrote it down above. 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 9 - WINDOWS 95 BOOT DISK INSTRUCTIONS

NOTE: Since IndyCar was released before Windows 95 became available, the game may not run under the Windows 95 environment. If you are having trouble running IndyCar under Windows 95, create a boot disk using the following instructions. Restart your computer in MS-DOS mode and play the game from DOS. 

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. 

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 MS-DOS.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. 

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.

STEP 2 - LOCATING THE MOUSE DRIVER
If you want to use a mouse with IndyCar Racing, 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, you can use Windows Explorer to find them. In Explorer, choose Tools, Find, Files or Folders. In the "Named" field, type MOUSE*; in the "Look In" field, type C:\, then click on Find Now. Explorer will search your hard drive for all files named MOUSE. All the MOUSE files will be listed at the bottom of the "Find: All Files" dialogue box. 

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. Select the driver you wish to use (MOUSE.COM, MOUSE.EXE or MOUSE.SYS) and right click on it. Choose Send to and copy the file to A:.

STEP 3 - LOCATING THE CD ROM DEVICE DRIVER (skip if not playing the CD version of IndyCar)
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
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. 

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 (skip if not playing the CD version)
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:\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. 

NOTE: If you cannot find the MSCDEX line in the AUTOEXEC.BAT file, you may need to look in the AUTOEXEC.DOS file. To access this file, choose Start, Run, then type NOTEPAD C:\AUTOEXEC.DOS. 

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, 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 

If you're playing a CD game, add the CD ROM device driver as you wrote it down in the "Locating the CD ROM Device Driver" section. If you're playing a standard DOS game, 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 clicking on File, Save. Close Notepad by clicking on File, Exit.

STEP 7 - 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 these 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 you're playing the CD version of IndyCar, 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 <ENTER>
SET SOUND=C:\SB16 <ENTER>
SET MIDI=SYNTH:1 MAP:E <ENTER>
C:\SB16\SB16SET /M:220 /VOC:220 /CD:220 /MIDI:220 /LINE:220 <ENTER>
C:\SB16\DIAGNOSE /S <ENTER>
Save the file by clicking on File, Save. Close Notepad by clicking on File, Exit.

STEP 8 - REBOOT THE COMPUTER
Leave the disk in the drive and restart the computer by clicking on Start, Shut Down. If you want to play your DOS game in Windows, click on Restart the computer. If you prefer to play in DOS, choose Restart the computer in MS-DOS mode.

NOTE: Many DOS games may not run well under Windows '95. Sierra highly recommends starting the computer in 
MS-DOS mode if you experience memory errors, lockups or other problems in Windows '95. 

STEP 9 (optional) - BOOTING TO YOUR PREVIOUS VERSION OF MS-DOS
In some instances, the above steps may not give you enough memory to run your MS-DOS game. If you continue to have problems after making the boot disk, you may want to boot your computer to your previous version of MS-DOS. This is especially helpful if the game was running without problems before you upgraded to Windows '95. 

To boot to your previous version of MS-DOS, you must edit the MSDOS.SYS file on the boot disk. Click on Start, Run, then type NOTEPAD A:\MSDOS.SYS in the command line. The MSDOS.SYS file will appear on the screen. Under the [options] section of this file, add the following lines:

BootMulti=1
BootMenu=1 

Save the file by clicking on File, Save. Close Notepad by clicking on File, Exit. Restart the computer. During the startup process, a menu will be displayed. The last choices on this menu will be "Previous DOS version". Select this option to start your computer in your previous version of MS-DOS.

NOTE: This procedure will only work on computers that have been upgraded to Windows '95 from a previous version of DOS. If there is no previous operating system on the computer, these steps will have no effect.


SECTION 10:  ON-LINE DOCUMENTATION INFORMATION

The complete Indy Car Racing Manual has been included on this CD.  To view the manual you will need to use Adobe Acrobat.  While we have included both the DOS and Windows versions of the Adobe Acrobat Reader, the Windows version is much easier to use and is more visually appealing.  Therefore we suggest that you install the Windows version of Adobe Acrobat.  Additional information is found in README1.TXT.

To install the Windows version in Windows 3.1x and 95:

        1.      Start Windows
        2.      If you are using Windows 3.1 select FILE then RUN from the menu. If you are using Windows 		   95 select START then RUN from the taskbar.
        3.      In the dialog box type in X:\ACROWIN\SETUP.EXE, where X: is your CD ROM drive letter.  	  	   (Example if your CD is D: type D:\ACROWIN\SETUP.EXE)  Then hit <ENTER>.
        4.      Follow the on-screen instructions.

To install the DOS version:

        1.     Change to the CD ROM drive.  To do this type your CD ROM drive letter and a colon (:)
                at the prompt and hit <ENTER>.
        2.     Change to the \ACRODOS directory. To do this type CD \ACRODOS and then hit <ENTER>.
        3.      Run the installation program INSTALL.EXE. To do this type INSTALL.EXE and then hit 	 	   <ENTER>.

Adobe Acrobat is not a Sierra product.  If you have difficulties with it please see the README.TXT provided in both the ACROWIN and ACRODOS directories.

SECTION 11:  CONTACTING SIERRA FOR FURTHER ASSISTANCE

Sierra On-Line has a full library of help documents available electronically.  You can download them from the following sources:

·	America On-Line: Use keyword SIERRA and choose "Software Libraries", then 	"Troubleshooting Guides & FAQ's"
·	CompuServe: Use go SIERRA, choose "The Sierra On-Line Forum", then search the "Help 		Documents" library.
·	Go to our home page on the World Wide Web at http://www.sierra.com and follow the on-screen 	information.

Additionally, you can get your document via our automated faxback service.  Call (206) 644-4343, choose to use the automated technical support system and follow the voice instructions provided.  You will
be faxed a catalog of all of the documents that we have to offer and you will then be able to get the documents you need.  If you prefer, you can also fax us at (206) 644-7697 with your document request.

If you prefer to get assistance from a technician, Sierra Technical Support will be happy to assist you.  All of the online services listed above are staffed by Sierra technicians.  Additionally, you can send e-mail to support@sierra.com.  

Additionally, a Sierra Technical Support Support request form has been enclosed in case you wish to contact us via fax or U.S. mail.  Simply fill it out and return it to us.  Our fax number is (206) 644-7697 and our mailing address is:

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

For phone assistance, you can reach Sierra Technical Support at (206) 644-4343 between 8:00 am and 4:45 pm, Monday through Friday.  Please try to be at your system or have a copy of a Microsoft Diagnostics (MSD) report from it when you call.

If you are in Europe, please contact our office in England. The Customer Service number is (0118) 920-9111, between 9:00 am and 5:00 pm, Monday through Friday.   The fax number is (0118) 987-5603. Customer Service can also be reached at the following address:

Sierra On-Line Limited
2 Beacontree Plaza
Gillette Way
Reading, Berkshire
RG2 0BS UNITED KINGDOM
Internet: http://www.sierra-online.co.uk
CompuServe United Kingdom: GO UKSIERRA

Thanks for choosing Sierra!
______________________________________
SOUND CARD CONFIGURATION

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.

Sound Card - Adlib
AUTOEXEC.BAT - NONE 				CONFIG.SYS - NONE 
Notes - This is a MIDI card only and will not play most sound effects.

Sound Card - 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

Notes - *This line is not always present.

Sound Card - Diamond
AUTOEXEC.BAT - SET BLASTER=*			CONFIG.SYS - NONE
                	     SET SOUND16=C:\DIAMOND
                	     C:\DIAMOND\SNDINIT /B**

Notes - *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.

Sound Card - Ensoniq Soundscape
Commom with Gateway 2000 computers.
AUTOEXEC.BAT -  SET BLASTER=A220 Ixx Dx		CONFIG.SYS - NONE
                 	      SET SNDSCAPE=C:\SNDSCAPE
                 	     C:\SNDSCAPE\SSINIT

*Use FM for FM synth, GM for General MIDI and MT32 for Roland MT32 emulation with older drivers.  Uses /I to automatically initialize FM and General MIDI with newer drivers.

Sound Card - ESS Audio Drive
Common on Compaqs
AUTOEXEC.BAT - NONE		CONFIG.SYS - DEVICE=C:\CPQDOS\VOLCTRL.EXE*
        						            DEVICE=C:\PCAUDIO\VOLCTRL.EXE**

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

Sound Card - Forte 16
Common on Packard Bells
AUTOEXEC.BAT - SET BLASTER=*			CONFIG.SYS - NONE
		     SET GALAXY=*
		     SET SOUND=C:\FORTE16
		     C:\FORTE16\UTILITY\EMUTSR

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

Sound Card - Gravis Ultrasound or Gravis ACE
AUTOEXEC.BAT - SET ULTRASND=*			CONFIG.SYS - NONE
     SET ULTRADIR=*
     C:\ULTRASND\ULTRINIT
     SBOS.BAT**
     SET BLASTER=A220 I5 D1

Notes - *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.

Sound Card - Jazz 16
AUTOEXEC.BAT - SET BLASTER=A220 I5 D1 		
CONFIG.SYS - DEVICE=C:\JAZZ\JAZZ.SYS D:* Q:*
           *D:  DMA CHANNEL. **Q: IRQ SETTING.
Notes - Specific values and directories may change

Sound Card - Mad 16
AUTOEXEC.BAT - SET MAD16=C:\MAD16		CONFIG.SYS - NONE
SET BLASTER=A220 I5 D1 
C:\MAD16\M16INIT /B /M*

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


Sound Card - Mozart Sound Card
Common on Canon systems
AUTOEXEC.BAT - SET BLASTER=A220 I5 D1	 
     SET SOUND=C:\MOZART
     C:\MOZART\MTZVOL.EXE
CONFIG.SYS - DEVICE=C:\MOZART\MZTINIT.SYS WSS /530*

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

Sound Card - Multi-Media Pro 16
AUTOEXEC.BAT - SET BLASTER=A220 I5 D1		CONFIG.SYS - NONE
SET GALAXY=*
SET SOUND=C:\MMP16P

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

Sound Card - MWave
Common on IBM Thinkpads and Aptivas
AUTOEXEC.BAT - SET BLASTER=SET MWPATH=C:\MWD\MANAGER;		CONFIG.SYS - NONE
               C:\MWD\MWGAMES*
               SET MWROOT=C:\MWD
               MWGAMES=ON**

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

Sound Card - 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.
Notes - <DIR> may be PROAUDIO on older drivers.

Sound Card - 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**

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

Sound Card - Soundblaster Pro
AUTOEXEC.BAT - SET BLASTER=A220 I5 D1		CONFIG.SYS - NONE
		     SET SOUND=C:\SBPRO*
		     C:\SBPRO\SBP_SET*
Notes - *On newer cards the drivers and such may look like the SB16 except loading out of a different directory.

Sound Card - 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***
Notes - *Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and SET BLASTER lines.
Sound Card - Sound 16A
Common on Packard Bell Computers
2 OF 2**
AUTOEXEC.BAT - SET BLASTER=A220 I5 D1		CONFIG.SYS - NONE
SET GALAXY=*
C:\AUDIO\SNDINIT.EXE /B**
SET SOUND16=C:\AUDIO
Notes - *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 Card - Sound 144
Common on Packard Bell Computers
AUTOEXEC.BAT - SET BLASTER=A220 I5 D1		CONFIG.SYS - NONE
SET GALAXY=*
SET SOUND=SOUND144
C:\SOUND144\UTILITY\SETMODE /SBP**
Notes - *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.

Sound Card - 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
Notes - *Check the AUTOEXEC.BAT on your hard drive for the complete SET MIDI line.
             **Older cards may use SBCONFIG instead of DIAGNOSE.

If your specific sound card is not listed here, check with your system manufacturer or contact their technical support for additional information about sound card configuration.SIERRA ON-LINE TECHNICAL SUPPORT REQUEST FORM (for IBM PC's & Compatibles)

Please provide as much of the information requested below as possible. Attach additional pages if necessary. Please Print clearly.)

Name :

Full Mailing Address :

FAX Number:

Phone Number:

Email Address:

Name/Description of Program:





Description of Problem  (Please be as specific an detailed as possible. Again, feel free to attach additional sheets if necessary.) 






How are you running the program? (Circle one)
* As a DOS Application in DOS
*  As a Windows Application in Windows
* As a DOS application in  or through Windows

Computer Brand:					Computer Model:


Operating System (circle all that apply)
DOS 5				DOS 6
DOS 6.2+			Win 3.1/3.11
Win 95				OS/2*
Windows NT*

*NOTE: Windows NT, OS/2 & Other Operating
 Systems are not officially supported.

CPU Brand (circle):
INTEL				AMD
CYRIX				NEXGEN
Other:

CPU Type (circle):
386SX				386DX
486SX				486DX
Pentium				Pentium Pro
Other:

CPU Speed (circle):
25				33
40				50
66				75
100				120
133				150 
166				Other:

Total RAM installed in the system in MB (circle)
1 MB				2 MB
4 MB				8 MB
16 MB				32 MB
Other:

Total Hard Drive Space in MB:
Free Hard Drive Space after installing the Program (in MB):


CD ROM Brand (circle):
NEC				Mitsumi
Creative Labs			Diamond
Sony				Teac
Other:

CD ROM Model:
CD ROM Speed (circle)
1x				2x
3x				4x
6x				8x

Video Card (circle):
Diamond			ATI
Number9			STB
Cirrus				Matrox
Hercules				Trident
Other:

Video Card Model:

Video Memory (circle):
512k or less			1 MB
2MB 				4MB or more

Screen resolution you are using in Windows currently (circle)
640x480				800x600
1024x768			1280x1024
1600x1200 +

Color Depth you are using in Windows currently (circle)
16				256
32,768+ (High Color)*		16.7 Million (True Color)*

*NOTE: If you are using anything other than 256 colors, we generally recommend using 256 for most programs.

Sound Card Brand/Model/Description (please write in):

DMA (circle)
0				1
3				5
Other:

IRQ (circle)
3				5
7				10
Other:

Port Address(circle)
220
240
Other:

Disk Compression Software (circle):
Doublespace 			DriveSpace
Stacker				SuperStor
None				Other:

Please check any steps below which you have tried:

1. SCANDISK, Delete & Re-install program
2. A DOS & Windows installation (for programs supporting both)
3. Boot Disk 
4. Disk or CD replacement
5. Patch Disk (If applicable) Name of patch:
6. Updated Drivers
7. Temporarily disabling Sound card/Sound in Program

Other: 
