                   ERROR MESSAGES FOR MEMORY MANAGERS

                Copyright 1993 Invisible Software, Inc.



       [See GUIDE.TXT for a list of all manuals and text files.]



This file describes the error messages that can be generated by the
Invisible RAM memory managers.  For each message, we give an
explanation, and a recommendation on how to correct the error.

Error message information is divided into four files:

     ERRORS1.TXT - Error Messages For Command Line Utilities
     ERRORS2.TXT - Error Messages For Network Installation
     ERRORS3.TXT - Error Messages For Memory Managers
     ERRORS4.TXT - Error Messages For The Windows Network Driver



------------------------------------------------------------------------



TABLE OF CONTENTS

1. Memory manager installation error messages
2. 386 control program installation error messages
3. 386 control program run-time error messages
4. LSHADOW.SYS error messages



------------------------------------------------------------------------



1. Memory Manager Installation Error Messages




NEAT chipset is not present in this computer.

Explanation:  You are attempting to install the NEAT chipset version of
Invisible RAM (NEATEMM.SYS), but your computer does not have the NEAT
chipset.

Recommended action:  Only use NEATEMM.SYS on computers with the NEAT
chipset.




NEAT EMS size configured incorrectly.  Use set-up program to change EMS
size.

Explanation:  You are attempting to install the NEAT chipset version of
Invisible RAM (NEATEMM.SYS), but the EMS size programmed into the NEAT
chipset is invalid.  For example, the EMS size may exceed the amount of
available memory.

Recommended action:  Run your computer's set-up program and change the
value for "EMS size."




NEAT configured incorrectly.  Use set-up program to disable memory
relocation.

Explanation:  You are attempting to install the NEAT chipset version of
Invisible RAM (NEATEMM.SYS), and:  (1) You are attempting to create
shadow RAM, but the NEAT chipset is programmed to enable 640K to 1M
memory relocation;  or (2) There is more than 1024K total RAM on the
motherboard, but the NEAT chipset is programmed to enable 640K to 1M
memory relocation.

Recommended action:  Run your computer's set-up program and disable 640K
to 1M memory relocation.




NEAT configured incorrectly.  Use set-up program to enable memory
relocation.

Explanation:  You are attempting to install the NEAT chipset version of
Invisible RAM (NEATEMM.SYS).  You are attempting to use expanded memory
with exactly 1024K total RAM on the motherboard, but the NEAT chipset is
programmed to disable 640K to 1M memory relocation.

Recommended action:  Run your computer's set-up program and enable 640K
to 1M memory relocation.




NEAT EMS is disabled.  Use set-up program to enable EMS.

Explanation:  You are attempting to install the NEAT chipset version of
Invisible RAM (NEATEMM.SYS).  You are attempting to use expanded memory,
but the NEAT chipset is programmed to disable the built-in expanded
memory controller.

Recommended action:  Run your computer's set-up program and enable the
EMS memory controller.




Insufficient memory installed on motherboard.

Explanation:  You are attempting to install the NEAT, AT/386, SCAT, or
PEAK chipset version of Invisible RAM (NEATEMM.SYS, A386SRM.SYS,
SCATEMM.SYS, or PEAKSRM.SYS).  The total RAM on the motherboard is
insufficient to create the requested shadow RAM and/or expanded memory.

Recommended action:  Install more memory on the motherboard.




AT/386 chipset is not present in this computer.

Explanation:  You are attempting to install the AT/386 chipset version
of Invisible RAM (A386SRM.SYS), but your computer does not have the
AT/386 chipset.

Recommended action:  Only use A386SRM.SYS on computers with the AT/386
chipset.




SCAT chipset is not present in this computer.

Explanation:  You are attempting to install the SCAT chipset version of
Invisible RAM (SCATEMM.SYS), but your computer does not have the SCAT
chipset.

Recommended action:  Only use SCATEMM.SYS on computers with the SCAT
chipset.




SCAT configured incorrectly.  Use set-up program to disable memory
relocation.

Explanation:  You are attempting to install the SCAT chipset version of
Invisible RAM (SCATEMM.SYS), and you are attempting to create shadow
RAM, but the SCAT chipset is programmed to enable 640K to 1M memory
relocation.

