PC PowerPlay 11/PCPP11.iso/faqs/sq6faq.doc

Text File | 1995-07-20 | 46.1 KB | 1,309 lines

SPACE QUEST VI TECHNICAL FAQ
revised 7/19/95

Sierra Technical Support          PHONE:  [phone]
PO Box 85006                      FAX:    [phone]
Bellevue, WA  98015-8506          BBS:    [phone]


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 - MEMORY TROUBLESHOOTING
SECTION 5 - COMMON GAME PROBLEMS (WINDOWS)
SECTION 6 - COMMON GAME PROBLEMS (DOS)
SECTION 7 - SOUND ISSUES AND SOUND CARD SETTINGS
SECTION 8 - IF YOU STILL HAVE PROBLEMS...
SECTION 9 - SPACE QUEST VI BOOT DISK INSTRUCTIONS
SECTION 10 - SOUND CARD DRIVER INFORMATION

SECTION 1 - HARDWARE REQUIREMENTS

REQUIRED
486SX/25
8MB RAM
2X CD ROM
5MB hard drive space  (compressed 10MB) for minimal
install
Sound Card with DAC
MS-DOS 5.0 or higher
SVGA (640 x 480 x 256 colors)
Mouse
Windows 3.1 or higher

RECOMMENDED FOR BEST PERFORMANCE
Pentium
4X CD ROM
45 MB hard drive space for full install

SECTION 2 - INSTALLATION PROCEDURES

WINDOWS
Insert 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 \SETUP.  Ex: D:\SETUP.

After performing the hardware tests, click on INSTALL to install Space
Quest VI.  If you fail any of the tests, see Section 3, Common
Installation Problems


DOS
Insert the CD into the appropriate drive.  Type the letter of the drive
followed by a colon, and press ENTER.
Ex:  D:.  Type INSTALL and proceed to the INSTALLATION
CHOICES screen.  Be sure that the correct choices have been made for
MUSIC and AUDIO.  Choose ACCEPT THESE CHOICES AND
INSTALL and follow the on-screen prompts.


SECTION 3 - COMMON INSTALLATION PROBLEMS

WINDOWS
Problem:  Your computer fails the Sound Card test; you cannot hear the
voice and/or fanfare in the Wave and MIDI tests.
Solution:  Your sound card is incorrectly configured for Windows.  See
Section 7, Sound Issues and Sound Card Settings for information on
setting up your sound card.

