ACES OF THE PACIFIC AND ACES OVER EUROPE TROUBLESHOOTING GUIDE revised 1/10/96 The following information should help you solve the problem you are experiencing with your Aces flight simulator. 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 - INSTALLATION PROBLEMS SECTION 4 - ACES OF THE PACIFIC COMMON PROBLEMS SECTION 5 - ACES OVER EUROPE COMMON PROBLEMS SECTION 6 - RUNNING THE ACES FLIGHT SIMULATORS IN WINDOWS 95 SECTION 7 - TROUBLESHOOTING STEPS SECTION 8 - SOUND ISSUES AND SOUND CARD SETTINGS SECTION 9 - JOYSTICK TROUBLESHOOTING SECTION 10 - MANUAL INSTALLATION INSTRUCTIONS SECTION 11 - DOS BOOT DISK INSTRUCTIONS SECTION 12 - WINDOWS 95 BOOT DISK INSTRUCTIONS SECTION 13 - OBTAINING A SIERRA PATCH DISK SECTION 14 - IF YOU STILL HAVE PROBLEMS... SECTION 15 - SOUND CARD DRIVER INFORMATION SECTION 1 - HARDWARE REQUIREMENTS REQUIRED FOR ACES OF THE PACIFIC 386 2 MB RAM 8 MB hard drive space (compressed 16 MB) MS DOS 5.0 or higher VGA (256 color) RECOMMENDED FOR BEST PERFORMANCE 486 DX 8 MB RAM Joystick with speed adjustable game card REQUIRED FOR ACES OVER EUROPE 386 DX 4 MB RAM 8 MB hard drive space (compressed 16 MB) MS DOS 5.0 or higher VGA (256 color) RECOMMENDED FOR BEST PERFORMANCE 486 DX 8 MB RAM Joystick with speed adjustable game card SECTION 2 - INSTALLATION PROCEDURES Note: The following examples assume that you are using hard drive C: and floppy disk A: or CD drive D: . If not, please substitute all references with the appropriate drive labels. ACES OF THE PACIFIC and ACES OVER EUROPE FLOPPY DISK VERSION DOS Insert Aces of the Pacific or Aces Over Europe Disk #1 in Drive A: and type A: , then INSTALL . Select which drive you wish to install the game to and follow the on- screen instructions. WINDOWS 95 Click on Start, then Run. In the Open field, type the letter of the floppy drive followed by \INSTALL. Example: A:\INSTALL. Follow the on- screen prompts to complete the installation. ACES OF THE PACIFIC CD VERSION DOS Insert the Aces of the Pacific CD into the CD drive and type D: . Then type CD\AOTP , INSTALL . Select which drive you wish to install the game to and follow the on- screen instructions. Click on Start, then Run. In the Open field, type the letter of the floppy drive followed by \AOTP\INSTALL. Example: D:\AOTP\INSTALL. Follow the on-screen prompts to complete the installation. ACES OVER EUROPE CD VERSION DOS Insert the Aces over Europe CD into the CD drive and type D: . Then type CD\AOE , INSTALL . Select which drive you wish to install the game to and follow the on- screen instructions. WINDOWS 95 Click on Start, then Run. In the Open field, type the letter of the floppy drive followed by \AOE\INSTALL. Example: D:\AOE\INSTALL. Follow the on-screen prompts to complete the installation. SECTION 3 - COMMON INSTALLATION PROBLEMS PROBLEM: After typing INSTALL, a row of dots goes across the screen and stops. The computer is locked up with this row of dots appearing on the screen. SOLUTION: The dots indicate the hardware detection portion of the installation program. You can bypass the hardware detection (and therefore the lockup) by typing INSTALL /M. If this entry doesn’t work, try INSTALL /F. One of these entries should get you past the lockup. If this does not work, create a boot disk using the boot disk instructions included with this document. After booting up with the boot disk, install the game. PROBLEM: When installing the game, you receive an "Error reading drive A" or "Error reading drive D". Message will vary depending on what drive you are installing from. SOLUTION: If you are installing the floppy disk version of an Aces game, this error message probably indicates a bad disk. The only way to correct this is to get a new set of disks. If you are installing the CD version of an Aces game, there are several factors that can cause a "read" error. The most common 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 the disk is scratched, it will need to be replaced. If cleaning the CD doesn't help, 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. 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 CD drivers can cause this type of problem. If you need to replace your disks or CD, replacement is FREE for the first 90 days of product ownership. After 90 days there is a $10.00 handling fee per program. For the fastest service, simply mail Disk #1 or the CD to us along with a copy of your sales receipt dated within 90 days or the $10.00 handling fee, and a note detailing your computer hardware and the problem that is occurring. Please include your full name, mailing address, and daytime telephone number so we can contact you if necessary. We will then send a complete replacement set of disks to you. The address is: Sierra On-Line Customer Service, PO Box 485, Coarsegold CA 93614-0485. PROBLEM: Disk Error - Read Error (notice no drive letter). This occurs with the floppy disk versions only. SOLUTION: This error occurs when a memory-resident program prevents the installation program from reading the game disk correctly. The easiest way to avoid this is to reboot the computer while holding down the SHIFT key. This will keep any memory-resident programs from loading and should allow the game to install correctly. If this does not help, create a boot disk using the instructions in Section 10. Reboot the computer using the boot disk, then install the game. SECTION 4 - ACES OF THE PACIFIC COMMON PROBLEMS PROBLEM: When starting the game, you receive the message "You computer does not have enough available memory". SOLUTION: The game needs more memory than what is currently available on your computer. Make sure you have the minimum requirements, (see Section 1 - Hardware Requirements) and make a boot disk using the instructions included in this document. PLEASE NOTE: On some computers, the boot disk created by the installation program will not free up enough memory. If this occurs, create a boot disk using the instructions included in Sections 11 or 12. PROBLEM: You bet the message, "A shell system error has occurred..." sometime during game play. SOLUTION: This error typically indicates that some of the data for the game is corrupted or missing. You should delete the and reinstall the game. See Section 7 - Troubleshooting Steps for information. PROBLEM: Error message "\ALRTLIB2:44 :PREFSIM.BOX" SOLUTION: This error indicates that some of the data for the game is corrupted or missing. You should delete and reinstall the game. See Section 6 - Troubleshooting Steps for information. PROBLEM: The automatic boot disk maker seems to work, but at the end of the process, you get a message stating "Boot disk not successful". (Floppy disk version only.) SOLUTION: This happens because the floppy disk version of Aces of the Pacific came out before DOS 6.0. When Aces of the Pacific attempts to create a boot disk, it does not recognize DOS 6.0 as a valid DOS version and the boot disk process is not completed. If you are having this problem, create a boot disk manually using the boot disk instructions included with this document. PROBLEM: Error message "Bad Human Error XXXX" SOLUTION: This error can be caused by two situations. Check the version of the game; if you have version 1.0 or 1.1 then you need the latest update patch, (see Section 9 - Obtaining a Sierra Patch). The message can also indicate that some of the data for the game is corrupted or missing. You should delete and reinstall the game. See Section 6 - Troubleshooting Steps for information and reinstall the game. PROBLEM: You cannot access your CD ROM drive after booting from a boot disk created by the CD ROM version of Aces of the Pacific. SOLUTION: Occasionally, the automatic boot disk maker does not load the CD drivers properly. Make a boot disk for the game using the boot disk instructions included with this document. PROBLEM: "Can't find text entry for Video Prompt" message. SOLUTION: This message appears if you try to run the INSTALL on the floppy disk from a different drive and directory. Change your DOS prompt to the A: or B: drive by typing A: or B: ; now type INSTALL . PROBLEM: No sound or music with a Gravis Ultrasound. SOLUTION: The GUS comes with a file called SBOS.BAT that will allow the Gravis card to run as a Sound Blaster compatible. The SBOS.BAT file executes two .EXE files called SBOSDRV and LOADSBOS. The second file has three variables (switches) that can be assigned. They are -O1 to control looping problems, -O2 & -O3 to enhance the {alias 4;13} Sound Blaster emulation. A problem may occur when you try to start Aces of the Pacific after running the SBOS.BAT file. SBOSDRV and LOADBOS take up conventional memory. After loading these you may not have enough conventional memory free to run the game. To overcome this, add the following lines to the AUTOEXEC.BAT file on a boot disk for the game, (this is in addition to the standard commands for the UltraSound Card). LH SBOSDRV LH LOADSBOS-O2 * Note: the switches are the letter O not the number 0. PROBLEM: INIT: XXX and EPT: 00XX errors SOLUTION: This error indicates that some of the data for the game is corrupted or missing. You should delete and reinstall the game. See Section 7 - Troubleshooting Steps for information and reinstall the game clean. PROBLEM: Game lockup with Packard Bell computers SOLUTION: Some Packard Bell computers have ROM addresses in locations normally available for use as EMS memory. Try adding "I=D000-EFFF M9" to the end of the EMM386 line in the CONFIG.SYS file on a boot disk. The line should read: DEVICE=C:\DOS\EMM386.EXE RAM I=D000-EFFF M9 PROBLEM: Lockup on PS/1 computers SOLUTION: If an error occurs when starting from a boot disk that reads: "Warning: option ROM/RAM detected within page frame", you must change the EMM386 line in the CONFIG.SYS on the boot disk to accommodate the PS/1 computer. Here's a standard PS/1 line: DEVICE=C:\DOS\EMM386.EXE RAM I=C000-DFFF M1 PROBLEM: Lockup at the "Please wait" screen SOLUTION: This may be due to a disk caching program such as SMARTDRV, PC-CACHE, etc. Using a boot disk without the disk caching program should correct the problem. PROBLEM: "OVL: XXXX" error message SOLUTION: This error indicates that some of the data for the game is corrupted or missing. You should delete and reinstall the game. See Section 6 - Troubleshooting Steps for information. PROBLEM: Cannot restore VCR files. SOLUTION: Tapes that were created in version 1.0 or 1.01 are not compatible with version 1.2 (which is the same as version 1.0 or 1.01 with ACEPATCH [patch B] installed). An asterisk will appear next to an incompatible tape name when attempting to load it. PROBLEM: Cannot save VCR files with a Thrustmaster Flight Control System. SOLUTION: This will only occur with the disk version 1.0 or 1.01 of Aces of the Pacific, you need the update to version 1.2 of Aces of the Pacific. See Section 9 - Obtaining a Sierra Patch Disk. PROBLEM: What do the Return Code Error Messages mean? RETURN CODE 2 - Insufficient Disk Space. RETURN CODE 5 - File does not exist (probably misspelled). Delete and reinstall the game. RETURN CODE 6 - Directory does not exist (probably misspelled). Delete and reinstall the game. PROBLEM: Sluggish performance. SOLUTION 1: If you have recently upgraded to DOS 6.0, sluggish performance may be related to the version of SMARTDRV being used. The WIN 3.1 version of SMARTDRV.EXE is version 4.0. If you are loading this version in addition to using the Double Space utility, SMARTDRV.EXE will not load and a message will be displayed that states: "You cannot use SMART DRIVE VERSION 4.0 with Double Space". This will zoom by quickly on the screen as the computer boots up, so you may not notice the message. If this is occuring, you will have to load version 4.1 of SMARTDRV.EXE from the \DOS directory. SOLUTION 2: If you're using version 1.0 or 1.01 of Aces of the Pacific then the update to version 1.2 will increase the speed of the program. See Section 9 - Obtaining a Sierra Patch Disk. SOLUTION 3: Some music cards can contribute to periodic slowness. Try using the PC Internal Speaker option and see if it improves. PROBLEM: Slow video frame rate. SOLUTION: A 256K VGA card can cause a slow frame rate. The only solution is to upgrade to a Super VGA card (with at least 512K, preferably 1 MB or more). PROBLEM: "The mission recorder has run out of disk space..." message and there is no TAPES subdirectory. SOLUTION: Create a TAPES directory under the ACES directory. See the Manual Installation Procedures included with this document for information on creating directories. PROBLEM: Torpedoes don't sink ships. SOLUTION: This is historically accurate. Early American torpedoes rarely worked; about 33% actually detonated. Page 177 of the Aces manual outlines specific flight tactics and requirements in order to accurately launch torpedos. Page 183 outlines the specific statistics showing how inaccurate the torpedoes were. PROBLEM: \UTIL:STRP.C:107 (or similar number) SOLUTION: This error indicates that some of the data for the game is corrupted or missing. You should delete and reinstall the game. See Section 7 - Troubleshooting Steps for information. PROBLEM: White bars appearing on screen. SOLUTION: If you are experiencing video problems where white bars appear on the screen, try the following suggestions: 1) Disable Shadow Ram - many computer systems have a BIOS configuration that allows you to set up Shadow RAM to help speed up computer operations. In your BIOS setup, try disabling this feature (if this option is active), and then try to run the game under the boot disk that our install program created. NOTE - If you are unsure about this setup, please consult your hardware dealer for further information. Because there are many BIOS setup procedures out for the various computer systems sold, your hardware dealer will be familiar with the specifics to your particular BIOS setup - Sierra Technical Support will not be able to help you with this operation. 2) Modify the EMM386 line - On the boot disk that the Aces of the Pacific program created, modify the EMM386.EXE line to read as follows: DEVICE=C:\DOS\EMM386.EXE RAM 1024 X=C800-CFFF M5 This statement prevents Aces from loading into an area of memory that your video card's ROM loaded into RAM might try to occupy. This could correct the problem if there was a memory conflict. 3) Mouse driver conflict - If you are using a mouse device that is not a true Microsoft or Logitech mouse, try using the latest Microsoft mouse driver. Unfortunately, due to Copyright agreements, Sierra can not send out other company's mouse drivers. When you have the true Microsoft drivers, copy the files into the directory that currently contains your current mouse drivers. 4) Do not run the game under Windows 3.1 - If you are attempting to run the game through Windows 3.1 (or even at the DOS prompt while under Windows), then the lines could appear as a result. Before attempting to start Aces, please make sure you have exited completely out of Windows and are running the game from a DOS prompt. 5) Check your hard drive - Lost allocation units on your hard drive can cause strange video problems. To see if indeed the lost allocation units are causing the problem, run the SCANDISK to detect and correct any possible hard drive errors. Once you have corrected these problems, delete any files associated with Aces from the hard drive and re-install the game. SECTION 5 - ACES OVER EUROPE COMMON PROBLEMS PROBLEM: "Can't find input file" (CD version) "Can't find input file: x:phone.txt" "Can't find input file: x:rbjoy.exe" "Can't find input file: x:patchpif.exe" "Can't find input file: x:twinion.doc" SOLUTION: These errors occur when trying to install the copy of INN that is included with AOE CD. This version will not work on your machine. Contact INN at 1-800-IMAGIN1 for a new version of INN software. PROBLEM: "Can't find text entry for Video Prompt" message. SOLUTION: This message appears if you try to run the INSTALL on the floppy disk from a different drive and directory. Change your DOS prompt to the A: or B: drive by typing A: or B: ; now type INSTALL . PROBLEM: "Cockpit 242 (EMS)/Cockpit 237 (EMS)" error messages. SOLUTION: Create a boot disk using the instructions included with this document and play the game from the boot disk. The game is experiencing a conflict with a TSR loading on your computer. PROBLEM: Error "EPT0015: Old File Does Not Exist". SOLUTION: This error occurs when typing "A:\INSTALL" instead of logging to the A drive before running install. See Section 2 - Installation Procedures for installation instructions. PROBLEM: Joystick loses calibration, using an adjustable game card. SOLUTION: Do not provide any controller input during transition screens. Be sure that you are not putting any pressure on the stick during screen changes. PROBLEM: Lockup at "Please Wait" screen. SOLUTION: This will occur on Packard Bell, Acer, and many other computers including "clones". The AOEPAT patch will correct this problem. See Section 9 - Obtaining a Sierra Patch. PROBLEM: Lockup entering simulation mode. SOLUTION: This will occur on Packard Bell, Acer, and many other computers including "clones". The AOEPAT patch will correct this problem. See Section 9 - Obtaining a Sierra Patch. PROBLEM: Lockup on PS/1 computers. SOLUTION: If you get DYNAMIX screen and then the screen goes blank and the computer locks up with the following error message: "Warning: option ROM/RAM detected within page frame." Make sure you are using a boot disk and change the EMM386 line in the CONFIG.SYS file on the boot disk to read:. DEVICE=C:\DOS\EMM386.EXE RAM I=C000-DFFF M1 PROBLEM: Norton Anti-Virus reports the MTE virus on the ADLIB.DRV & IBMPS1.DRV Files. SOLUTION: This is not a virus. Viruses cannot infect .DRV files. This is caused by an older version of the Norton Anti-Virus program, which is reporting a virus that is not present. Symantec refers to this as a "false- positive". Contact Symantec at (310) 449-4900 for upgrade information. PROBLEM: Not enough memory even though 610K available. SOLUTION: Make sure you have sufficient memory before starting the application. The error message on screen will indicate 610,000 bytes of conventional is required. This is incorrect — the manual and Readme file requirements of 614,400 bytes conventional are correct. If you have insufficient conventional memory available, you will need to run the game with a boot disk. Boot disk instructions are included with this document, or you can create a boot disk automatically through the game's installation program. PROBLEM: Screen goes blank or becomes garbled when plane is hit by enemy fire. SOLUTION: Some video cards cannot display the "screen shake" that occurs when planes are hit by enemy fire. To fix the problem, change to the AOE directory and type: SHAKEOFF. This will turn off the screen shaking feature. SHAKEMED will allow a medium amount of screen shake and may be an option for some video cards. SHAKEON will turn the screen shaking back on. PROBLEM: Tanks survive when bridge is blown out from underneath them. SOLUTION: When bombing tanks, if you destroy a bridge the tanks will continue to cross the water as if a bridge were still there. If you crash into a river it will leave a "hulk" shape floating on the surface. Technically, rivers are just "blue ground," not water. SECTION 6 - RUNNING ACES GAMES IN WINDOWS 95 Windows 95 is designed to run MS-DOS programs as well as windows programs. The following basic troubleshooting steps should help you resolve problems such as memory errors, crashes, lockups and illegal instruction errors (GPFs). STEP 1 - Run the program from a minimal boot disk. Memory conflicts are a common cause of problems with DOS games in the Windows 95 environments. Creating a boot disk 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 TSRs and utilities that can sometimes cause conflicts. Detailed Windows 95 boot disk instructions are included in Section 12 of this document. STEP 2 - Check for corrupted files and hard drive errors. Windows 95 contains a program called Scandisk that will check your hard drive for errors. To run Scandisk, click on Start, Programs, Accessories, System Tools and choose Scandisk from the list. If Scandisk finds any errors on the hard drive, fix them, then delete your game and reinstall it. STEP 3 - Check your sound card drivers. Windows 95 ships with many sound card divers, however, there are many sound cards are not directly supported. When a sound card is not directly supported by windows 95, the game may lock up or crash. Check with your sound card manufacturer to see if they have Windows 95 drivers. If no Windows 95 drivers are available, running the game in MS-DOS mode may correct the problem. 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 during the game installation. You should install the game in a "clean" boot environment. See Section 12 for complete Windows 95 boot disk instructions. STEP 5 - Create a clean Windows environment. Make sure that all screen savers, virus scans and sound-related Windows programs (IconHear It, Wired for Sound, etc.) are disabled before starting the game. You should also check to make sure that you have virtual memory enabled. You can check this by clicking on Start, Settings, Control Panel, System, Performance, Virtual Memory. Make sure that Let Windows manage my virtual memory settings is checked. STEP 6 - Check your CD-ROM drivers. Windows 95 ships with the most common CD-ROM drivers, however, there are some CD-ROM drives out there that Windows 95 does not support directly. If you are having trouble reading CDs, check with your CD-ROM drive manufacturer to find out what lines need to appear in your CONFIG.SYS and AUTOEXEC.BAT. STEP 7 - Check your mouse driver. In addition to the Windows mouse driver, you may need to load a DOUS mouse driver to allow the mouse to function in your DOS game. The boot disk instructions in Sections 11 and 12 contain detailed information on locating this mouse driver, or you can check in your mouse documentation. Sierra games work best with a Microsoft (v8.2 or higher) or Logitech (v6.0 or higher) mouse driver. STEP 8 - Run the game in MS-DOS mode. To restart the computer in MS-DOS mode, choose Start, Shut Down, Restart in MS-DOS mode. Many games will run better in this environment. However, you may need a boot disk to free up enough conventional memory. See Section 12 for Windows 95 boot disk instructions. STEP 9 - Boot to your previous version of MS-DOS. If you upgraded to Window 95 from a previous version of MS-DOS, you have the option to run the game in that previous operating system. If the game ran without problems before you upgraded to Windows 95, this procedure should help you. See the Windows 95 boot disk instructions in Section 12 for detailed instructions. SECTION 7 - TROUBLESHOOTING STEPS If you do not see your specific problem listed, these Standard Troubleshooting Procedures correct most problems running Sierra On- Line's DOS games. 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 free of extra TSR and utilities that can cause conflicts. The INSTALL program with Aces of the Pacific and Aces Over Europe includes the option to "Make Bootable Floppy Disk". You can use this option to make a boot disk for your game. Note: The boot disk maker with Aces of the Pacific will make a boot disk for MS-DOS 5.0 only; the boot disk maker with Aces Over Europe will make a boot disk for MS-DOS 5.0 through MS-DOS 6.22. You can also make a boot disk using the instructions in Section 11. STEP 2 - Check for sound card conflicts. Many lockups in games can be traced to sound card lockups. To determine if you have a sound card lockup, run the INSTALL program and check the current setting for "MUSIC". Make sure the selection is supported by the hardware in your computer. Test for conflicts by changing the "MUSIC" selection to "IBM PC or Compatible Speaker" and then playing the game. If the game works with the internal speaker and locks up with the sound card; you will know there is some sort of sound card conflict. See Section 7 - Sound Issues and Sound Card Settings and your sound card's documentation for help resolving sound card conflicts. STEP 3 - 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 the files are corrupted. Most corruptions will occur during the installation of the game. This is 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. Booting your computer from a boot disk, (see attached instructions), will create a clean boot environment for installation purposes. With DOS 6.0 or above you can quickly clean boot your computer by holding down the [SHIFT] key when the words "Starting MS-DOS" appear on the monitor during boot up. Once you have your computer in a "clean" boot environment, you can reinstall the game using the instructions in Section 2 - Installation Instructions. STEP 4 - Manually install the game. If you are still having technical difficulties, manually install the game in a clean environment. See Section 10 - Manual Installation Procedures. SECTION 8 - SOUND ISSUES AND SOUND CARD SETTINGS The Aces games are designed to work with the following sound card settings: SoundBlaster, DMA 1, I/O 220 and IRQ 3, 5 or 7; ProAudio, DMA 3, IRQ 5 and I/O 220. If your sound card settings are outside these parameters, you may have problems with the sound. There is no way to change the game to use different sound card settings; the sound card settings will need to be changed. Please consult your sound card documentation for more information. PROBLEM: No music. SOLUTION: If the PC Internal Speaker option is chosen during installation, there will be no music. The sound effects will still be heard and all menu choices for music will still be active, however even with the music option turned on, there will be no music from the PC Internal Speaker. PROBLEM: Strange sounds in the game (i.e. gunfire sounds like a piano or thrust sounds like a phone ringing). SOLUTION: You have either "General MIDI" or "Roland MT-32" selected as your sound card. These drivers are for music cards, and can only play sound effects by reassigning them to a MIDI channel that normally would play a musical instrument. If you are experiencing these illogical sound effects, your sound card does not support this MIDI "patch map" reassignment and you must rely on your sound card's Sound Blaster emulation. If your sound card does not support Sound Blaster, you will have to use the internal speaker for sound reproduction. To change your sound settings, run INSTALL from the game directory. PROBLEM: The game locks up or fails to play sounds while using a Pro Audio Spectrum 16 or Jazz 16 sound card. SOLUTION: First, make certain that the proper sound card configuration line appears in the CONFIG.SYS file. For the Pro Audio Spectrum 16, the line loads a device driver called MVSOUND.SYS. The Jazz 16 uses the JAZZ.SYS driver. Specific path and settings may vary, but the line should look similar to this: DEVICEHIGH=C:\FUSIONLX\MVSOUND.SYS /D:5 /Q:7 /B:1,220,1,3 /J:0 NOTE: These sound cards need to have different DMA and IRQ settings for the Pro Audio Spectrum mode and the Sound Blaster mode. Check your sound card documentation for more information. PROBLEM: The game either locks up or fails to play sounds while using a MAD16 sound card in Sound Blaster emulation mode, while using a boot disk.. SOLUTION: Manually add the following lines to the AUTOEXEC.BAT on the boot disk: SET MAD16=C:\MAD16 C:\MAD16\M16INIT /B NOTE: These lines should appear immediately below the "SET BLASTER=" line. If this line does not appear on your boot disk, consult your sound card documentation. PROBLEM: Lockups or no sound while using other sound cards that use some form of INIT.EXE file , (eg. SNDINIT.EXE, ISPINIT.EXE, etc...) to set your sound emulation mode. You should check your sound card documentation to see if your sound card uses one of these initialization files. These sound initialization files are in the directory where your sound card files are located. SOLUTION: Look in your AUTOEXEC.BAT on your C: drive for the lines that belong to your sound card. Example: SET (SOUND, M16, IPS16, etc...)=C:\(path to your sound card files directory) SET BLASTER=A220 I5 D1 T4 C:\(path to your sound card files directory)\(some type of XXinit.exe file name) Add these lines to the AUTOEXEC.BAT file on the boot disk. PROBLEM: You do not get any sound in the game with a Creative Labs Sound Blaster 16, while using a boot disk. SOLUTION: The boot disk maker may miss some lines necessary to configure the SB16 properly. Make sure that the following lines appear in the files on the boot disk. NOTE: The following lines are for default configuration of the SB16 16 and may vary with your particular system. Please consult your sound card documentation for further information. AUTOEXEC.BAT SET SOUND=C:\SB16 SET BLASTER=A220 I5 D1 H1 P300 T6 SET MIDI=SYNTH:1 MAP:E C:\SB16\SB16SET /P /Q C:\SB16\DIAGNOSE /S CONFIG.SYS DEVICEHIGH=C:\SB16\DRV\CTMMSYS.SYS DEVICEHIGH=C:\SB16\DRV\CTSB16.SYS /BLASTER:A220 I5 D1 /UNIT:0 PROBLEM: No sound or music with a Gravis Ultrasound. SOLUTION: The GUS comes with a file called SBOS.BAT that will allow the Gravis card to run as a Sound Blaster compatible. The SPOS.BAT file executes two .EXE files called SBOSDRV and LOADSBOS. The second file has three variables (switches) that can be assigned. They are -O1 to control looping problems, and -O2 and -O3 to enhance the Sound Blaster emulation. A problem may occur when you try to start Aces of the Pacific after running the SBOS.BAT file. SBOSDRV and LOADSBOS take up conventional memory. After loading these you may not have enough conventional memory free to run the game To overcome this, create a boot disk, then add the following lines to the AUTOEXEC.BAT file. Note that these lines are in addition to the standard commands for the GUS card: LH SBOSDRV LH LOADSBOS -O2 Note: The switch is the letter O, not the number 0. PROBLEM: You do not get sound in the game while using a sound card other than the ones listed above, running a boot disk. SOLUTION: As with the sound cards discussed above, lines may have been omitted from the AUTOEXEC.BAT or CONFIG.SYS files. Section 11 of this document contains a list of common sound cards and their drivers and/or initialization lines for the AUTOEXEC.BAT and CONFIG.SYS. If your sound card is not on this list, please consult the sound card documentation or contact the manufacturer. SECTION 9 - JOYSTICK TROUBLE SHOOTING If you are having trouble using your joystick, here are some possible solutions: Try running the product from a boot disk made by the installation program's Make Bootable Floppy Disk option first. There are many TSR's (Terminate and Stay Resident) programs that can cause problems with joysticks. The problem may also stem from the fact that your joystick port cannot keep up with polling requests from the game. If you have a 386, 486 or a Pentium computer and you are using a generic game port, or the port on your sound card, the 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 Dynamix programs use. Polling the joystick port at a high rate insures the smoothest possible joystick control. Dynamix 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. Another reason for erratic joystick behavior or no joystick response is having two separate joystick ports active at the same time. If you have a single card with dual joystick ports, you should not encounter difficulties since each port has separate settings. However, if one port is on a sound card and one is on a multifunction (joystick) card, there could be a conflict. There may even be a joystick port enabled on the system even though there is not one visible at the back of the computer. This happens when a card (usually a multifunction I/O card) with a joystick port that can be attached by a ribbon cable is installed, but the ribbon cable is not attached to the card. If the joystick port is not disabled by the jumper on the card then the game will often still detect a joystick port and try to use it. The way to conclusively test if there is another joystick port enabled is to either remove any card with a known joystick port or disable the joystick port on any known cards. Then run the MSD (Microsoft Diagnostics) utility and see if it reports a gameport being present. If it does then the port must be disabled (check the appropriate hardware documentation). Additionally, when recalibrating the joystick, don't go all the way to the left and right corners - back off from the corner about a quarter of an inch, then press the key. Don't press the joystick button as this sometimes throws the calibration off. JOYSTICKS WITH MULTI-POSITION SWITCHES (HATS) All joysticks that have "hats" require the use of a dedicated joystick card. Aces of the Pacific does not support joystick "hats." ACES OVER EUROPE AND ACES OF THE PACIFIC CALIBRATION PROBLEMS Ensure that the joystick is calibrated in flight. Pressing will give you the joystick calibration option while you are flying. If calibration is lost during the change between screens, do not put pressure on the stick between screens. SECTION 10 - MANUAL INSTALLATION INSTRUCTIONS Occasionally, some memory-resident programs or hardware configurations may conflict with the installation procedure. If you are experiencing installation problems, such as lockups or read errors, with an Aces flight simulator, the following instructions will allow you to manually copy the game to your hard drive. The differences between the installations for Aces Over Europe and Aces of the Pacific are noted in each pertinent step. MANUAL INSTALLATION INSTRUCTIONS FOR DISKETTE GAMES NOTE: The following lines assume you are installing the game from game disks in your A: drive to your C: hard drive. If you are installing from or to a different drive, then substitute the appropriate drive letters. 1) Check your hard disk drive to confirm that you have enough disk space available, (see Section 1 - HARDWARE REQUIREMENTS to determine how much space is needed). Run the CHKDSK utility to verify "bytes available on disk". If CHKDSK reports any errors found on the hard drive, you will need to correct these errors before installing the program. Please consult your MS-DOS manual for information on how to correct these errors. 2) Create the directory structure for the game. To do this, type: C: CD \ MD DYNAMIX CD DYNAMIX MD AOE (for Aces Over Europe) or MD ACES (for Aces of the Pacific) CD AOE (for Aces Over Europe) or MD ACES (for Aces of the Pacific) MD TAPES 3) Copy all the files from each disk into the game directory. To do this, type: COPY A:*.* C:\DYNAMIX\AOE (for Aces Over Europe) or COPY A:*.* C:\DYNAMIX\ACES (for Aces of the Pacifc) 4) Copy all .VCR files on the last disk into the \TAPES subdirectory. To do this, type: COPY A:*.VCR C:\DYNAMIX\AOE\TAPES (for Aces Over Europe) or COPY A:*.VCR C:\DYNAMIX\ACES\TAPES (for Aces of the Pacific) 5) Type CD\DYNAMIX\AOE or CD\DYNAMIX\ACES 6) Change into the game directory and expand the compressed RESOURCE files. To do this, type: UNCHUNK RESOURCE.000 . NOTE: Remember to include the " ." after the 000 in step 4. 7) There will be a long pause while this process is working. If it is successful, UNCHUNK will notify you. Use UNCHUNK on all other RESOURCE files by substituting the appropriate file extension in the UNCHUNK statement in step 4. NOTE: Be sure to unchunk these resource files in order. If you make a mistake, or if the unchunked files are in the wrong order, you will need to erase all of the files from the \DYNAMIX\AOE or \DYNAMIX\ACES subdirectory and restart the process at Step 2. 8) Type: INSTALL . Verify that the hardware settings listed are appropriate for your system. 9) Exit out of the Install program and start the game. If the game works, type DEL RESOURCE.* in the game directory to delete the compressed files from the hard drive. MANUAL INSTALLATION INSTRUCTIONS FOR CD-ROM GAMES NOTE: The following statements assume you are installing the game from CD ROM drive D: to hard drive C:. If you are installing to or from different drives, then substitute the appropriate drive letters in the above copy statements. 1) Check your hard disk drive to confirm that you have enough disk space available, (see Section 1 - HARDWARE REQUIREMENTS to determine how much space is needed). Run the CHKDSK utility to verify "bytes available on disk". If CHKDSK reports any errors found on the hard drive, you will need to correct these errors before installing the program. Please consult your MS-DOS manual for information on how to correct these errors. 2) Copy the game files from the CD-ROM to the appropriate subdirectories. Type: C: CD\ MD DYNAMIX CD DYNAMIX XCOPY D:\AOE\*.* C:\DYNAMIX\AOE /S (Aces Over Europe) or XCOPY D:\AOTP\*.* C:\DYNAMIX\ACES /S (Aces of the Pacific) 3)Type CD\DYNAMIX\AOE or CD\DYNAMIX\AOTP. 4) Type: INSTALL . Verify that the hardware settings listed are appropriate for your system. 5) Exit out of the Install program and start the game. SECTION 11 - DOS BOOT DISK INSTRUCTIONS IMPORTANT NOTE: Please read the entire instructions prior to starting at Step 1. You can skip Steps 3 and 4 if you are playing a floppy disk version, or if you did a large install of a CD version. 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 If you get a "Bad command or file name" error message, type: PATH=C:\DOS 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 want to use a mouse with your Aces game, 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 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: 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\ EDIT CONFIG.SYS 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 , , then 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\ EDIT AUTOEXEC.BAT 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. To exit the AUTOEXEC.BAT, press the , , then 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 this document, 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: CD\ EDIT CONFIG.SYS This will display the blank (usually blue) screen of the DOS Editor. Enter the following lines: DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE RAM 1024 DOS=HIGH,UMB FILES=30 BUFFERS=20 If you're using MOUSE.SYS to load your mouse, add the following line: DEVICEHIGH=A:\MOUSE.SYS If necessary, add the CD ROM device driver as you wrote it down in the "Locating the CD ROM Device Driver" section. DEVICEHIGH=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: DEVICEHIGH=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5 DEVICEHIGH=C:\SB16\DRV\CTMMSYS.SYS Save the file by pressing , , then . Exit the file by pressing , , then . 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: CD\ EDIT AUTOEXEC.BAT 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: LH A:\MOUSE.COM If necessary, add the MSCDEX line as you write it down in the "Locating the MSCDEX CD ROM Extension" section. For example: LH 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 , , then . Exit the file by pressing , , then . STEP 8 REBOOT THE COMPUTER AND START THE GAME Reboot your system by pressing the button on your computer or by using the key sequence on your keyboard. Follow the instructions in the game manual to start the game. If you continue to have memory problems even when using the boot disk, try the following: 1. Don't load the mouse driver. Mouse drivers can take a substantial amount of conventional memory. Take the mouse driver line out of the AUTOEXEC.BAT or CONFIG.SYS, depending on what file it loads in. You don't need the mouse driver if you are flying your plane with a joystick or the keyboard. 2. If you did a small install of the Aces Collection, do a full install and play the games from the hard drive. This allows you to take the CD- ROM drivers out of the CONFIG.SYS and AUTOEXEC.BAT, which frees up more conventional memory. 3. If you are attempting to run the game from within Windows 3.1, run the game in DOS instead. This will clear up many memory errors, General Protection Faults and Application Errors. SECTION 12 - WINDOWS 95 BOOT DISK INSTRUCTIONS IMPORTANT NOTE: Please read all instructions before beginning this procedure. If you are playing a floppy disk version, or did a large install of a CD version, you can skip Steps 2 and 3. 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 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. 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 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 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 3 LOCATING THE MSCDEX CD ROM EXTENSION (May be optional - See Note below) NOTE: If your CD ROM drive has native 32-bit Windows 95 drivers, you will NOT need to load MSCDEX.EXE on your boot disk. If you are unable to access your CD ROM drive if MSCDEX is not loaded, contact your system manufacturer or CD ROM drive manufacturer for Windows 95 CD ROM drivers. In the meantime, you can use these instructions to load MSCDEX in the AUTOEXEC.BAT file on your boot disk. 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. If you cannot find the MSCDEX line in the AUTOEXEC.BAT file, then most likely you do not need to load it to access your CD ROM drive in Windows 95. Skip this step and continue to Step 4. STEP 4 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 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: DEVICEHIGH=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220 Save the file by clicking on File, Save. Close Notepad by clicking on File, Exit. STEP 5 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 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 6 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 or Restart the computer in MS-DOS mode. The computer will now reboot with the boot disk configuration. When your computer restarts, start the game. STEP 7 (optional) BOOTING TO YOUR PREVIOUS VERSION OF MS-DOS In some instances, the above steps may not give you enough memory to run your Aces game in Windows 95. 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 choice 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 computer that have been upgraded to Window s95 from a previous version of DOS. If there is no previous operating system on the computer, these steps will have no effect. SECTION 13 - OBTAINING A SIERRA PATCH DISK ACEPATCH - Updates Aces of the Pacific to version 1.02. This patch is not needed if you have version 1.02, the WWII: 1946 Expansion or the CD version of the game. This patch will work with the floppy version ONLY. AOEPAT - Patch fixes lock ups at the "Please Wait" screen on several computer models. This patch will work with the floppy version ONLY. The fastest way to obtain a Sierra patch disk is to download it from one of the following on-line services: Sierra BBS (206-644-0112), CompuServe (GO SIERRA) or America OnLine (KEYWORD SIERRA). You can also request a patch disk be mailed to you by calling Sierra Technical Support at 206-644-4343, faxing us at 206- 644-7696 or writing to Sierra On-Line Patch Disks, Dept. 10, PO Box 485, Coarsegold, CA 93614-0485. SECTION 14 -SHOULD YOU STILL HAVE PROBLEMS If you continue to experience any problems with Aces of the Pacific or Aces Over Europe, or if you have further questions, 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 be reached by fax at (206) 644-7697 or by mail at: 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 support@sierra.com OR http://www.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 CARDS 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. turns up the volume, 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. 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.