Recommended action:  Run your computer's set-up program and disable 640K
to 1M memory relocation.




No EMS memory available.  Use set-up program to allocate EMS memory.

Explanation:  You are attempting to install the SCAT chipset version of
Invisible RAM (SCATEMM.SYS), and you are attempting to create expanded
memory, but the SCAT chipset is set up not to provide any expanded
memory.

Recommended action:  Run your computer's set-up program and change the
value for "Extended Memory Boundary."




PEAK chipset is not present in this computer.

Explanation:  You are attempting to install the PEAK chipset version of
Invisible RAM (PEAKSRM.SYS), but your computer does not have the PEAK
chipset.

Recommended action:  Only use PEAKSRM.SYS on computers with the PEAK
chipset.




Invisible RAM 386/486 Control Program is not installed.

Explanation:  You are attempting to install the expanded memory manager
for Invisible RAM 386 (C386EMM.SYS), but the Invisible RAM 80386 control
program (CP386.SYS) is not installed.

Recommended action:  Install CP386.SYS.




Hardware mapping register test failed.

Explanation:  You are attempting to install the expanded memory manager
for Invisible EMS (IEMSEMM.SYS), but the Invisible EMS board is not
installed;  or else you have not specified the correct I/O port address.

Recommended action:  Make sure the Invisible EMS board is installed.
Make sure the value you specify for I/O port is the same as the address
you set with the DIP switch on the Invisible EMS board.




Backfill switch setting is invalid for use with 256K DRAM chips.

Explanation:  You are attempting to install the expanded memory manager
for Invisible EMS (IEMSEMM.SYS).  There is 512K RAM on the Invisible EMS
board, but the backfill you selected with the DIP switch requires more
than 512K RAM.

Recommended action:  Change the DIP switch setting.  Refer to your
Invisible EMS user manual for instructions.




Expanded Memory Manager is not installed.

Explanation:  You are attempting to install the Invisible RAM for
Generic EMS (GEMSSRM.SYS), but the underlying expanded memory manager is
not installed.

Recommended action:  Install the underlying expanded memory manager
before installing Invisible RAM for Generic EMS.




This program requires EMS version 4.0 or later.

Explanation:  You are attempting to install the Invisible RAM for
Generic EMS (GEMSSRM.SYS).  The underlying expanded memory manager is
installed, but it is not version 4.0.

Recommended action:  Obtain an updated version of the underlying
expanded memory manager software.




Expanded Memory Manager malfunction.

Explanation:  You are attempting to install the Invisible RAM for
Generic EMS (GEMSSRM.SYS), but the underlying expanded memory manager is
not working correctly.

Recommended action:  Make sure the expanded memory hardware and software
is correctly installed.




No free expanded memory available.

Explanation:  You are attempting to install the Invisible RAM for
Generic EMS (GEMSSRM.SYS).  The underlying expanded memory manager is
installed, but it has no free expanded memory.

Recommended action:  Make sure the expanded memory hardware and software
is correctly installed.  If necessary, add more expanded memory.




Another program is already using expanded memory.

Explanation:  You are attempting to install the Invisible RAM for
Generic EMS (GEMSSRM.SYS).  The underlying expanded memory manager is
installed, but some other program is already using expanded memory.
With DOS 4.0, this will occur if you use expanded memory for DOS BUFFERS
or VDISK, and then install Invisible RAM with the NET30 command.

Recommended action:  Do not start any expanded memory applications
before starting Invisible RAM for Generic EMS.  With DOS 4.0, if you
want to use expanded memory for BUFFERS or VDISK, then you must install
GEMSSRM.SYS from the CONFIG.SYS file.




Memory hardware is not present or incorrectly configured.

Explanation:  The memory hardware in your computer is not functioning
correctly.

Recommended action:  (1) Check the switches and jumpers on your
computer's motherboard, and any memory expansion boards, to be sure they
are set correctly.  (2) Make sure that you ran your computer's set-up
program correctly.  (3) Make sure that the memory chips in your computer
are fast enough.  If necessary, replace the memory chips with faster
chips.




Expanded memory hardware malfunction.

Explanation:  The memory hardware in your computer is not functioning
correctly.