Problem:  Your computer fails the Display test; you get a message
saying "Your video display supports 16 colors...".
Solution:  Sierra's Windows games require that Windows is running in
256 color mode.  Even though your monitor and video card may be
capable of displaying 256 colors, Windows may not be set up to use this
resolution.  To check, double-click on Windows Setup in the Main
program group.  If the Display line reads "VGA" or "16 color", you will
need to change to a driver that supports 256 colors.  ("VGA" is a default
Windows video driver that only supports 16 colors and will not work
with Sierra's Windows games.)  To change video drivers, select Options,
then Change System Settings.  Open the Display box to see the list of
video drivers that are currently available.   You should check your video
card documentation for information on what 256 color driver to select.
Do not use more than 256 colors with Space Quest VI.  Although it
will run, you will not be able to view some of the visual effects in the
game.

Warning: Be careful when changing video drivers!  If you choose one
that is not designed for your particular video card, Windows will not
display properly.  If this occurs, change to your Windows directory,
type: SETUP, and choose the "VGA" driver again.  You should then
contact your video card manufacturer for the correct driver.

Problem:  Your computer fails the Memory test in Windows; you get a
message stating you do not have enough memory to run Space Quest VI.
Solution:  First, create a Space Quest VI boot disk using the
instructions at the end of this document.  Reboot the system using the
boot disk, then create a clean Windows environment.  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.  If you have sound-related Windows programs
installed (IconHearIt, SoundBits, etc.), make sure they are disabled
before starting the game.  Also, turn off your Wallpaper in Desktop in
Control Panel.  Wallpaper can sometimes take up a considerable amount
of memory.  These steps should give you enough memory to run the
game.  If they do not, please refer to Section 4,
Windows Memory Troubleshooting.

Problem: Space Quest VI icon was not created during game installation.
Sierra group and other icons are created fine.
Solution:  This is usually caused by an alternate Windows desktop, like
Norton Desktop, PC Tools or Tabworks. You must disable these
desktops before installing the game.   The easiest way to do this is to
type PATH=C:\WINDOWS at the DOS prompt, then start Windows.
This should start Windows with Program Manager as the desktop.
When you are back in Windows, reinstall the game.  The icons will be
created normally.   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: Space Quest VI
has not been tested under any alternate desktop environment, therefore
Sierra cannot guarantee that the game will function properly under these
desktops.

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.
Solution:  The dots indicate the hardware detection portion of the
installation program.  You can bypass the hardware detection (and
therefore the lockup) by typing INSTALL /M.  If this entry doesn't
work, try INSTALL /F.  One of these entries should get you past the
lockup.


SECTION 4 -  WINDOWS MEMORY
TROUBLESHOOTING

If you are having trouble getting enough memory to run Space Quest VI,
these steps should help you.

Create a Boot Disk:  Sierra has included a boot disk maker with Space
Quest VI.  You can run the boot disk creator by double-clicking on the
boot disk creator icon in the SIERRA program group.   In addition,
instructions for creating a boot disk manually are included at the end of
this troubleshooting guide.

Disable SMARTDRV:  Space Quest VI will often run better with
SMARTDRV disabled on systems with 8 mb of RAM.  Making a boot
disk will disable SMARTDRV.  Boot disk instructions for Space Quest
VI are at the end of this document.

Disable any hardware cache:  Some CD ROM drives, such as the Teac
4x, install their own cache.  This cache may use as much as 2 MB of
memory.  Consult with the manufacturer if you do not know how to
disable this cache.

Create a Clean Windows Environment:  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, Tabworks, etc.), use plain Program
Manager instead.   If you have sound-related Windows programs
installed (IconHearIt, SoundBits, etc.), make sure they are disabled
before starting the game.  Also, turn off your Wallpaper in Desktop in
Control Panel.  Wallpaper can sometimes take up a considerable amount
of memory.

Turn Off 32-Bit File Accessing: Windows for Workgroups and
Windows 3.11 include a setting for 32-bit File Access in the Virtual
Memory settings.  This should be turned off.  If you are using Windows
3.1, you will see 32-bit Disk Access instead.  Leave this on.

Start Windows for Workgroups with WIN/N.  This will start WFW
without the network drivers.  This will help if the total memory is very
close, but not quite enough.


SECTION 5 - COMMON GAME PROBLEMS (WINDOWS)

Problem:  When game starts, it displays a black screen or throws you
out to DOS.  This can also happen randomly during the game.
Solution:  First, create a boot disk.  Running the game from the boot
disk will usually correct this problem.  You can create a boot disk
automatically using the boot disk maker in the Sierra group, or manually
using the boot disk instructions in Section 9. In addition, the problem
may be caused by outdated or incompatible video or sound card drivers.
You should check with your video and sound card manufacturers to
make sure you have the latest versions of their drivers.

Problem: "General Protection Fault caused by GROWSTUB in
POINTER.DLL" when game starts.
Solution:  This is caused by a Microsoft mouse driver version 9.01
GROWSTUB component. One of these three suggestions should correct
the problem.

1. Remove POINTER.EXE from the load= line in the file WIN.INI and
then restart Windows.

2. Download the file HD1061.EXE from the Microsoft BBS at (206)
936-6735.  This file is self-extracting.  Run "HD1061" and follow the
instructions in the newly created README.TXT file.

3. Upgrade to the Microsoft Mouse IntelliPoint software version 1.0.
For information about obtaining this upgrade, call the Microsoft Sales
Information Center at [phone].  Microsoft charges a fee for this
upgrade.

