
King's Quest VII
Troubleshooting Guide
revised 12/14/95

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

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

IMPORTANT NOTE:  After King's Quest VII 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 - COMMON PROBLEMS
SECTION 5 - SOUND ISSUES AND SOUND CARD SETTINGS
SECTION 6 - OBTAINING A SIERRA PATCH DISK
SECTION 7 - DOS AND WINDOWS 3.1 BOOT DISK INSTRUCTIONS
SECTION 8 - WINDOWS 95 BOOT DISK INSTRUCTIONS
SECTION 9 - IF YOU STILL HAVE PROBLEMS...
SECTION 10 - SOUND CARD DRIVER INFORMATION 


SECTION 1 - HARDWARE REQUIREMENTS

REQUIRED
386SX
4MB RAM for the DOS version
8 MB RAM for the Windows version
CD ROM drive
1MB hard drive space for small install
100 MB hard drive space for full install
MS-DOS 5.0 or higher
VGA (256 colors)
Mouse
DOS 5.0 or higher
Windows 3.1 or higher for the Windows version
Sound Card with DAC

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



SECTION 2 - INSTALLATION PROCEDURES 

Note: The following examples assume that you are using hard drive C: 
and CD-ROM drive D:.  If not, substitute all references with the 
appropriate drive letters.

DOS INSTALLATION
Exit Windows completely by closing Program Manager. Place the CD in 
the drive.  Type C: and press <Enter> to make sure that you are logged to 
the hard drive.  Then, type CHKDSK and press <Enter>.  If any errors or 
problems are found, type CHKDSK /F and press <Enter> to correct them.  
Also, check the "bytes available on disk" line to insure that you have 
sufficient hard drive space to do the installation.  Please note that you 
should double the hard drive space requirement when installing to drives 
that are compressed with utilities like DriveSpace or Stacker.

Assuming you have sufficient space, type D: and press <Enter> to switch 
to the CD ROM drive.  Then, type INSTALL and press <Enter> to begin 
installation.  Follow the on-screen prompts, making sure to verify that all 
hardware selections are correct for your system.

WINDOWS 3.1 INSTALLATION
Exit Windows completely by closing Program Manager. Place the CD in 
the drive.  Type C: and press <Enter> to make sure that you are logged to 
the hard drive.  Then, type CHKDSK and press <Enter>.  If any errors or 
problems are found, type CHKDSK /F and press <Enter> to fix them.  
Also, check the "bytes available on disk" line to insure that you have 
sufficient hard drive space to do the installation.  Please note that you 
should double the hard drive space requirement when installing to drives 
that are compressed with utilities like DriveSpace or Stacker.

Assuming that you have sufficient space to proceed, type WIN and press 
<Enter> to restart Windows.  Then, from Program Manager, select <File> 
<Run> D:\SETUP and click on "OK".  From this point, follow the on-
screen prompts.

WINDOWS 95 INSTALLATION
Run SCANDISK from the Start, Programs, Accessories, System Tools 
menu. Allow SCANDISK to correct any errors it finds. Check the "bytes 
available on disk" line to insure that you have sufficient hard drive space 
to install the game.  Please note that you should double the hard drive 
space requirement when installing to drives that are compressed with 
utilities like DriveSpace or Stacker.

Assuming that you have sufficient space to proceed, insert the CD into 
your CD-ROM drive.  After a few seconds, a window will automatically 
appear on your Desktop and ask you if you would like to install King's 
Quest VII. Choose "Install" and follow the on-screen instructions.

To play King's Quest VII in Windows 95 after installation, insert the CD 
in your CD-ROM drive and follow the on-screen instructions.


SECTION 3 - COMMON SETUP AND INSTALLATION PROBLEMS

ALL PLATFORMS
PROBLEM:  When installing the game, you receive the message "Error 
reading drive D".  Message will vary depending on what drive you are 
installing from.
SOLUTION: There are several factors that can cause a "read" error of this 
type. The most common is a dirty or scratched CD.  You should check the 
CD to make sure that there are no smudges, fingerprints, scratches or 
cracks on it.   If you see any smudges on the CD, clean it off with a soft 
cloth and try it again.  If the disk is scratched, it will need to be replaced.

If cleaning the CD doesn't help, the problem may lie with the CD ROM 
drivers.  You should make sure that you are using a recent version of 
MSCDEX in your AUTOEXEC.BAT.  If you're using DOS 6.0 or 
higher, use version 2.23 of MSCDEX in your C:\DOS directory.  If 
you're using Windows 95, use version 2.95 of MSCDEX in the 
C:\WINDOWS\SYSTEM directory. You should also check with the CD 
ROM drive manufacturer to make sure that you have the latest version of 
their CD drivers.  Outdated or incompatible CD drivers can cause this 
type of problem.  

If you need to replace your disks or CD, replacement is FREE for the first 
90 days of product ownership.  After 90 days there is a $10.00 handling 
fee per program.  For the fastest service, simply mail Disk #1 or the CD 
to us along with a copy of your sales receipt dated within 90 days or the 
$10.00 handling fee, and a note detailing your computer hardware and the 
problem that is occurring.  Please include your full name, mailing address, 
and daytime telephone number so we can contact you if necessary. We 
will then send a complete replacement set of disks to you.  The address is:  
Sierra On-Line Customer Service, PO Box 485, Coarsegold CA  93614-
0485.