Recommended action:  (1) Check the switches and jumpers on your
computer's motherboard, and any memory expansion boards, to be sure they
are set correctly.  (2) Make sure that you ran your computer's set-up
program correctly.  (3) Make sure that the memory chips in your computer
are fast enough.  If necessary, replace the memory chips with faster
chips.




Unable to locate required standard window for expanded memory.

Explanation:  The expanded memory manager cannot locate a 64K-byte block
of available memory to use for the standard EMS area.

Recommended action:  (1) Try to change the addresses used by ROM and RAM
in your computer to free up a contiguous 64K-byte block.  You can use
SHADOW /M to help determine what ROM and RAM is present in your
computer.  (2) Use the /I or Include parameter to include additional
page frames as paged EMS memory.  (3) If you specified the /A or Frame
Address parameter, make sure there is 64K of memory available at the
specified address.  (4) If you specified the /P or Non-standard Page
parameter, remove it.  (5) In case of the NEAT chipset, use your
computer's set-up program to change "EMS memory address" to an address
that does not conflict with other equipment in the computer.




No RAM available for use as expanded memory.

Explanation:  All the RAM in the computer was used up for backfill,
frontfill, shadow RAM, and high RAM.

Recommended action:  (1) Reduce the amount of RAM used for backfill,
frontfill, shadow RAM, and high RAM.  (2) Use the /Z=2 or SHADOW_ONLY
configuration.  (3) In case of Invisible RAM 386, reduce the amount of
extended memory reserved by the /E or EXTENDED parameter of the 386
control program.




Invalid parameters.

Explanation:  You are installing Invisible RAM from the CONFIG.SYS file,
and one or more parameters on the Invisible RAM command line are
invalid, or given in incorrect form, or have unacceptable values.

Recommended action:  Edit the CONFIG.SYS file and correct the erroneous
parameters.  If you don't know which parameters are erroneous, remove
all parameters from the Invisible RAM command line, and then add them
back one-by-one.




Conflicting parameters.

Explanation:  Two or more of the memory manager parameters are in
conflict with each other.  For example, the same page frame may be
specified for both shadow RAM and paged EMS memory.

Recommended action:  Correct the erroneous parameters.  If you're
installing Invisible RAM from CONFIG.SYS, and you don't know which
parameters are erroneous, remove all parameters from the Invisible RAM
command line and then add them back one-by-one.




Ctrl-Alt-Shift detected.  At user request, program will not install.

Explanation:  You pressed Ctrl-Alt-Shift.  Invisible RAM does not load
if these keys are pressed.

Recommended action:  None.




Include, Shadow, or High RAM addresses conflict with installed hardware.

Explanation:  The page frames you specified for use as paged EMS memory,
shadow RAM, or high RAM are in conflict with equipment installed in your
computer.

Recommended action:  (1) Change the page frame addresses you specify for
paged EMS memory, shadow RAM, or high RAM.  If you are installing
Invisible RAM from CONFIG.SYS, change the /I, /S, or /R parameters.  If
you are installing Invisible RAM with the NET30 command, change the
INCLUDE, SHADOW_RAM, or HIGH_RAM parameters in the initialization file.
(With the Invisible LAN Setup program, this is done on the System Memory
Configuration screen.) (2) Change the addresses used by RAM or ROM in
your computer.




Include addresses are too low in memory.

Explanation:  You tried to create paged EMS too low in DOS memory.

Recommended action:  Change the /I or INCLUDE parameter.  (With the
Invisible LAN Setup program, this is done on the System Memory
Configuration screen.)




Cannot create High RAM inside DOS memory.

Explanation:  You tried to create high RAM inside DOS memory.  This is
not permitted.

Recommended action:  Change the /R or HIGH_RAM parameter.  (With the
Invisible LAN Setup program, this is done on the System Memory
Configuration screen.)




Cannot create Shadow RAM inside DOS memory.

Explanation:  You tried to create shadow RAM inside DOS memory.  This is
not permitted.

Recommended action:  Change the /S or SHADOW_RAM parameter.  (With the
Invisible LAN Setup program, this is done on the System Memory
Configuration screen.)




Cannot locate standard EMS area inside DOS memory.