Problem: "General Protection Fault in Module ... " The module name
will vary.
Solution:  A General Protection Fault (GPF) in a module other than
POINTER.DLL 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.   If you have sound-related Windows programs
installed (IconHearIt, SoundBits, etc.), disable these before starting the
game.

A Windows boot disk also helps with GPFs.  Instructions for creating a
boot disk are at the end of this document.  In addition, GPFs are often
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: "EMM386 Error 06 ... " The error number may vary.
Solution:  This is caused by a memory conflict.  Running the game from
the boot disk will usually correct this problem.  Please see "Create a
Boot Disk" and "Create a Clean Windows Environment" under Section
4, Memory Troubleshooting.

Problem: "The instruction at (memory address) referenced memory at
(memory address).  The memory could not be read from".
Solution:  This is called a "bad pointer".  It usually happens if you don't
have the latest SoundBlaster 16 drivers for Windows. Download the file
SB16UP.EXE from the Creative Labs BBS at [phone].  This
file is self-extracting.  Run "SB16UP" and follow the instructions in the
newly created README.TXT file.  If you do not have a modem, you
can contact Creative Labs at 405-742-6622 and request the latest
SoundBlaster 16 Windows drivers.  If you do not have a SoundBlaster
16 card, or are still receiving the error after updating the drivers, the
message indicates a memory conflict.  See Section 4, Memory
Troubleshooting for information on resolving memory conflicts.

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

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

This error can also be caused by a defective CD.  The easiest way to get
a new CD is to exchange it at the store where you bought the game.  If
they are unable to exchange it for you, you can contact Sierra Customer
Service at 1-800-SIERRA5 to arrange a CD replacement.

Problem:  Space Quest VI runs slowly on your computer.
Solution:  Make a boot disk with the Boot Disk maker by double-
clicking on the Boot Disk icon in the Sierra Group.  Or you can create a
boot disk manually by following the instructions at the end of this
document.  In addition, with Windows for Workgroups and Windows
3.1.1, we recommend NOT using 32-bit file access (which can be
changed in your Virtual Memory settings dialog box).  Also, make sure
you have a permanent swap file of 6-8 MEGS.   See "Check the Swap
File" under Section 4, Memory Troubleshooting for complete
instructions on changing the swap file.  Try adding Smartdrive to your
boot disk.  Smartdrive is a disk cache that will speed up CD ROM
access.  Edit the AUTOEXEC.BAT on the boot disk and add the
following line after the line that has MSCDEX.EXE:

C:\DOS\SMARTDRV.EXE 512

Do not raise the number 512 if you have less than 10mb of RAM.  With
10mb or more, you can raise this to 2048.

Problem:  "Error 105: Attempt to load wrong type" or "Error 99: Error
loading resource 10005".  Error numbers may vary.
Solution:  This type of error is usually caused by corrupted program
files or a bad installation of the game.  To correct this, delete the game
and run CHKDSK /F or SCANDISK to detect and correct any hard
drive errors.  Then, boot up with a Space Quest VI boot disk and
reinstall the game in a clean Windows environment.  Please see "Create
a Boot Disk" and "Create a Clean Windows Environment" under Section
4, Windows Memory Troubleshooting for complete steps.

Problem:  The game runs fine until you play Djurkwhad in Stooge
Fighter.  Then the speed slows to a crawl.
Solution:  This is the section of the game that requires the most
memory.  Running the game with a boot disk will usually correct the
problem. If you are using Smartdrive to cache your CD ROM and hard
drive, lower the cache to 512k.

Problem:  Made a boot disk, but now Windows won't run.
Solution:  Edit the CONFIG.SYS in the boot disk.  On some systems
the boot disk maker may fail to find some items.  Be sure there is a line
that loads HIMEM.SYS and one that loads your CD ROM drive.  Refer
to the instructions in Section 9 for an example of a boot disk
CONFIG.SYS .

Problem:  Error 47:  Not an Object, when clicking the Buckazoids on
the cash drawer in Boot Liquor.
Solution:  Don't do that.  Click the Buckazoids on the man behind the
counter instead.