DOS
PROBLEM:  You do not have an INSTALL command on your CD. 
SOLUTION:   The earlier versions (v1.1 and v1.5) of King's Quest VII did 
not include a DOS version of the game. Based on customer requests for a 
DOS game, we have included a DOS version with the recent re-release of 
King's Quest VII. If you do not have an INSTALL command on your 
CD, you will need to obtain version 2.00b. Please contact Sierra 
Customer Service at 1-800-SIERRA5 for information on upgrading to 
this newer version. 

PROBLEM:  After typing INSTALL, a row of dots goes across the screen 
and stops.  The computer is locked up with this row of dots appearing on 
the screen.  (DOS installation). 
SOLUTION:  The dots indicate the hardware detection portion of the 
installation program.  You can bypass the hardware detection (and 
therefore the lockup) by typing INSTALL /F /M.


WINDOWS 3.1
PROBLEM:  Your computer fails the Display test under the Windows setup; 
you get a message saying "Your video display supports 16 colors...", or 
"King's Quest VII requires a 256 color video driver".  
SOLUTION:  Sierra's Windows games require that Windows is running in 
256 or better color mode.  Using more or less colors will cause errors.  
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.

If you've never changed or updated video drivers in Windows, contact the 
video card manufacturer, refer to the video card manual, or ask a 
technically inclined friend to walk you through  this. To change video 
drivers, in the Main group in Program Manager, double- click on 
Windows Setup icon, then pull down the Options menu, then select 
Change System Settings. Open the Display pulldown box to see the list of 
video drivers that are currently available.  Choose "Other Display".  You 
may be asked to insert your original Windows disks during this process. If 
you do not see an appropriate 256 color video driver listed, contact your 
video card manufacturer. 

Warning: Be cautious 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 contact your 
video card manufacturer for the correct driver.  For complete information, 
consult your video card documentation.
 
PROBLEM:  Your Mitsumi double-speed CD ROM drive does not pass the 
hardware test. 
SOLUTION:  Mitsumi double-speed CD ROM drives have two different 
software drivers available to use with them: a direct memory access 
(DMA) driver called MTMCDAE.SYS and a non-DMA driver called 
MTMCDAS.SYS.  The MTMCDAE.SYS driver is faster, but can prove 
to be incompatible with some software.  The solution is to load the 
MTMCDAS.SYS driver when you want to play the game.  The simplest 
way to do this is to make a boot disk for the game and modify the 
CONFIG.SYS file on it so the MTMCDAS.SYS driver loads.  This 
driver should be in the same directory as MTMCDAE.SYS.  If not, you'll 
need to re-run the installation program for your CD ROM drivers.  See 
the attached boot disk instructions for additional assistance.

PROBLEM:  "Setup was unable to add an item for King's Quest VII to a 
program group" message when installing the game.  Game icon not 
created during game installation. 
SOLUTION #1: You may have run out of hard drive space. Free up more 
hard drive space and try again.  See Section 1 for hard drive space 
requirements. 
SOLUTION #2:  This can be caused by an alternate Windows desktop, like 
PC Tools, Norton Desktop or Packard Bell Navigator.  You must disable 
your alternate desktop before installing the game.  One quick way to do 
this is to type "WIN PROGMAN" to start Windows to use Program 
Manager rather than the alternate desktop shell.  When you are back in 
Windows, reinstall the game.  The icons will be created in the Sierra 
group in Program Manager.  The next time you go into Windows, the 
alternate desktop will display. Tip For PC Tools: Once you finish 
installing the game, click on FILE, then IMPORT.  Import the Sierra 
group so all the game icons will appear in PC Tools.  To restart Windows 
using your normal desktop, exit Windows and reboot the computer.  The 
next time you go into Windows, the alternate desktop will display.   
PLEASE NOTE:  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.  If you wish to try, 
however, here are the game icon properties:

Description:        King's Quest VII
Command Line:		C:\SIERRA\KQ7\SIERRAW.EXE -o 
                    C:\SIERRA\KQ7\RESOURCE.WIN
Working Directory:	D:\
Shortcut Key:       None

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:  Remember that the Windows version of King's Quest VII 
requires 8 MB of RAM. If you have only 4 MB, you must run the DOS 
version. If you have 8 MB, these steps should help you free up enough 
memory for the game. 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 take up a considerable amount of memory.  These steps 
should give you enough memory to run the game. 

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 or 640x480x256 
colors. 


WINDOWS 95
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 may be incorrectly configured for DAC 
(Audio) or your sound card drivers may not be properly installed or 
configured for Windows 95. Make sure your speakers are turned on and 
run the Windows mixer program for your sound card so you can increase 
its volume levels for MIDI (music) and DAC (Audio). You should consult 
your sound card documentation or the manufacturer for information 
regarding the correct configuration of your sound card in Windows 95.  