Explanation:  You tried to specify a standard EMS frame address within
DOS memory.  This is not permitted.

Recommended action:  (1) Change the /A or FRAME_ADDRESS parameter.  (2)
Delete the /A or FRAME_ADDRESS parameter and let Invisible RAM select
the standard EMS address.  (With the Invisible LAN Setup program, this
is done on the Memory Manager Parameters screen.)




Memory hardware cannot create Shadow or High RAM at the specified
addresses.

Explanation:  The page frames specified you selected for shadow RAM or
high RAM cannot be used for shadow or high RAM.

Recommended action:  For shadow RAM, change the /S or SHADOW_RAM
parameter.  For high RAM, change the /R or HIGH_RAM parameter.  (With
the Invisible LAN Setup program, this is done on the System Memory
Configuration screen.)




No Shadow RAM available.

Explanation:  You specified the /Z=2 or SHADOW_ONLY configuration, but
Invisible RAM is unable to create any shadow RAM because (1) all
available RAM was used up for backfill and frontfill, or (2) there are
no page frames available.

Recommended action:  (1) Reduce the amount of RAM used for backfill,
frontfill, and the high memory area.  (2) Change the addresses used by
RAM or ROM in your computer.  (3) In the case of Invisible RAM 386,
reduce the amount of extended memory reserved by the /E or EXTENDED
parameter for the 386 control program.




Unexpected internal driver error.

Explanation:  Invisible RAM has a bug.

Recommended action:  Write down the circumstances under which this error
occurred and contact Invisible Software technical support.




Parameters /A, /C, /E, /H, /I, /K, and /P are not valid with /Z=2.

Explanation:  You are installing Invisible RAM from CONFIG.SYS.  When
you select the /Z=2 configuration, you cannot use the /A, /C, /E, /H,
/I, /K, or /P parameters.

Recommended action:  Edit the CONFIG.SYS file and correct the
parameters.




Memory hardware cannot include mappable memory at the specified
addresses.

Explanation:  The page frames specified in the /I or INCLUDE parameter
cannot be used for paged EMS memory.

Recommended action:  Change the /I or INCLUDE parameter.  (With the
Invisible LAN Setup program, this is done on the System Memory
Configuration screen.)




Requested frontfill size is out of range.

Explanation:  The value specified with the /F or FRONTFILL_SIZE
parameter is either too large or too small.

Recommended action:  Change the /F or FRONTFILL_SIZE parameter.  (With
the Invisible LAN Setup program, this is done on the Memory Manager
Parameters screen.)




Memory hardware does not provide page frames for requested frontfill.

Explanation:  The amount of frontfill requested by the /F or
FRONTFILL_SIZE parameter cannot be provided because one or more of the
required page frames is not available.

Recommended action:  Change the /F or FRONTFILL_SIZE parameter.  (With
the Invisible LAN Setup program, this is done on the Memory Manager
Parameters screen.)




Insufficient memory to perform frontfill.

Explanation:  The requested frontfill cannot be provided because all the
RAM in the computer was used up for backfill, shadow RAM, and high RAM.

Recommended action:  (1) Reduce the requested frontfill.  (2) Reduce the
amount of RAM used for backfill, shadow RAM, and high RAM.  (3) In the
case of Invisible RAM 386, reduce the amount of extended memory reserved
by the /E or EXTENDED parameter for the 386 control program.




No page frames available for requested non-standard pages.

Explanation:  The expanded memory manager cannot find any page frames to
use for the non-standard pages requested with the /P or NONSTANDARD_PAGE
parameter.

Recommended action:  (1) Try to change the addresses used by ROM and RAM
in your computer to free up more page frames.  You can use SHADOW /M to
help determine what ROM and RAM is present in your computer.  (2) Use
the /I or INCLUDE parameter to include additional page frames as paged
EMS memory.  (With the Invisible LAN Setup program, non-standard pages
are requested on the Memory Manager Parameters screen, and including
page frames as paged EMS memory is done on the System Memory
Configuration screen.)




Testing page frames: XXXX
Memory test failed.

Explanation:  The expanded memory manager was unable to read and write
memory in the page frame indicated by XXXX.

