home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-06-16 | 56.8 KB | 1,601 lines |
- LODE RUNNER TECHNICAL FAQ
- revised 6/14/95
-
- Sierra Technical Support Phone: (206) 644-4343
- PO Box 85006 FAX: (206) 644-7697
- Bellevue, WA 98015-8506 BBS: (206) 644-0112
-
-
- 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 DOS ISSUES
- SECTION 5 - COMMON WINDOWS ISSUES
- SECTION 6 - SOUND CARD CONFIGURATION AND SOUND CARD ISSUES
- SECTION 7 - OBTAINING A SIERRA PATCH DISK
- SECTION 8 - DOS BOOT DISK INSTRUCTIONS
- SECTION 9 - WINDOWS BOOT DISK INSTRUCTIONS
- SECTION 10 - WINDOWS JOYSTICK INSTALLATION INSTRUCTIONS
- SECTION 11 - SOUND CARD DRIVER INFORMATION
- SECTION 12 - IF YOU STILL HAVE PROBLEMS...
-
-
-
- SECTION 1 - HARDWARE REQUIREMENTS
-
- WINDOWS FLOPPY DISK (3.5) VERSION
- REQUIRED
- 386SX/25
- 4 MB RAM
- 4 MB permanent swap file
- 12 MB hard drive space (compressed 24 MB)
- Windows 3.1
- VGA
-
- RECOMMENDED FOR BEST PERFORMANCE
- 486
- SVGA (640x480x256 color)
- Sound card with DAC
-
-
-
- WINDOWS CD ROM VERSION
- REQUIRED
- 486SX/25
- 4 MB RAM
- CD ROM drive
- 4 MB permanent swap file
- Full Install: 17 MB hard drive space (compressed 34 MB)
- Small Install: 1 MB (compressed 2 MB)
- Windows 3.1
- VGA
-
- RECOMMENDED FOR BEST PERFORMANCE
- SVGA (640x480x256 color)
- Sound card with DAC
- Double speed CD ROM drive
-
-
-
- DOS FLOPPY DISK (3.5) VERSION
- REQUIRED
- 386SX/20
- 2MB RAM (3 MB required for color)
- Conventional: 550K
- Expanded: 1MB (2MB required for color)
- 15 MB hard drive space (compressed 30 MB)
- MS-DOS 5.0 or higher
- Mouse
- VGA
-
- RECOMMENDED FOR BEST PERFORMANCE
- 486 with 4 MB RAM
- 2 MB EMS
- SVGA (640x480x256 color)
- Sound card with DAC
-
-
-
- SECTION 2 - INSTALLATION PROCEDURES
- DOS: Insert Disk 1 and
- switch to the floppy disk prompt by typing A: or B:. Then type INSTALL
- to begin the installation program. Follow the on-screen prompts to
- complete the installation.
-
- WINDOWS:
- Insert Disk 1 or the CD into the appropriate drive. From Program
- Manager, click on File, then Run. In the Command Line field, type the
- letter of the drive followed by \INSTALL. Ex: B:\INSTALL,
- D:\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 then locked up, with the row of dots on
- screen. (DOS version only.)
- SOLUTION: The dots indicate the hardware detection portion of the
- installation program. You can bypass this section (and therefore the lock-
- up) by typing INSTALL/M. If this does not work, try INSTALL/F. One
- of these entries should get you past the lock-up.
-
- PROBLEM: When installing the game, you receive an error message: 'Data
- error reading drive A'. Drive letter will vary depending on what drive
- you're using. (DOS and Windows versions.)
- SOLUTION: This is probably a faulty disk, and should be returned for
- replacement. Please see your game documentation for disk replacement
- procedures.
-
-
- SECTION 4 - COMMON DOS ISSUES
-
- PROBLEM: When you attempt to start Lode Runner, you get a message
- indicating that you have insufficient memory to run the game.
- SOLUTION: Lode Runner requires 2 MB of EMS memory, which is not
- allocated on some computers. The easiest way to allocate the memory
- correctly is to create a boot disk and run the game under the boot disk
- environment. You can create a boot disk automatically by running the
- INSTALL program or manually using the Lode Runner DOS boot disk
- instructions included with this document.
-
- PROBLEM: Black and White Graphics.
- SOLUTION: Black and white graphics in Lode Runner usually occur when
- not enough EMS memory is being allocated. The easiest way to correct
- this is to create a boot disk that allocates the memory correctly. You can
- create a boot disk automatically by running the INSTALL program or
- manually using the Lode Runner DOS boot disk instructions included with
- this document.
-
- PROBLEM: The game starts and Jake appears on the screen, but he just
- stands there shooting at the ground and can't move.
- SOLUTION: Go into the GAME OPTIONS (the check-mark icon) and look
- at the key commands for Player One (the ones on the left side). You will
- find they are all blank. Set them up for the correct keys (any keys you
- want) and you should be able to control Jake's movements.
-
- PROBLEM: Occasional graphics distortion.
- SOLUTION: When exploding a bomb near the edge of the screen, sometimes
- a 'piece' of the border goes with it and remains gone. There is no fix for
- this small graphics distortion; however, it will not cause any problem in
- the game.
-
- PROBLEM: Joystick response is erratic.
- SOLUTION: You can calibrate the joystick in Lode runner by clicking the
- upper left corner of the joystick icon in the game's 'control panel' (the icon
- represented by a check mark). Erratic joystick behavior can also be
- caused by having two separate joystick ports active at the same time. You
- should disable any extra ports; however, single cards with dual ports
- should pose no problem. If the game does not recognize the joystick port,
- or the joystick response is erratic, the problem may be that the joystick
- port is unable to support the joystick properly. Joystick ports built onto
- the motherboard or sound card are often very slow (8 MHz) and unable to
- comply with the polling requests of advanced games on fast computers.
- Installing a dedicated game card with adjustable speed should solve the
- problem.
-
-
- PROBLEM: You are unable to get past Level 24 because the exit never
- appears.
- SOLUTION: The exit on this level appears only after you find the hidden
- gold. You must dig or bomb until the hidden gold is found. If you're
- really stuck, you can request a map of this level from the Sierra Hint
- Department. You can write them at PO Box 53210, Bellevue, WA
- 98015-3210 or fax them at 206-562-4223.
-
- PROBLEM: The game runs extremely slowly.
- SOLUTION: This usually happens when the SETSOUND program detects
- your sound card settings incorrectly. To correct this, run the
- SETSOUND program in the game directory and manually select your
- sound card and settings. Do not use the auto-detect feature. If this does
- not correct the problem, run the game with a boot disk. Lode Runner
- DOS boot disk instructions are included in this document.
-
- PROBLEM: Game locks up randomly during play.
- SOLUTION: Lockups can be caused by a number of factors. If you are
- getting lockups during the game, try the following:
-
- MAKE A BOOT DISK. You can use the automatic boot disk creator by
- running INSTALL in the game directory or you can make one manually
- using the boot disk instructions included with this document. The boot
- disk will eliminate any possible memory conflicts that could be causing
- lockups. Be very careful that your sound card and CD ROM drivers are
- loaded onto the boot disk!
-
- CHECK THE SOUND CARD CONFIGURATION. Run the
- SETSOUND program in the game directory and choose 'No Digital
- Sound Driver'. Run the game. If the game does not lock up, then the
- problem is probably in the sound card configuration. Re-run
- SETSOUND and manually choose your sound card and its settings.
- Occasionally, the auto-detect feature of SETSOUND will detect your
- sound card incorrectly and this can cause the game to lock up. If you
- don't see your sound card listed under the Digital Sound Driver section of
- the SETSOUND program, refer to your sound card documentation or
- contact the manufacture of your sound card for help in setting up your
- card to run in a Sound Blaster compatible mode.
-
- CHECK FOR CORRUPTED FILES. At the DOS prompt, run
- CHKDSK /F for DOS versions up to 6.0 or SCANDISK for DOS version
- 6.20 or later. This will allow to you to detect and correct any lost
- allocation units, crosslinked files or other hard drive errors. If you find
- any, fix them, then delete and reinstall the game. Errors on the hard drive
- can corrupt files and cause lockups.
-
- CHECK YOUR CD ROM DRIVERS: Outdated CD ROM drivers can
- cause lockups, pauses and CD read errors. Make sure you are using
- MSCDEX version 2.23 in your AUTOEXEC.BAT. If you're using DOS
- 6.2 or higher, you will find MSCDEX 2.23 in the DOS directory. If you
- are not using DOS 6.20, your CD drive manufacturer should be able to
- provide you with MSCDEX 2.23. You should also check with your CD
- ROM drive manufacturer to make sure that you have the latest version of
- your CD drivers in your CONFIG.SYS.
-
-
-
- SECTION 5 - COMMON WINDOWS ISSUES
- Issues in this section cover both the floppy and CD versions of Lode
- Runner, unless otherwise noted.
-
- PROBLEM: When starting the game, Windows displays 'Insufficient
- memory. Close one or more applications and try again.'
- SOLUTION: First, make sure you are not running any other programs in
- Windows. Disable all screen savers, virus scans, IconHearIt, etc. Then,
- make sure your swap file is set to permanent and between 5 and 10 MB in
- size. You can change the swap file through the Virtual Memory Setting in
- the 386 Enhanced section of Control Panel. In addition, if you're using an
- alternate Windows desktop like Norton or PCTools, use plain Program
- Manager instead. If these steps do not give you enough memory to run
- the game, you should create a Windows boot disk. Lode Runner Windows
- boot disk instructions are included with this document.
-
- PROBLEM: After losing your last life in Lode Runner, you get an
- 'Application Error' or 'General Protection Fault' if you attempt to restore.
- (Floppy disk version only.)
- SOLUTION: This is corrected by the patch LRWIN. Please see Section 7 -
- Obtaining a Sierra Patch Disk.
-
- PROBLEM: When starting or playing Lode Runner, you receive a 'General
- Protection Fault in module LOAD.EXE'.
- SOLUTION: This is usually caused by an outdated or incompatible Windows
- video driver. You should contact your video card manufacturer to obtain
- updated drivers. You can also try running Windows in a different video
- resolution. For example, if you're using 1024x768, try 800x600 instead.
- Remember that Lode Runner runs best in 256 colors, so if you're using a
- driver with more than 256 colors, change it to 256. Switching from a
- large fonts driver to a small fonts driver may also correct the problem.
-
- PROBLEM: Occasional graphics distortion.
- SOLUTION: When exploding a bomb near the edge of the screen, sometimes
- a 'piece' of the border goes with it and remains gone. There is no fix for
- this small graphics distortion; however, it will not cause any problem in
- the game.
-
- PROBLEM: The game starts and Jake appears on the screen, but he just
- stands there shooting at the ground and can't move.
- SOLUTION: Go into the GAME OPTIONS (the check-mark icon) and look
- at the key commands for Player One (the ones on the left side). You will
- find they are all blank. Just set them up for the correct keys (any keys you
- want) and you should be able to control Jake's movements.
-
- PROBLEM: Joystick response is erratic.
- SOLUTION: You can calibrate the joystick in Lode runner by clicking the
- upper left corner of the joystick icon in the game's 'control panel' (the icon
- represented by a check mark). Erratic joystick behavior can also be
- caused by having two separate joystick ports active at the same time. You
- should disable any extra ports; however, single cards with dual ports
- should pose no problem. If the game does not recognize the joystick port,
- or the joystick response is erratic, the problem may be that the joystick
- port is unable to support the joystick properly. Joystick ports built onto
- the motherboard or sound cards or multi I/O cards are usually very slow
- (8 MHz) and unable to transfer data quickly enough to handle the polling
- requests of advanced games on fast computers. Installing a dedicated
- speed-adjustable game card will solve this problem.
-
- PROBLEM: You are unable to get past Level 24 because the exit never
- appears.
- SOLUTION: The exit on this level appears only after you find the hidden
- gold. You must dig or bomb until the hidden gold is found. If you're
- really stuck, you can request a map of this level from the Sierra Hint
- Department. You can write the Hint Department at PO Box 53210,
- Bellevue, WA 98015-3210 or fax them at 206-562-4223.
-
- PROBLEM: When installing or starting the game, you get an error message
- stating, 'WinG has found a problem with your video driver.'
- SOLUTION: This is usually caused by an outdated or incompatible Windows
- video driver. You should contact your video card manufacturer to obtain
- updated drivers. You can also try running Windows in a different video
- resolution. For example, if you're using 1024x768, try 800x600 instead.
- Remember that Lode Runner runs best in 256 colors, so if you're using a
- driver with more than 256 colors, change it to 256. If this is not possible,
- see the solution for 'Other WinG errors' below.
-
- PROBLEM: Other WinG errors.
- SOLUTION: WinG is Microsoft's newest video accelerator. Some systems
- have trouble running WinG. You can easily disable WinG if it continues
- to cause error messages. To do so, edit the LODERUNN.INI file in the
- C:\WINDOWS directory and change the following lines to read like this:
-
- DibBlit=GDI
- WinGFound=1
-
- This will disable WinG. NOTE: On some computers, disabling WinG
- causes Lode Runner to run slightly slower.
-
- PROBLEM: During play, the game pauses for a second, then continues. (CD
- version only.)
- SOLUTION: Because of CD seek times, there can be a slight pause when the
- music loops, or when a new song is starting. This is corrected in the
- patch LRWIN. Please see Section 7 - Obtaining a Sierra Patch Disk.
-
- PROBLEM: When attempting to restore a saved game, you get an error
- message stating, 'This is not a valid saved game file.' This happens with
- the small install of the CD version only.
- SOLUTION: The patch LRCDPT will correct this problem. Please see
- Section 7 - Obtaining a Sierra Patch Disk.
-
- PROBLEM: The joystick is not functioning and the joystick driver is not
- present in the Drivers section of Control Panel. (CD version only.)
- SOLUTION: Occasionally, the Windows joystick driver fails to install
- correctly. If this occurs, you will need to manually install the driver.
- Please see Section 13 - Windows Joystick Driver Installation Instructions.
-
- PROBLEM: Random lockups or General Protection Faults (GPFs).
- SOLUTION: Lockups and GPFs can be caused by a number of factors. If
- you are getting lockups and/or GPFs during the game, try the following:
-
- CREATE A CLEAN WINDOWS ENVIRONMENT: Be sure that no
- other applications are running before you install or play the game. To
- check, hold down the CTRL key and press the ESC key. This will bring
- up the Task List. If anything other than Program Manager shows up on
- this list, select it and click on End Task. Repeat these steps until nothing
- but Program Manager shows up on the list. Alternate Windows desktops
- such as Navigator, Norton Desktop, Dashboard and Tab Works can
- interfere with the game. Try running Windows with the Program
- Manager. Check your desktop documentation for more information.
-
- Sound-related Windows programs (like Icon Hear It, Wired for Sound,
- Packard Bell Navigator) can also cause conflicts with Windows games.
- You should make sure that no program of this type is running at the same
- time as the game. In addition, check your sound card settings; these
- settings should be the same in both DOS and Windows.
-
- Your Windows swap file should be permanent and 5 to 10 MB in size.
- You can check your swap file settings in the 386 Enhanced icon in the
- Control Panel.
-
- USE CHKDSK: Run the MS-DOS CHKDSK program to check for lost
- allocation units or other errors on your hard drive; if you have MS-DOS
- 6.2 or higher, SCANDISK will do this more effectively. If MS-DOS
- reports errors, correct the allocation table problems. First, back up any
- irreplaceable data from the affected hard drive. (NOTE: Correcting hard
- drive errors will not damage uncorrupted data, but it may make already
- corrupted data unusuable.) To correct lost allocation units or other errors
- on the hard drive, use the CHKDSK /F command or any other disk
- diagnostics utility such as PC Tools, Norton Utilities, or SCANDISK.
- Consult your MS-DOS or disk utility manual for more information. Once
- you have corrected these hard drive errors, delete any files associated with
- the game from your hard drive, verify that you have plenty of free hard
- drive space and re-install the game from the original disks.
-
- CHECK HARD DISK SPACE: When running the CHKDSK command,
- check the available hard disk space ('Bytes Available on Disk'). Running
- out of hard drive space while installing or playing the game can cause file
- corruption and other problems. Remember, games double in size if
- installed to a compressed drive; a game that requires 10 meg of
- uncompressed space will need 20 meg of compressed space. After
- installation, there should be at least 5 MB of disk space available (roughly
- 10 under a compressed environment).
-
- UPDATE VIDEO AND SOUND CARD DRIVERS: Outdated or
- incompatible drivers can cause lockups, black screens, error messages and
- General Protection Faults. Check with your video card and sound card
- manufacturers to make sure that you have the latest versions of your
- Windows video and sound drivers. Some manufacturers update their
- drivers several times a year, so it's easy to get behind. You can also try
- running Windows in a different video resolution. For example, if you're
- using 1024x768, try 800x600 instead. Remember that Lode Runner runs
- best in 256 colors, so if you're using a driver with more than 256 colors,
- change it to 256. Switching from a large fonts driver to a small fonts
- driver may also correct the problem.
-
- MAKE A BOOT DISK: A boot disk will free up memory and prevent
- conflicts with other TSRs. Windows boot disk instructions are included
- with this document.
-
- REINSTALL THE GAME: Delete and re-install the program. Delete all
- files and sub directories off the hard drive and reinstall from scratch. It is
- highly recommended that you re-install after booting up with a boot disk
- and running CHKDSK /F or SCANDISK.
-
- CHECK YOUR CD ROM DRIVERS: Outdated CD ROM drivers can
- cause lockups, pauses and CD read errors. Make sure you are using
- MSCDEX version 2.23 in your AUTOEXEC.BAT. If you're using DOS
- 6.2 or higher, you will find MSCDEX 2.23 in the DOS directory. If you
- are not using DOS 6.20, your CD drive manufacturer should be able to
- provide you with MSCDEX 2.23. You should also check with your CD
- ROM drive manufacturer to make sure that you have the latest version of
- your CD drivers in your CONFIG.SYS.
-
-
-
- SECTION 6 - SOUND CARD CONFIGURATION AND SOUND ISSUES
-
- CONFIGURING YOUR SOUND CARD IN DOS
- Lode Runner supports a variety of different sound cards in DOS. The
- game's sound and music configuration is set up through a program called
- SETSOUND in the directory C:\SIERRA\LODERUNN. The
- SETSOUND program is run automatically when you first install Lode
- Runner, but you can run it again at any time to change the sound card
- configuration. If you are having any kind of sound problems during the
- game, Sierra recommends that you run SETSOUND and choose your
- sound card and settings manually instead of letting the program auto-
- detect them. The auto-detect program occasionally detects the sound card
- incorrectly and this can cause problems within the game. If you don't see
- your sound card listed under the Digital Sound Driver section of the
- SETSOUND program, refer to your sound card's documentation or
- contact the manufacturer of your sound card for help in setting your card
- to run in a Sound Blaster compatible mode.
-
- CONFIGURING YOUR SOUND CARD IN WINDOWS
- Windows games such as Lode Runner use Windows' built-in sound set up.
- There are no adjustments that can be made to the game. Windows sound
- configuration may be checked in the Drivers and MIDI Mapper sections.
- You will find icons for these sections in Control Panel in the Main
- program group.
-
- First, you should verify that your Windows sound drivers are installed
- correctly. You will find these in the Drivers section of Control Panel.
- Make sure the brand-specific MIDI and wave drivers for your brand of
- sound card are there, as well as Timer, MIDI Mapper, [MCI] Sound and
- [MCI] MIDI Sequencer. If you are playing the CD version of Lode
- Runner, you will also need the [MCI] CD Audio Driver. If any are
- missing, refer to your Windows manual and install them.
-
- Now check your MIDI Mapper settings. The SoundBlaster 16, Pro Audio
- Spectrum 16, SoundBlaster Pro and compatibles support 'Base FM' or
- 'All FM' in Windows. If your MIDI Mapper is configured incorrectly,
- you may hear just music and no sound effects, or vice versa. The
- following MIDI Mapper instructions cover the most common types of
- sound card setups.
-
- Click on Main, then Control Panel and then on MIDI Mapper. If you
- have an option called Basic FM, All FM, or something similar, choose it.
- (Don't use Extended FM, however.) Close MIDI Mapper and run Lode
- Runner. If you don't have a Basic or All FM option you will need to
- create an 'All FM' setup. From the MIDI Mapper screen, click on New.
- Enter a name such as 'All FM' and then hit OK. You will be at a screen
- with four columns and 16 rows. Click on the word 'None' in the 3rd
- column and the 1st row. Now click on the small arrow that appears on
- the right of this box. One of the choices should mention 'FM' or
- 'synthesis'; choose this one. Do this for ports 1-16. Click on OK and
- close out the MIDI Mapper. The music and sound effects should now
- play correctly in Lode Runner. For further information on the correct
- MIDI Mapper configuration for your sound card, please contact your
- sound card manufacturer.
-
- CONFIGURING LODE RUNNER TO USE THE PC SPEAKER (DOS ONLY)
- If you have no sound card in your computer, you will need to set up Lode
- Runner to use the PCs internal speaker. There will be NO MUSIC for a
- system without a sound card, but there are sound effects. The best choices
- for sound effects are 'No digital sound' or 'IBM Internal speaker - 1-bit
- sound'. Using 'IBM internal speaker -background', and 'IBM internal
- speaker foreground' can cause the PC to make a long pause or lockup
- whenever it makes a sound.
-
- For the music settings, choose 'IBM Internal speaker'. When you test the
- music setting, it will not play any music. If you choose 'N' for 'No, I don't
- hear music.', it will put you back to the sound card choices. Instead
- choose 'Y', even though you don't hear anything. This will configure the
- game correctly for the PC speaker.
-
- PROBLEM: No music or sound effects in DOS.
- SOLUTION: Type SETSOUND from the C:\SIERRA\LODERUNN
- directory. Select the sound card drivers manually, do not use the
- autodetect. Make sure the DMA, IRQ and Port Address settings agree
- with your sound card.
-
- PROBLEM: Lock ups or distorted sounds using no sound card
- SOLUTION: Run the SETSOUND program in the game directory and
- choose 'IBM Internal speaker - 1-bit sound' for digital sounds. Choose
- 'IBM Internal speaker' for music. The sound test will not play any music
- when it tests the setting. If you choose N for 'no, I don't hear music' it will
- put you back to the sound card choices and the game's configuration file
- will not be written correctly. You have to lie and hit Y, for 'Yes, I pretend
- I hear music' to get through the installation. NOTE: There is NO
- MUSIC for a system without a sound card, but there are sound effects.
-
- PROBLEM: No music or sound effects in DOS, using the Ensonic
- Soundscape card.
- SOLUTION: The Ensonic drivers are probably not loading correctly on the
- boot disk. If you look in the AUTOEXEC.BAT file on your C drive by
- typing TYPE AUTOEXEC.BAT, you should see 3 lines in this order if
- your Soundscape is installed properly.
-
- SET BLASTER=A220 Ixx Dx T1
- SET SNDSCAPE=C:\SNDSCAPE
- C:\SNDSCAPE\SSINIT /I
-
- Copy these lines into the AUTOEXEC.BAT on your boot disk, reboot the
- computer and play Lode Runner. The sound should work correctly.
-
- NOTE: If the last line ends in a GM, FM or MT32, instead of a /I, you
- do not have the latest set of Soundscape drivers. We recommend that you
- get the latest drivers since they have many improvements including the
- ability to load both the General Midi and FM Synthesis modes at the same
- time. You can get this software by contacting the computer manufacturer
- if your Soundscape came installed on your system. If the card was bought
- separately you should contact the technical support numbers listed in the
- Soundscape manual or download the drivers from their BBS at 914-966-
- 1216 for up to 9600 modems or 914-966-0023 or 914-966-0021 for
- 14.4 modems. As of this writing, the latest Soundscape drivers are
- version 1.20.02.
-
- PROBLEM: No music or sound effects in Windows.
- SOLUTION: Windows games such as Lode Runner use Windows' built-in
- sound set up. Please see CONFIGURING YOUR SOUND CARD IN WINDOWS.
-
- PROBLEM: No music in Windows, Lode Runner CD only.
- SOLUTION: Lode Runner CD uses CD audio for music. To play CD audio,
- there must be a proper connection between the CD ROM drive and the
- sound card. To check your hardware, plug a set of headphones or
- powered speakers to the headphone jack on the front of the CD ROM
- drive. If you hear music through this jack, but not through your sound
- card, then your sound card is not set up for CD audio. Contact your
- sound card's manufacturer for information concerning this hook-up.
-
- PROBLEM: No sound or music when using a boot disk.
- SOLUTION: Many sound cards require drivers to be loaded in the
- AUTOEXEC.BAT and CONFIG.SYS. These sound card drivers may
- have been left off the boot disk. Section 12 - Sound Card Driver
- Information contains a list of these sound cards and their required drivers.
- If your sound card is on the list, you will need to add the specified lines to
- the boot disk. If your sound card is not on the list, check your hard drive
- AUTOEXEC.BAT and CONFIG.SYS for the drivers or consult your
- sound card documentation.
-
-
- SECTION 7 - OBTAINING A SIERRA PATCH DISK
-
- There are two patches available for Lode Runner: LRWIN is for the
- Windows 3.5' floppy disk version, LRCDPT is for the Windows CD
- version. There is no patch for the DOS version.
-
- LRCDPT corrects the problem restoring saved games in a small
- installation of the game.
-
- LRWIN address the following issues:
-
- Adds the high scores list.
- CD optimizations were worked into this version.
- Corrects 'Divide by Zero' error some computers encounter after the
- Windows joystick drivers are installed.
- Corrects GPF error messages encountered when restoring games.
- In two player mode, some users have had the Bunglers freeze. This
- has been corrected.
- Pauses in animation when the music loops is corrected.
-
-
-
- SECTION 8 - 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 not playing the CD
- version of Lode Runner.
-
-
- STEP 1
- FORMATTING THE DISK
- To make a boot disk, format a high density diskette in the A: drive. (It is
- necessary to reformat the disk if it is already formatted.) Formatting the
- disk with the /S switch 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. Type the FORMAT command
- as follows:
-
- FORMAT A: /S <ENTER>
-
- If you get a 'Bad command or file name' error message, type:
-
- PATH=C:\DOS <ENTER>
-
- Then retype the FORMAT command above. If you receive the error
- again, the MS-DOS FORMAT command may not be on your system, or
- it may have been renamed. Programs such as PC Tools and Norton Disk
- Utilities sometimes rename the FORMAT command to prevent accidental
- loss of data. If you are using a program of this type, check your
- documentation to find out how to format a SYSTEM DISK, then proceed
- to Step 2.
-
-
- STEP 2
- LOCATING THE MOUSE DRIVER
- If you are playing a game that uses a mouse, the Microsoft compatible
- mouse driver must be loaded into memory with the boot disk. There are
- two kinds of mouse drivers available: those that load in the CONFIG.SYS
- file and those that load in the AUTOEXEC.BAT file. CONFIG.SYS
- mouse drivers have an extension of .SYS (MOUSE.SYS) and
- AUTOEXEC.BAT drivers have either a .COM or .EXE extension
- (MOUSE.COM, MOUSE.EXE). You must load at least one of these
- drivers, but it is not necessary to load them all.
-
- If you do not know where the mouse drivers are located on your system,
- the command below should help you locate them. Type the following at
- the C:\ prompt:
-
- DIR MOUSE* /S <ENTER>
-
- This command will cause the system to search all subdirectories for a file
- called MOUSE. If the system locates a MOUSE file, it will display the
- path where the file is located. For example, if the MOUSE.COM file is
- located in a C:\MOUSE directory, the system will display:
-
- Directory of C:\MOUSE
- MOUSE.SYS 55160 03-10-92 3:10a
- MOUSE.COM 56408 03-10-03 6:00a
-
- If this procedure does not locate a MOUSE file, your mouse driver may
- have a different name. Some common names for mouse drivers are
- IMOUSE, GMOUSE and HPMOUSE. Your should check your mouse
- documentation for the exact file names and how to install them.
-
- Once you have located the mouse driver, you must copy it to the boot
- disk. The following example assumes that the mouse drivers are located
- in the C:\MOUSE directory as shown in the step above. To copy the
- MOUSE files to the boot disk, type:
-
- COPY C:\MOUSE\MOUSE.* A: <ENTER>
-
- Substitute the appropriate path and file names for your mouse drivers in
- the command above. After you press ENTER, you should see a message
- indicating that some files were copied.
-
-
- STEP 3
- LOCATING THE CD ROM DEVICE DRIVER (skip if not playing the CD version)
- 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. At the C:\ prompt, type:
-
- TYPE CONFIG.SYS|MORE
-
- NOTE: The | is called a 'pipe' command and is created by pressing
- <SHIFT> <BACKSLASH>.
-
- The CONFIG.SYS file will display on the screen. Look for the line that
- loads the CD ROM device driver. This line will contain the same '/D:'
- switch as the MSCDEX line in the AUTOEXEC.BAT file. Using the
- MSCDEX example above, you would be looking for a line containing
- '/D:MSCD001'. 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.
- Leave out the '/L:' information, if any. Your CD ROM device line should
- appear as follows:
-
- DEVICEHIGH=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
-
- NOTE: 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.
-
-
- 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, look at the AUTOEXEC.BAT
- on the hard drive and copy the MSCDEX line from there. At the C:\
- prompt, type:
-
- TYPE AUTOEXEC.BAT|MORE <ENTER>
-
- The AUTOEXEC.BAT file will display on the screen. Look for the line
- that loads the MSCDEX extension. 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.
- Leave out the '/L:' information, if any. If the 'LH' is missing, add it. For
- example, any of the above lines will appear on your boot disk as follows:
-
- LH C:\DOS\MSCDEX /D:MSCD001
-
-
- 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.
-
- Section 11 contains the sound card lines for many
- common sound cards. Check to see if your sound card is on the list. If it
- is, then 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 on the list, 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, switch to the A: drive
- and type the following:
-
- COPY CON CONFIG.SYS <ENTER> (the cursor will drop down one line and blink)
- DEVICE=C:\DOS\HIMEM.SYS <ENTER>
- DEVICE=C:\DOS\EMM386.EXE RAM 2800 <ENTER>
- DOS=HIGH,UMB <ENTER>
- FILES=30 <ENTER>
- BUFFERS=20 <ENTER>
-
- If you are using the MOUSE.SYS file to load your mouse, add the
- following line to the CONFIG.SYS:
-
- DEVICEHIGH=A:\MOUSE.SYS <ENTER>
-
- 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. For
- example:
-
- DEVICEHIGH=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220 <ENTER>
-
- 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 <ENTER>
- DEVICEHIGH=C:\SB16\DRV\CTMM.SYS <ENTER>
-
- Complete the file by pressing <F6> <ENTER>.
-
-
- STEP 7
- CREATING THE AUTOEXEC.BAT FILE
- To create the AUTOEXEC.BAT file on the boot disk, switch to the A:
- drive and type the following:
-
- COPY CON AUTOEXEC.BAT <ENTER> (the cursor will drop down one line and blink)
- @ECHO OFF <ENTER>
- C: <ENTER>
- SET COMSPEC=C:\COMMAND.COM <ENTER>
- PROMPT SIERRA BOOT DISK $_$P$G <ENTER>
- PATH=C:\;C:\DOS;C:\SIERRA <ENTER>
-
- If you are using the MOUSE.COM or MOUSE.EXE file to load your
- mouse driver, add the appropriate line:
-
- LH A:\MOUSE.EXE <ENTER>
-
- If you're playing a CD game, 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 <ENTER>
-
- 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>
-
- Complete the file by pressing <F6> <ENTER>.
-
- STEP 8
- REBOOT THE SYSTEM AND START THE GAME
- Reboot your system by pressing the <RESET> button on your computer
- or by using the <CTRL>, <ALT>, <DEL> key sequence on your
- keyboard. Once you receive an C:\>, type the following commands to
- begin the game:
-
- CD\SIERRA\LODERUNN <ENTER>
- LR <ENTER>
-
-
-
- SECTION 9 - WINDOWS BOOT DISK INSTRUCTIONS
-
-
- IMPORTANT NOTE: Please read the entire instructions prior to starting
- at Step 1. You can skip Steps 2 and 3 if you are not playing a CD game.
-
-
- STEP 1
- FORMATTING THE DISK
- To make a boot disk, format a high density diskette in the A: drive. (It is
- necessary to reformat the disk if it is already formatted.) Formatting the
- disk with the /S switch 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. 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)
- 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. At the C:\ prompt, type:
-
- TYPE CONFIG.SYS|MORE
-
- NOTE: The | is called a 'pipe' command and is created by pressing
- <SHIFT> <BACKSLASH>.
-
- The CONFIG.SYS file will display on the screen. Look for the line that
- loads the CD ROM device driver. This line will contain the same '/D:'
- switch as the MSCDEX line in the AUTOEXEC.BAT file. Using the
- MSCDEX example above, you would be looking for a line containing
- '/D:MSCD001'. 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.
- Leave out the 'HIGH' in 'DEVICEHIGH' ant the '/L:' information, if any.
- Your CD ROM device line should appear as follows:
-
- DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
-
- NOTE: 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.
-
-
- 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 make sure that
- MSCDEX loads correctly on the boot disk, look at the AUTOEXEC.BAT
- on the hard drive and copy the MSCDEX line from there. At the C:\
- prompt, type:
-
- TYPE AUTOEXEC.BAT|MORE <ENTER>
-
- The AUTOEXEC.BAT file will display on the screen. Look for the line
- that loads the MSCDEX extension. 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.
- Leave out the '/L:' information, if any. For example, any of the above lines
- will appear on your boot disk as follows:
-
- C:\DOS\MSCDEX /D:MSCD001
-
-
- 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 sound cards that
- require these drivers or initialization routines are the SoundBlaster 16,
- MAD16 and the Aria 16. Section 11 - Sound Card Driver Information
- contains the sound card lines for many common sound cards. Check to
- see if your sound card is on the list. If it is, add the appropriate lines to
- the AUTOEXEC.BAT and/or CONFIG.SYS on your boot disk. If your
- sound card is not listed, 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, switch to the A: drive
- and type the following:
-
- COPY CON CONFIG.SYS <ENTER> (the cursor will drop down one
- line and blink)
- DEVICE=C:\DOS\HIMEM.SYS <ENTER>
- DOS=HIGH,UMB <ENTER>
- FILES=30 <ENTER>
- BUFFERS=20 <ENTER>
-
- 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. For
- example:
-
- DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220 <ENTER>
-
- 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 <ENTER>
- DEVICE=C:\SB16\DRV\CTMM.SYS <ENTER>
-
- Complete the file by pressing <F6> <ENTER>.
-
-
- STEP 6
- CREATING THE AUTOEXEC.BAT FILE
- To create the AUTOEXEC.BAT file on the boot disk, switch to the A:
- drive and type the following:
-
- COPY CON AUTOEXEC.BAT <ENTER> (the cursor will drop down one line and blink)
- @ECHO OFF <ENTER>
- C:\ <ENTER>
- SET COMSPEC=C:\COMMAND.COM <ENTER>
- PROMPT SIERRA BOOT DISK $_$P$G <ENTER>
- PATH=C:\;C:\DOS;C:\SIERRA <ENTER>
-
- If you're playing a CD game, 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 <ENTER>
-
- 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>
-
- Complete the file by pressing <F6> <ENTER>.
-
-
- STEP 7
- REBOOT THE SYSTEM AND START WINDOWS
- Reboot your system by depressing the <RESET> button on your
- computer or by using the <CTRL>, <ALT>, <DEL> key sequence on
- your keyboard. When you are at a C:\ prompt, type WIN /3 to start
- Windows.
-
-
- STEP 8
- CREATE A CLEAN WINDOWS ENVIRONMENT
- You should make sure that all screen savers, virus scans, and sound-
- related Windows programs (IconHear It, Wired for Sound, etc.) are
- disabled before starting your game. In addition, if you are using an
- alternate Windows desktop like Norton Desktop or PCTools, disable this
- and use standard Program Manager
-
- Also, make sure you have a swap file set up that is at least 8 MB
- permanent or 16 MB temporary. You can check your swap file settings in
- the 386Enhanced icon in the Control Panel.
-
-
-
- SECTION 10 - WINDOWS JOYSTICK INSTALLATION INSTRUCTIONS
-
-
- Occasionally, the Windows joystick driver included with Lode Runner CD
- will fail to install correctly. This will cause the game to be unable to
- recognize the joystick. The following steps will help you manually install
- the Windows joystick driver.
-
-
-
- STEP 1
- INSTALL THE GAME
- During the installation of Lode Runner make sure that you check the
- INSTALL JOYSTICK box on the INSTALL ME Windows Screen.
-
-
- STEP 2
- COPY DRIVER FILES
- Once the game is installed copy the three drivers from the
- C:\SIERRA\LODERUNN\JOYSTICK directory into the Windows
- directory. The files are:
-
- JOYSTICK.CPL
- IBMJOY.DRV
- OEMSETUP.INF
-
-
- STEP 3
- EDIT OEMSETUP.INF
- EDIT the oemsetup.inf file in the Windows directory. Break the lines at
- each location marked <ENTER> so it looks like this below:
-
- Names of the disks Setup can prompt for.<ENTER>
- [disks]<ENTER>
- 1 =. ,"",ibmjoy.drv<ENTER>
- [Installable.Drivers]
- ; key = filename, type(s), description, VxD(s), Default
- Params<ENTER>
- joystick = 1:ibmjoy.drv, "joystick", "Driver for Joystick",,,
-
- Add another comma at the end of the last line so there is a total of three
- (there are only 2 commas
- originally).
-
- Save the file by choosing SAVE AS. Make sure you save the file in the
- Windows directory.
-
-
- STEP 4
- ADD THE JOYSTICK DRIVER IN CONTROL PANEL
- Click on ADD in the Drivers section of Control Panel.
-
- Click on UNLISTED DRIVERS (default)
-
- Type in C:\WINDOWS (to indicate path)
-
- Click on OKAY
-
- The driver that appears is 'DRIVER FOR JOYSTICK'. (If it doesn't then
- the OEMSETUP.INF was not edited
- properly - Go to step 3).
-
- Click on OKAY
-
- Select the game adapter type (it should normally be 2-dimensional type
- joystick).
-
- Restart Windows
-
-
- STEP 5
- CALIBRATE THE JOYSTICK
- Calibrate the joystick by clicking on the joystick ICON in the drivers
- group.
-
-
- STEP 6
- CONFIGURE THE GAME TO USE THE JOYSTICK
- Start Lode Runner and click on the check mark on the opening screen.
- When it displays the Keyboard, Mouse and Joystick select the joystick - it
- will highlight in orange when it is selected.
-
-
- SECTION 11 - SOUND CARD DRIVER INFORMATION
-
- NOTE: The sound card drivers and initialization lines in this
- section are the default settings for these devices. You should
- check your AUTOEXEC.BAT and CONFIG.SYS on your hard
- drive to see if you are using any non-default settings.
-
- 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
-
-
-
- BOKA SOUND EXPRESS
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1 T5
-
- CONFIG.SYS
- DEVICE=C:\SE1440\CSACMOD1.EXE*
-
-
-
- CRYSTAL CLEAR WAVETABLE BY CRYSTAL LAKE
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1 T5
- C:\CCLEAR\CSACMAX1
- C:\CCLEAR\CSACHMX1
-
- CONFIG.SYS
- DEVICE=C:\CCLEAR\CSAMOD1.EXE
-
-
-
- DIAMOND LX
- AUTOEXEC.BAT
- SET SONIC=C:\SONIC
- C:\SONIC\SONIC /B/C*
- SET BLASTER=A220 I5 D1 T5
-
- CONFIG.SYS
- NONE
-
- *Use /C switch for SB mode
- *Use /B switch for MSS mode
-
-
- ENSONIQ SOUNDSCAPE (Common on Gateways)
- AUTOEXEC.BAT
- SET BLASTER=A220 Ixx Dx
- SET SNDSCAPE=C:\SNDSCAPE
- C:\SNDSCAPE\SSINIT /I*
-
- CONFIG.SYS
- NONE
-
- *older drivers use /FM for Soundblaster mode, /GM
- for General Midi mode.
-
-
-
- ESS AUDIO DRIVE (Common on Compaqs)
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- NONE
-
-
-
- FORTE 16 (Common on Packard Bells)
- AUTOEXEC.BAT
- SET BLASTER=
- SET GALAXY=
- SET SOUND=C:\FORTE16
- C:\FORTE16\UTILITY\EMUTSR
-
- CONFIG.SYS
- NONE
-
-
-
- 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\GWBVOLO
- SET BLASTER=A220 I5 D1 T5
- SET GALAXY=*
- SET SOUND=C:\G2K
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the full SET GALAXY line.
-
-
-
- GRAVIS ULTRASOUND
- 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 loading to enable the
- card's Soundblaster emulation.
-
-
-
-
- IBM PS/1
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- NONE
-
-
-
- ISP 16
- AUTOEXEC.BAT
- C:\ISP16\ISPINIT /B/M*
-
- CONFIG.SYS
- NONE
-
- *Use /B switch for SB mode
- *Use /M switch for MSS Mode
-
-
-
- JAZZ 16 BY MEDIAVISION
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- DEVICE=C:\JAZZ\JAZZ.SYS D:* Q:*
-
- CONFIG.SYS
- NONE
-
- *D: DMA CHANNEL.
- *Q: IRQ SETTING.
- Specific values and directories may change - check your hard drive's
- AUTOEXEC.BAT.
-
-
-
- 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 SB mode
- *Use /M switch for MSS Mode
-
-
-
- MAGIC S20
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET SOUND16=C:\MAGICS20
- C:\MAGICS20\SNDINIT /B /M*
-
- CONFIG.SYS
- NONE
-
- *Use /B switch for SB mode
- *Use /M switch for MSS Mode
-
-
-
- MAGITEK 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
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\MEDVSN\PROS.SYS
-
-
-
- MONTE CARLO BY TURTLE BEACH
- AUTOEXE.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 MSS Mode
-
-
-
- MOZART SOUND CARD (Common on Cannons)
- 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.
-
-
- ORCHID GAMEWAVE
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET SOUND=*
- C:\GW32\GW32.EXE
-
- CONFIG.SYS
- NONE
-
-
- 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 line.
-
-
-
- PRO AUDIO SPECTRUM 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\SPECTRUM\MVSOUND.SYS D:*Q:*
-
- D: DMA CHANNEL. Q: IRQ SETTING.
- <DIR> may be PROAUDIO on older drivers.
-
-
-
- PRO SONIC
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\PROSONIC\PROSYS.SYS
-
-
-
- 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\CTMM.SYS**
-
- **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\CTMM.SYS***
-
- *Check the AUTOEXEC.BAT on your hard drive for
- the complete SB16SET line as the values may vary.
- **May be C:\SB16\SBCoFIG /S on older cards.
- ***This line is only required to enable the sound card's
- cd-rom interface.
-
-
-
- SOUND EZ
- See Mad 16
- See Mad 16
-
-
-
- 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
-
- *Use /SB switch for SB mode
- *Use /MSS switch for MSS 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 MSS Mode
-
-
-
- SOUND 144 (Common on Packard Bells)
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET GALAXY=*
- SET SOUND=SOUND144
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
-
-
-
- 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.
- **This line is required for CD ROM compatibility.
-
-
-
- VOYETRA SOUND
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET ISP16=ISP16*
- C:\ISP16\ISPINIT /B
-
- CONFIG.SYS
- NONE
-
- *May be SET ISP16=VOYETRA
-
-
-
- SECTION 12 - IF YOU STILL HAVE PROBLEMS...
-
- If you continue to experience any problems with the game, or if you have
- any questions concerning any of the above steps, Sierra Technical Support
- will be happy to assist you. You can reach Technical Support at (206)
- 644-4343 between 8:15 am and 4:45 pm, Monday through Friday. We
- can also be reached by fax at (206) 644-7697 or by mail at the following
- address:
-
- Sierra On-Line Technical Support
- PO Box 85006
- Bellevue, WA 98015-8506
-
- In Europe, please contact our office in England. The Customer Service
- number is (44) 1734-303171, between
- 9:00 am and 5:00 pm, Monday through Friday. The BBS number is (44)
- 1734-304227 and the fax number
- is (44) 1734-303201. Customer Service can also be reached at the
- following address:
-
- Sierra On-Line Limited
- 4 Brewery Court
- The Old Brewery
- Theale, Reading, Berkshire
- RG7 5AJ UNITED KINGDOM
-
- You can also contact our Technical Support Team on one of the following
- services:
-
- Sierra BBS (206) 644-0112
- CompuServe GO SIERRA
- America Online KEYWORD SIERRA
-
-
- If you decide to email, write or fax, please provide the following
- information so that Technical Support can help you as efficiently as
- possible.
-
-
-
- Game name, version number and S/N number (from disk #1)
-
- 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?
-
-
- 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/O 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.)
-
- If possible, please attach copies of your CONFIG.SYS and
- AUTOEXEC.BAT. Thanks!
-