PROBLEM:  Your computer fails the Display test because you are not 
running in 256 colors,  or your video card does not meet the Pixels-per-
second second Speed requirement for the game. 
SOLUTION:  First make sure you are running Windows in 256 colors. Even 
though your monitor and video card may be capable of displaying 256 
colors, Windows may not be set up to use this resolution.  Click on the 
Start button, select Settings, then Control Panel. Double-click the 
Display icon. You will see four tabs: Background, Screen Saver, 
Appearance, and Settings. Click on Settings. In the box under Color 
Palette, it should say 256 Color. If it does not, click on the down arrow 
next to the window to view a list of choices, and select the one that says 
256 Color.  You will also notice a slider bar under Desktop Area for 
adjusting resolution from 640 by 480 pixels (the lowest setting) upwards. 
If your video card failed the initial speed test, try adjusting the resolution 
to 640 by 480 pixels. This will decrease the screen resolution but may 
improve the speed of your video card. 

PROBLEM:  Your computer fails the Memory test; you get a message 
stating you do not have enough memory to run King's Quest VII. 
SOLUTION:  King's Quest VII requires a computer with a minimum of  8 
MB (8192k) of RAM to run in Windows 95. To free up memory in 
Windows 95, close any and all Windows programs (including screen 
savers, wallpaper, virus detection programs, shell programs like Norton 
Desktop or Packard Bell Navigator, etc.) that may be running. On your 
Taskbar, right-click on the program tab for the program you wish to shut 
down, and select Close. Then run the Setup test program again. If your 
system still fails the test, consult the Windows 95 boot disk instructions in 
Section 8 and create a  boot disk for your system. Then boot up with the 
boot disk, disable any and all other Windows programs, and start the 
Setup/Install program again. These steps should give you enough memory 
to run the program.


SECTION 5 - COMMON GAME PROBLEMS

PLEASE NOTE:  Unless otherwise stated, the following issues occur in 
both the DOS and Windows versions of King's Quest VII. 

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, type TYPE VERSION in 
DOS at the CD drive prompt. If you have version 1.1, you need the 
update. See the IMPORTANT NOTE on the first page of this document 
for information on obtaining the updated version.

If you have version 1.4, 1.5 or 2.00, the problem you are experiencing is 
probably caused by a memory conflict.  Running the game from the boot 
disk will usually correct this problem.  If you are running in Windows, 
make sure that you have no other programs (screen savers, virus scans, 
etc.) running at the same time as the game. 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".  (Windows 3.1)
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. To disable 
WinG, type the following at the C:\SIERRA\KQ7 prompt:

COPY D:\SIERRAW.EXE SIERRAWS.EXE <ENTER> 

This will disable WinG and should prevent the error.

PROBLEM: "General Protection Fault caused by GROWSTUB in 
POINTER.DLL" when game starts. (Windows 3.1)
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: This error is usually caused by a conflict with WinG. Disable 
WinG by typing the following at the C:\SIERRA\KQ7 prompt:

COPY D:\SIERRAW.EXE SIERRAWS.EXE <ENTER> 

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: Error 105 at the bottom of the well, or graphics distortion in the 
scorpion's lair.
SOLUTION: These problems only occured in version 2.0A of the game.  All 
defective copies have now been pulled from our warehouse.  A CD 
replacement will solve the problem. Please contact Sierra Customer 
Service at 1-800-SIERRA5 for information on replacing the CD.

PROBLEM: You receive a "DOS 4/GW" error when starting the game, even 
when using a boot disk. (DOS version)
SOLUTION: This is caused by an incompatible VESA driver or on-card 
VESA support.  Download the universal VESA driver (UNIVBE) from 
our BBS (206-644-7697), an online service or obtain it from your video 
card manufacturer. Load this driver prior to starting the game to avoid 
this error.

PROBLEM: "AVI Open Failed" error when trying to play introduction. 
(Windows 95)
SOLUTION:  This problem occurs when a video drivers is set up incorrectly, 
causing it to be unable to play AVI files. Contact your video card 
manufacturer for assistance in configuring your video to support AVI 
files. 

PROBLEM: "General Protection Fault in Module ... " The module name will 
vary. (Windows 3.1)
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 at the end of this document.  GPFs can also be caused by 
outdated or incompatible sound or video drivers.  If the above steps do not 
solve the GPF for you, contact your video and sound card manufacturers 
to obtain the latest versions of their Windows drivers.

PROBLEM: While running King's Quest VII in Windows 95, you receive a 
message saying "This program has performed an illegal Instruction...".
SOLUTION: An "Illegal Instruction" in Windows 95 is similar to a General 
Protection Fault in Windows 3.1 and occurs for the same reasons. 
Therefore, the solutions are similar as well. First, make sure that you are 
not running any Windows programs other than Print Artist. Programs like 
screen savers and virus detection programs should be disabled. If you are 
using an alternate Windows desktop (PC Tools, Dashboard, Packard Bell 
Navigator, etc.), use the default Windows 95 desktop instead. If you have 
sound-related Windows programs installed (IconHearIt, SoundBits, etc.), 
make sure they are disabled before starting the program. 

You should also make sure that you are running Windows in 256 colors. 
Running in less or more colors can cause errors of this type. 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 well with Print 
Artist. You should contact your video and sound card manufacturers to 
make sure that you have the latest version of their Windows drivers. 

Windows 95 allows you to disable some video acceleration. This often 
helps with Illegal Instruction errors. To do this, 
click on Start, then Settings, Control Panel. Double-click the System 
icon, choose Performance, then Graphics. You should see a slider bar 
labeled Hardware Acceleration. Lower the bar a notch (slide it to the left), 
then restart Windows when you are prompted and run Print Artist again. 
Continue doing this until you cannot lower the bar any more or the 
problem is corrected. If this corrects the problem, you should contact your 
video card manufacturer to obtain updated video drivers.