Problem:  Error message "Robot Source 410 Script 64960/$306"
Solution:  Check the RESOURCE.WIN file.  There will be several lines
missing, most notably, the path to the Robots directory on the CD ROM.
The RESOURCE.WIN should look like this:

     [Windows]
     title=Space Quest 6: Roger Wilco in The Spinal Frontier
     wwidth=640
     wheight=480
     allowresize=false
     sciMinK=2100
     sciMaxK=5000
     winG=false
     confirmmidi=true
     confirmdac=true
     audioSize=60k
     dacSize=16384
     VideoSpeed=300
     cacheSize1=500
     cacheSize2=600
     movieDir=D:\movies
     robot=D:\robots
     patchDir=C:\SIERRA\SQ6;D:\
     resMap=D:\;C:\SIERRA\SQ6
     synthtype=basesynth


If you don't see your question listed in this document:  Most
difficulties with Space Quest VI, including lockups and Fatal or Panic
errors can be resolved by simply running the game with a boot disk and
in a clean Windows environment.  Please see "Create a Boot Disk" and
"Create a Clean Windows Environment" under Section 4, Windows
Memory Troubleshooting.  Incompatible or outdated sound card and
video drivers can also cause lockups and errors.  You should make sure
that you are using the latest versions of your sound card and video
drivers.  Contact your sound and video card manufacturers to obtain the
latest drivers.


SECTION 6 - COMMON GAME PROBLEMS (DOS)

Problem:  You get an "insufficient memory" message when starting the
game.
Solution:  Rerun the INSTALL program, and go to the
INSTALLATION CHOICES screen.  Select the option to MAKE A
BOOTABLE FLOPPY DISK.  When finished, reboot the system with
the boot disk in the A: drive.

Problem:  Made a boot disk, but now there are error messages, such as
"Can't find SIERRA.ERR."
Solution:  Edit the CONFIG.SYS in the boot disk.  On some systems
the boot disk maker may fail to find some items.  Be sure there is a line
that loads your CD ROM drive.  Refer to the boot disk instructions in
section 9 for an example of a boot disk CONFIG.SYS.

Problem:  The game runs fine until you play Djurkwhad in Stooge
Fighter.  Then the speed slows to a crawl.
Solution:  This is the section of the game that requires the most
memory.  Make a boot disk.  If you are using Smartdrive to cache your
CD ROM and hard drive, lower the cache to 512k.


Problem:  Space Quest VI runs slowly on your computer.
Solution:  Make a boot disk with the Boot Disk maker by double-
clicking on the Boot Disk icon in the Sierra Group.  Or you can create a
boot disk manually by following the instructions at the end of this
document.  Try adding Smartdrive to your boot disk.  Smartdrive is a
disk cache that will speed up CD ROM access.  Edit the
AUTOEXEC.BAT on the boot disk and add the following line after the
line that has MSCDEX.EXE:

C:\DOS\SMARTDRV.EXE 512

Do not raise the number 512 if you have less than 10mb of RAM.  With
10mb or more, you can raise this to 2048.

Problem:  Error 47:  Not an Object, when clicking the Buckazoids on
the cash drawer in Boot Liquor.
Solution:  Don't do that.  Click the Buckazoids on the man behind the
counter instead.

Problem:  Error 44:  Bad Opcode.
Solution:  This usually occurs when playing in DOS using a
SoundBlaster AWE32.  The AWE32 does not work in General Midi
mode with DOS extenders unless you have the latest driver.  Either play
in Windows, play in DOS but in SoundBlaster mode rather than General
Midi, or contact Creative Labs to obtain the newer drivers.



SECTION 7 - SOUND CARD CONFIGURATION AND SOUND ISSUES

CONFIGURING YOUR SOUND CARD FOR DOS

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 ProAudio card,
the best settings are I/O 220, DMA 3 and IRQ 5 for the ProAudio
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.

Many sound cards require special drivers or initialization lines be loaded
in the AUTOEXEC.BAT and/or the CONFIG.SYS.  Section 10 - Sound
Card Driver Information lists many common sound cards and their
AUTOEXEC.BAT and CONFIG.SYS requirement.  You should check
to see if your sound card is in this list.