Recommended action:  (1) Check the switches and jumpers on your
computer's motherboard, and any memory expansion boards, to be sure they
are set correctly.  (2) Make sure that you ran your computer's set-up
program correctly.  (3) Check to see that the memory chips in your
computer are fast enough.  If necessary, replace the memory chips with
faster chips.




Testing memory: XXXX
Memory test failed.

Explanation:  An error was detected in testing the expanded memory.
XXXX indicates how much memory was successfully tested before the error
occurred.

Recommended action:  (1) Check the switches and jumpers on your
computer's motherboard, and any memory expansion boards, to be sure they
are set correctly.  (2) Make sure that you ran your computer's set-up
program correctly.  (3) Check to see that the memory chips in your
computer are fast enough.  If necessary, replace the memory chips with
faster chips.




Memory size set incorrectly.

Explanation:  The computer's memory is not functioning correctly.

Recommended action:  (1) Check the switches and jumpers on your
computer's motherboard, and any memory expansion boards, to be sure they
are set correctly.  (2) Make sure that you ran your computer's set-up
program correctly.  (3) Check to see that the memory chips in your
computer are fast enough.  If necessary, replace the memory chips with
faster chips.




EGA/VGA high resolution graphics have been disabled.
Use VGAON to enable high resolution graphics.

Explanation:  Invisible RAM is using the page frames required for
high-resolution graphics, thereby disabling high-resolution graphics.
This can be caused by (1) specifying /V=0 or Initial VGA State ON to
allow Invisible RAM to frontfill into the high resolution graphics
memory (segments A000-AFFF), or (2) using the /I or INCLUDE parameter to
create paged EMS memory within memory segments A000-AFFF.

Recommended action:  (1) Run the VGAON program before running an
application that uses high-resolution graphics.  (2) Configure your
applications to use low-resolution graphics (also called <MI>CGA
graphics) or text mode.  (3) Use the /X=A000-AFFF or EXCLUDE parameter
to prevent Invisible RAM from using the area of memory required for EGA
or VGA high-resolution graphics.  (4) Remove the /V=0 or Initial VGA
State ON parameter if you prefer for high-resolution graphics to be
enabled when Invisible RAM first loads.  (5) Remove the /I or INCLUDE
parameter that creates paged EMS memory in segments A000-AFFF, if you
want to be able to use high-resolution graphics (note that using
segments A000-AFFF for paged EMS memory permanently disables
high-resolution graphics;  you can't use VGAON if there is paged EMS
memory in segments A000-AFFF).




EGA/VGA high resolution graphics are enabled.
Use VGAOFF to disable high resolution graphics and increase DOS memory 
size.

Explanation:  DOS memory size is limited to 640K, because
high-resolution graphics uses the same page frames required to increase
DOS memory size above 640K.  However, you can increase DOS memory size
by using the VGAOFF program to disable high-resolution graphics.

Recommended action:  (1) Run the VGAOFF program to disable
high-resolution graphics and increase the size of DOS memory.  (2) Use
the /V=0 or Initial VGA State OFF parameter if you prefer to have
high-resolution graphics disabled at the time Invisible RAM first loads.



------------------------------------------------------------------------



2. 386 Control Program Installation Error Messages




Invalid parameters.

Explanation:  You are installing the 386 control program from
CONFIG.SYS.  One or more parameters on the CP386.SYS command line are
invalid, or given in incorrect form, or have unacceptable values.

Recommended action:  Edit the CONFIG.SYS file and correct the erroneous
parameters.  If you don't know which parameters are erroneous, remove
all parameters from the CP386.SYS command line, and then add them back
one-by-one.




This program requires an 80386 or 80486.

Explanation:  Your computer does not have an 80386, 80386SX, or 80486
microprocessor.

Recommended action:  Use a computer with an 80386, 80386SX, or 80486
microprocessor.




Insufficient extended memory.

Explanation:  There is not enough extended memory to install the 386
control program.

Recommended action:  (1) Reduce the amount of extended memory reserved
with the /E or EXTENDED parameter.  (2) Reduce the size of the DMA data
buffers.  (3) Add more extended memory to your computer.




Ctrl-Alt-Shift detected.  At user request, program will not install.