You can also free up memory by lowering your CD ROM Supplemental 
Cache Size. From Control Panel, click on System, then Performance, 
File System. Click on the tab for CD ROM. Adjust the slider bar for 
Supplemental Cache Size from "Large" to "Small", then click on OK.

PROBLEM: "EMM386 Error 06 ... " The error number may vary. 
(Windows 3.1)
SOLUTION:  This is caused by a memory conflict.  Running the game from 
the boot disk will usually correct this problem.  Use the appropriate 
instructions in Sections 7 and 8 to create a boot disk.

PROBLEM:  "Application Error: C:\SIERRAWS.EXE..." When attempting 
to run the game. (Windows 3.1)
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". (Windows 3.1)
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.  Use the appropriate instructions in 
Sections 7 or 8 to create a boot disk and run the game under the boot disk 
environment. 

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. (All platforms)
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. (Windows 3.1)
SOLUTION:  Your MIDI Mapper is probably set up incorrectly for the 
game.  See Section 5, Sound Issues for information on configuring your 
MIDI Mapper. 

PROBLEM:  When starting the game, you get "EMM386 Error 6 - No XMS 
memory".  (Windows 3.1)
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". (Windows 3.1 and Windows 
95)
SOLUTION:  This is caused by a very small or nonexistent swap file.  Create 
a 6 MB permanent swap file. 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.

When Windows restarts, run the game again. The error should not recur.

PROBLEM:   Game will not start and displays an error message indicating 
improper WIN32S installation. (Windows 3.1 and Windows 95)
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. Disable WinG by typing the following at the C:\SIERRA\KQ7 
prompt:

COPY D:\SIERRAW.EXE SIERRAWS.EXE <ENTER> 

Then start the game normally. This should prevent the error from 
ocurring.

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. 
(Windows 3.1)
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".  (Windows 3.1 and Windows 95)
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 (Windows 3.1) or right 
click (Windows 95) 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.) (Windows 3.1 and Windows 95)
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 original releases (versions 1.1, 1.4 and 1.5) did not have a 
traditional saved game feature. Based on customer feedback, Sierra added 
this feature to version 2.0. If you're interested in obtaining version 2.0, 
please contact Sierra Customer Service at 1-800-SIERRA5.

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).  In Windows 3.1, 3.1.1 and 
Windows for Workgroups, make sure you have a permanent swap file of 
6-8 MB. .   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. In 
Windows 95, check the virtual memory setting in Control Panel, System, 
Performance. Virtual memory should be enabled, and the size of the swap 
file should be handled by Windows 95.

If you are using Windows 3.1, you should 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. (Windows 3.1 or Windows 95)
SOLUTION:  You need the King's Quest VII patch disk.  See Section 6 - 
Obtaining a Sierra Patch Disk.

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