CONFIGURING YOUR SOUND CARD FOR WINDOWS

The SoundBlaster 16, Pro Audio Spectrum 16, and compatibles support
"Extended FM" in Windows.  SoundBlaster Pro, SoundBlaster 2.0 and
compatibles, use "Base FM" in Windows.  The Extended and Base FM
settings are defined in the MIDI Mapper.  If your MIDI Mapper is
configured incorrectly, you may hear just music and no voice, or vice
versa.  The following MIDI Mapper instructions cover the most
common types of sound card setups.  If you are using a sound card that
is not listed here, please consult your sound card documentation for the
correct MIDI Mapper setup.

SoundBlaster 16, ProAudio Spectrum 16 and compatibles:  Click on
Main, then Control Panel and then on MIDI Mapper.  If you have an
option called Extended FM or something similar, choose it.  Close MIDI
Mapper and run Space Quest VI.  If you don't have this option, you will
need to make a new MIDI Mapper setup.  From the MIDI Mapper
screen, click on New.  Enter a name such as "Extended 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.  Choose the FM choice
or Synthesizer choice.  Do this for ports 1 through 9.  Then, make sure
that the SRC Channel values match the Dest Channel values (i.e. if the
SRC Channel is 10, the Dest Channel should be 10).  If they are
different, change the Dest Channel to match the SRC Channel by
clicking in the Dest Channel box and changing its value.  Click on OK
and close out the MIDI Mapper.  The music and voices should now play
correctly in Space Quest VI.  For further information on the correct
MIDI Mapper configuration for your sound card, please contact your
sound card manufacturer.

SoundBlaster Pro and compatibles:  Click on Main, then Control
Panel and then on MIDI Mapper.  If you have an option called Basic
FM or something similar, choose it.  Close MIDI Mapper and run Space
Quest VI.  If you don't have a Basic FM option you will need to make a
new setup.  From the MIDI Mapper screen, click on New.  Enter a name
such as "Basic 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 13th row.  Now click on the small arrow that appears on the right of
this box.  Choose the FM choice or Synthesizer choice.  Do this for
ports 13, 14 , 15, and 16.  Click on OK and close out the MIDI Mapper.
The music and voices should now play correctly in Space Quest VI.  For
further information on the correct MIDI Mapper configuration for your
sound card, please contact your sound card manufacturer.

Problem:  You get an "Error 29:  Unable to Initialize Sound Card" in
DOS.  This seems to happen on some systems with SoundBlaster sound
cards.
Solution:  There are no reported incidences in Windows.  Try running
the Windows version of the game.  We are currently investigating this
error in the DOS version of the game, but at this time, we have no work-
around.

Problem:  Playing in DOS with a SoundBlaster sound card, the game
locks-up during the intro.
Solution:  This is related to the error 29 above.  This will happen to
some SoundBlasters with older DSP versions.  Play in Windows instead
of DOS.

Problem:  The speech is full of static in Stooge Fighter.
Solution:  The .WAV files used in Stooge Fighter have been enhanced
with extra bass response.  Some sound cards or speakers may not handle
this well.  Most powered speakers have a bass control which can be
turned down.

Problem: The speech breaks up or hesitates in Space Quest VI in
Windows.
Solution:  Each speech sample or recording needs to be loaded into
memory before it can be played.  By reducing the buffer size, you will
cause the CD to actually play the speech segments faster, because it
does not have to fill a large buffer area.  The buffer size is set in the
C:\SIERRA\SQ6\RESOURCE.WIN text file.  Edit this file and change
the dacSize" line to dacSize =15360.

Problem:  You get a "Divide by Zero" error, using the Gravis Ultra
Sound in Windows.
Solution:  You must load the GUS patches before running the game.
Open the Accessories group and choose Media Player.  Click on Device,
and select Midi Sequencer.  Load the correct GUS patch file.  It must
match the on-board memory of your GUS.  For example, if you have
512k on-board memory, you would load the file LOAD512.MID.
Playing this file will load the patches and prevent the error message.

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.

