KING'S QUEST VII TECHNICAL FAQ
revised 6/14/95


Sierra Technical Support      Phone: (206) 644-4343
PO Box 85006                  FAX:    (206) 644-7697
Bellevue, WA  98015-8506      BBS:(206) 644-0112


Sierra Technical Support provides this documentation as a reference to Sierra 
customers using Sierra software products.  Sierra Technical Support makes 
reasonable efforts to ensure that the information contained in this 
documentation is accurate.  However, Sierra makes no warranty, either express 
or implied, as to the accuracy, effectiveness, or completeness of the information 
contained in this documentation.

SIERRA ON-LINE, INC. DOES NOT WARRANTY OR PROMISE THAT 
THE INFORMATION HEREIN WILL WORK WITH ANY OR ALL 
COMPUTER SYSTEMS.  SIERRA DOES NOT ASSUME ANY LIABILITY, 
EITHER INCIDENTAL OR CONSEQUENTIAL, FOR THE USE OF THE 
INFORMATION HEREIN, INCLUDING ANY AND ALL DAMAGE TO OR 
LOST USE OF COMPUTER HARDWARE OR SOFTWARE PRODUCTS, 
LOSS OF WARRANTIES, OR LOST DATA BY THE CUSTOMER OR ANY 
THIRD PARTY.  NO ORAL OR WRITTEN INFORMATION OR ADVICE 
GIVEN BY SIERRA, ITS EMPLOYEES, DISTRIBUTORS, DEALER OR 
AGENTS SHALL CHANGE THE RESTRICTION OF LIABILITY OR 
CREATE ANY NEW WARRANTIES.  IN NO CASE SHALL SIERRA'S 
LIABILITY EXCEED THE PURCHASE PRICE OF THE SIERRA 
SOFTWARE PRODUCT.


IMPORTANT NOTE:  After the game shipped, we discovered some 
problems with version 1.1 of the program.  These problems show up as 
errors during installation, lockups and fatal errors during the game.  We 
have corrected these problems and currently have a new version of the 
game available.  To find out what version of the program you have, check 
the label on the floppy disk that was included with the game.  If it says 
'VER 1.1', you need the update.  If the floppy says 'VER 1.4' or you did 
not receive a floppy, you have the latest version and do not need the 
update.

Please fax or mail Customer Service the S/N number from the floppy disk 
or a photocopy of the floppy or CD, and a note indicating you would like 
a replacement for King's Quest VII.  Their address is Sierra Customer 
Service, PO Box 3404, Salinas, CA 93912.  Their fax number is 408-
644-2018.  Please include your name and mailing address so we send the 
new game to the right place!  If you have any questions regarding the 
exchange procedure, you can reach Sierra Customer Service at 1-800-
SIERRA5.



TABLE OF CONTENTS
SECTION 1 - HARDWARE REQUIREMENTS
SECTION 2 - INSTALLATION PROCEDURES
SECTION 3 - COMMON INSTALLATION PROBLEMS
SECTION 4 - MEMORY TROUBLESHOOTING
SECTION 5 - COMMON PROBLEMS
SECTION 6 - SOUND ISSUES AND SOUND CARD SETTINGS
SECTION 7 - OBTAINING A SIERRA PATCH DISK
SECTION 8 - BOOT DISK INSTRUCTIONS 
SECTION 9 - SOUND CARD DRIVER INFORMATION
SECTION 10 - IF YOU STILL HAVE PROBLEMS...



SECTION 1 - HARDWARE REQUIREMENTS