Explanation:  You pressed Ctrl-Alt-Shift.  Invisible RAM 386 does not
load if these keys are pressed.

Recommended action:  None.




The 386/486 Control Program is already installed.

Explanation:  You tried to install the 386 control program when it has
already been installed.

Recommended action:  Do not try to install more than one 386 control
program.




Cannot determine DMA controller type (standard PC or Micro Channel).

Explanation:  When the 386 control program is installed, it needs to
determine whether your computer has the Industry Standard Architecture
(ISA) or the Micro Channel Architecture (MCA).  This error message
indicates that the 386 control program was not able to make the required
determination.

Recommended action:  Write down the make and model of computer that you
have, and contact Invisible Software technical support.




Fixed disk read error - cannot determine fixed disk DMA channel.

Explanation:  When the 386 control program is installed, it needs to
determine which DMA channel is used by your hard disk, if any.  This
error message indicates that the 386 control program was not able to
make the determination because a disk read error occurred.

Recommended action:  Correct the problem with your hard disk.  Make sure
that the hard disk is correctly formatted, and that the disk type is
correctly specified in your computer's set-up program.




Cannot determine fixed disk DMA channel.

Explanation:  When the 386 control program is installed, it needs to
determine which DMA channel is used by your hard disk, if any.  This
error message indicates that the 386 control program was not able to
make the required determination.

Recommended action:  Write down the make and model of your computer and
hard disk, and contact Invisible Software technical support.




XMS interface already installed.

Explanation:  The 386 control program cannot be installed, because an
XMS (eXtended Memory Specification) device driver has already been
installed.

Recommended action:  Remove the XMS device driver, and enable the XMS
interface that is built in to the 386 control program.



------------------------------------------------------------------------



3. 386 Control Program Run-Time Error Messages



Run-time error messages occur after the 386 control program is
installed.  They indicate a condition that makes it impossible for the
386 control program to continue executing.

When a run-time error occurs, CP386 (the 386 control program) halts
execution of the system and displays the following information:

     * An error code. This numerical code identifies the exact cause of
       the error.

     * An error message. This message describes the general nature of
       the error.

     * A diagnostic memory dump. This is a hexadecimal display of the
       contents of certain memory locations internal to CP386.  In some
       cases, Invisible Software personnel can use the diagnostic memory
       dump to help determine the source of an error.

After a run-time error, it is not possible to continue executing your
application program.  You must re-boot the system, either by pressing
Ctrl-Alt-Del or by turning off the power.




CP386 fatal system failure:  Error code 12-1

Stack error (exception 0C hex)

Explanation:  A stack exception occurred while executing the CP386
kernel.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 12-2

Stack error (exception 0C hex)

Explanation:  A stack exception occurred while executing the real-mode
application.

Recommended action:  One of your DOS programs has a bug in it, or has
crashed.




CP386 fatal system failure:  Error code 13-1

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
the CP386 kernel.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-2

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, and the CP386 kernel cannot read the limit of the
offending code segment.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-3

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, and the CP386 kernel cannot read the access rights
of the offending code segment.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-4

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, and the CP386 kernel cannot read the offending
instruction because the offending code segment is marked execute-only.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-5

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred because an attempt
was made to execute past the end of the code segment.  This can occur in
both real-mode and protected-mode code.

Recommended action:  There is probably a bug in your DOS application
program, or in a DOS memory-resident program (TSR) or device driver.
Try to determine which program is causing the error.

Most likely, this error message is revealing a bug that has always been
present in the DOS program, but has never been noticed before.  Running
the 386 in virtual mode tends to reveal latent bugs, because the 386
virtual mode enforces programming rules more strictly than the normal
mode.  Some things that might fix the problem are:  (1) If the program
was loaded into shadow RAM, try loading it into DOS memory instead.  (2)
Load programs in a different order.  (3) Make the program load in a
different address by changing some CONFIG.SYS parameters.




CP386 fatal system failure:  Error code 13-6

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred because an attempt
was made to execute a priveleged 80386 instruction, or an invalid
instruction.  This can occur in both real-mode and protected-mode code.

Recommended action:  A DOS application program may have tried to switch
the processor into protected mode, or tried to use special features of
the 80386.  See if the application can be configured not to do this.