Problem:  The last note played before a screen change is "stuck".
Solution:  This is a result of incorrect MIDI Mapper configuration.  See
the above information on configuring your MIDI Mapper.  Be very
careful that the SRC and Dest Channels in your MIDI Mapper match.
Most sound cards experiencing this problem will run better if the game
is set to "base midi" support instead of "extended midi".

If you are still experiencing sound problems, you may need to update
your sound drivers.  If you do not have the current Windows drivers for
your sound device,  you may need to contact the manufacturer of your
sound device or your local hardware supplier for an updated set of
sound drivers.  Check your Windows documentation or your sound
device documentation for full instructions on updating your sound
drivers.

Problem:  During the introduction there are problems with the speech.
It is sometimes doubled, or stutters.  DOS version.
Solution:  Make sure there is adequate memory available.  Even if there
is enough memory to start the game, this problem may occur if the
computer is running slow.  More memory is the best way to speed up the
game.  Use a boot disk, and try adding Smartdrive set to 512k.

Problem:  In DOS, using a Reveal or Aztech labs sound card, the music
is fine but the speech is barely audible.
Solution:  The chip set used to emulate the SoundBlaster digital to
analog conversion is not 100% compatible with the SoundBlaster driver
built-in to the game.  Install Space Quest VI into Windows, for full
sound.


SECTION 8 - IF YOU STILL HAVE PROBLEMS...

If you continue to experience any problems with Space Quest VI, or if
you have any questions, our Technical Support Department will be more
than 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 [phone] 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              [phone]
CompuServe        GO SIERRA
America Online        KEYWORD SIERRA


If you decide to write or fax, please provide the following information. This
will give us the information we need to help you as efficiently as possible.

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

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/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.)


SECTION 9 - BOOT DISK INSTRUCTIONS

The following boot disk instructions will work with both the DOS and
Windows versions of Space Quest VI.

Please read the entire instructions prior to starting at Step 1.  If you are
playing the Windows version of Space Quest VI, 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 this step if you are
playing the Windows version)
The DOS version of Space Quest VI requires a Microsoft compatible
mouse driver be loaded into memory before playing the game.  There are
two kinds of mouse drivers available: those that load in the
CONFIG.SYS file and those that load in the AUTOEXEC.BAT file.
CONFIG.SYS mouse drivers have an extension of .SYS (MOUSE.SYS)
and AUTOEXEC.BAT drivers have either a .COM or .EXE extension
(MOUSE.COM, MOUSE.EXE).  You must load at least one of these
drivers, but it is not necessary to load them all.

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

DIR MOUSE* /S <ENTER>

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

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

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

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

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

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

STEP 3
LOCATING THE CD ROM DEVICE DRIVER
The CD ROM drive requires a device driver loaded in the
CONFIG.SYS file.  This driver must be loaded correctly or you will be
unable to access your CD ROM drive. To make sure that the device
driver loads correctly on the boot disk, look at the CONFIG.SYS on the
hard drive and copy the driver line from there.  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" and 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 ROM 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 entire line following the drive
letter.  Include the full drive and path to the MSCDEX file and leave out
any LH or LOADHIGH commands.  For example, any of the above
lines should appear as follows:

C:\DOS\MSCDEX /D:MSCD001

This is how the line will appear in the AUTOEXEC.BAT on your boot
disk.

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:  SoundBlaster 16,
MAD16 and the Aria 16.

At the end of these Boot Disk Instructions, you will find a section
labeled "Sound Cards".  These tables contain the sound card lines for
many common sound cards.  Check to see if your sound card is on the
list.  If it is, 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 be loading 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>
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:

DEVICE=A:\MOUSE.SYS <ENTER>

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

A:\MOUSE.EXE <ENTER>

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 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> <DELETE> key sequence
on your keyboard.  Follow the instructions in the game manual to start
the game.

SOUND CARDS

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

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