PROBLEM:  "Panic! Error 47 not an object " in Chapter 4.  (Versions 1.1 
and 1.4 only in Windows 3.1 or Windows 95)
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. (Windows 3.1)
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. (Windows 3.1)
SOLUTION:, it is caused by an incorrect MIDI Mapper configuration. See 
Section 5 - 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. 
(Windows 3.1)
SOLUTION:  This is caused by an incorrect MIDI Mapper setup.  See 
Section 5 - 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. 
See sections 8 and 9 for boot disk instructions. 

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 (if you're running in Windows). 
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

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.

WINDOWS 3.1
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.

WINDOWS 95
To make sure that your sound card is configured correctly in 
Windows 95, check the Audio and MIDI settings in the Multimedia 
section of Control Panel.  The Audio setting defines what driver will 
be used to produce digitized sound (DAC). Speech and sound effects 
in a game are usually DAC sounds. The MIDI setting indicates what 
driver is being used for music playback. The following examples are 
for the SoundBlaster 16:

AUDIO: SB16 Wave Out
MIDI: MIDI for Internal OPL2/OPL3 FM Synthesis

The names of the Audio and MIDI drivers will vary, depending on 
your sound card. However, they should be similar to these 
SoundBlaster 16 drivers. For complete information (including driver 
names and installation instructions) on Windows 95 drivers for your 
sound card, contact your sound card manufacturer. 

PROBLEM:  You hear no sound during the game in Windows 95.
SOLUTION:  This usually occurs when your sound card's Windows 95 
drivers are not installed correctly. See the above paragraphs for 
information on checking your Windows 95 sound card drivers.

PROBLEM: The speech breaks up or hesitates in King's Quest VII. 
(Windows 3.1 or Windows 95)
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. (Windows 3.1)
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".  
(Windows 3.1)
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. 
(Windows 3.1)
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. (Windows 3.1)
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, 
and are playing King's Quest VII in Windows 3.1, you will need to run 
King's Quest VII without loading WinG. Disable WinG by typing the 
following at the C:\SIERRA\KQ7 prompt:

COPY D:\SIERRAW.EXE SIERRAWS.EXE <ENTER> 

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 
and are running the game in Windows 3.1, you will need to run King's 
Quest VII without loading WinG. Disable WinG by typing the following 
at the C:\SIERRA\KQ7 prompt:

COPY D:\SIERRAW.EXE SIERRAWS.EXE <ENTER> 

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 6 - OBTAINING A SIERRA PATCH DISK

There is one patch available for King's Quest VII.  This patch corrects 
possible lockups or looping situations in versions 1.4 and 1.5 of King's 
Quest VII.  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 7 - DOS AND WINDOWS 3.1 BOOT DISK INSTRUCTIONS

IMPORTANT NOTE: Please read the entire instructions prior to 
starting at Step 1.  If you are playing the Windows version of King's 
Quest VII, you can skip Step 2.

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

FORMAT A: /S <ENTER>

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

PATH=C:\DOS <ENTER>

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

STEP 2
LOCATING THE MOUSE DRIVER  (Skip if playing the Windows 
version of King's Quest VII) 
If you are playing a game that uses a mouse, the Microsoft compatible 
mouse driver must be loaded into memory with the boot disk. There are 
two kinds of mouse drivers available: those that load in the CONFIG.SYS 
file and those that load in the AUTOEXEC.BAT file.  CONFIG.SYS 
mouse drivers have an extension of .SYS (MOUSE.SYS) and 
AUTOEXEC.BAT drivers have either a .COM or .EXE extension 
(MOUSE.COM, MOUSE.EXE).  You must load at least one of these 
drivers, but it is not necessary to load them all. 

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

DIR MOUSE* /S <ENTER>

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

C:\MOUSE directory, the system will display:

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

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

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

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

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

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

TYPE CONFIG.SYS|MORE

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

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

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

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

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

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



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

TYPE AUTOEXEC.BAT|MORE <ENTER>

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

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

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

C:\DOS\MSCDEX /D:MSCD001

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

At the end of this document, you will find a section labeled "Sound 
Cards".  These tables contain the sound card lines for many common 
sound cards.  Check to see if your sound card is on the list.  If it is, then 
you will need to add the appropriate lines to the AUTOEXEC.BAT and/or 
CONFIG.SYS on your boot disk.  If your sound card is not on the list, 
you should check your documentation for information on what needs to 
load in the AUTOEXEC.BAT and CONFIG.SYS. 

STEP 6
CREATING THE CONFIG.SYS FILE
To create the CONFIG.SYS file on the boot disk, type the following at a 
DOS prompt:

A: <ENTER>
CD\ <ENTER>
EDIT CONFIG.SYS <ENTER>

This will display the blank (usually blue) screen of the DOS Editor. Enter 
the following lines:

DEVICE=C:\DOS\HIMEM.SYS 
DOS=HIGH,UMB 
FILES=30
BUFFERS=20 

If you're using MOUSE.SYS to load your mouse, add the following line:

DEVICE=A:\MOUSE.SYS 

Add the CD ROM device driver as you wrote it down in the "Locating the 
CD ROM Device Driver" section.  The device driver should look 
something like this:

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

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

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

Save the file by pressing <ALT>, <F>, then <S>.  Exit the file by 
pressing <ALT>, <F>, then <X>.


STEP 7
CREATING THE AUTOEXEC.BAT FILE
To create the AUTOEXEC.BAT file on the boot disk, type the following 
at a DOS prompt:

A: <ENTER>
CD\ <ENTER>
EDIT AUTOEXEC.BAT <ENTER>

This will display the blank (usually blue) screen of the DOS Editor. Enter 
the following lines:

@ECHO OFF
C:\ 
SET COMSPEC=C:\COMMAND.COM 
PROMPT SIERRA BOOT DISK $_$P$G 
PATH=C:\;C:\DOS;C:\SIERRA 

If you are using the MOUSE.COM or MOUSE.EXE file to load your 
mouse, add the appropriate line:

A:\MOUSE.COM

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

C:\DOS\MSCDEX /D:MSCD001 

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

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

Save the file by pressing <ALT>, <F>, then <S>.  Exit the file by 
pressing <ALT>, <F>, then <X>.

STEP 8
REBOOT THE SYSTEM AND START THE GAME
Reboot your system by pressing the <RESET> button on your computer 
or by using the <CTRL-ALT-DEL> key combination on your keyboard.  
Once you get to a DOS prompt, follow the instructions in the game 
manual to begin.  

Note:  If your system does not seem to recognize the boot disk, check 
your system documentation to insure that your computer does not use a 
hard disk manager that requires a special procedure to boot from a floppy 
disk.


SECTION 8 - WINDOWS 95 BOOT DISK INSTRUCTIONS

IMPORTANT NOTE:  Please read all instructions before beginning this 
procedure. 

STEP 1
FORMATTING THE DISK
To make a boot disk, you must system format a high density diskette in 
the A: drive. This procedure will transfer the "system files" to the disk and 
allow the computer to boot up correctly.  The disk must be in the A: drive; 
the computer will not boot from the B: drive. 

To format a disk in Windows 95, put the disk in the drive, open My 
Computer, then right click on the A: icon. From the pop-up menu, select 
Format. Under "Format type" select Full; under "Other options", choose 
Copy system files. Click on Start. 

After the disk is formatted, you must copy the MSDOS.SYS file from the 
hard drive to the floppy disk.  To do this, leave the floppy disk in the 
drive, open Windows Explorer and find the MSDOS.SYS file in the root 
of the C: drive.  Right click on the file, then select Send to from the pop-
up menu.  Send the file to the A: drive. 

NOTE:  If you don't see the MSDOS.SYS file in Explorer, the file is 
hidden.  To make the file visible, select View, Options, then Show all 
files. If you do not wish the hidden files to remain visible, you can hide 
them again after you've made the boot disk by choosing View, Options, 
Hide files of this type.

STEP 2 
LOCATING THE CD ROM DEVICE DRIVER
The CD ROM drive requires a device driver loaded in the CONFIG.SYS 
file.  This driver must be loaded correctly or you will be unable to access 
your CD ROM drive. To make sure that the device driver loads correctly 
on the boot disk, look at the CONFIG.SYS on the hard drive and copy the 
driver line from there.  To display the CONFIG.SYS, click on the Start 
button, then choose Run.  In the command line, type SYSEDIT.  The 
SYSEDIT window will appear.  Click on the CONFIG.SYS title bar to 
display the CONFIG.SYS file. Look for the line that loads the CD ROM 
device driver. The line should look something like this:

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

The device driver in your CONFIG.SYS may differ slightly from those 
listed above.  Carefully write down the line for use in your boot disk.  

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

NOTE:  If you cannot find your CD ROM driver in the CONFIG.SYS 
file, you may need to look in the CONFIG.DOS file. To access this file, 
choose Start, Run, then type NOTEPAD C:\CONFIG.DOS. If you still 
cannot locate the driver, check your CD ROM drive documentation or 
contact the drive's manufacturer. 

STEP 3
LOCATING THE MSCDEX CD ROM EXTENSION (May be optional - See Note below)
NOTE: If your CD ROM drive has native 32-bit Windows 95 drivers, 
you will NOT need to load MSCDEX.EXE on your boot disk. If you are 
unable to access your CD ROM drive if MSCDEX is not loaded, contact 
your system manufacturer or CD ROM drive manufacturer for Windows 
95 CD ROM drivers. In the meantime, you can use these instructions to 
load MSCDEX in the AUTOEXEC.BAT file on your boot disk.

In addition to the CD ROM device driver in the CONFIG.SYS, your CD 
ROM drive requires MSCDEX, the Microsoft extension for CD ROM 
drives.  If this extension is not loaded correctly in the AUTOEXEC.BAT, 
you will be unable to access your CD ROM drive.  To make sure that 
MSCDEX loads correctly on the boot disk, use SYSEDIT to look at the 
AUTOEXEC.BAT on your C: drive and copy the MSCDEX line from 
there.  It should look something like this:

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

The MSCDEX line in your AUTOEXEC.BAT may differ slightly from 
the ones above. Carefully write down the line for use in your boot disk.  

If you cannot find the MSCDEX line in the AUTOEXEC.BAT file, then 
most likely you do not need to load it to access your CD ROM drive in 
Windows 95. Skip this step and continue to Step 4.

STEP 4
CREATING THE CONFIG.SYS FILE
To create the CONFIG.SYS file on the boot disk, choose Start, Run, then 
type NOTEPAD A:\CONFIG.SYS in the command line field. This will 
start the Windows Notepad program. In the new Notepad screen, enter the 
following lines:

DEVICE=C:\WINDOWS\HIMEM.SYS 
DOS=HIGH,UMB 
FILES=30
BUFFERS=20 

Add the CD ROM device driver as you wrote it down in the "Locating the 
CD ROM Device Driver" section.  The device driver should look 
something like this:

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

Save the file by clicking on File, Save.  Close Notepad by clicking on 
File, Exit.

STEP 5
CREATING THE AUTOEXEC.BAT FILE
To create the AUTOEXEC.BAT file on the boot disk, choose Start, Run, 
then type NOTEPAD A:\AUTOEXEC.BAT

in the command line field. This will start the Windows Notepad program. 
In the new Notepad screen, enter the following lines:

@ECHO OFF
C:\ 
SET COMSPEC=C:\COMMAND.COM 
PROMPT SIERRA BOOT DISK $_$P$G 
PATH=C:\;C:\DOS;C:\SIERRA 

If your CD ROM drive requires the MSCDEX CD-ROM extension, add 
the line loading MSCDEX that you wrote down in Step 3

Save the file by clicking on File, Save.  Close Notepad by clicking on 
File, Exit.

STEP 6
REBOOT THE COMPUTER AND RUN THE GAME
Leave the disk in the drive and restart the computer by clicking on Start, 
Shut Down., then Restart the computer. The computer will now re-boot 
with the boot disk. When Windows 95 restarts, start King's Quest VII.


SECTION 9 - 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
Internet			support@sierra.com
			http://www.sierra.com


If you decide to write or fax, please provide the following information so
that Sierra Technical Support can assist you as efficiently as possible:

Name:
Fax number:
Phone number:
Address:

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

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





Floppy or CD?

Are you playing in Windows or DOS?

Type of computer (386, 486, etc.)

Brand of video card (Trident, Diamond, etc.)

Amount of RAM (4 meg, 8 meg, etc.)

DOS version (MS-DOS 6.0, PC-DOS 6.2, etc.)

Windows version (3.1, WFWG, Win95, etc.)

Brand of sound card and sound card settings (SoundBlaster Pro, 
Forte16, Mozart, etc.  Please be VERY specific with the brand 
name. Sound card settings include DMA, IRQ and I/" values.)

Any disk compression?  What kind? (Doublespace, Stacker, etc.)

Any third-part memory manager?  What kind?  (QEMM, 386MAX, 
etc.)

Largest executable program size or bytes free after booting with the 
boot disk. (Type MEM to find out.) 

What have you tried so far?  (Boot disk, no sound, etc.)



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




SOUND CARD DRIVER INFORMATION

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


ADLIB
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE

This is a MIDI card only and will not play most sound 
effects.


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

        CONFIG.SYS
        DEVICE=C:\ARIA\BIN\SOUNDCFG.SYS
        DEVICE=C:\ARIA\BIN\SNDSAVER.SYS
        
*This line is not always present.


ATI STEREO FXCD
        AUTOEXEC.BAT
        SET ATI_SND=C:\SFXCD

        CONFIG.SYS
        NONE


AUDIO ROCK IT 16
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE


AUDIO 16 BY AZTECH
        AUTOEXEC.BAT
        C:\GB2KAUDIO\UTILITY\GWBVOL
        SET BLASTER=*
        SET SOUND=*

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for
the SET BLASTER and SET SOUND parameters.


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

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


BREVE TECHNOLOGIES
        AUTOEXEC.BAT
        C:\BRV16F\DOSDRV\INIT16
        C:\BRV16F\DOSDRV\MIXER

        CONFIG.SYS
        NONE


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

        CONFIG.SYS
        DEVICE=C:\CCLEAR\CSAMOD1.EXE -S***

*Enables Soundblaster compatibility.
**Add /ON to enable Soundblaster compatibility, /OFF to disable it.
***Use -S for Soundblaster mode and -W for Windows Sound System mode.


DIAMOND
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND16=C:\DIAMOND
        C:\DIAMOND\SNDINIT /B**

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.
**Use /C for Soundblaster mode and /B for Microsoft Sound System mode.


DIAMOND LX
        AUTOEXEC.BAT
        SET SOUND=C:\SONIC
        SET BLASTER=A220 I5 D1 T5
        C:\SONIC\MZTVOL.EXE
        C:\SONIC\MZTINIT WSS*
        C:\SONIC\MTZINIT.SYS

        CONFIG.SYS
        NONE

*Use WSS for Windows Sound System mode and SB for Soundblaster mode.


DSP16
        AUTOEXEC.BAT
        SET BLASTER=*

        CONFIG.SYS
        NONE

*Check your AUTOEXEC.BAT on the hard drive for the SET BLASTER parameters.


ENSONIQ SOUNDSCAPE - Common on Gateways
Driver version 1.10 dated 11/31/94
        AUTOEXEC.BAT
        SET BLASTER=A220 Ixx Dx
        SET SNDSCAPE=C:\SNDSCAPE
        C:\SNDSCAPE\SSINIT FM*
        C:\SNDSCAPE\VSB_EMM.COM**

        CONFIG.SYS
        DEVICE=C:\DOS\EMM386.EXE***

*Use FM for FM synth, GM for General MIDI and MT32 for Roland MT32 emulation.
**Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT


ENSOMIQ SOUNDSCAPE - Common on Gateways
Driver version 1.20.02 dated 12/19/94
        AUTOEXEC.BAT
        SET BLASTER=A220 Ixx Dx
        SET SNDSCAPE=C:\SNDSCAPE
        C:\SNDSCAPE\SSINIT /I*
        C:\SNDSCAPE\VSB_EMM.COM**

        CONFIG.SYS
        DEVICE=C:\DOS\EMM386.EXE***

*/I enables FM synth and General MIDI emulation.
Run MT32.EXE to enable Roland MT32 emulation.
**Can help with Soundblaster emulation. Requires the EMM386 line in the CONFIG.SYS
***Necessary for the VSB_EMM.COM line in the AUTOEXEC.BAT


ESS AUDIO DRIVE - Common on Compaqs
        AUTOEXEC.BAT            
        NONE     

        CONFIG.SYS
        DEVICE=C:\CPQDOS\VOLCTRL.EXE*
        DEVICE=C:\PCAUDIO\VOLCTRL.EXE**

*Loads the DOS mixer. <Ctrl/Right Shift> turns up the volume, <Ctrl/Left Shift>
turns it down.
**Necessary to load Windows mixer.


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

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for these settings.
**Enables the Soundblaster emulation.


FUSION 16
        AUTOEXEC.BAT
        SET BLASTER=*

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

*Check the AUTOEXEC.BAT on your hard drive for these settings.
**D: is the DMA channel and Q: is the IRQ setting


GALANT
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        NONE


GALAXY - See Multi-Media Pro 16


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

        CONFIG.SYS
        NONE

This sound card will autoconfigure itself to Soundblaster or Microsoft
Sound System mode.


GOLDEN SOUND BY TOPEK
        AUTOEXEC.BAT
        C:\GS16\GS-ENV PC:\GS16ES

        CONFIG.SYS
        NONE


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

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for complete SET lines for the GUS.
**The SBOS.BAT line must be loaded to enable the card's Soundblaster
emulation. This line is not needed for the ACE.


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

        CONFIG.SYS
        NONE


ISP 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET ISP16=C:\ISP16
        C:\ISP16\ISPINIT /B/M*

        CONFIG.SYS
        NONE
*Use /B switch for SB mode
*Use /M switch for  Microsoft Sound System mode



JAZZ 16
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\JAZZ\JAZZ.SYS D:* Q:*

*D:  DMA CHANNEL.
*Q:  IRQ SETTING.
Specific values and directories may change



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

        CONFIG.SYS
        NONE

*Use /B switch for Soundblaster  mode.  Use /M switch for Microsoft Sound
System Mode



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

        CONFIG.SYS
        NONE

*Use /B switch for Soundblaster  mode.  Use /M switch for  Microsoft Sound
System Mode



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

        CONFIG.SYS
        NONE



MEDIA CONCEPT
        AUTOEXEC.BAT
        SET MC=C:\MC

        CONFIG.SYS
        NONE



MEDIA VISION DELUXE
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\MEDVSN\VBEAI.COM

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



MEDIA VISION PREMIUM 3D SCSI2
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\MEDVSN\PA3D.SYS
        DEVICE=MINI406A.SYS



MMCD16W
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=C:\MMCD16W
        SET GALAXY=*

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT for the SET BLASTER and SET GALAXY parameters



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

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

*Use -S switch for SB mode
*Use -W switch for  Microsoft Sound System Mode



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

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

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



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

        CONFIG.SYS
        NONE

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



MW WAVE - Common on IBM Thinkpads
        AUTOEXEC.BAT
        SET BLASTER=
        SET MWPATH=C:\MWD\MANAGER;C:\MWD\MWGAMES*
        SET MWROOT=C:\MWD
        MWGAMES=ON**

        CONFIG.SYS
        NONE

*This is all one line.
**ON turns on Soundblaster emulation and OFF turns it off.



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

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
SET BLASTER lines.



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

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET SOUND and
SET BLASTER lines.



PHILLIPS
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE



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

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

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



PRO SONIC
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

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



SC400
        AUTOEXEC.BAT
        SET SOUND=C:\SC400
        SET BLASTER=A220 I5 D1
        C:\SC400\UTILITY\SNDINIT /B

        CONFIG.SYS
        NONE



SGBAS16
        AUTOEXEC.BAT
        SET BLASTER=*
        SET SOUND=C:\SGBAS16
        SET GALAXY=*

        CONFIG.SYS
        DEVICE=C:\SGBAS16\DRIVERS\EEPRO.SYS

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY and
SET BLASTER lines.



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

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

*May be SBCONFIG on older cards.
**This line is only required to enable the sound card's CD-ROM interface.



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

        CONFIG.SYS
        NONE

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



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

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

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




SOUND EXPRESSION BY BOCA
        AUTOEXEC.BAT
        SET BLASTER=
        C:\CE1440\CSACMAX1.COM*
        C:\CE1440\CSACHMX1.COM**

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

*Enables Soundblaster compatibility.
**/ON turns on Soundblaster compatibility, /OFF turns it off.
***-S for Soundblaster mode and -W for Windows Sound System mode.




SOUND EZ - See Mad 16



SOUND FX PLUS
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SOUND=C:\MMSUP

        CONFIG.SYS
        NONE




SOUNDMAND BY LOGITECH
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1

        CONFIG.SYS
        DEVICE=C:\SOUNDMAN\MVSOUND.SYS




SOUND 16A - Common on Packard Bells 1 OF 2**
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        C:\SOUND16A\UTILITY\SETMODE /MSS**
        SET SOUND16=C:\SOUND16A

        CONFIG.SYS
        NONE

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




SOUND 16A - Common on Packard Bells 2 OF 2**
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        C:\AUDIO\SNDINIT.EXE /B**
        SET SOUND16=C:\AUDIO

        CONFIG.SYS
        NONE

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




SOUND 144 - Common on Packard Bells
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        SET GALAXY=*
        SET SOUND=SOUND144
        C:\SOUND144\UTILITY\SETMODE /SBP**

        CONFIG.SYS
        NONE

*Check the AUTOEXEC.BAT on your hard drive for the complete SET GALAXY line.
**Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.




STRAUSS
        AUTOEXEC.BAT
        NONE

        CONFIG.SYS
        NONE





TROPEZ BY TURTLE BEACH 
        AUTOEXEC.BAT
        SET BLASTER=A220 I5 D1
        C:\TROPEZ\DOSAPPS\SETUPSND*
        C:\TROPEZ\DOSAPPS\TZMODE -S*

        CONFIG.SYS
        DEVICE=C:\TROPEZ\DOSAPPS\TZMODE**

*Windows will disable these lines, so they will need to be run again
if Windows is started and shut down.  Use -S for Soundblaster mode and -W
for Windows Sound System mode on the TZMODE line.
**This line is necessary if the sound card is also 
acting as the CD-ROM controller.




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

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

*Check the AUTOEXEC.BAT on your hard drive for the complete SET MIDI line.
**Older cards may use SBCONFIG instead of DIAGNOSE.




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

        CONFIG.SYS
        NONE

*May be SET ISP16=VOYETRA




WAVERIDER BY AZTECH
        AUTOEXEC.BAT
        SET BLASTER=
        SET SOUND=C:\WAVRIDER
        SET GALAXY=
        C:\WAVRIDER\DRIVERS\WAVERIDE.EXE
        C:\WAVRIDER\SETMODE /SBP*

        CONFIG.SYS
        NONE

*Use /SBP for Soundblaster mode and /MSS for Microsoft Sound System mode.