More likely, however, the DOS program has simply crashed.  This error
message may be revealing a bug that has always been present in the DOS
program, but has never been noticed before.  Running the 386 in virtual
mode tends to reveal latent bugs, because the 386 virtual mode enforces
programming rules more strictly than the normal mode.  Some things that
might fix the problem are:  (1) If the program was loaded into shadow
RAM, try loading it into DOS memory instead.  (2) Load programs in a
different order.  (3) Make the program load in a different address by
changing some CONFIG.SYS parameters.




CP386 fatal system failure:  Error code 13-7

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred because an attempt
was made to read a non-existent 80386 control register.  This can occur
in both real-mode and protected-mode code.

Recommended action:  There is probably a bug in your DOS application
program.  Try to determine which program is causing the error.




CP386 fatal system failure:  Error code 13-8

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred because an attempt
was made to read a non-existent 80386 debug register.  This can occur in
both real-mode and protected-mode code.

Recommended action:  There is probably a bug in your DOS application
program.  Try to determine which program is causing the error.




CP386 fatal system failure:  Error code 13-9

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred because an attempt
was made to write a non-existent 80386 debug register.  This can occur
in both real-mode and protected-mode code.

Recommended action:  There is probably a bug in your DOS application
program.  Try to determine which program is causing the error.




CP386 fatal system failure:  Error code 13-10

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred because an attempt
was made to execute a priveleged 80386 instruction, or an invalid
instruction.  This can occur in both real-mode and protected-mode code.

Recommended action:  A DOS application program may have tried to switch
the processor into protected mode, or tried to use special features of
the 80386.  See if the application can be configured not to do this.

More likely, however, the DOS program has simply crashed.  This error
message may be revealing a bug that has always been present in the DOS
program, but has never been noticed before.  Running the 386 in virtual
mode tends to reveal latent bugs, because the 386 virtual mode enforces
programming rules more strictly than the normal mode.  Some things that
might fix the problem are:  (1) If the program was loaded into shadow
RAM, try loading it into DOS memory instead.  (2) Load programs in a
different order.  (3) Make the program load in a different address by
changing some CONFIG.SYS parameters.




CP386 fatal system failure:  Error code 13-11

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
real-mode code, because an attempt was made to read or write past the
end of the data segment (i.e., to an offset greater than 0FFFFH).

Recommended action:  There is probably a bug in your DOS application
program.  Try to determine which program is causing the error.

Most likely, this error message is revealing a bug that has always been
present in the DOS program, but has never been noticed before.  Running
the 386 in virtual mode tends to reveal latent bugs, because the 386
virtual mode enforces programming rules more strictly than the normal
mode.  Some things that might fix the problem are:  (1) If the program
was loaded into shadow RAM, try loading it into DOS memory instead.  (2)
Load programs in a different order.  (3) Make the program load in a
different address by changing some CONFIG.SYS parameters.




CP386 fatal system failure:  Error code 13-12

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, and the CP386 kernel cannot read the access rights
of the offending data segment.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-13

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, and the offending data segment has an invalid type
code in its segment descriptor.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-14

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, because an attempt was made to write into a
read-only data segment.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-15

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, and the CP386 kernel cannot read the limit of the
offending data segment.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-16

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, because an attempt was made to read or write
outside the data segment limit.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-17

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, because an attempt was made to write into a code
segment.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 13-18

General protection error (exception 0D hex)

Explanation:  A general protection exception occurred while executing
protected-mode code, because an attempt was made to read from an
execute-only code segment.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 32-1

DMA channel x requires a buffer of at least yyK

Explanation:  An attempt was made to perform a DMA operation too large
to fit in the DMA data buffer.  In the error message, x indicates the
offending DMA channel number, and yy gives the buffer size, in
kilobytes, that would be required for the DMA operation to proceed.

Recommended action:  Use the appropriate parameter on the CP386 command
line to increase the buffer size for the offending DMA channel.  For
example, if the error message is "DMA channel 3 requires a buffer of at
least 48K", you would specify the parameter /3=48 on the CP386 command
line;  or else put CP386.DMA_3_BUFFER_SIZE=48 in the initialization
file;  or set DMA Channel 3 Buffer Size to 48 on the 386 Control Program
Parameters screen in the Invisible LAN Setup program.




