home *** CD-ROM | disk | FTP | other *** search
Text File | 1996-01-15 | 71.4 KB | 1,969 lines |
- GABRIEL KNIGHT: THE BEAST WITHIN TROUBLESHOOTING GUIDE
- revised 1/15/95
-
- Sierra Technical Support provides this documentation as a reference to
- Sierra customers using Sierra software products. Sierra Technical
- Support makes reasonable efforts to ensure that the information contained
- in this documentation is accurate. However, Sierra makes no warranty,
- either express or implied, as to the accuracy, effectiveness, or
- completeness of the information contained in this documentation.
-
- SIERRA ON-LINE, INC. DOES NOT WARRANTY OR PROMISE
- THAT THE INFORMATION HEREIN WILL WORK WITH ANY OR
- ALL COMPUTER SYSTEMS. SIERRA DOES NOT ASSUME ANY
- LIABILITY, EITHER INCIDENTAL OR CONSEQUENTIAL, FOR
- THE USE OF THE INFORMATION HEREIN, INCLUDING ANY
- AND ALL DAMAGE TO OR LOST USE OF COMPUTER
- HARDWARE OR SOFTWARE PRODUCTS, LOSS OF
- WARRANTIES, OR LOST DATA BY THE CUSTOMER OR ANY
- THIRD PARTY. NO ORAL OR WRITTEN INFORMATION OR
- ADVICE GIVEN BY SIERRA, ITS EMPLOYEES, DISTRIBUTORS,
- DEALER OR AGENTS SHALL CHANGE THE RESTRICTION OF
- LIABILITY OR CREATE ANY NEW WARRANTIES. IN NO CASE
- SHALL SIERRA'S LIABILITY EXCEED THE PURCHASE PRICE
- OF THE SIERRA SOFTWARE PRODUCT.
-
-
- TABLE OF CONTENTS
-
- SECTION 1 - HARDWARE REQUIREMENTS
- SECTION 2 - INSTALLATION PROCEDURES
- SECTION 3 - COMMON INSTALLATION PROBLEMS
- SECTION 4 - COMMON GAME PROBLEMS
- SECTION 5 - MEMORY AND SPEED TROUBLESHOOTING
- SECTION 6 - SOUND CARD CONFIGURATION AND SOUND ISSUES
- SECTION 7 - DOS AND WINDOWS 3.1 BOOT DISK INSTRUCTIONS
- SECTION 8 - WINDOWS 95 BOOT DISK INSTRUCTIONS
- SECTION 9 - OBTAINING A SIERRA PATCH DISK
- SECTION 10 - IF YOU STILL HAVE PROBLEMS...
- SECTION 11 - SOUND CARD DRIVER INFORMATION
-
- SECTION 1 - HARDWARE REQUIREMENTS
-
- REQUIRED
-
- 486/33
- 8MB RAM
- Hard Drive Space (not including space for a Temporary
- Swap File)
- Small Install: 17 MB (compressed 34 MB)
- Medium Install: 27 MB (compressed 54 MB)
- Large Install: 42 MB (compressed 84 MB)
- Double Speed CD-ROM Drive
- MSCDEX version 2.2 or higher
- MS-DOS 5.0
- SVGA (640x480x256 colors)
- Sound card with DAC (Sound Blaster compatible)
- Mouse
-
- RECOMMENDED FOR BEST PERFORMANCE:
-
- Pentium
- 16MB RAM
- Quad speed CD ROM
-
-
- SECTION 2 - INSTALLATION PROCEDURES
-
- Note: The following examples assume that you are using hard drive C:
- and CD-ROM drive D:. If not, substitute all references with the
- appropriate drive letters.
-
- DOS INSTALLATION
- Exit Windows completely by closing Program Manager. Place the CD in
- the drive. Type C: and press <Enter> to make sure that you are logged to
- the hard drive. Then, type CHKDSK and press <Enter>. If any errors or
- problems are found, type CHKDSK /F and press <Enter> to correct them.
- Also, check the "bytes available on disk" line to insure that you have
- sufficient hard drive space to do the installation. Please note that you
- should double the hard drive space requirement when installing to drives
- that are compressed with utilities like DriveSpace or Stacker.
-
- Assuming you have sufficient space, type D: and press <Enter> to switch
- to the CD ROM drive. Then, type INSTALL and press <Enter> to begin
- installation. Follow the on-screen prompts, making sure to verify that all
- hardware selections are correct for your system.
-
- WINDOWS 3.1 INSTALLATION
- Exit Windows completely by closing Program Manager. Place the CD in
- the drive. Type C: and press <Enter> to make sure that you are logged to
- the hard drive. Then, type CHKDSK and press <Enter>. If any errors or
- problems are found, type CHKDSK /F and press <Enter> to fix them.
- Also, check the "bytes available on disk" line to insure that you have
- sufficient hard drive space to do the installation. Please note that you
- should double the hard drive space requirement when installing to drives
- that are compressed with utilities like DriveSpace or Stacker.
-
- Assuming that you have sufficient space to proceed, type WIN and press
- <Enter> to restart Windows. Then, from Program Manager, select <File>
- <Run> D:\SETUP and click on "OK". From this point, follow the on-
- screen prompts.
-
- WINDOWS 95 INSTALLATION
- Run SCANDISK from the Start, Programs, Accessories, System Tools
- menu. Allow SCANDISK to correct any errors it finds. Check the "bytes
- available on disk" line to insure that you have sufficient hard drive space
- to do the installation. Please note that you should double the hard drive
- space requirement when installing to drives that are compressed with
- utilities like DriveSpace or Stacker.
-
- Assuming that you have sufficient space to proceed, insert Disk 1 into
- your CD-ROM drive. After a few seconds, a window will automatically
- appear on your Desktop and ask you if you would like to install Gabriel
- Knight: The Beast Within. Choose "Install" and follow the on-screen
- instructions.
-
- To play Gabriel Knight: The Beast Within in Windows 95 after
- installation, insert the CD in your CD-ROM drive and follow the on-
- screen instructions.
-
-
- SECTION 2 - COMMON SETUP AND INSTALLATION PROBLEMS
-
- ALL PLATFORMS
- PROBLEM: When installing the game, you receive the message "Error
- reading drive D". Message will vary depending on what drive you are
- installing from.
- SOLUTION: There are several factors that can cause a "read" error of this
- type. 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 a recent version of
- MSCDEX in your AUTOEXEC.BAT. If you're using DOS 6.0 or
- higher, use version 2.23 of MSCDEX in your C:\DOS directory. If
- you're using Windows 95, use version 2.95 of MSCDEX in the
- C:\WINDOWS\SYSTEM directory. 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.
-
-
- DOS
- 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. (DOS installation).
- 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 /F /M.
-
-
- WINDOWS 3.1
- PROBLEM: Your computer fails the Display test because you are not
- running in 256 colors, or your video card does not meet the Pixels-per-
- second second Speed requirement for the game.
- SOLUTION: First make sure you are running Windows in 256 colors. Even
- though your monitor and video card may be capable of displaying 256
- colors, Windows may not be set up to use this resolution.
-
- If you've never changed your video display settings in Windows 3.1
- before, or if you are not familiar with the brand and type of video card
- installed in your system, then we recommend contacting your system
- manufacturer or your video card manufacturer for assistance with
- changing your Windows video display driver. The steps below are generic
- and may not necessarily apply to your particular video card.
-
- From the Program Manager double-click the Main program group icon,
- then select Windows Setup. You will see a dialog box with "Display"
- "Keyboard", "Mouse", and "Network". Click on Options, then select
- Change System Settings. You will see another dialog box, similar to the
- previous one. Click on the down arrow to the right of "Display" to view a
- list of video drivers available to you. Use the scroll bar to scroll up and
- down the list of drivers. Select a 256 color driver appropriate for your
- video card. If you are installing the driver from floppy disks or some other
- source, choose "Other Display", and you will be instructed to type a path
- to the driver, or to insert the disk with the drivers into your floppy drive.
-
- Again, if you have any problems changing your video driver and need
- more information, consult your Windows documentation, or contact the
- hardware or video card manufacturer. Additionally, if you do not seem to
- have the appropriate video drivers available to you, you will need to
- contact the hardware or video card manufacturer to obtain them.
-
- PROBLEM: Your Mitsumi double-speed CD ROM drive does not pass the
- hardware test.
- SOLUTION: Mitsumi double-speed CD ROM drives have two different
- software drivers available to use with them: a direct memory access
- (DMA) driver called MTMCDAE.SYS and a non-DMA driver called
- MTMCDAS.SYS. The MTMCDAE.SYS driver is faster, but can prove
- to be incompatible with some software. The solution is to load the
- MTMCDAS.SYS driver when you want to play the game. The simplest
- way to do this is to make a boot disk for the game and modify the
- CONFIG.SYS file on it so the MTMCDAS.SYS driver loads. This
- driver should be in the same directory as MTMCDAE.SYS. If not, you'll
- need to re-run the installation program for your CD ROM drivers. See
- the attached boot disk instructions for additional assistance.
-
- PROBLEM: "Setup was unable to add an item for Gabriel Knight to a
- program group" message when installing the game. Game icon not
- created during game installation.
- SOLUTION #1: You may have run out of hard drive space. Free up more
- hard drive space and try again. See Section 1 for hard drive space
- requirements.
- SOLUTION #2: This can be caused by an alternate Windows desktop, like
- PC Tools, Norton Desktop or Packard Bell Navigator. You must disable
- your alternate desktop before installing the game. One quick way to do
- this is to type "WIN PROGMAN" to start Windows to use Program
- Manager rather than the alternate desktop shell. When you are back in
- Windows, reinstall the game. The icons will be created in the Sierra
- group in Program Manager. The next time you go into Windows, the
- alternate desktop will display. Tip For PC Tools: Once you finish
- installing the game, click on FILE, then IMPORT. Import the Sierra
- group so all the game icons will appear in PC Tools. To restart Windows
- using your normal desktop, exit Windows and reboot the computer. The
- next time you go into Windows, the alternate desktop will display.
- PLEASE NOTE: The Beast Within has not been tested under any
- alternate desktop environment, therefore Sierra cannot guarantee that the
- game will function properly under these desktops. If you wish to try,
- however, here are the game icon properties:
-
- Description: The Beast Within
- Command Line: C:\SIERRA\GK2WIN\SIERRAW.EXE C:\SIERRA\GK2WIN\RESOURCE.WIN
- Working Directory: D:\
- Shortcut Key: None
-
-
- WINDOWS 95
- PROBLEM: Your computer fails the Sound Card test; you cannot hear the
- voice and fanfare in the Wave and MIDI tests.
- SOLUTION: Your sound card may be incorrectly configured for DAC
- (Audio) or your sound card drivers may not be properly installed or
- configured for Windows 95. Make sure your speakers are turned on and
- run the Windows mixer program for your sound card so you can increase
- its volume levels for MIDI (music) and DAC (Audio). You should consult
- your sound card documentation or the manufacturer for information
- regarding the correct configuration of your sound card in Windows 95.
-
- PROBLEM: Your computer fails the Display test because you are not
- running in 256 colors, or your video card does not meet the pixels-per-
- second second speed requirement for the game.
- SOLUTION: First make sure you are running Windows in 256 colors. Even
- though your monitor and video card may be capable of displaying 256
- colors, Windows may not be set up to use this resolution. Click on the
- Start button, select Settings, then Control Panel. Double-click the
- Display icon. You will see four tabs: Background, Screen Saver,
- Appearance, and Settings. Click on Settings. In the box under Color
- Palette, it should say 256 Color. If it does not, click on the down arrow
- next to the window to view a list of choices, and select the one that says
- 256 Color. You will also notice a slider bar under Desktop Area for
- adjusting resolution from 640 by 480 pixels (the lowest setting) upwards.
- If your video card failed the initial speed test, try adjusting the resolution
- to 640 by 480 pixels. This will decrease the screen resolution but may
- improve the speed of your video card.
-
- PROBLEM: Your computer fails the Memory test; you get a message stating
- you do not have enough memory to run Gabriel Knight: The Beast Within.
- SOLUTION: Gabriel Knight requires a computer with a minimum of 8 MB
- (8192k) of RAM to run. To free up memory in Windows 95, close any
- and all Windows programs (including screen savers, wallpaper, virus
- detection programs, shell programs like Norton Desktop or Packard Bell
- Navigator, etc.) that may be running. On your Taskbar, right-click on the
- program tab for the program you wish to shut down, and select Close.
- Then run the Setup test program again. If your system still fails the test,
- consult the boot disk instructions at the end of this document and create a
- Windows 95 boot disk for your system. Then boot up with the boot disk,
- disable any and all other Windows programs, and start the Setup/Install
- program again. These steps should give you enough memory to run the
- program.
-
-
- SECTION 4 - COMMON GAME PROBLEMS
-
- PLEASE NOTE: Unless otherwise stated, the following issues occur in
- both the DOS and Windows versions of Gabriel Knight: The Beast
- Within.
-
- PROBLEM: You receive "You need XXXXXX bytes more memory to run
- this application," "DOS4GW Professional error", "Insufficient memory"
- or "Out of Memory" messages when attempting to run The Beast Within.
- SOLUTION: See Section 5 - Memory and Speed Troubleshooting for help
- with memory problems.
-
- PROBLEM: You receive an "EMM386 Error #6" while playing the game.
- The error number may vary.
- SOLUTION: This error is caused by a memory conflict. Create a boot disk
- using the appropriate instructions in Sections 7 or 8 and run the game
- under the boot disk environment to avoid these errors.
-
- PROBLEM: You receive an "Out of memory" or "Out of moveable memory"
- in Chapter Four when talking to Gerde at Schloss Ritter.
- SOLUTION: You need the patch GK2PAT. Please see Section 9 for
- information on obtaining this patch. NOTE: The patch fixes this memory
- error ONLY. Any other memory errors are related to your computer's
- memory configuration. Please see Section 5 - Memory and Speed
- Troubleshooting for help resolving other memory problems.
-
- PROBLEM: You receive the error message, "Cannot find 999.pal resource.
- If this is a CD-ROM game, please make sure that a CD-ROM is loaded.
- If you continue to experience this dialog, make sure your CD-ROM
- drivers are loaded properly."
- SOLUTION: This error occurs when the game program is unable to locate
- the Gabriel Knight CD in the CD-ROM drive. Make sure a CD is in the
- drive. If there is a CD in the drive, then your CD-ROM drivers are not
- loading properly and the game is not recognizing your CD drive. Create a
- boot disk using the appropriate instructions in Sections 7 or 8 and make
- sure the CD-ROM drivers load correctly.
-
- PROBLEM: "Error 53: Can't find sound driver ''. Please run INSTALL"
- message when starting the game. (DOS version)
- SOLUTION: This error will occur if you type "D:\INSTALL" to install The
- Beast Within. To solve this problem, you must type "D:" and press the
- ENTER key (if your CD-ROM drive is D:), then type "INSTALL" and
- press ENTER.
-
- PROBLEM: When starting the game, you receive the error message, "No
- mouse driver was found in MS-DOS". (DOS version)
- SOLUTION: Locate and run a DOS mouse driver before running The Beast
- Within. Check your mouse documentation for complete instructions on
- running your mouse driver.
-
- PROBLEM: Your mouse pointer only works on one side of the screen. (DOS
- version)
- SOLUTION: This is indicative of a conflict between your VESA driver and
- your mouse driver. Contact your video card and mouse manufacturers to
- obtain updated drivers.
-
- PROBLEM: You receive the error message, "No VESA support detected"
- when starting the game. (DOS version)
- SOLUTION: This error occurs when your video card's VESA driver is not
- loaded before the game is run. The VESA driver allows DOS games to
- run in the resolution of 640x480x256 colors. Sierra has provided many
- popular VESA drivers for your use on CD #1. You will find them in the
- \VESA\VESA directory on the CD. If you do not see your video card
- listed, or the drivers on the CD do not work for you, please contact your
- video card to obtain the latest VESA driver for your card.
-
- PROBLEM: "DOS/4GW Professional Fatal Error", followed by a screen of
- technical information while running GK2 in an MS-DOS box under
- Windows 95.
- SOLUTION: Although you can run The Beast Within through an MS-DOS
- box under Windows 95, Sierra recommends running the Windows version
- of the game in Windows 95 or rebooting into an MS-DOS session before
- installing and running the DOS version of the game. To allow Win95 to
- boot to an MS-DOS session, reboot your computer and press the F8 key
- on your keyboard when you see the screen message "Starting Windows
- 95".
-
- PROBLEM: The game is too dark. (DOS version)
- SOLUTION: Edit the game's configuration file on the hard drive to increase
- the brightness. To do this, type the following command at the
- C:\SIERRA\GK2DOS prompt:
-
- EDIT C:\SIERRA\GK2DOS\RESOURCE.CFG
-
- You'll see a line "brightness = 0". Increase this number to 4. Save this
- change, then start GK2 to see an increase in the game brightness. NOTE:
- If you increase the brightness to 5 or more, you'll see very odd colors or a
- black screen in the game.
-
- PROBLEM: The game is too dark. (Windows version)
- SOLUTION: Edit the game's configuration file on the hard drive to increase
- the brightness. To do this, type the following command at the
- C:\SIERRA\GK2WIN prompt:
-
- EDIT C:\SIERRA\GK2WIN\RESOURCE.WIN
-
- You'll see a line "brightness = 0". Increase this number to 4. Save this
- change, then start GK2 to see an increase in the game brightness. NOTE:
- If you increase the brightness to 5 or more, you'll see very odd colors or a
- black screen in the game.
-
- PROBLEM: Choppy video playback.
- SOLUTION: In the game's Control Panel, click on the "Big Movies" icon to
- toggle the "Small Movies" option. This should allow the movies to run
- faster on your computer. You should also create a boot disk using the
- appropriate instructions in Sections 7 or 8. Using a boot disk to run the
- game will maximize your computer's resources and allow the video
- sequences to play as smoothly as possible. In addition, if you chose the
- small (17 meg) or medium (27 meg) installation, delete and reinstall using
- the large (42 meg) installation. This will let critical parts of the game run
- from your faster hard drive instead of the slower CD-ROM drive.
-
- PROBLEM: You receive an "Error 111: Screen item does not exist in list"
- or "Error loading 2230.vmd" when prompted to switch CDs. (Error
- numbers may vary.)
- SOLUTION: These errors occur when you press the <Enter> key too soon
- after inserting the new CD. Wait for the light on your CD drive to go off
- before pressing the <Enter> key.
-
- PROBLEM: You receive an "Error 99: Error loading resource 122v56"
- when switched from CD #1 to CD #2.
- SOLUTION: You need the patch GK2PAT. Please see Section 9 for
- information on obtaining this patch. NOTE: This patch correct the error
- with resource 122v56 ONLY. Similar errors when switching CDs are
- caused by pressing the <Enter> key too soon. After inserting the new CD,
- wit for the light on your CD drive to go off before pressing the <Enter>
- key.
-
-
- PROBLEM: You receive a "CDR 101" or "DOS Error, Read Error"
- message while playing the game.
- SOLUTION: There are several factors that can cause "read" errors of this
- type. 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 a recent version of
- MSCDEX in your AUTOEXEC.BAT. If you're using DOS 6.0 or
- higher, use version 2.23 of MSCDEX in your C:\DOS directory. If
- you're using Windows 95, use version 2.95 of MSCDEX in the
- C:\WINDOWS\SYSTEM directory. 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: When game starts in Windows, it crashes to a black screen or
- throws you out to DOS.
- SOLUTION: First, create a boot disk using the appropriate instructions in
- Sections 7 or 8, then make sure that there are no other programs running
- in Windows. If this does not help, the problem probably lies with your
- video or sound card drivers. Outdated drivers can cause this type of
- program crash. Contact your video and sound card manufacturers to
- obtain the latest version of their drivers.
-
- PROBLEM: "General Protection Fault in Module ... " The module name will
- vary. (Windows 3.1)
- SOLUTION: A General Protection Fault (GPF) is usually caused by a
- memory conflict. Make sure that there are no other Windows programs
- running; disable all screen savers, virus scans, etc.
-
- If you are using an alternate Windows desktop (PC Tools, Dashboard,
- Packard Bell Navigator, etc.), use plain Program Manager instead. One
- quick way to do this is to type "WIN PROGMAN" to start Windows
- using the regular Program Manager rather than the alternate desktop shell.
- If you have sound-related Windows programs installed (IconHearIt,
- SoundBits, etc.), make sure they are disabled before starting the game.
-
- Outdated or incompatible video or sound drivers can also cause this type
- of error. Contact your video and sound card manufacturers to obtain the
- latest version of their drivers.
-
- A Windows boot disk also helps with GPFs. Instructions for creating a
- boot disk are at the end of this document. GPFs can also be caused by
- outdated or incompatible sound or video drivers. If the above steps do not
- solve the GPF for you, contact your video and sound card manufacturers
- to obtain the latest versions of their Windows drivers.
-
- PROBLEM: While playing The Beast Within in Windows 95, you receive a
- message saying "This program has performed an illegal operation...".
- SOLUTION: An "Illegal Operation" in Windows 95 is similar to a General
- Protection Fault in Windows 3.1 and occurs for the same reasons.
- Therefore, the solutions are similar as well. First, make sure that you are
- not running any Windows programs other than the game. Programs like
- screen savers and virus detection programs should be disabled. If you are
- using an alternate Windows desktop (PC Tools, Dashboard, Packard Bell
- Navigator, etc.), use the default Windows 95 desktop instead. If you have
- sound-related Windows programs installed (IconHearIt, SoundBits, etc.),
- make sure they are disabled before starting the game.
-
- Outdated or incompatible video or sound drivers can also cause this type
- of error. Contact your video and sound card manufacturers to obtain the
- latest version of their drivers.
-
- You should also make sure that you are running Windows 256 colors.
- Running in less or more colors can cause errors of this type. (Consult the
- steps given for changing display settings in Section 2 - Common
- Installation PROBLEMs.)
-
- Windows 95 allows you to disable some video acceleration. This often
- helps with Illegal Operation errors. To do this,
- click on Start, then Settings, Control Panel. Double-click the System
- icon, choose Performance, then Graphics. You should see a slider bar
- labeled Hardware Acceleration. Lower the bar a notch (slide it to the left),
- then restart Windows when you are prompted and run the game again.
- Continue doing this until you cannot lower the bar any more or the
- problem is corrected. If this corrects the problem, you should contact your
- video card manufacturer to obtain updated video drivers.
-
- You can also free up memory by lowering your CD ROM Supplemental
- Cache Size. From Control Panel, click on System, then Performance,
- File System. Click on the tab for CD ROM. Adjust the slider bar for
- Supplemental Cache Size from "Large" to "Small", then click on OK.
-
- PROBLEM: "Divide by zero" error using a Gravis Ultrasound in Windows.
- SOLUTION: This error occurs when the GUS patches are not loaded
- correctly. To load the patches, use Media Player to play one of the
- following .MID files: LOAD256.MID, LOAD512.MID,
- LOAD1024.MID. For example, if you have 512k of memory on the GUS,
- play the LOAD512.MID file. Playing the appropriate .MID file will load
- the patches and prevent the error.
-
- PROBLEM: After talking with Leber in Chapter One, you cannot get back
- to his office to ask him about the "Black Wolf".
- SOLUTION: This error occurs when you talk to Leber before visiting
- Ubergrau's office for the first time. The patch, GK2PAT, corrects this
- problem. Please see Section 9 for information on obtaining a Sierra patch
- disk.
-
- PROBLEM: In the map screen, the Neuschwanstein border does not stop
- blinking, even though you have listened to every tour tape.
- SOLUTION: The patch, GK2PAT, corrects this problem. Please see Section
- 9 for information on obtaining a Sierra patch disk.
-
- PROBLEM: You cannot ask Georg about the "Lost Opera" topic, then
- cannot get back to the Museum.
- SOLUTION: The patch, GK2PAT, corrects this problem. Please see Section
- 9 for information on obtaining a Sierra patch disk.
-
- NOTE: If you do not see your specific problem listed above, these
- standard troubleshooting procedures correct most problems running The
- Beast Within.
-
- Step 1 - Run the program from a minimal boot disk. (DOS and
- Windows versions)
- A boot disk is a tool that can be used to resolve most conflicts. Boot disks
- will free up more system resources and memory for your games. The boot
- disk also creates an environment that is "cleaner" or free of extra TSR
- and utilities that can sometimes cause conflicts. Boot disk instructions are
- included in Sections 7 and 8 of this document.
-
- Step 2 - Check for corrupted files. (DOS and Windows versions)
- Run CHKDSK /F or SCANDISK to detect and correct any hard drive
- errors and corrupted files. If you find any errors such as cross-linked or
- truncated files or lost allocation units, correct them, then delete and
- reinstall the game.
-
- Step 3 - Check for sound card conflicts. (DOS version)
- Many lockups in games can be traced to sound card configuration. 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 your sound card's documentation for help
- resolving sound card conflicts.
-
- Step 4 - Reinstall the game in a clean boot environment. (DOS and
- Windows versions)
- Lockups and other technical problems can be caused by corrupted game
- files. No program will run correctly if the data or executable files are
- corrupted. These corruptions will occur during the installation of the
- game and are usually due to conflicts with TSRs or other utilities running
- in DOS during the installation. Reinstalling the game in the same DOS
- environment will usually result in the same corrupted data. You should
- install the game in a "clean" boot environment.
-
- Step 5 - Create a clean Windows environment (Windows version)
- 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. In addition, if you are using an alternate Windows desktop like
- Norton Desktop or PCTools, use the default Windows desktop instead.
- Check your swap file settings. If you are using Windows 3.1, swap file
- should be between 6-10 MB. If you are playing in Windows 95, make
- sure that your virtual memory is enabled.
-
- Step 6 - Check your drivers! Outdated or incompatible video or sound
- drivers can also cause lockups and errors in Windows. Sierra
- recommends you check with your sound and video card manufacturers to
- make sure you have the latest versions of these drivers. Some
- manufacturers update their drivers several times a year, so it's easy to get
- behind.
-
-
- SECTION 5 - MEMORY/SPEED TROUBLESHOOTING
-
- If you are having difficulties freeing up sufficient memory to play The
- Beast Within or are experiencing problems with choppy video playback,
- try the following steps:
-
- Make a Boot Disk: A boot disk will allow you to start your system with
- only the minimal memory-resident programs necessary to run and with a
- memory configuration optimal to the game. To make a boot disk, simply
- place a new, high-density diskette in your A: drive and either double-click
- on the Boot Disk Maker icon in the Sierra Windows program group or run
- the game's DOS INSTALL program and choose the "Make bootable
- floppy disk." option then follow the on-screen prompts. If, for any reason,
- the game will not make you a proper boot disk, consult the appropriate
- manual boot disk creation instructions in Sections 7 and 8. Please note:
- Many systems equipped with large IDE hard drives have special
- procedures that must be followed to boot from a boot disk. Two common
- examples are holding the <Shift> key while pressing the Reset button or
- pressing the <Spacebar> after rebooting. If your system has difficulties
- reading the boot disk, check your system documentation for the correct
- procedure to boot from a boot disk in the A: drive.
-
- Close Other Memory-Resident Programs: If playing in Windows, try
- to free up as many resources as possible. If you have Windows 3.11, start
- Windows from your DOS prompt with the command WIN /N. This will
- disable the built-in network drivers that Win 3.11 loads. You should also
- make sure to close any other memory-resident programs before playing
- The Beast Within. If you are using an alternate Windows desktop shell,
- like PC Desktop, Norton Desktop or Tabworks, try disabling in to free up
- more resources to the game.
-
- Make Virtual Memory Adjustments: If playing in Windows 3.11 or
- Windows for Workgroups, disable 32-bit file access as it by default takes
- up at least 2 MB of RAM. To do this, double click on the 386 Enhanced
- icon in Control Panel. When the dialog box pops up, click on the Virtual
- Memory button and then the Change button. If the 32-bit file access box
- has an "X" in it, remove it. If you are using Windows 3.1, you will see a
- 32-bit disk access option. Do not disable this option. For these versions
- of Windows, make sure that you are using a permanent Windows swap
- file of about 8-9 MB. You can make these changes in the "New Settings"
- section of the Virtual Memory screen. In Windows 95, make sure that
- virtual memory is enabled and that the virtual memory settings are being
- handled by Windows.
-
- Play the Game in DOS: The Windows operating system takes up
- resources above and beyond those of DOS. To free up the most resources
- for the game, try running the game in DOS instead. If you're using
- Windows 3.1, exit Windows. If you're playing in Windows 95, restart in
- DOS mode. Place the first CD in the drive, change to that drive by typing
- the drive letter of the CD ROM followed by a " : " (colon) and pressing
- <Enter>. From the resulting prompt, type INSTALL, press <Enter> and
- follow the on-screen prompts.
-
- Adjust the SMARTDRV cache: If you are playing the game in Windows
- 3.1, adjust your SMARTDRV cache. The default size for SMARTDRV
- on most computer systems is 2048K or 2 megabytes. On a computer with
- 8 MB RAM, there may not be enough free memory left over for the game.
- On your boot disk, reduce SMARTDRV 2048,2048 to SMARTDRV
- 1024,512. If you still get the error, remove the SMARTDRV line from the
- boot disk's AUTOEXEC.BAT.
-
- Reduce the "sciMinK" value: If you are playing in Windows and you
- continue to receive memory errors after creating a boot disk and adjusting
- the SMARTDRV cache, edit the file
- C:\SIERRA\GK2WIN\RESOURCE.WIN. Look for the line
- "sciMinK=2100". Change this line to read "sciMinK=1900". Save this
- change, then run the game again.
-
- Reduce the Game Window: Graphics are an extremely memory-
- intensive operation. To free up memory, and make the game run more
- smoothly, access the game's Control Panel and toggle from "Big Movie"
- to "Small Movie". The game videos will play in a smaller window, but
- should run more smoothly.
-
-
- SECTION 6 - SOUND CARD CONFIGURATION AND SOUND ISSUES
-
- DOS SOUND CARD CONFIGURATION
- In DOS, the best sound card settings for a SoundBlaster compatible card
- are I/O 220, DMA 1 and IRQ 5 or 7. If you're using a Pro Audio card,
- the best settings are I/O 220, DMA 3 and IRQ 5 for the Pro Audio portion
- of the card, set the SoundBlaster portion of the card to DMA 1 and IRQ
- 7. Make sure that the Soundblaster and ProAudio portions do not share
- the same DMA! Settings outside these parameters can cause lockups
- and/or choppy, repeating or garbled speech. Most sound cards have test
- utilities that will tell you what settings you are using. Check your sound
- card documentation for more information.
-
- WINDOWS 3.1 SOUND CARD CONFIGURATION
- Sierra's Windows games should work correctly with any sound card
- settings, providing there are no hardware conflicts. However, as in DOS,
- Sierra recommends using the sound card's default settings. When
- configuring your sound card in Windows, there are two locations to check:
- the Drivers section of Control Panel and the MIDI Mapper. NOTE: The
- beast Within doesn't use MIDI music and therefore doesn't require
- the use of the MIDI Mapper or MIDI sequencer. However, these
- drivers should be installed on most machines for other programs that use
- MIDI to function properly.
-
- In the Drivers section, you should see the following:
-
- MIDI Mapper
- Timer
- [MCI] CD Audio
- [MCI] MIDI Sequencer
- [MCI] Sound
-
- These drivers come with Windows, so if you are missing any, they can be
- installed by choosing the Add button in the Drivers window and installing
- them off of your Microsoft Windows Installation disks. In addition to
- these standard Windows drivers, there should be two or three sound card-
- specific drivers. These drivers should have the name of your sound card
- in their title. If these are missing, you will need to reinstall the sound card
- drivers off of the sound card installation disks. Your sound card
- documentation will tell you the names of these drivers and how to install
- them.
-
- WINDOWS 95 SOUND CARD CONFIGURATION
- To make sure that your sound card is configured correctly in
- Windows 95, check the Audio and MIDI settings in the Multimedia
- section of Control Panel. The Audio setting defines what driver will
- be used to produce digitized sound (DAC). Speech and sound effects
- in a game are usually DAC sounds. The MIDI setting indicates what
- driver is being used for music playback. The following examples are
- for the SoundBlaster 16:
-
- AUDIO: SB16 Wave Out
- MIDI: MIDI for Internal OPL2/OPL3 FM Synthesis
-
- The names of the Audio and MIDI drivers will vary, depending on
- your sound card. However, they should be similar to these
- SoundBlaster 16 drivers. For complete information (including driver
- names and installation instructions) on Windows 95 drivers for your
- sound card, contact your sound card manufacturer.
-
-
- DOS SOUND ISSUES
- PROBLEM: Choppy, repeating or garbled speech.
- SOLUTION: This is caused by non-standard sound card settings or a conflict
- between the sound card and another piece of hardware on your computer.
- See "DOS Sound Card Configuration" above for supported settings and
- refer to your sound card documentation for information on resolving
- hardware conflicts.
-
-
- WINDOWS 3.1X AND WINDOWS 95 SOUND ISSUES
- PROBLEM: No sound or music.
- SOLUTION: This may be caused by incorrect driver selection or outdated or
- incompatible sound card drivers. See the above sections on Windows
- Sound Card Configurations for information on sound card drivers. Even
- if you have all of the required drivers installed sometimes they can become
- corrupted thereby not functioning properly. In these cases removing and
- reinstalling the driver will help. If you need help with this, contact your
- Sound card Manufacturer.
-
- PROBLEM: Starting the game gives you a "Waveout Open" or "Waveout
- Prepare Header" error message. Windows only.
- SOLUTION: This error message indicates that your sound card is in use by
- another program. This is usually caused by another sound program
- taking control in Windows and not sharing the sound card properly.
- Programs like Icon Hear It, Wired for Sound or Packard Bell Navigator
- can cause this type of problem. Some screen savers like After Dark will
- also access the sound card directly instead of using Windows to produce
- sounds. You should disable all programs of this type before playing the
- game.
-
-
- SECTION 7 - DOS AND WINDOWS 3.1 BOOT DISK INSTRUCTIONS
-
- IMPORTANT NOTE: Please read the entire instructions prior to
- starting at Step 1. If you are playing the Windows version of The Beast
- Within, you can skip Step 2.
-
- 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 (Skip if playing the Windows
- version of The Beast Within)
- 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
- 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, and the "HIGH" in
- "DEVICEHIGH". 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 4
- LOCATING THE MSCDEX CD ROM EXTENSION
- In addition to the CD ROM device driver in the CONFIG.SYS, your CD
- ROM drive requires MSCDEX, the Microsoft extension for CD ROM
- drives. If this extension is not loaded correctly in the AUTOEXEC.BAT,
- you will be unable to access your CD ROM drive. To make sure that
- MSCDEX loads correctly on the boot disk, 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 and the "LH" at the beginning of
- the line. For example, any of the above lines will appear on your boot disk
- as follows:
-
- 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.
-
- 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, 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, type the following at a
- DOS prompt:
-
- A: <ENTER>
- CD\ <ENTER>
- EDIT CONFIG.SYS <ENTER>
-
- This will display the blank (usually blue) screen of the DOS Editor. Enter
- the following lines:
-
- DEVICE=C:\DOS\HIMEM.SYS
- DOS=HIGH,UMB
- FILES=30
- BUFFERS=20
-
- If you're using MOUSE.SYS to load your mouse, add the following line:
-
- DEVICE=A:\MOUSE.SYS
-
- Add the CD ROM device driver as you wrote it down in the "Locating the
- CD ROM Device Driver" section. The device driver should look
- something like this:
-
- DEVICE=C:\DRV\CDROMDRV.SYS /D:MSCD001 /P:220
-
- If you need to load any sound card drivers, copy them from the "Sound
- Cards" section now. The following example lines are for the
- SoundBlaster 16:
-
- DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
- DEVICE=C:\SB16\DRV\CTMMSYS.SYS
-
- Save the file by pressing <ALT>, <F>, then <S>. Exit the file by
- pressing <ALT>, <F>, then <X>.
-
- STEP 7
- CREATING THE AUTOEXEC.BAT FILE
- To create the AUTOEXEC.BAT file on the boot disk, type the following
- at a DOS prompt:
-
- A: <ENTER>
- CD\ <ENTER>
- EDIT AUTOEXEC.BAT <ENTER>
-
- This will display the blank (usually blue) screen of the DOS Editor. Enter
- the following lines:
-
- @ECHO OFF
- C:\
- SET COMSPEC=C:\COMMAND.COM
- PROMPT SIERRA BOOT DISK $_$P$G
- PATH=C:\;C:\DOS;C:\SIERRA
-
- If you are using the MOUSE.COM or MOUSE.EXE file to load your
- mouse, add the appropriate line:
-
- A:\MOUSE.COM
-
- Add the MSCDEX line as you write it down in the "Locating the
- MSCDEX CD ROM Extension" section. For example:
-
- C:\DOS\MSCDEX /D:MSCD001
-
- If you need to run any sound card initialization programs or load any
- drivers, copy them from the "Sound Cards" section now. The following
- example lines are for the SoundBlaster 16:
-
- SET BLASTER=A220 I5 D1 H5 T6
- SET SOUND=C:\SB16
- SET MIDI=SYNTH:1 MAP:E
- C:\SB16\SB16SET /M:220 /VOC:220 /CD:220 /MIDI:220 /LINE:220
- C:\SB16\DIAGNOSE /S
-
- Add a MS DOS Smartdrive disk cache to enhance performance of the
- videos in the game. If you have an 8 MB system, type the following line:
-
- C:\DOS\SMARTDRV /512
-
- If you have 12 or more MB of RAM, use the following line instead:
-
- C:\DOS\SMARTDRV /2048
-
- Save the file by pressing <ALT>, <F>, then <S>. Exit the file by
- pressing <ALT>, <F>, then <X>.
-
- 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 combination on your keyboard.
- Once you get to a DOS prompt, follow the instructions in the game
- manual to begin.
-
- Note: If your system does not seem to recognize the boot disk, check
- your system documentation to insure that your computer does not use a
- hard disk manager that requires a special procedure to boot from a floppy
- disk.
-
-
- SECTION 8 - WINDOWS 95 BOOT DISK INSTRUCTIONS
-
- IMPORTANT NOTE: Please read all instructions before beginning this
- procedure.
-
- 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. The computer will now re-boot
- with the boot disk. When Windows 95 restarts, start the game.
-
-
- SECTION 9 - OBTAINING A SIERRA PATCH DISK
-
- There is one patch available for Gabriel Knight II: The Beast Within. This
- patch (GK2PAT) corrects the following issues:
-
- 1. Corrects "Out of memory" message at Schloss Ritter in Chapter 4.
- 2. Corrects "Error 99: Error Loading Resource 122v56" that occurs
- when switching to CD #2.
- 3. Fixes "dead end" that occurs when player exhausts dialogue with
- Leber before visiting Ubergrau's office for the first time and then
- can't get back to Leber to ask about "Black Wolf".
- 4. Fixes problem where Neuschwanstein border does not stop blinking
- even after player has heard every tour tape.
- 5. Fixes problem where Georg does not have "Lost Opera" topic if
- player hasn't clicked on "Letter to Conductor" in the Museum but has
- exhausted topics with Frau Miller, then cannot get back to the
- Museum.
- 6. Allows Grace to get holy water only once.
-
- The fastest way to obtain this patch disk is to download it from one of the
- following on-line services: the Sierra BBS (206-644-0112), FTP to the
- Sierra BBS (bbs.sierra.com), 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-7697,
- faxing to 206-644-7697 or writing to Sierra On-Line Patch Disks, Dept.
- 10, PO Box 485, Coarsegold, CA 93614-0485.
-
-
- SECTION 9 - IF YOU STILL HAVE PROBLEMS
-
- If you continue to experience any problems with Gabriel Knight: The
- Beast Within or if you have technical 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 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 or Telnet bbs.sierra.com
- CompuServe GO SIERRA
- America Online KEYWORD SIERRA
- Internet support@sierra.com
- 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 CARD DRIVER INFORMATION
-
- NOTE: The sound card drivers and initialization lines in this section are
- the default settings for these devices. You should check your AUTOEXEC.BAT
- and CONFIG.SYS on your hard drive to see if you are using any non-default
- settings.
-
-
- ADLIB
- AUTOEXEC.BAT
- NONE
-
- CONFIG.SYS
- NONE
-
- This is a MIDI card only and will not play most sound
- effects.
-
-
- ARIA 16 - Common on IBMs
- AUTOEXEC.BAT
- SET ARIA=C:\ARIA
- SET BLASTER=A220 I5 D1 T5
- C:\DOS\SOUNDCLT.COM*
-
- CONFIG.SYS
- DEVICE=C:\ARIA\BIN\SOUNDCFG.SYS
- DEVICE=C:\ARIA\BIN\SNDSAVER.SYS
-
- *This line is not always present.
-
-
- ATI STEREO FXCD
- AUTOEXEC.BAT
- SET ATI_SND=C:\SFXCD
-
- CONFIG.SYS
- NONE
-
-
- AUDIO ROCK IT 16
- AUTOEXEC.BAT
- NONE
-
- CONFIG.SYS
- NONE
-
-
- AUDIO 16 BY AZTECH
- AUTOEXEC.BAT
- C:\GB2KAUDIO\UTILITY\GWBVOL
- SET BLASTER=*
- SET SOUND=*
-
- CONFIG.SYS
- NONE
-
- *Check your AUTOEXEC.BAT on the hard drive for
- the SET BLASTER and SET SOUND parameters.
-
-
- BOCA SOUND EXPRESS
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1 T5
-
- CONFIG.SYS
- DEVICE=C:\SE1440\CSACMOD1.EXE
-
-
- BREVE TECHNOLOGIES
- AUTOEXEC.BAT
- C:\BRV16F\DOSDRV\INIT16
- C:\BRV16F\DOSDRV\MIXER
-
- CONFIG.SYS
- NONE
-
-
- CRYSTAL CLEAR WAVE TABLE BY CRYSTAL LAKE
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1 T5
- C:\CCLEAR\CSACMAX1.COM*
- C:\CCLEAR\CSACHMX1.COM**
-
- CONFIG.SYS
- DEVICE=C:\CCLEAR\CSAMOD1.EXE -S***
-
- *Enables Soundblaster compatibility.
- **Add /ON to enable Soundblaster compatibility, /OFF to disable it.
- ***Use -S for Soundblaster mode and -W for Windows Sound System mode.
-
-
- DIAMOND
- AUTOEXEC.BAT
- SET BLASTER=*
- SET SOUND16=C:\DIAMOND
- C:\DIAMOND\SNDINIT /B**
-
- CONFIG.SYS
- NONE
-
- *Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.
- **Use /C for Soundblaster mode and /B for Microsoft Sound System mode.
-
-
- DIAMOND LX
- AUTOEXEC.BAT
- SET SOUND=C:\SONIC
- SET BLASTER=A220 I5 D1 T5
- C:\SONIC\MZTVOL.EXE
- C:\SONIC\MZTINIT WSS*
- C:\SONIC\MTZINIT.SYS
-
- CONFIG.SYS
- NONE
-
- *Use WSS for Windows Sound System mode and SB for Soundblaster mode.
-
-
- DSP16
- AUTOEXEC.BAT
- SET BLASTER=*
-
- CONFIG.SYS
- NONE
-
- *Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.
-
-
- ENSONIQ SOUNDSCAPE - Common on Gateways
- Driver version 1.10 dated 11/31/94
- AUTOEXEC.BAT
- SET BLASTER=A220 Ixx Dx
- SET SNDSCAPE=C:\SNDSCAPE
- C:\SNDSCAPE\SSINIT FM*
- C:\SNDSCAPE\VSB_EMM.COM**
-
- CONFIG.SYS
- DEVICE=C:\DOS\EMM386.EXE***
-
- *Use FM for FM synth, GM for General MIDI and MT32 for Roland MT32 emulation.
- **Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
- ***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT
-
-
- ENSOMIQ SOUNDSCAPE - Common on Gateways
- Driver version 1.20.02 dated 12/19/94
- AUTOEXEC.BAT
- SET BLASTER=A220 Ixx Dx
- SET SNDSCAPE=C:\SNDSCAPE
- C:\SNDSCAPE\SSINIT /I*
- C:\SNDSCAPE\VSB_EMM.COM**
-
- CONFIG.SYS
- DEVICE=C:\DOS\EMM386.EXE***
-
- */I enables FM synth and General MIDI emulation.
- Run MT32.EXE to enable Roland MT32 emulation.
- **Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
- ***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT
-
-
- ESS AUDIO DRIVE - Common on Compaqs
- AUTOEXEC.BAT
- NONE
-
- CONFIG.SYS
- DEVICE=C:\CPQDOS\VOLCTRL.EXE*
- DEVICE=C:\PCAUDIO\VOLCTRL.EXE**
-
- *Loads the DOS mixer. <Ctrl/Right Shift> turns up the volume, <Ctrl/Left Shift>
- turns it down.
- **Necessary to load Windows mixer.
-
-
- FORTE 16 - Common on Packard Bells
- AUTOEXEC.BAT
- SET BLASTER=*
- SET GALAXY=*
- SET SOUND=C:\FORTE16
- C:\FORTE16\UTILITY\EMUTSR
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for these settings.
- **Enables the Soundblaster emulation.
-
-
- FUSION 16
- AUTOEXEC.BAT
- SET BLASTER=*
-
- CONFIG.SYS
- DEVICE=C:\SPECTRUM\MVSOUND.SYS D: Q:**
-
- *Check the AUTOEXEC.BAT on your hard drive for these settings.
- **D: is the DMA channel and Q: is the IRQ setting
-
-
- GALANT
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- NONE
-
-
- GALAXY - See Multi-Media Pro 16
-
-
- GATEWAY 2000 AUDIO DRIVE
- AUTOEXEC.BAT
- C:\G2KAUDIO\UTILITY\GWBVOL
- SET BLASTER=A220 I5 D1 T5
- SET SOUND=C:\G2KAUDIO
-
- CONFIG.SYS
- NONE
-
- This sound card will autoconfigure itself to Soundblaster or Microsoft
- Sound System mode.
-
-
- GOLDEN SOUND BY TOPEK
- AUTOEXEC.BAT
- C:\GS16\GS-ENV PC:\GS16ES
-
- CONFIG.SYS
- NONE
-
-
- GRAVIS ULTRASOUND OR GRAVIS ACE
- AUTOEXEC.BAT
- SET ULTRASND=*
- SET ULTRADIR=*
- C:\ULTRASND\ULTRINIT
- SBOS.BAT**
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for complete SET lines for the GUS.
- **The SBOS.BAT line must be loaded to enable the card's Soundblaster
- emulation. This line is not needed for the ACE.
-
-
- IBM PS/1
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- NONE
-
-
- ISP 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET ISP16=C:\ISP16
- C:\ISP16\ISPINIT /B/M*
-
- CONFIG.SYS
- NONE
- *Use /B switch for SB mode
- *Use /M switch for Microsoft Sound System mode
-
-
-
- JAZZ 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\JAZZ\JAZZ.SYS D:* Q:*
-
- *D: DMA CHANNEL.
- *Q: IRQ SETTING.
- Specific values and directories may change
-
-
-
- MAD 16
- AUTOEXEC.BAT
- SET MAD16=C:\MAD16
- SET BLASTER=A220 I5 D1
- C:\MAD16\M16INIT /B /M*
-
- CONFIG.SYS
- NONE
-
- *Use /B switch for Soundblaster mode. Use /M switch for Microsoft Sound
- System Mode
-
-
-
- MAGIC S20 - Common on Acers
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET SOUND16=C:\MAGICS20
- C:\MAGICS20\SNDINIT /B /M*
-
- CONFIG.SYS
- NONE
-
- *Use /B switch for Soundblaster mode. Use /M switch for Microsoft Sound
- System Mode
-
-
-
- MAGITEC GREEN 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- NONE
-
-
-
- MEDIA CONCEPT
- AUTOEXEC.BAT
- SET MC=C:\MC
-
- CONFIG.SYS
- NONE
-
-
-
- MEDIA VISION DELUXE
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- C:\MEDVSN\VBEAI.COM
-
- CONFIG.SYS
- DEVICE=C:\MEDVSN\PROS.SYS
-
-
-
- MEDIA VISION PREMIUM 3D SCSI2
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\MEDVSN\PA3D.SYS
- DEVICE=MINI406A.SYS
-
-
-
- MMCD16W
- AUTOEXEC.BAT
- SET BLASTER=*
- SET SOUND=C:\MMCD16W
- SET GALAXY=*
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT for the SET BLASTER and SET GALAXY parameters
-
-
-
- MONTE CARLO BY TURTLE BEACH
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- C:\MCARLO\MCHKMIX
-
- CONFIG.SYS
- DEVICE=C:\MCARLO\MCMODE -S -W*
-
- *Use -S switch for SB mode
- *Use -W switch for Microsoft Sound System Mode
-
-
-
- MOZART SOUND CARD Common on Canons
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET SOUND=C:\MOZART
- C:\MOZART\MTZVOL.EXE
-
- CONFIG.SYS
- DEVICE=C:\MOZART\MZTINIT.SYS WSS /530*
-
- *WSS /530 Puts the card into WSS mode port 530
-
-
-
- MULTI-MEDIA PRO 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET GALAXY=*
- SET SOUND=C:\MMP16P
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the full SET GALAXY line.
-
-
-
- MW WAVE - Common on IBM Thinkpads
- AUTOEXEC.BAT
- SET BLASTER=
- SET MWPATH=C:\MWD\MANAGER;C:\MWD\MWGAMES*
- SET MWROOT=C:\MWD
- MWGAMES=ON**
-
- CONFIG.SYS
- NONE
-
- *This is all one line.
- **ON turns on Soundblaster emulation and OFF turns it off.
-
-
-
- ORCHID GAMEWAVE
- AUTOEXEC.BAT
- SET BLASTER=*
- SET SOUND=*
- C:\GW32\GW32.EXE
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
- SET BLASTER lines.
-
-
-
- ORCHID SOUNDWAVE
- AUTOEXEC.BAT
- SET BLASTER=*
- SET SOUND=*
- C:\SW32\SW32.EXE
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
- SET BLASTER lines.
-
-
-
- PHILLIPS
- AUTOEXEC.BAT
- NONE
-
- CONFIG.SYS
- NONE
-
-
-
- PRO AUDIO SPECTRUM 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\SPECTRUM\MVSOUND.SYS D:*Q:*
-
- *D: DMA CHANNEL. Q: IRQ SETTING.
- <DIR> may be PROAUDIO on older drivers.
-
-
-
- PRO SONIC
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\PROSONIC\PROSYS.SYS
-
-
-
- SC400
- AUTOEXEC.BAT
- SET SOUND=C:\SC400
- SET BLASTER=A220 I5 D1
- C:\SC400\UTILITY\SNDINIT /B
-
- CONFIG.SYS
- NONE
-
-
-
- SGBAS16
- AUTOEXEC.BAT
- SET BLASTER=*
- SET SOUND=C:\SGBAS16
- SET GALAXY=*
-
- CONFIG.SYS
- DEVICE=C:\SGBAS16\DRIVERS\EEPRO.SYS
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY and
- SET BLASTER lines.
-
-
-
- SOUNDBLASTER AWE 32
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET SOUND=C:\SB16
- C:\SB16\SB16SET /P/Q
- C:\SB16\DIAGNOSE /S*
- C:\SB16\AWEUTIL /S
-
- CONFIG.SYS
- DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
- DEVICE=C:\SB16\DRV\CTMMSYS.SYS**
-
- *May be SBCONFIG on older cards.
- **This line is only required to enable the sound card's CD-ROM interface.
-
-
-
- SOUNDBLASTER PRO
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET SOUND=C:\SBPRO*
- C:\SBPRO\SBP_SET*
-
- CONFIG.SYS
- NONE
-
- *On newer cards the drivers and such may look like
- the SB16 except loading out of a different directory.
-
-
-
- SOUNDBLASTER 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1 H5 T6
- SET SOUND=C:\SB16
- SET MIDI=SYNTH:1 MAP:E
- C:\SB16\SB16SET*
- C:\SB16\DIAGNOSE /S**
-
- CONFIG.SYS
- DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
- DEVICE=C:\SB16\DRV\CTMMSYS.SYS***
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SB16SET line.
-
-
-
-
- SOUND EXPRESSION BY BOCA
- AUTOEXEC.BAT
- SET BLASTER=
- C:\CE1440\CSACMAX1.COM*
- C:\CE1440\CSACHMX1.COM**
-
- CONFIG.SYS
- DEVICE=C:\SE1440\CSACMOD1.EXE -S -W***
-
- *Enables Soundblaster compatibility.
- **/ON turns on Soundblaster compatibility, /OFF turns it off.
- ***-S for Soundblaster mode and -W for Windows Sound System mode.
-
-
-
-
- SOUND EZ - See Mad 16
-
-
-
- SOUND FX PLUS
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SOUND=C:\MMSUP
-
- CONFIG.SYS
- NONE
-
-
-
-
- SOUNDMAND BY LOGITECH
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
-
- CONFIG.SYS
- DEVICE=C:\SOUNDMAN\MVSOUND.SYS
-
-
-
-
- SOUND 16A - Common on Packard Bells 1 OF 2**
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET GALAXY=*
- C:\SOUND16A\UTILITY\SETMODE /MSS**
- SET SOUND16=C:\SOUND16A
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
- **Use /SB switch for SB mode. Use /MSS switch for Microsoft Sound System Mode.
-
-
-
-
- SOUND 16A - Common on Packard Bells 2 OF 2**
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET GALAXY=*
- C:\AUDIO\SNDINIT.EXE /B**
- SET SOUND16=C:\AUDIO
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
- **Use /B switch for SB mode
- **Use /M switch for Microsoft Sound System Mode
-
-
-
-
- SOUND 144 - Common on Packard Bells
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET GALAXY=*
- SET SOUND=SOUND144
- C:\SOUND144\UTILITY\SETMODE /SBP**
-
- CONFIG.SYS
- NONE
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
- **Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.
-
-
-
-
- STRAUSS
- AUTOEXEC.BAT
- NONE
-
- CONFIG.SYS
- NONE
-
-
-
-
-
- TROPEZ BY TURTLE BEACH
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- C:\TROPEZ\DOSAPPS\SETUPSND*
- C:\TROPEZ\DOSAPPS\TZMODE -S*
-
- CONFIG.SYS
- DEVICE=C:\TROPEZ\DOSAPPS\TZMODE**
-
- *Windows will disable these lines, so they will need to be run again
- if Windows is started and shut down. Use -S for Soundblaster mode and -W
- for Windows Sound System mode on the TZMODE line.
- **This line is necessary if the sound card is also
- acting as the CD-ROM controller.
-
-
-
-
- VIBRA 16
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1 H5 T6
- SET SOUND=C:\VIBRA16
- SET MIDI=*
- C:\VIBRA16\DIAGNOSE /S**
- C:\VIBRA16\MIXERSET /P/Q
-
- CONFIG.SYS
- DEVICE=C:\VIBRA16\DRV\VIBRA16.SYS
- DEVICE=C:\VIBRA16\DRV\CTMMSYS.SYS
-
- *Check the AUTOEXEC.BAT on your hard drive for the complete SET MIDI line.
- **Older cards may use SBCONFIG instead of DIAGNOSE.
-
-
-
-
- VOYETRA SOUND
- AUTOEXEC.BAT
- SET BLASTER=A220 I5 D1
- SET ISP16=ISP16*
- C:\ISP16\ISPINIT /B
-
- CONFIG.SYS
- NONE
-
- *May be SET ISP16=VOYETRA
-
-
-
-
- WAVERIDER BY AZTECH
- AUTOEXEC.BAT
- SET BLASTER=
- SET SOUND=C:\WAVRIDER
- SET GALAXY=
- C:\WAVRIDER\DRIVERS\WAVERIDE.EXE
- C:\WAVRIDER\SETMODE /SBP*
-
- CONFIG.SYS
- NONE
-
- *Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.
-
-
-