Unprotect 6/Unprotect-6.0.iso/update/kq7/kq7mem.txt

Text File | 1995-06-01 | 10.0 KB | 260 lines

KING'S QUEST VII
MEMORY TROUBLESHOOTING for IBM compatibles using Windows 3.1
or higher and MS-DOS 5.0 or higher

Revised 1/10/95


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, however, it may occur on systems with more memory.  If
you are having memory problems or are receiving memory-related errors
during the game, here is a list of troubleshooting steps to try.

The following instructions have been prepared by Sierra's Technical
Support Department as an added service to our customers.  PLEASE
NOTE: SIERRA DOES NOT MAKE ANY CLAIMS, GUARANTEES, AND/OR PROMISES THAT
THE FOLLOWING INSTRUCTIONS WILL WORK ON ANY AND/OR ALL COMPUTER SYSTEMS.


DO NOT LOAD WING:  To make sure WinG is not activated, edit
the RESOURCE.WIN file and make sure the following line appears:

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 WinG 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 6 to 10 MEGS.
This will help free up memory.  Do not set the swap file too high, 6-10
MEGS permanent should be enough.


CREATE A BOOT DISK:  Sierra has included a boot disk maker with
the game.  The Boot Disk Creator is the last option available in the Setup
program.  You can run it 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 actually 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 (Norton 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.


WINDOWS FOR WORKGROUPS v3.11:  Because of the memory requirements of
Windows for Workgroups, you may experience trouble getting enough memory
for the game if you have only 4 megs of RAM.  If you are using Windows for
Workgroups, we highly recommend that you have at least 8 megs 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 [phone].  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.


SHOULD YOU STILL HAVE PROBLEMS
If you continue to experience memory problems, or if you have any questions
concerning any of the above steps, our Technical Support Department will be
more than happy to assist you.  Please call [phone] between 8:15 am
and 4:45 PM Monday through Friday.  We can also be reached by fax at
[phone], by BBS at [phone], or by mail at the following address:

Sierra On-Line
P.O. Box 85006
Bellevue, WA  98015-8506
ATTN:  TECHNICAL SUPPORT

You can also reach our Technical Support Team on one of the following
services:
Sierra BBS      [phone]  (settings 8, N, & 1, up to 38,400 baud)
Compuserve      Sierra: GAMAPUB (ID 76004,2143)
        Dynamix: GAMCPUB (ID 72662, 1174)
America Online  Keyword: SIERRA

Please outline the problems along with detailed information about your
computer system, and we will gladly respond to your fax, letter or
message as soon as possible.



*************************************************************************


KING'S QUEST VII BOOT DISK INSTRUCTIONS
for IBM Compatibles using MS-DOS 5.0 or above and Windows 3.1 or
higher

Revised 1/10/94

The following instructions have been prepared by Sierra's Technical
Support Department as an added service to our customers.  PLEASE

NOTE: SIERRA DOES NOT MAKE ANY CLAIMS, GUARANTEES, AND/OR PROMISES
THAT THE FOLLOWING INSTRUCTIONS WILL WORK ON ANY AND/OR ALL COMPUTER
SYSTEMS.


STEP 1
FORMATTING THE DISK
PLEASE NOTE: It is necessary to format the disk even if the disk is
already formatted.  The /S switch will transfer files to the boot disk which
are necessary for the disk to work correctly.  To make a  CD-
ROM Boot Disk, format a high density diskette in the A: drive.  (Use
/F:360 or  /F:720 parameter if using a low density diskette) For more
information on using the FORMAT command, consult your DOS
manual. Note: This will not work in the B: drive.

Type the command as follows:

FORMAT  A:/S  <ENTER>

If after entering this command the system responds with a "Bad command
or file name" error, then type:

PATH=C:\DOS  <ENTER>

Now retype the FORMAT command above.  If you still receive the same
error, 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 can rename the format command to prevent accidental loss of
data. If you are using a program like this, check your documentation to
find out how to format a SYSTEM DISK, then proceed to Step 2.

STEP 2
LOCATING THE MSCDEX CD ROM EXTENSION
MSCDEX is the Microsoft extension for CD ROM drives.  It must be loaded
in order for your CD ROM drive to operate.  The following steps should
assist you in locating this file on your system.  To locate MSCDEX, at
the C:\> prompt, type:

TYPE  AUTOEXEC.BAT  |  MORE  <ENTER>

NOTE: The | is called a "pipe" command and is created by pressing
<SHIFT> \ (backslash).  Now look for the line which loads "MSCDEX".
This line should look something like this: :

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

Your line may differ from the ones listed above.  Please write down the
entire line following the drive letter.  Be sure to include the full drive
and path to your MSCDEX file.  For example, any of the above lines should
appear as follows:

C:\DOS\MSCDEX  /D:MSCD001


STEP 3
LOCATING THE CD ROM DEVICE DRIVER
Along with MSCDEX, the CD ROM also needs a device driver.  This
driver is loaded in the CONFIG.SYS file.   To determine the correct CD
ROM device driver, at the C:\> prompt type:

TYPE  CONFIG.SYS  |  MORE  <ENTER>

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

Now look for the line that contains CD ROM device name which
immediately follows the same "/D:" switch as the MSCDEX line in the
AUTOEXEC.BAT file.  Using the example above, we would be looking
for a line containing "MSCD001".  This line should look something like
one of  the following lines:

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

Your line may differ from the ones listed above.  Please write down the
entire line following the drive letter.  Be sure to include the full drive
and path to your CD ROM device driver.  For example, any of the above lines
should appear as follows:

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


STEP 4
CREATING THE CONFIG.SYS FILE
Now 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>
FILES=30 <ENTER>
BUFFERS=20 <ENTER>
DOS=HIGH  <ENTER>

Now add the CD ROM driver line as you wrote it down in the "Locating
the CD ROM device driver" section above.  Complete the file by pressing
the  F6  Function key <ENTER>

STEP 5
CREATING THE AUTOEXEC.BAT FILE
Now create an AUTOEXEC.BAT file by typing:

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

Add the MSCDEX line as you wrote it down in the "Locating the MSCDEX CD ROM
extension" section listed above.

Complete the file by pressing the  F6  Function key <ENTER>

STEP 6
REBOOT THE SYSTEM
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.