CP386 fatal system failure:  Error code 33-1

Unexpected operating system service call (interrupt 5B hex)

Explanation:  The CP386 kernel attempted to call itself recursively.

Recommended action:  Write down the diagnostic memory dump and contact
Invisible Software technical support.




CP386 fatal system failure:  Error code 34-1

Exhausted resources for handling hardware interrupts

Explanation:  There were no kernel interrupt stack frames available to
handle a hardware interrupt.

Recommended action:  Increase the number of hardware interrupt stacks.
When loading CP386 from CONFIG.SYS, increase the value of the /S
parameter on the CP386 command line.  When loading CP386 using the NET30
command, increase the STACKS parameter.




CP386 fatal system failure:  Error code 34-2

Exhausted resources for handling hardware interrupts

Explanation:  There were no real-mode interrupt stack frames available
to handle a hardware interrupt.

Recommended action:  Increase the number of hardware interrupt stacks.
When loading CP386 from CONFIG.SYS, increase the value of the /S
parameter on the CP386 command line.  When loading CP386 using the NET30
command, increase the STACKS parameter.




CP386 fatal system failure:  Error code 34-3

Exhausted resources for handling hardware interrupts

Explanation:  An error occurred while attempting to free a real-mode
interrupt stack frame at the conclusion of a hardware interrupt handler.

Recommended action:  There is probably a bug in a DOS device driver,
memory-resident program (TSR), or application program.  Try to determine
which program is causing the error.




CP386 fatal system failure:  Error code 35-1

Unable to process software interrupt xx hex

Explanation:  The CP386 kernel attempted to execute an invalid software
interrupt (INT) instruction.  In the error message, xx indicates which
software interrupt was attempted.

This error message may also indicate that your computer's extended
memory is not working reliably.

Recommended action:  Try reducing your computer's clock rate, or
increasing the number of wait states for the system memory.  If your
computer has a memory cache, try disabling the cache.  If the error
persists, write down the diagnostic memory dump and contact Invisible
Software technical support.




CP386 fatal system failure:  Error code 35-2

Unable to process software interrupt xx hex

Explanation:  Real-mode code attempted to execute a software interrupt
(INT) instruction, but there was insufficient stack space to process the
instruction.  In the error message, xx indicates which software
interrupt was attempted.

Recommended action:  There is probably a bug in a DOS device driver,
memory-resident program (TSR), or application program.  Try to determine
which program is causing the error.



------------------------------------------------------------------------



4. LSHADOW.SYS Error Messages




Invalid parameters.

Explanation:  The parameters you entered on the LSHADOW.SYS command line
are invalid.

Recommended Action:  Correct the parameters.




LSHADOW:  Shadow RAM manager not installed.

Explanation:  LSHADOW.SYS cannot be used because (a) Invisible RAM is
not installed, or (b) Invisible RAM did not create any shadow RAM.

Recommended Action:  Only use LSHADOW.SYS after Invisible RAM is
installed, and configured to create shadow RAM.  Remember that in order
to use LSHADOW.SYS, you need to install Invisible RAM from the
CONFIG.SYS file.




LSHADOW:  No shadow RAM is available for loading memory-resident
programs.

Explanation:  LSHADOW.SYS cannot be used because Invisible RAM did not
create any shadow RAM.

Recommended Action:  Only use LSHADOW.SYS if Invisible RAM is configured
to create shadow RAM.




LSHADOW:  Insufficient memory.

Explanation:  The isn't enough shadow RAM to install the device driver.

Recommended Action:  Check to see if you can create more shadow RAM.  If
you can't, then use DOS memory instead.




LSHADOW:  Bad or missing device driver.

Explanation:  The device driver you specified on the LSHADOW.SYS command
line could not be found, or could not be read.

Recommended Action:  Make sure that you entered the device driver name
correctly, including the .SYS extension.




LSHADOW:  Device driver uses too much memory.  System halted.

Explanation:  The isn't enough shadow RAM to run the device driver.

Recommended Action:  Check to see if you can create more shadow RAM.  If
you can't, then use DOS memory instead.