REQUIRED
386SX
4MB RAM
CD ROM drive
1MB hard drive space  (compressed 2MB)
MS-DOS 5.0 or higher
VGA (256 colors)
Mouse
Windows 3.1 or higher (King's Quest VII runs in Windows ONLY)
Sound Card with DAC

RECOMMENDED FOR BEST PERFORMANCE
486DX
8MB RAM
Double speed CD ROM




SECTION 2 - INSTALLATION PROCEDURES 

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.  

Click on TEST HARDWARE to perform the hardware checks to verify 
that your computer can run King's Quest VII.

If you fail any of the tests, see Section 3, Common Installation Problems

After performing the hardware tests, click on INSTALL to install King's 
Quest VII.



SECTION 3 - COMMON INSTALLATION PROBLEMS

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 is incorrectly configured for Windows.  See 
Section 6, 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.  

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; you get a message 
stating you do not have enough memory to run King's Quest 7.
SOLUTION:  First, create a King's Quest VII 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, Memory Troubleshooting. 

PROBLEM:  Game installation halts and displays a STOP message with a 
path and filename.  The only way out is to reboot the computer.
SOLUTION:  Take careful note of the path and filename.  Reboot the 
computer and change to the directory that the error message specified (for 
example, C:\WINDOWS\SYSTEM\WIN32S).  In that directory, type 
ATTRIB -R *.* then go back into Windows and reinstall the game. 

PROBLEM:  During installation you receive a message stating that 'WinG 
has encountered a problem with your video driver'.
SOLUTION:  This usually means that you need to update your Windows 
video drivers.  You should check with your video card manufacturer to 
obtain the latest version of their drivers.  You can also try running 
Windows in a different video resolution.  For example, if you are running 
in 1024x768x64k colors, try 800x600x256 colors. 

PROBLEM:  King's Quest VII 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:  King's Quest VII has 
not been tested under any alternate desktop environment, therefore Sierra 
cannot guarantee that the game will function properly under these 
desktops.



SECTION 4 - MEMORY TROUBLESHOOTING

Some game players have experienced difficulty getting enough memory to 
run King's Quest VII.  This usually occurs on computer systems with 4 
megabytes of RAM, but can happen on machines with more memory.  If 
you are having trouble starting the game because of memory problems or 
are receiving memory-related errors during the game, here is a list of 
troubleshooting steps to try.

Do Not Load WinG:  Follow these steps to make sure WinG is not 
activated

1. Edit the RESOURCE.WIN file and  make sure the following line 
appears:  

WING=FALSE

If this line does not appear, or if the WinG line is set to a TRUE value, 
WinG will be loaded.  This 
will take up 200K+ of memory and can cause memory problems. 

2.  Copy the file SIERRAW.EXE from the CD to the C:\SIERRA\KQ7 
directory. 

3.  Access the King's Quest 7 icon properties by pressing ALT-ENTER 
when the KQ7 icon is highlighted.  Change the Command Line to read:

C:\SIERRA\KQ7\SIERRAW.EXE C:\SIERRA\KQ7\RESOURCE.WIN

This line usually defaults to SIERRAWS.EXE; changing it to 
SIERRAW.EXE will force WIN-G not to load.

Lower SCIMinK Value:  Edit the RESOURCE.WIN file and lower the 
SCIMINK value to 1900.  Do not lower this line below 1900; values 
lower than 1900 will cause problems during the game.  NOTE - Lowering 
the SCIMINK to 1900 will force the CD drive to access more often, and 
will result in slightly slower game play, but may help solve memory 
problems. 

Check the Swap File: Establish a permanent swap file at about 6 MB.  
This will help free up memory.  Do not set the swap file too high, 6-8 MB 
permanent should be enough.   Follow these steps to access and change 
the Windows swap file. 

1. Close all Windows applications.

2. Open the 'Main' folder on your Windows desktop.

3. Double-click on the 'Control Panel' icon.

4. Double-click on the '386 Enhanced' icon.

5. Click on the 'Virtual Memory . . .' button.

6. Click on the 'Change>>' button.

7. Type '6000' in the 'New Size' selection box, under the 'New Settings' 
heading.

8. Select 'Permanent' from the 'Type' pull down combination box, if it is 
available. If 'Permanent' is not available, select 'Temporary'.

9. If '32-bit File Access' is checked, un-check it.  This should remain 
turned off.  If you have a '32-bit Disk Access' option, leave it checked.

10. Click the 'OK' button.

11. Click the 'Restart Now' button.

Windows will restart and take you back to the main Windows desktop. 

Create a Boot Disk:  Sierra has included a boot disk maker with King's 
Quest VII.   The Boot Disk Creator is the last option available in the 
Setup program.  You can run it manually 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:  King's Quest VII will often run faster with 
SMARTDRV disabled.  Making a boot disk will disable SMARTDRV.  
Boot disk instructions for King's Quest VII are at the end of this 
document. 

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. 

Windows for Workgroups v3.11: Because of Windows for Workgroups' 
memory requirements, you may experience trouble getting enough 
memory for the game if you have only 4 MB of RAM.  If you are using 
Windows for Workgroups, we highly recommend that you have at least 8 
MB of RAM on your computer. 

Update Win32s: King's Quest VII uses WinG, Microsoft's video 
accelerator, to improve speed performance within the game.  Microsoft 
has recently updated Win32s, a key element of the WinG drivers.  Version 
1.2 of Win32s may improve game performance and help eliminate random 
lockups, memory errors, or random reboots of the computer.  You can 
download this latest  version from the Microsoft BBS at (206) 936-6735.  
Download the file called PW1118.EXE from the Articles file area.  The 
file is also available on CompuServe.  Download the file WIN32S.ZIP 
from the PCEForum/Material location.



SECTION 5 - COMMON GAME PROBLEMS

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, make sure you have the latest version of the game.  To 
find out what version of the program you have, check the label on the 
floppy disk that was included with the game.  If it says 'VER 1.1', you 
need the update.  If the floppy says 'VER 1.4' or you did not receive a 
floppy, you have the latest version and do not need the update.  See the 
IMPORTANT NOTE on the first page of this document for information 
on obtaining the updated version.

If you have the latest version, the problem you are experiencing is 
probably 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.  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:  When you double-click on the KQ7 icon, the game displays the 
error 'The application is not a Windows NT executable'. 
SOLUTION:  This is usually caused by a conflict with a high-resolution bit 
map being used as Windows wallpaper.  Go into Desktop under Control 
Panel in the Mail program group and set Wallpaper to <none>.  This 
usually stops this error from occurring.  If this does not help you, then the 
problem is caused by a memory conflict, usually with WinG.  Follow the 
steps under 'Do not load WinG' in Section 4 - Memory Troubleshooting'. 

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 (800) 426-9400.  Microsoft charges a fee for this 
upgrade.

PROBLEM:  When starting the game you get a 'DOS Error 21' error 
message.
SOLUTION:  Follow these steps to change the game's executable from 
SIERRAWS.EXE to SIERRAW.EXE:

Copy the file SIERRAW.EXE from the CD to the C:\SIERRA\KQ7 
directory. 

Access the King's Quest 7 icon properties by pressing ALT-ENTER when 
the KQ7 icon is highlighted.  Change the Command Line to read:  
C:\SIERRA\KQ7\SIERRAW.EXE C:\SIERRA\KQ7\RESOURCE.WIN

This error may also occur when the game is unable to read data from the 
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: '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.), make sure they are disabled before starting 
the game.  

A Windows boot disk also helps with GPFs.  Instructions for creating a
boot disk are in Section 8.  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: '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:  'Application Error: C:\SIERRAWS.EXE...' When attempting 
to run the game.
SOLUTION:   If you are using Stacker 4.0, and have Windows 3.11, you 
may receive this error message when attempting to start the game.  This 
problem is caused by the IFSHLP.SYS driver.  To get around this error, 
simply remove the IFSHLP.SYS driver.  The easiest way to do this is to 
create a King's Quest VII boot disk.  You can use the automatic boot disk 
maker (double-click on Boot Disk in the Sierra Group) or create one 
manually by using the boot disk instructions included at the end of this 
document.

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 (405) 742-6660.  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 
probably 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:  Error message 'Panic. Error 76 - invalid handle 45' at game's 
title screen.
SOLUTION:  Your MIDI Mapper is probably set up incorrectly for the 
game.  See Section 6, Sound Issues for information on configuring your 
MIDI Mapper. 

PROBLEM:  When starting the game, you get 'EMM386 Error 6 - No XMS 
memory'.  
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.  

PROBLEM:  When starting the game, you get an error message 'Cannot 
load Win32 because paging is not enabled'. 
SOLUTION:  This is caused by a very small or nonexistent swap file.  Create 
a 6 MB permanent swap file.  See 'Check the Swap File' under Section 4, 
Memory Troubleshooting for complete instructions on changing the swap 
file settings.  

PROBLEM:   Game will not start and displays an error message indicating 
improper WIN32S installation.
SOLUTION:  First, delete the directory C:\WINDOWS\SYSTEM\WIN32S.  
Make sure you ONLY delete the WIN32S directory.  Do not delete the 
other directories!  Then, at the C:\WINDOWS\SYSTEM prompt, type 
REN W32SYS.DLL W32SYS.OLD to rename the WIN32S file.  
Reinstall the game.  This should install WIN32S correctly on your system 
and prevent the error message from occurring when you restart the game.  
You should also make sure that the following line is in your SYSTEM.INI 
file:

DEVICE=C:\WINDOWS\SYSTEM\WIN32S\W32S.386

If this does not work, you will need to run the game without loading 
WinG.  See 'Do Not Load WinG' in Section 4, Memory Troubleshooting.

PROBLEM:   You experience random lockups during the game, or your 
computer reboots during the middle of game play.  Sometimes you receive 
memory errors or other problems when playing King's Quest VII. 
SOLUTION:  Update Win32s.  King's Quest VII uses WinG, Microsoft's 
video accelerator, to improve speed performance within the game.  
Microsoft has recently updated Win32s, a key element of the WinG 
drivers.  Version 1.2 of Win32s may improve game performance and help 
eliminate random lockups, memory errors, or random reboots of the 
computer.  You can download this latest version from the Microsoft BBS 
at (206) 936-6735.  Download the file called PW1118.EXE from the 
Articles file area.  The file is also available on CompuServe.  Download 
the file WIN32S.ZIP from the PCEForum/Material location.

PROBLEM:  'Windows title not found' error when starting game, followed 
by 'Cannot find SIERRA.ERR'. 
SOLUTION:  These error messages are caused by a corrupted or incorrect 
RESOURCE.WIN file.  The RESOURCE.WIN is a small text file that 
contains information about your computer.  The game program looks at 
this file to determine where the game is installed and where to look for the 
game CD.  If this file is missing information, you will get the above error 
messages.  To correct this, edit the RESOURCE.WIN file (it's in the game 
directory!) and check that the first three lines look like this:

[Windows]
title=King's Quest VII
titleBar=TRUE

If these two lines are missing or show different information, add them or 
change them to match the ones above.  Remember, they must be the first 
three lines in the file.  Then, check that the last five lines look like this:

resAud=D:\
resSfx=D:\
patchDir=C:\SIERRA\KQ7
movieDir=D:\AVI
audio=C:\SIERRA\KQ7

These lines assume that King's Quest VII is installed to C: and that your 
CD ROM drive is D:.  If your drive letters are different, make the 
appropriate substitutions.   If these five lines are missing or show different 
information, add them or change them to match the ones above. 

You should also check that the King's Quest VII icon's properties indicate 
the correct working directory.  To do this, click once on the King's Quest 
VII icon to highlight it.  Then press ALT-ENTER to access the icon's 
properties.  The command line should read:

C:\SIERRA\KQ7\SIERRAWS.EXE C:\SIERRA\KQ7\RESOURCE.WIN

The working directory should be your CD ROM drive, for example, D:\.  
If your CD ROM drive is another letter, substitute the appropriate letter.  
Click on OK when the working directory is correct.

PROBLEM:  During the game you get 'Error 99: Cannot find file10.wav'.  
(File name may vary.)
SOLUTION:  This happens when the game is looking to the wrong drive to 
find a particular file.  Edit your C:\SIERRA\KQ7\RESOURCE.WIN file 
and check the following lines:
resAud=D:\
resSfx=D:\
patchDir=C:\SIERRA\KQ7
movieDir=D:\AVI
audio=C:\SIERRA\KQ7

Note that D:\ represents your CD-ROM drive.  If your CD drive is a letter 
other than D:, substitute that letter.


PROBLEM:  'I can't save my games!'
SOLUTION:  The King's Quest VII save game feature is different than in 
previous King's Quests.  Your game is saved automatically for you when 
you leave the program.  In King's Quest VII, it is impossible to get 'stuck' 
by missing something from earlier in the game.  The program will not let 
you finish a chapter unless you have completed the minimum of puzzles 
necessary to continue.  Remember there are several different ways to 
complete each chapter!

PROBLEM:  King's Quest VII 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.

You may also try updating Win32s.  King's Quest VII uses WinG, 
Microsoft's video accelerator, to improve speed performance within the 
game.  Microsoft has recently updated Win32s, a key element of the 
WinG drivers.  Version 1.2 of Win32s may improve game performance 
and help eliminate random lockups, memory errors, or random reboots of 
the computer.  You can download this latest version from the Microsoft 
BBS at (206) 936-6735.  Download the file called PW1118.EXE from the 
Articles file area.  The file is also available on CompuServe.  Download 
the file WIN32S.ZIP from the PCEForum/Material location.  If you do 
not have a modem, contact Microsoft's Customer Service at 1-800-426-
9400 for information on obtaining the update.

PROBLEM:  'Error 111' in Chapter 1 when clicking the turquoise piece 
several times on the stone head. 
SOLUTION:  Don't do that!  You only need to click the turquoise there one 
time.  HINT: Make sure the turquoise piece is 'complete'!

PROBLEM:  'Error 108' in Chapter 3 when using the comb on the statuette.
SOLUTION:  Don't do that!  This is an action the programmers did not 
anticipate, so the game gives an error message when you try it.  Just take 
the statue instead of using the comb on it.

PROBLEM:  You can't get the shop keeper to take the wooden nickel in 
Chapter 3.
SOLUTION:  You need the King's Quest VII patch disk.  See Section 7 - 
Obtaining a Sierra Patch Disk.

PROBLEM:  The game loops or locks up in Chapter 4 when Rosella is 
trying to get past the werebeast.
SOLUTION:  You need the King's Quest VII patch disk.  See Section 7 - 
Obtaining a Sierra Patch Disk.

PROBLEM:  'Panic! Error 47 not an object ' in Chapter 4.  (Versions 1.1 
and 1.4 only.)
SOLUTION:  The floppy disk was not installed.  The game program is 
looking for a file that is copied into the game directory when you install 
the floppy disk.   Exit Windows, put the disk in the drive and change to 
the floppy drive prompt.  Type INSTALL.  Restart Windows and go back 
into the game.  This should prevent the error from occurring.

PROBLEM:  '955.snd not found' error message.
SOLUTION:  You have version 1.1 of King's Quest VII and need to get the 
latest version.  See the IMPORTANT NOTE at the beginning of this 
document for information on obtaining the new version. 

PROBLEM:  When Valanice takes the bone from the mummy in Chapter 5, 
the crown cursor appears and the game locks up.
SOLUTION:  You need the King's Quest VII patch disk.  See Section 7 - 
Obtaining a Sierra Patch Disk.

If the patch does not correct the problem, it is caused by an incorrect
MIDI Mapper configuration. See Section 6 - Sound Card Issues and 
Sound Card Settings for information on correctly configuring the MIDI 
Mapper.



PROBLEM:  You can't hear the dragonets sing in Etheria in Chapter 5.
SOLUTION:  This is caused by an incorrect MIDI Mapper setup.  See 
Section 6 - Sound Card Issues and Sound Card Settings for information 
on correctly configuring the MIDI Mapper. 

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 King's Quest VII 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, Memory 
Troubleshooting for complete steps. 

These errors can also occur when the King's Quest VII program is unable 
to read files off the CD. The most common reason for this 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.
 
If you don't see your question listed in this document:  Most 
difficulties with King's Quest 7, 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, 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 - SOUND CARD CONFIGURATION AND SOUND ISSUES

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 King's Quest VII.  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 King's 
Quest VII.  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 King's Quest 
VII.  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 King's Quest VII.  For 
further information on the correct MIDI Mapper configuration for your 
sound card, please contact your sound card manufacturer.

PROBLEM: The speech breaks up or hesitates in King's Quest VII.
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\KQ7\RESOURCE.WIN text file.  Edit this file and change 
the dacSize' line to dacSize =15360.

PROBLEM:  Starting the game gives you a 'Waveout Open' or 'Waveout 
Prepare Header' error message. 
SOLUTION:  The Windows error message you are receiving indicates that 
your sound card is in use by another program.  This is occasionally 
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.

PROBLEM:  You can't hear the dragonets sing in Etheria in Chapter 5.
SOLUTION:  This is caused by an incorrect MIDI Mapper setup. See the 
above information on configuring your MIDI Mapper.  Be very careful 
that the SRC and Dest Channels in your MIDI Mapper match.

PROBLEM:  Using a Pro Audio Spectrum 16, the speech and other digitized 
sounds are full of static.
SOLUTION:  This is caused by using the DMA 3 (the 8-bit DMA) for the 
Pro Audio portion of the sound card.  Change to DMA 5 or 7 (16-bit 
DMAs) and the static should go away.

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.

Note to Gravis UltraSound owners:  If you have a Gravis UltraSound, 
you will need to run King's Quest VII without loading WinG.  (See 'Do 
Not Load WinG' in Section 4, Memory Troubleshooting).  Then, you 
must have the game re-initialize the sound card.   To do this, click on the 
Sierra Setup icon and run the hardware test for sound, then run the game.  
This will load the MIDI patches for you and you should get full sound 
within the game. 

Note to Mozart sound card owners:  If you have a Mozart sound card, 
you will need to run King's Quest VII without loading WinG.  (See 'Do 
Not Load WinG' in Section 4, Memory Troubleshooting).  Then, you 
must change your MIDI Mapper to use Mozart FM Synth.  To do this, 
click on Main, then Control Panel and then on MIDI Mapper.  The MIDI 
Mapper name will probably be set to Mozart MIDI Out, change it to 
Mozart FM Synth.  If you do not have this FM Synth option, please 
contact your sound card manufacturer for help in setting up the correct 
MIDI Mapper. 



SECTION 7 - OBTAINING A SIERRA PATCH DISK

There is one patch available for King's Quest VII .  This patch corrects 
possible lockups or looping situations within the game.  The fastest way to 
obtain a Sierra patch disk is to download it from one of the following on-
line services:  the Sierra BBS (206-644-0112), CompuServe (GO 
SIERRA) or America OnLine (KEYWORD SIERRA).   Look for the file 
KQ7PAT.  You can also request a patch disk be mailed to you by calling 
Sierra Customer Service at 1-800-SIERRA5 or writing to Sierra On-Line 
Patch Disks, Dept. 10, PO Box 485, Coarsegold, CA  93614-0485. 


SECTION 8 - BOOT DISK INSTRUCTIONS

IMPORTANT NOTE: Please read the entire instructions prior to 
starting at Step 1.  You can skip Steps 2 and 3 if you are not playing a 
CD game.


STEP 1
FORMATTING THE DISK
To make a boot disk, format a high density diskette in the A: drive.  (It is 
necessary to reformat the disk if it is already formatted.) Formatting the 
disk with the /S switch will transfer the 'system files' to the disk and allow 
the computer to boot up correctly.  The disk must be in the A: drive; the 
computer will not boot from the B: drive.  Type the FORMAT command 
as follows:

FORMAT A: /S <ENTER>

If you get a 'Bad command or file name' error message, type: 

PATH=C:\DOS <ENTER>

Then retype the FORMAT command above.  If you receive the error 
again, the MS-DOS FORMAT command may not be on your system, or 
it may have been renamed.  Programs such as PC Tools and Norton Disk 
Utilities sometimes rename the FORMAT command to prevent accidental 
loss of data.  If you are using a program of this type, check your 
documentation to find out how to format a SYSTEM DISK, then proceed 
to Step 2. 


STEP 2
LOCATING THE CD ROM DEVICE DRIVER 
The CD ROM drive requires a device driver loaded in the CONFIG.SYS 
file.  This driver must be loaded correctly or you will be unable to access 
your CD ROM drive. To make sure that the device driver loads correctly 
on the boot disk, look at the CONFIG.SYS on the hard drive and copy the 
driver line from there.  At the C:\ prompt, type:

TYPE CONFIG.SYS|MORE

NOTE:     The | is called a 'pipe' command and is created by pressing 
<SHIFT> <BACKSLASH>.


The CONFIG.SYS file will display on the screen.  Look for the line that 
loads the CD ROM device driver.  This line will contain the same '/D:' 
switch as the MSCDEX line in the AUTOEXEC.BAT file.  Using the 
MSCDEX example above, you would be looking for a line containing 
'/D:MSCD001'.  The line should look something like this:

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

The device driver in your CONFIG.SYS may differ slightly from those 
listed above.  Carefully write down the line for use in your boot disk.  
Leave out the 'HIGH' in 'DEVICEHIGH' ant the '/L:' information, if 
any.  Your CD ROM device line should appear as follows:

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

NOTE:  If you have a SCSI CD ROM drive, there may be an additional 
driver in your CONFIG.SYS that must be loaded for the CD ROM device 
drivers to load correctly.  Check your CD drive documentation for more 
information. 


STEP 3
LOCATING THE MSCDEX CD ROM EXTENSION 
In addition to the CD ROM device driver in the CONFIG.SYS, your CD 
ROM drive requires MSCDEX, the Microsoft extension for CD ROM 
drives.  If this extension is not loaded correctly in the AUTOEXEC.BAT, 
you will be unable to access your CD ROM drive.  To make sure that 
MSCDEX loads correctly on the boot disk, look at the AUTOEXEC.BAT 
on the hard drive and copy the MSCDEX line from there.  At the C:\ 
prompt, type:

TYPE AUTOEXEC.BAT|MORE <ENTER>

The AUTOEXEC.BAT file will display on the screen.  Look for the line 
that loads the MSCDEX extension.  It should look something like this:

C:\DOS\MSCDEX /D:MSCD001
LH C:\DOS\MSCDEX /D:MSCD001 
LOADHIGH /L:14429 C:\DOS\MSCDEX /D:MSCD001

The MSCDEX line in your AUTOEXEC.BAT may differ slightly from 
the ones above. Carefully write down the line for use in your boot disk.  
Leave out the '/L:' information, if any. For example, any of the above 
lines will appear on your boot disk as follows:

C:\DOS\MSCDEX /D:MSCD001


STEP 4
LOCATING THE SOUND CARD DRIVERS
Many sound cards have drivers or initialization lines that must be loaded 
in the AUTOEXEC.BAT or CONFIG.SYS.   Some sound cards that 
require these drivers or initialization routines are the SoundBlaster 16, 
MAD16 and the Aria 16.

Section 9 contains the sound card lines for many 
common sound cards.  Check to see if your sound card is on the list.  If it 
is, you will need to add the appropriate lines to the AUTOEXEC.BAT 
and/or CONFIG.SYS on your boot disk.  If your sound card is not listed, 
you should check your documentation for information on what needs to 
load in the AUTOEXEC.BAT and CONFIG.SYS. 


STEP 5
CREATING THE CONFIG.SYS FILE
To create the CONFIG.SYS file on the boot disk, 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>

Add the CD ROM device driver as you wrote it down in the 'Locating the CD
ROM Device Driver' section.  For example:

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

If you need to load any sound card drivers, copy them from the 'Sound 
Cards' section now.  The following example lines are for the 
SoundBlaster 16:

DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 
I:5 D:1 H:5 <ENTER>
DEVICE=C:\SB16\DRV\CTMM.SYS <ENTER>

Complete the file by pressing <F6> <ENTER>.


STEP 6
CREATING THE AUTOEXEC.BAT FILE
To create the AUTOEXEC.BAT file on the boot disk, switch to the A: 
drive and type the following:

COPY CON AUTOEXEC.BAT <ENTER>  (the cursor will drop down one line and blink)
@ECHO OFF <ENTER>
C:\ <ENTER>
SET COMSPEC=C:\COMMAND.COM <ENTER>
PROMPT SIERRA BOOT DISK $_$P$G <ENTER>
PATH=C:\;C:\DOS;C:\SIERRA <ENTER>

Add the MSCDEX line as you write it down in the 'Locating the MSCDEX CD ROM
Extension' section.  For example:

C:\DOS\MSCDEX /D:MSCD001 <ENTER>

If you need to run any sound card initialization programs or load any 
drivers, copy them from the 'Sound Cards' section now.  The following 
example lines are for the SoundBlaster 16:

SET BLASTER=A220 I5 D1 H5 T6 <ENTER>
SET SOUND=C:\SB16 <ENTER>
SET MIDI=SYNTH:1 MAP:E <ENTER>
C:\SB16\SB16SET /M:220 /VOC:220 /CD:220 /MIDI:220 /LINE:220 <ENTER>
C:\SB16\DIAGNOSE /S <ENTER>

Complete the file by pressing <F6> <ENTER>


STEP 7
REBOOT THE SYSTEM AND START WINDOWS
Reboot your system by depressing the <RESET> button on your 
computer or by using the <CTRL>, <ALT>, <DEL> key sequence on 
your keyboard.  When you are at a C:\ prompt, type WIN /3 to start 
Windows.


STEP 8
CREATE A CLEAN WINDOWS ENVIRONMENT
You should make sure that all screen savers, virus scans, and sound-
related Windows programs (IconHear It, Wired for Sound, etc.) are 
disabled before starting your game. In addition, if you are using an 
alternate Windows desktop like Norton Desktop or PCTools, disable this 
and use standard Program Manager

Also, make sure you have a swap file set up that is at least 8 MB 
permanent or 16 MB temporary.  You can check your swap file settings in 
the 386Enhanced icon in the Control Panel.


SECTION 9 - SOUND CARD DRIVER INFORMATION

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

ARIA 16 (Common on IBMs)
        AUTOEXEC.BAT
        SET ARIA=C:\ARIA
        SET BLASTER=A220 I5 D1 T5
        C:\DOS\SOUNDCLT.COM*

        CONFIG.SYS
        DEVICE=C:\ARIA\BIN\SOUNDCFG.SYS
        DEVICE=C:\ARIA\BIN\SNDSAVER.SYS



BOKA SOUND EXPRESS
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 T5

        CONFIG.SYS
        DEVICE=C:\SE1440\CSACMOD1.EXE*



CRYSTAL CLEAR WAVETABLE BY CRYSTAL LAKE
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 T5
        C:\CCLEAR\CSACMAX1
        C:\CCLEAR\CSACHMX1

        CONFIG.SYS
        DEVICE=C:\CCLEAR\CSAMOD1.EXE



DIAMOND LX
        AUTOEXEC.BAT
        SET SONIC=C:\SONIC
        C:\SONIC\SONIC /B/C*
        SET BLASTER=A220 I5 D1 T5

        CONFIG.SYS
        NONE

*Use /C switch for SB mode
*Use /B switch for MSS mode


ENSONIQ SOUNDSCAPE (Common on Gateways)
        AUTOEXEC.BAT
        SET BLASTER=A220 Ixx Dx
        SET SNDSCAPE=C:\SNDSCAPE
        C:\SNDSCAPE\SSINIT /I*

        CONFIG.SYS
        NONE

*older drivers use /FM for Soundblaster mode, /GM
for General Midi mode.



ESS AUDIO DRIVE (Common on Compaqs)
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE



FORTE 16 (Common on Packard Bells)
        AUTOEXEC.BAT
        SET BLASTER=
        SET GALAXY=
        SET SOUND=C:\FORTE16
        C:\FORTE16\UTILITY\EMUTSR

        CONFIG.SYS
        NONE



GALANT
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE


GALAXY - See Multi-Media Pro 16


GATEWAY 2000 AUDIO DRIVE 
        AUTOEXEC.BAT
        C:\G2KAUDIO\UTILITY\GWBVOLO
        SET BLASTER=A220 I5 D1 T5
        SET GALAXY=*
        SET SOUND=C:\G2K

        CONFIG.SYS
        NONE

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



GRAVIS ULTRASOUND 
        AUTOEXEC.BAT
        SET ULTRASND=*
        SET ULTRADIR=*
        C:\ULTRASND\ULTRINIT
        SBOS.BAT**
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for
complete SET lines for the GUS.
**The SBOS.BAT line must be loading to enable the 
card's Soundblaster emulation.




IBM PS/1
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE



ISP 16
        AUTOEXEC.BAT
        C:\ISP16\ISPINIT /B/M*

        CONFIG.SYS
        NONE

*Use /B switch for SB mode
*Use /M switch for  MSS Mode



JAZZ 16 BY MEDIAVISION
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        DEVICE=C:\JAZZ\JAZZ.SYS D:* Q:*

        CONFIG.SYS
        NONE

*D:  DMA CHANNEL.
*Q:  IRQ SETTING.
Specific values and directories may change - check your hard drive's
AUTOEXEC.BAT. 



MAD 16
        AUTOEXEC.BAT
        SET MAD16=C:\MAD16
        SET BLASTER=A220 I5 D1 
        C:\MAD16\M16INIT /B /M*

        CONFIG.SYS
        NONE

*Use /B switch for SB mode
*Use /M switch for  MSS Mode



MAGIC S20
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND16=C:\MAGICS20
        C:\MAGICS20\SNDINIT /B /M*

        CONFIG.SYS
        NONE

*Use /B switch for SB mode
*Use /M switch for  MSS Mode



MAGITEK GREEN 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE



MEDIA CONCEPT 
        AUTOEXEC.BAT
        SET MC=C:\MC
        
        CONFIG.SYS
        NONE



MEDIA VISION 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\MEDVSN\PROS.SYS



MONTE CARLO BY TURTLE BEACH 
        AUTOEXE.BAT
        SET BLASTER=A220 I5 D1
        C:\MCARLO\MCHKMIX

        CONFIG.SYS
        DEVICE=C:\MCARLO\MCMODE -S -W*

*Use -S switch for SB mode
*Use -W switch for  MSS Mode



MOZART SOUND CARD (Common on Cannons)
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\MOZART
        C:\MOZART\MTZVOL.EXE

        CONFIG.SYS
        DEVICE=C:\MOZART\MZTINIT.SYS WSS /530*

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



MULTI-MEDIA PRO 16 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        SET SOUND=C:\MMP16P

        CONFIG.SYS
        NONE

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


ORCHID GAMEWAVE 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=*
        C:\GW32\GW32.EXE

        CONFIG.SYS
        NONE


ORCHID SOUNDWAVE
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=*
        C:\SW32\SW32.EXE

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND line.



PRO AUDIO SPECTRUM 16 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\SPECTRUM\MVSOUND.SYS D:*Q:*

D:  DMA CHANNEL.      Q:  IRQ SETTING.
<DIR> may be PROAUDIO on older drivers.



PRO SONIC
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\PROSONIC\PROSYS.SYS



SOUNDBLASTER AWE 32
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\SB16
        C:\SB16\SB16SET /P/Q
        C:\SB16\DIAGNOSE /S
        C:\SB16\AWEUTIL /S

        CONFIG.SYS
        DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
        DEVICE=C:\SB16\DRV\CTMM.SYS**

**This line is only required to enable the sound card's 
cd-rom interface.



SOUNDBLASTER PRO
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET SOUND=C:\SBPRO*
        C:\SBPRO\SBP_SET*

        CONFIG.SYS
        NONE

*on newer cards the drivers and such may look like 
the SB16 except loading out of a different directory.



SOUNDBLASTER 16 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 H5 T6
        SET SOUND=C:\SB16
        SET MIDI=SYNTH:1 MAP:E
        C:\SB16\SB16SET*
        C:\SB16\DIAGNOSE /S**

        CONFIG.SYS
        DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5
        DEVICE=C:\SB16\DRV\CTMM.SYS***

*Check the AUTOEXEC.BAT on your hard drive for 
the complete SB16SET line as the values may vary.
**May be C:\SB16\SBCoFIG /S on older cards.
***This line is only required to enable the sound card's 
cd-rom interface.



SOUND EZ 
See Mad 16
See Mad 16



SOUND 16A (Common on Packard Bells)
1 OF 2**

        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=
        C:\SOUND16A\UTILITY\SETMODE /MSS*
        SET SOUND16=C:\SOUND16A

        CONFIG.SYS
        NONE

*Use /SB switch for SB mode
*Use /MSS switch for  MSS Mode


SOUND 16A (Common on Packard Bells)
2 OF 2**

        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        C:\AUDIO\SNDINIT.EXE /B**
        SET SOUND16=C:\AUDIO

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /B switch for SB mode
**Use /M switch for  MSS Mode



SOUND 144 (Common on Packard Bells)
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        SET SOUND=SOUND144

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.



VIBRA 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1 H5 T6
        SET SOUND=C:\VIBRA16
        SET MIDI=*
        C:\VIBRA16\DIAGNOSE /S
        C:\VIBRA16\MIXERSET /P/Q

        CONFIG.SYS
        DEVICE=C:\VIBRA16\DRV\VIBRA16.SYS
        DEVICE=C:\VIBRA16\DRV\CTMMSYS.SYS**

*Check the AUTOEXEC.BAT on your hard drive for the complete SET MIDI line.
**This line is required for CD ROM compatibility.



VOYETRA SOUND 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET ISP16=ISP16*
        C:\ISP16\ISPINIT /B

        CONFIG.SYS
        NONE

*May be SET ISP16=VOYETRA


SECTION 10 - IF YOU STILL HAVE PROBLEMS...

If you continue to experience any problems with King's Quest VII, or if 
you have any 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 
CompuServe		GO SIERRA
America Online		KEYWORD SIERRA


If you decide to email, write or fax, please provide the following
information so that we can help you as efficiently as possible:

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

What problem are you having?  Be VERY specific.  Is there an 
error message?  What is it?  Where does it occur? Does it happen 
the same way each time?

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

Please attach copies of your CONFIG.SYS and AUTOEXEC.BAT 
from your hard drive and the boot disk. 

