                ERROR MESSAGES FOR NETWORK INSTALLATION

                Copyright 1993 Invisible Software, Inc.



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



This file describes the error messages that you may encounter when
starting Invisible LAN.  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. NET30 installation error messages
2. SHARE installation error messages
3. TransBIOS installation error messages
4. Disk Cache installation error messages
5. Server installation error messages
6. Redirector installation error messages
7. Mail installation error messages



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



1. NET30 Installation Error Messages




Invalid DOS environment.

Explanation:  NET30 cannot execute because of an unexpected DOS error.

Recommended Action:  Reboot the computer, then retry the command.  If
the error persists, you may have an invalid copy of DOS.




Unexpected DOS error while locating origin directory.

Explanation:  NET30 cannot execute because of an unexpected DOS error.

Recommended Action:  Reboot the computer, then retry the command.  If
the error persists, you may have an invalid copy of DOS.




Cannot open initialization file.

Explanation:  NET30 cannot access the specified initialization file.

Recommended Action:  If you entered an initialization file name on the
command line, make sure you entered the correct name.  Type NET30<N>?
if you need help.




Invalid parameter on DOS command line.

Explanation:  You entered an incorrect parameter on the NET30 command
line.

Recommended Action:  Correct the parameter.  Type NET30<N>?  if you need
help.




DOS error while reading initialization file.

Explanation:  A disk error occurred while reading the Invisible LAN
initialization file.

Recommended Action:  Retry the command.  If the error recurs, you may
need to re-create the initialization file.




Initialization file too large.

Explanation:  There are too many parameters in the initialization file.

Recommended Action:  Edit the initialization file, and eliminate
incorrect or unnecessary parameters.




Error in initialization file at line xxx.
Invalid parameter.

Explanation:  A parameter in the initialization file is incorrect.  In
the error message, xxx denotes the line number that contains the
incorrect parameter.  This message has many possible causes, including:
(1) a parameter with invalid value;  (2) a parameter with an
unrecognized keyword;  (3) a parameter with incorrect syntax;  (4) a
memory manager parameter that is invalid for the type of memory hardware
(for example, specifying ROM COPY for Invisible EMS or Generic EMS;  or
attempting to create paged EMS memory with AT/386 chipset or Generic
EMS;  or specifying an I/O port for any memory hardware other than
Invisible EMS).

Recommended Action:  Correct the invalid parameter.  You may want to use
a text editor to look at the initialization file.




Error in initialization file at line xxx.
Conflicting parameters.

Explanation:  Two or more parameters in the initialization file conflict
with each other.  In the error message, xxx denotes the line number that
contains one of the conflicting parameters.

Recommended Action:  Correct the invalid parameter.  You may want to use
a text editor to look at the initialization file.




Parameter NET30.HARDWARE= is missing from initialization file.

Explanation:  The initialization file does not specify what type of
network hardware to use.

Recommended Action:  Edit the initialization file, and add the required
parameter.




Parameter CACHE.DATA_LOCATION= is missing from initialization file.

Explanation:  The initialization file specifies that the disk cache
should be loaded, but does not specify whether the cache data should be
in expanded or extended memory.

Recommended Action:  Edit the initialization file, and add the required
parameter.




No programs loaded.

Explanation:  The initialization file does not request any programs to
be installed.

Recommended Action:  Correct the initialization file.




Device driver N30DEV.SYS is not installed.

Explanation:  The DEVICE=N30DEV.SYS statement is missing from the
CONFIG.SYS file.

Recommended Action:  Edit the CONFIG.SYS file, and add
DEVICE=N30DEV.SYS.  Note that this must be the last DEVICE statement in
the CONFIG.SYS file.




Memory configuration is too complex, remove some EMM.XXXX= parameters.

Explanation:  Too many parameters are specified for the memory manager.

Recommended Action:  Edit the configuration file, and remove unnecessary
memory manager parameters.  See if parameters that specify individual
page frames can be consolidated by specifying a range of page frames.




NET30:  Unable to perform program load.

Explanation:  NET30 cannot load the network programs due to an
unexpected DOS error.

Recommended Action:  If you are using a replacement for COMMAND.COM, try
removing it.




NET30:  Cannot find program file filename.

Explanation:  One of the Invisible LAN program files is missing.  In the
message, filename is the name of the missing program file.

Recommended Action:  Get your original Invisible LAN diskettes, and copy
the missing file into the directory where you keep Invisible LAN.




NET30:  Cannot execute program file filename.

Explanation:  NET30 cannot load one of the Invisible LAN program files.
In the message, filename is the name of the program file.

Recommended Action:  The program file may be corrupted.  Get your
original Invisible LAN diskettes, and make a fresh copy of the program
file.



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



2. SHARE Installation Error Messages




LSHADOW:  Execute error.

Explanation:  You tried to load SHARE into shadow RAM, but an error
occured while trying to execute SHARE.EXE.

Recommended Action:  Your copy of SHARE.EXE may be corrupted.  Make a
fresh copy from your original DOS diskettes.




LSHADOW:  File not found.

Explanation:  You tried to load SHARE into shadow RAM, but the program
file SHARE.EXE is not in the directory where the Invisible LAN program
files are kept.

Recommended Action:  Copy SHARE.EXE into the directory where you keep
the Invisible LAN program files.




LSHADOW:  Insufficient memory.

Explanation:  You tried to load SHARE into shadow RAM, but there is
insufficient shadow RAM available.

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




LSHADOW:  Invalid format.

Explanation:  You tried to load SHARE into shadow RAM, but the SHARE.EXE
program file is corrupted.

Recommended Action:  Get your original DOS diskettes, and make a fresh
copy of SHARE.EXE.



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



3.  TransBIOS Installation Error Messages




System configuration too big - Reduce some parameters.

Explanation:  The resource allocation parameters are so big that
TransBIOS cannot fit into available memory.

Recommended Action:  Reduce the values of TransBIOS Applications,
Sessions, Names, Polls, or Responses.  Also reduce the values of NetBIOS
Sessions, Names, and Commands.




No expanded memory manager installed.

Explanation:  You attempted to load TransBIOS into EMS, but there is no
expanded memory installed in the system.

Recommended Action:  Install the expanded memory software, or else load
TransBIOS into shadow RAM or DOS memory instead of EMS.




This program requires expanded memory version 4.0 or later.

Explanation:  You attempted to load TransBIOS into EMS, but your
expanded memory software is not version 4.0.

Recommended Action:  Get updated expanded memory software, or else load
TransBIOS into shadow RAM or DOS memory instead of EMS.




Unable to allocate required amount of expanded memory.

Explanation:  You attempted to load TransBIOS into EMS, but there is
insufficient free expanded memory.

Recommended Action:  Free up some expanded memory, or add more expanded
memory;  or else load TransBIOS into shadow RAM or DOS memory instead of
EMS.




3050 Network:  Hardware failed.

Explanation:  This message only occurs on Model 300 series products.  It
means that a timeout occurred while TransBIOS was waiting for the
hardware to start up.  It may indicate an interrupt conflict, an I/O
port conflict, or a failure of the network controller chip.

Recommended Action:  Check to make sure that the interrupt (IRQ) jumper
is installed, and that the interrupt level does not conflict with any
other equipment in the computer.  Make sure the I/O port does not
conflict with any other cards.  If the error persists, try swapping out
the network card.




3051 Network:  Timer failed.

Explanation:  This message only occurs on Model 300 series products.  It
means that the built-in timer circuit is not working.  It may indicate
an I/O port conflict, or a failure of the network controller chip.

Recommended Action:  Check to make sure that the I/O port does not
conflict with any other equipment in the computer.  If the error
persists, try swapping out the network card.




3052 Network:  Interrupt failed.

Explanation:  The network hardware is not able to generate interrupts.
This probably indicates that there is an interrupt level conflict.  It
may also indicate that interrupt selection jumpers are missing, or that
the network hardware has failed.  In the case of an Ethernet unit that
plugs into the printer port, it may indicate that the printer port's
interrupt signal has reversed polarity (especially likely to happen if
you use a printer port that is built in to a monochrome video card).  In
the case of a Model 300 series product, this may indicate that the board
is not installed, or that there is an I/O port conflict.

Recommended Action:  Check to make sure that the interrupt level does
not conflict with any other equipment in the computer.  Make sure that
any jumpers used to select the interrupt level are correctly inserted.
Try selecting a different interrupt level.  In the case of an Ethernet
unit that plugs into a printer port, try using a different printer port.
In the case of a Model 300 series product, make sure that the board is
installed, and that the I/O port does not conflict with any other
equipment in the computer.  If the error persists, try swapping out the
network card.




3052 Network:  Cannot locate hardware interrupt.

Explanation:  This message only occurs on Token Ring hardware.  It means
that TransBIOS cannot determine which interrupt level the hardware is
using.

Recommended Action:  Go to the TransBIOS Parameters screen in the
Advanced Configuration section of SETUP30, and enter the interrupt
level.  Alternatively, you can use the TRCPARM environment variable to
specify the interrupt level (for example, SET TRCPARM=7 to specify
interrupt level 7).




3053 Network:  Unable to transmit.

Explanation:  The network hardware is unable to transmit packets onto
the network.  This may indicate an I/O port address conflict, or a
failure of the network hardware.  For hardware that uses DMA (direct
memory access), this may indicate a DMA channel conflict.

Recommended Action:  Check to make sure that the I/O port does not
conflict with any other equipment in the computer.  If possible, try
selecting a different I/O port.  If the network hardware uses DMA, make
sure that any required jumpers or switches are correctly set, and that
the selected DMA channel does not conflict with any other equipment.  If
possible, try selecting a different DMA channel.  Make sure that the
network cable is connected and properly terminated.  If the error
persists, try swapping out the network card.




3054 Network:  No heartbeat.

Explanation:  This message only occurs on Model 300 series products.  It
means that TransBIOS is not able to detect the heartbeat signal that is
transmitted by the master station.

Recommended Action:  Make sure that one, and only one, computer on the
network is set up as the master station.  Make sure that the master
station is turned on.  Make sure that the master station has a higher
address than any other station in the network.  Make sure that the cable
is properly connected, and properly terminated.  If the error persists,
try swapping out the network card.  If the error occurs on more than one
station, try swapping out the master station's network card.




3055 Network:  Invalid switch or jumper setting.

Explanation:  This message only occurs on Models 100, 200, and 300.  It
means that the switches and jumpers on the card are set incorrectly.
For example, this will occur on Model 200 if you use an invalid speed
setting;  or on Model 300 if you attempt to use a 16-bit DMA channel
when the board is set for 0.7 Mbps.

Recommended Action:  Check the switch and jumper settings, and correct
them.




3055 Network:  Invalid configuration data.

Explanation:  This message only occurs on Models 200/A and 300/A (Micro
Channel boards).  It means that setup configuration data is invalid.

Recommended Action:  Run the computer's setup program, and enter correct
configuration information.




3056 Network:  Loopback error.

Explanation:  This message only occurs on Model 300 series products.  It
means that data being transmitted by the card is not being received.
This probably indicates a failure of the line driver chips.  It may also
indicate a problem with the cable, or some other problem with the
network hardware.

Recommended Action:  Make sure that the cable is correctly connected and
terminated.  If the error persists, try swapping out the network
hardware.  If necessary, replace the line driver chips.




3057 Network:  Static RAM failed.

Explanation:  This message only occurs on hardware that has built-in RAM
(random-access memory).  For hardware that uses shared RAM (such as
Western Digital Ethernet and Invisible Ethernet VL), this probably
indicates a memory addressing conflict.  It may also indicate a problem
with bus timing.  Also, it could indicate a failure of the network
hardware.

Recommended Action:  If your network hardware uses shared RAM, then:
(a) make sure the memory address does not conflict with any other
equipment in the computer;  (b) if you are using a 386 memory manager,
make sure to "exclude" the memory range used by the network hardware;
and (c) try changing the memory address, either by reconfiguring the
network hardware or by using the TransBIOS Parameters screen in the
Advanced Configuration section of SETUP30.  If your network hardware has
any bus timing adjustments (often called something like "turbo mode", or
"early mode", or "wait state"), try changing the bus timing.  If your
computer's BIOS has the ability to adjust bus wait states, it may help
to increase the wait states for 16-bit bus cycles.  If the problem
persists, try swapping out the network hardware.




3058 Network:  Invalid station address setting.

Explanation:  This message only occurs on hardware that uses switches to
select the station address.  It means that the switches have been set to
an invalid address.

Recommended Action:  Check the switches that are used to select the
station address, and make sure they are set correctly.




3060 Network:  DIR.INITIALIZE command failed.

Explanation:  This message only occurs on Token Ring hardware.  It means
that TransBIOS could not initialize the Token Ring adapter.

Recommended Action:  Make sure that the Token Ring hardware is correctly
installed and configured, that the cable is properly connected, and that
the IBM LAN Support Program is correctly installed.  Make sure that
there are no interrupt conflicts, I/O port conflicts, or memory address
conflicts.  If you have any programs installed that use the 802.2
interface, try removing them.




3060 Network:  RESET command failed.

Explanation:  This message only occurs with the NDIS driver.  It means
that TransBIOS could not initialize the network hardware.

Recommended Action:  Make sure that the network hardware and the NDIS
hardware driver are correctly installed.




3061 Network:  DIR.OPEN.ADAPTER command failed.

Explanation:  This message only occurs on Token Ring hardware.  It means
that the Token Ring adapter did not begin operation when TransBIOS
commanded it to do so.

Recommended Action:  Make sure that the Token Ring hardware is correctly
installed and configured, that the cable is properly connected, and that
the IBM LAN Support Program is correctly installed.  Make sure that
there are no interrupt conflicts, I/O port conflicts, or memory address
conflicts.  If you have any programs installed that use the 802.2
interface, try removing them.




3061 Network:  OPEN ADAPTER command failed.

Explanation:  This message only occurs with the NDIS driver.  It means
that the network adapter did not begin operation when TransBIOS
commanded it to do so.

Recommended Action:  Make sure that the network hardware and the NDIS
hardware driver are correctly installed.




3062 Network:  DIR.OPEN.ADAPTER command reports insufficient buffer RAM.

Explanation:  This message only occurs on Token Ring hardware.  It means
that the Token Ring adapter does not have sufficient buffer RAM to
support TransBIOS.  This should never happen, since TransBIOS can run
with the minimum 8K of buffer RAM.

Recommended Action:  Make sure that the Token Ring hardware is correctly
installed and configured, that the cable is properly connected, and that
the IBM LAN Support Program is correctly installed.  Make sure that
there are no interrupt conflicts, I/O port conflicts, or memory address
conflicts.  If you have any programs installed that use the 802.2
interface, try removing them.




3070 Network:  Presence test failed.

Explanation:  TransBIOS could not detect the network hardware.  This may
indicate that the hardware is not installed, or that there is an I/O
port conflict.  It may also indicate a hardware failure.

Recommended Action:  Make sure that the network hardware is installed.
Make sure that the I/O address used by the network hardware does not
conflict with any other hardware in the computer.  If the network
hardware requires an external power source (like many Ethernet units
that plug in to the printer port), make sure the power source is
connected and turned on.  Try entering the network hardware's I/O
address into the TransBIOS Parameters screen in the Advanced
Configuration section of SETUP30.  If the problem persists, try swapping
out the network hardware.




3070 Network:  Adapter support program not installed.

Explanation:  This message only occurs on Token Ring hardware.  It means
that the IBM LAN Support Program is not installed.

Recommended Action:  Install the IBM LAN Support Program.
(Alternatively, you can install TOKREUI.) If you have any programs
installed that use the 802.2 interface, try removing them.




3070 Network:  NDIS protocol driver not installed or not bound.

Explanation:  This message only occurs with the NDIS driver.  It means
that you have not installed the NDIS hardware driver, the NDIS protocol
manager (PROTMAN.DOS), or the TransBIOS NDIS protocol driver
(TBPROTO.DOS);  or that you have not run the NETBIND program.

Recommended Action:  Install the NDIS hardware driver, the NDIS protocol
manager (PROTMAN.DOS), and the TransBIOS NDIS protocol driver
(TBPROTO.DOS).  Make sure that you include the NETBIND command in your
AUTOEXEC.BAT file.  Refer to HARDWARE.TXT for instructions on installing
the drivers and creating the required PROTOCOL.INI file.




3071 Network:  Hardware failed.

Explanation:  This message only occurs on Model 300 series products.  It
means that TransBIOS is not able to identify which model is installed.

Recommended Action:  Make sure the network board's I/O port does not
conflict with any other cards.  If the error persists, try swapping out
the network card.




3071 Network:  Incompatible hardware type.

Explanation:  This message only occurs with the NDIS driver.  It means
the network hardware is something other than Ethernet or Token Ring.
The NDIS driver only supports Ethernet or Token Ring hardware.

Recommended Action:  Use Ethernet or Token Ring hardware.  If you want
to use some other type of hardware (such as ARCNET), you may be able to
obtain an NDIS driver that "pretends" to be an Ethernet driver;  you
should be able to run TransBIOS on any driver that "pretends" to be an
Ethernet driver.




3080 Network:  Copyright violation.

Explanation:  You are using the serialized version of Invisible LAN, and
you are trying to use the same copy of the software on two different
network stations.

Recommended Action:  Buy a separate copy of the software for each
network station.  Make sure that you use a different serial number on
each station.  You can display your serial number with the following DOS
command:  TYPE SERIAL.DAT.




3083 Network:  Duplicate address.

Explanation:  Two network stations are set to use the same address.
This should only happen on hardware that uses switches to select the
station address.

Recommended Action:  Set the switches so that each station in the
network has a different address.



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



4. Disk Cache Installation Error Messages




No expanded memory (EMS) in this computer.

Explanation:  You are attempting to install the cache in expanded
memory, but there is no expanded memory in the computer.

Recommended action:  Either install some expanded memory, or else
install the cache in extended memory.




This program requires expanded memory (EMS) version 4.0.

Explanation:  You are attempting to install the cache in expanded
memory, and there is expanded memory in the computer, but you have the
wrong version of expanded memory.

Recommended action:  Obtain updated expanded memory software.




No extended memory in this computer.

Explanation:  You are attempting to install the cache in extended
memory, but there is no extended memory in the computer.

Recommended action:  Either install some extended memory, or else
install the cache in expanded memory.  If you are using Invisible RAM
386, make sure to reserve some extended memory for the cache to use
(using the Reserved Extended Memory parameter for the 386 control
program).




No fixed disk in this computer.

Explanation:  The disk cache does not work with floppy disks, so you
must have a hard disk in order to use the cache.

Recommended action:  Install a hard disk.




Insufficient memory to install cache.

Explanation:  There is not enough expanded or extended memory to install
the cache.

Recommended action:  Install more memory.  You may also be able to
install the cache by reducing the value of the Associativity parameter.




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

Explanation:  The cache program cannot determine if your computer has a
standard expansion bus or a Micro Channel expansion bus.

Recommended action:  Write down the make and model of computer you are
using and contact Invisible Software technical support.




Error reading fixed disk.

Explanation:  The cache program could not read the boot sector from the
hard disk.

Recommended action:  Check for possible malfunctions of the hard disk.
Check to make sure that all the disk cables are securely connected.
Make sure that the hard disk has been properly formatted.  Run any disk
diagnostic programs that you have.




Error reading fixed disk partition table.

Explanation:  The cache program could not read the partition table from
the hard disk.

Recommended action:  Check for possible malfunctions of the fixed disk.
Check to make sure that all the disk cables are securely connected.
Make sure that the hard disk has been properly formatted.  Run any disk
diagnostic programs that you have.




Invalid or inconsistent disk partition table.

Explanation:  The cache program could not understand the contents of the
hard disk partition table.

Recommended action:  Make sure that you partitioned the hard disk
correctly.




Cannot determine fixed disk DMA channel.

Explanation:  The cache program cannot determine which DMA (direct
memory access) channel, if any, is used by the hard disk.

Recommended action:  Write down the make and model of computer and disk
controller you are using and contact Invisible Software technical
support.




Error allocating expanded memory (EMS).

Explanation:  You are attempting to install the cache in expanded
memory, but the expanded memory software was not able to supply any
expanded memory.

Recommended action:  Make sure that your expanded memory software is
correctly installed, and that there is some free expanded memory.




Device driver CACHE30.SYS is not installed.

Explanation:  You did not place the DEVICE=CACHE30.SYS command in the
CONFIG.SYS file, or else the CACHE30.SYS program is missing.

Recommended action:  Make sure that DEVICE=CACHE30.SYS is in the
CONFIG.SYS file, and that CACHE30.SYS is on the disk.  Note that
CACHE30.SYS must be the first device driver installed.




Device driver CACHE30.SYS is not the first device driver installed.

Explanation:  The DEVICE=CACHE30.SYS command is not the first DEVICE=
statement in the CONFIG.SYS file.

Recommended action:  Place the DEVICE=CACHE30.SYS command at the start
of the CONFIG.SYS file.



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



5. Server Installation Error Messages




Network card is not present or not working.

Explanation:  The network hardware is not installed or malfunctioning;
or else the TransBIOS/NetBIOS software is not installed.

Recommended Action:  Check that the network hardware and software is
installed and operating.




This program requires TransBIOS/NetBIOS version 4.0 or later.

Explanation:  You have an incorrect version of the TransBIOS/NetBIOS
software.

Recommended Action:  Use the correct version of the software.




Unable to use the specified machine name.

Explanation:  The server cannot register your user name with the
network.

Recommended Action:  Select a different user name.




This station is already using the name.

Explanation:  The server cannot register your user name with the
network.

Recommended Action:  Select a different user name.




Another station is already using the name.

Explanation:  The server cannot register your user name with the
network, because someone else is already using the name.

Recommended Action:  Select a different user name.




Local name table is full.

Explanation:  The server cannot register your user name with the
network, because the TransBIOS or NetBIOS name limit has been exhausted.

Recommended Action:  Increase TransBIOS Names parameter, or the NetBIOS
Names parameter.




This program requires DOS 3.10 or later.

Explanation:  The server requires that you use DOS version 3.10 or
higher.

Recommended Action:  Update to a later version of DOS.




You must give the DOS SHARE command before running this program.

Explanation:  SHARE is not installed.  The server requires SHARE.

Recommended Action:  Install SHARE.




Unable to set the DOS sharing retry count.

Explanation:  An unexpected DOS error occurred.

Recommended Action:  If the error recurs, your copy of DOS may be
corrupted.  Get your original DOS diskettes, and make a fresh copy of
DOS.




Network operating system is already installed.

Explanation:  The server cannot be installed, because network software
is already installed.

Recommended Action:  Reboot the system if you want to re-install the
server.




The machine name is limited to a maximum of 15 characters.

Explanation:  The user name you specified is too long.

Recommended Action:  Correct the user name.




Server cannot be installed because DOS PRINT is already installed.

Explanation:  The DOS PRINT command is not compatible with the network.

Recommended Action:  Do not install PRINT.  You can use NETPRINT
instead.




Server cannot be installed because DOS ASSIGN is already installed.

Explanation:  The DOS ASSIGN command cannot be installed before the
server.

Recommended Action:  Do not use ASSIGN until after the server is
installed.




Server cannot be installed because DOS APPEND is already installed.

Explanation:  The DOS APPEND command cannot be installed before the
server.

Recommended Action:  Do not use APPEND until after the server is
installed.




This program requires Expanded Memory (EMS) version 4.0.

Explanation:  You attempted to load the server into expanded memory, but
there is no expanded memory installed, or the expanded memory is not
version 4.0.

Recommended Action:  Install the expanded memory hardware and software,
and make sure your expanded memory software is version 4.0 or higher;
or else load the server into shadow RAM or DOS memory instead of EMS.




Unable to allocate EMS memory and handles.

Explanation:  You attempted to load the server into expanded memory, but
there is insufficient free expanded memory available.

Recommended Action:  Add more expanded memory;  or else load the server
into shadow RAM or DOS memory instead of EMS.




Invalid spool device name.

Explanation:  You specified an invalid device name for one of the
network printer.

Recommended Action:  Correct the parameter.




Invalid DOS environment.

Explanation:  The server could not be installed due to an unexpected DOS
error.

Recommended Action:  If you are using a replacement for COMMAND.COM,
remove it.




Cannot specify the same device name twice.

Explanation:  You specified the same device for both network printers.

Recommended Action:  Edit the initialization file, and correct the
parameters.




Unable to add the Remote Program Load Server name IBMNETBOOT.

Explanation:  The RPL Server could not be started because the network
refused to register its name.

Recommended Action:  Try to determine the source of the error.




This station is already a Remote Program Load Server.

Explanation:  The RPL Server could not be started because the network
refused to register its name.

Recommended Action:  Try to determine the source of the error.




Another station is already a Remote Program Load Server.

Explanation:  The RPL Server could not be started another station on the
network is already running the RPL Server.  Only one station can be an
RPL Server.

Recommended Action:  Do not start the RPL Server on more than one
station.




Error reading the RPL image file.

Explanation:  You attempted to start the RPL Server, but a DOS error
occured while reading the boot diskette image file.

Recommended Action:  Retry the command.  If the error recurs, you may
need to re-create the boot diskette image file.




Cannot open the RPL image file:  Access denied.

Explanation:  You attempted to start the RPL Server, but an unexpected
DOS error occurred while opening the boot diskette image file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot open the RPL image file:  No file handles available.

Explanation:  You attempted to start the RPL Server, but DOS has no
handles available to open the boot diskette image file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot open the RPL image file:  File not found.

Explanation:  You attempted to start the RPL Server, but the boot
diskette image filename you specified could not be found.

Recommended Action:  Make sure you entered the correct filename in the
Server's RPL parameter.




Cannot open the RPL image file:  Path not found.

Explanation:  You attempted to start the RPL Server, but the boot
diskette image filename you specified contains an invalid directory
path.

Recommended Action:  Make sure you entered the correct filename in the
Server's RPL parameter.




Cannot open security file BINDERY.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while reading security
information.

Recommended Action:  Reboot the computer and retry the operation.




Cannot open security file BINDERY.DAT:  No file handles available.

Explanation:  DOS has no handles available to open the security system
file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot open security file BINDERY.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while reading security
information.

Recommended Action:  Reboot the computer and retry the operation.




Error creating security file BINDERY.DAT.

Explanation:  An unexpected DOS error occurred while creating a new
security system.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create security file BINDERY.DAT:  Disk full.

Explanation:  The server could not create a new security system, because
the server's disk is full.

Recommended Action:  Free up some disk space, and delete the BINDERY.DAT
file.  Then reboot the computer and retry the operation.




Cannot create security file BINDERY.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while creating a new
security system.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create security file BINDERY.DAT:  No file handles available.

Explanation:  DOS has no handles available to create a new security
system file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot create security file BINDERY.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while creating a new
security system.

Recommended Action:  Reboot the computer and retry the operation.




Security file BINDERY.DAT is corrupted.

Explanation:  The security information has been corrupted.

Recommended Action:  Delete BINDERY.DAT.  Then reboot the computer and
retry the operation.  You will have to re-create the security system.




Incorrect version of security file BINDERY.DAT.

Explanation:  The security information has been corrupted;  or else the
security information is not compatible with the server software version.

Recommended Action:  Use the correct version of the server software.  If
the security information is corrupted, delete BINDERY.DAT.  Then reboot
the computer and retry the operation.  You will have to re-create the
security system.




Error in initialization file at line xxx. 
Invalid parameter.

Explanation:  A parameter in the initialization file is incorrect.  In
the error message, xxx denotes the line number that contains the
incorrect parameter.  This message has many possible causes, including:
(1) a parameter with invalid value;  (2) a parameter with an
unrecognized keyword;  (3) a parameter with incorrect syntax.

Recommended Action:  Correct the invalid parameter.  You may want to use
a text editor to look at the initialization file.




Error in initialization file at line xxx. 
Conflicting parameters.

Explanation:  Two or more parameters in the initialization file conflict
with each other.  In the error message, xxx denotes the line number that
contains one of the conflicting parameters.

Recommended Action:  Correct the invalid parameter.  You may want to use
a text editor to look at the initialization file.




Parameter NET30.NAME= is missing from initialization file.

Explanation:  The initialization file does not specify a user name.

Recommended Action:  Edit the initialization file, and add the required
parameter.




User name is too long or contains invalid characters.

Explanation:  The user name parameter you specified is invalid.

Recommended Action:  Edit the initialization file and correct the user
name.




Cannot specify network printer #2 without specifying network printer #1.

Explanation:  You specified a device for network printer #2, but you did
not specify a device for network printer #1.  If you only want one
network printer, it must be network printer #1.

Recommended Action:  Edit the initialization file, and correct the
parameters.




Cannot specify same device for printer #1 and printer #2.

Explanation:  You entered the same device name for both network
printers.

Recommended Action:  Edit the initialization file, and correct the
parameters.




Spool directory must include complete drive and path.

Explanation:  You specified a value for the Spool Directory parameter,
but you did not include a complete drive and path specification.

Recommended Action:  Change the Spool Directory parameter so it includes
a complete drive and path specification.




Spool directory is not valid.

Explanation:  You specified a value for the Spool Directory parameter,
but the value is not a valid drive and path specification.

Recommended Action:  Edit the initialization file, and correct the
parameter.




Spool directory path not found.

Explanation:  You specified a value for the Spool Directory parameter,
but the directory path you specified could not be found.

Recommended Action:  Make sure you specified the correct value for the
Spool Directory parameter.




Remote program load filename must include complete drive and path.

Explanation:  You specified a value for the RPL parameter, but the value
you specified does not include a complete drive and path specification.

Recommended Action:  Change the RPL parameter so it includes a complete
drive and path specification.




Remote program load filename is not valid.

Explanation:  You specified a value for the RPL parameter, but the value
you specified is not a legal filename.

Recommended Action:  Change the RPL parameter so it is a legal filename.




Remote program load file not found.

Explanation:  You specified a value for the RPL parameter, but the
server could not find the file you specified.

Recommended Action:  Make sure you entered the correct filename for the
RPL parameter.




Server configuration is too big.

Explanation:  You allocated so many resources for the server and print
spooler that it cannot fit into available memory.  This is most likely
to happen if you install the server in EMS, because the EMS version of
the server is limited to a maximum size of 48K.

Recommended Action:  Try reducing the following server parameters:
Buffers, Sessions, Locks, and Files.  Also try reducing the following
print spooler parameters:  Spool Files and Spool Buffer Size.  If you
are loading the server into EMS, you can try loading it into shadow RAM
or DOS memory instead.




Converting security file BINDERY.DAT to new format.

Explanation:  You have updated from an earlier version of Invisible LAN.
The server automatically converts BINDERY.DAT from the old format to the
current format.

Recommended Action:  None.




Error converting security file BINDERY.DAT.

Explanation:  A DOS error occurred while the server was converting
BINDERY.DAT from an old format to the current format.

Recommended Action:  Delete BINDERY.DAT, or restore it from a backup.




Cannot convert security file BINDERY.DAT:  Object bindery is full.

Explanation:  The BINDERY.DAT could not be converted from the old format
to the current format, because there is no room for adding new security
objects.

Recommended Action:  Start the old version of Invisible LAN and delete
some of your security objects.  Or delete the entire BINDERY.DAT file,
and let the server create a new one.




Cannot open bulletin board file BBSNDX.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while opening the
bulletin board index file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot open bulletin board file BBSNDX.DAT:  No file handles available.

Explanation:  DOS has no handles available to open the bulletin board
index file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot open bulletin board file BBSNDX.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while opening the
bulletin board index file.

Recommended Action:  Reboot the computer and retry the operation.




Error reading bulletin board file BBSNDX.DAT.

Explanation:  An unexpected DOS error occurred while reading the
bulletin board index file.

Recommended Action:  Reboot the computer and retry the operation.




Error writing bulletin board file BBSNDX.DAT.

Explanation:  An unexpected DOS error occurred while writing the
bulletin board index file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot open bulletin board file BBSMSG.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while opening the
bulletin board message file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot open bulletin board file BBSMSG.DAT:  No file handles available.

Explanation:  DOS has no handles available to open the bulletin board
message file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot open bulletin board file BBSMSG.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while opening the
bulletin board message file.

Recommended Action:  Reboot the computer and retry the operation.




Error reading bulletin board file BBSMSG.DAT.

Explanation:  An unexpected DOS error occurred while reading the
bulletin board message file.

Recommended Action:  Reboot the computer and retry the operation.




Error writing bulletin board file BBSMSG.DAT.

Explanation:  An unexpected DOS error occurred while writing the
bulletin board message file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot open bulletin board file BBSMSG.DAT:  File not found.

Explanation:  The bulletin board message file is missing.

Recommended Action:  Delete BBSNDX.DAT, and let the server create a new
bulletin board system.




Cannot create bulletin board file BBSNDX.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while creating the
bulletin board index file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create bulletin board file BBSNDX.DAT:  No file handles
available.

Explanation:  DOS has no handles available to create the bulletin board
index file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot create bulletin board file BBSNDX.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while creating the
bulletin board index file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create bulletin board file BBSNDX.DAT:  Disk full.

Explanation:  The bulletin board index file could not be created because
the disk is full.

Recommended Action:  Free up some disk space and retry the operation.




Error creating bulletin board file BBSNDX.DAT.

Explanation:  An unexpected DOS error occurred while creating the
bulletin board index file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create bulletin board file BBSMSG.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while creating the
bulletin board message file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create bulletin board file BBSMSG.DAT:  No file handles
available.

Explanation:  DOS has no handles available to create the bulletin board
message file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot create bulletin board file BBSMSG.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while creating the
bulletin board message file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create bulletin board file BBSMSG.DAT:  Disk full.

Explanation:  The bulletin board message file could not be created
because the disk is full.

Recommended Action:  Free up some disk space and retry the operation.




Error creating bulletin board file BBSMSG.DAT.

Explanation:  An unexpected DOS error occurred while creating the
bulletin board message file.

Recommended Action:  Reboot the computer and retry the operation.




Bulletin board files BBSNDX.DAT and BBSMSG.DAT are corrupted.

Explanation:  The bulletin board files are corrupted.

Recommended Action:  Reboot the computer and retry the operation.  If
the error recurs, delete the bulletin board files or restore them from a
backup.




Incorrect version of bulletin board files BBSNDX.DAT and BBSMSG.DAT.

Explanation:  The version number of the bulletin board files does not
match the version number of the network software.

Recommended Action:  Use the correct software version.




Creating new bulletin board files BBSNDX.DAT and BBSMSG.DAT.

Explanation:  There are no bulletin board files, so the server is
creating new ones.

Recommended Action:  None.




Cannot locate internal DOS System File Table.

Explanation:  An unexpected error occurred while the server was linking
itself into DOS.

Recommended Action:  Your DOS may be corrupted.  Try installing a fresh
copy of DOS.  If you have an unusual version of DOS, try replacing it
with a standard MS-DOS or IBM DOS version.




Cannot open audit trail file AUDIT.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while opening the audit
trail file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot open audit trail file AUDIT.DAT:  No file handles available.

Explanation:  DOS has no handles available to open the audit trail file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot open audit trail file AUDIT.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while opening the audit
trail file.

Recommended Action:  Reboot the computer and retry the operation.




Error reading audit trail file AUDIT.DAT.

Explanation:  An unexpected DOS error occurred while reading the audit
trail file.

Recommended Action:  Reboot the computer and retry the operation.




Error writing audit trail file AUDIT.DAT.

Explanation:  An unexpected DOS error occurred while writing the audit
trail file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create audit trail file AUDIT.DAT:  Access denied.

Explanation:  An unexpected DOS error occurred while creating the audit
trail file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create audit trail file AUDIT.DAT:  No file handles available.

Explanation:  DOS has no handles available to create the audit trail
file.

Recommended Action:  Increase the FILES= value in the CONFIG.SYS file.




Cannot create audit trail file AUDIT.DAT:  Path not found.

Explanation:  An unexpected DOS error occurred while creating the audit
trail file.

Recommended Action:  Reboot the computer and retry the operation.




Cannot create audit trail file AUDIT.DAT:  Disk full.

Explanation:  The audit trail file could not be created because the disk
is full.

Recommended Action:  Free up some disk space and retry the operation.




Error creating audit trail file AUDIT.DAT.

Explanation:  An unexpected DOS error occurred while creating the audit
trail file.

Recommended Action:  Reboot the computer and retry the operation.




Audit trail file AUDIT.DAT is corrupted.

Explanation:  The audit trail file is corrupted.

Recommended Action:  Reboot the computer and retry the operation.  If
the error recurs, delete the audit trail file or restore it from a
backup.




Incorrect version of audit trail file AUDIT.DAT.

Explanation:  The version number of the audit trail files does not match
the version number of the network software.

Recommended Action:  Use the correct software version.




Creating new audit trail file AUDIT.DAT.

Explanation:  There is no audit trail file, so the server is creating a
new one.

Recommended Action:  None.




UPS power fail signal is on.

Explanation:  You have enabled UPS monitoring, and the UPS is signaling
that power has failed.  The server will not start if the UPS is
signaling a power failure.

Recommended Action:  Make sure the power is good.  Check the connection
from the UPS to the computer.  Check the server configuration and make
sure you have specified the correct I/O port and signaling method.




This program requires a 386 or 486.

Explanation:  You are installing Ultra Server, and your computer does
not have a 386 or 486 processor.  Ultra Server requires a 386 or 486.

Recommended Action:  Only install Ultra Server on 386 or 486 computers.
If you don't have a 386 or 486, then use the standard server instead of
Ultra Server.




File cache cannot load because there is a 386 control program running.

Explanation:  You are installing Ultra Server, and you have a 386 memory
manager running in your computer.  Ultra Server is not compatible with
386 memory managers (such as EMM386, QEMM-386, 386-MAX, Invisible RAM
386, etc.).

Recommended Action:  Remove the 386 memory manager.  Or, if you want to
retain the memory manager, then use the standard server instead of Ultra
Server.




Insufficient extended memory to install the file cache.

Explanation:  You are installing Ultra Server, and there is insufficient
extended memory available.

Recommended Action:  Make sure that your computer has extended memory.
Try reducing some Ultra Server parameters (like file handles or
directories).  If all else fails, use the standard server instead of
Ultra Server.




Unable to control A20 address line.

Explanation:  You are installing Ultra Server, and Ultra Server is not
able to turn on your computer's A20 address line.  The A20 address line
is required for access to extended memory.

Recommended Action:  Make sure that your computer has extended memory.
Check your computer's BIOS setup program to see if there are any
adjustments you can make relating to the A20 address line.




Internal error in file cache.

Explanation:  You are installing Ultra Server, and an error was detected
while initializing the cache.

Recommended Action:  Make sure that your computer's extended memory is
functioning properly.  Try reducing the computer's clock speed;  if that
seems to cure the problem, you may be running your CPU or memory faster
than it is able to go.  If this error persists, try reinstalling the
network software from the original distribution disks.




Extended memory test failed at address XXXXXXXX (hexadecimal).

Explanation:  You are installing Ultra Server, and Ultra Server detected
an error in your computer's extended memory.  XXXXXXXX indicates the
memory address, in hexadecimal, at which the error was detected.  For
example, address 00400000 would indicate that the error occured at the
4M boundary.

Recommended Action:  Make sure that your computer has extended memory.
Check your computer's BIOS setup program to make sure that the extended
memory size is set correctly.  If you have any memory-resident programs
that use extended memory (like HIMEM.SYS), try removing them.




Hyper-extended memory test failed at address XXXXXXXX (hexadecimal).

Explanation:  You are installing Ultra Server, and Ultra Server detected
an error in your computer's hyper-extended memory.  (Hyper-extended
memory is memory that is located above the 16M boundary.) XXXXXXXX
indicates the memory address, in hexadecimal, at which the error was
detected.  For example, address 02000000 would indicate that the error
occured at the 32M boundary.

Recommended Action:  Make sure that your computer has hyper-extended
memory.  Make sure that the hyper-extended starting address and size
specified in SETUP30 is correct.



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



6. Redirector Installation Error Messages




Network card is not present or not working.

Explanation:  The network hardware is not installed or malfunctioning;
or else the TransBIOS/NetBIOS software is not installed.

Recommended Action:  Check that the network hardware and software is
installed and operating.




This program requires TransBIOS/NetBIOS version 4.0 or later.

Explanation:  You have an incorrect version of the TransBIOS/NetBIOS
software.

Recommended Action:  Use the correct version of the software.




This program requires DOS 3.10 or later.

Explanation:  The redirector requires that you use DOS version 3.10 or
higher.

Recommended Action:  Update to a later version of DOS.




Incorrect version of Network Operating System is already installed.

Explanation:  The redirector's version number does not match the version
number of other network software which is already installed.

Recommended Action:  Use the correct version of the software.




Redirector is already installed.

Explanation:  The redirector cannot be installed, because it is already
installed.

Recommended Action:  Reboot the system if you want to re-install the
redirector.




Redirector cannot be installed because DOS PRINT is already installed.

Explanation:  The DOS PRINT command is not compatible with the network.

Recommended Action:  Do not install PRINT.  You can use NETPRINT
instead.




Unable to register machine name - this station is already using the
name.

Explanation:  The redirector cannot register your user name with the
network.

Recommended Action:  Select a different user name.




Unable to register machine name - another station is already using the
name.

Explanation:  The redirector cannot register your user name with the
network, because someone else is already using the name.

Recommended Action:  Select a different user name.




Unable to register machine name - local name table is full.

Explanation:  The redirector cannot register your user name with the
network, because the TransBIOS or NetBIOS name limit has been exhausted.

Recommended Action:  Increase TransBIOS Names parameter, or the NetBIOS
Names parameter.




Unable to register machine name.

Explanation:  The server cannot register your user name with the
network.

Recommended Action:  Select a different user name.




This program requires expanded memory version 4.0 or later.

Explanation:  You attempted to load the redirector into expanded memory,
but there is no expanded memory installed, or the expanded memory is not
version 4.0.

Recommended Action:  Install the expanded memory hardware and software,
and make sure your expanded memory software is version 4.0 or higher;
or else load the redirector into shadow RAM or DOS memory instead of
EMS.




Unable to allocate expanded memory handles.

Explanation:  You attempted to load the redirector into expanded memory,
but there is insufficient free expanded memory available.

Recommended Action:  Add more expanded memory;  or else load the
redirector into shadow RAM or DOS memory instead of EMS.




Device driver N30DEV.SYS is not installed.

Explanation:  The DEVICE=N30DEV.SYS command is missing from the
CONFIG.SYS file.

Recommended Action:  Add DEVICE=N30DEV.SYS to the CONFIG.SYS file.  Note
that N30DEV.SYS must be the last device driver installed.




Unable to locate DOS Ctrl-Break handler.

Explanation:  The redirector cannot locate the routine in DOS that
handles the Ctrl-Break key.  This may also be indicated if the
redirector aborts with a <169>^C<170> message, or if the redirector
aborts with no message at all.

Recommended Action:  If you are using any type of keyboard handler or
keyboard accelerator, try removing it (or installing it after starting
the redirector).  Also, if you are using ANSI.SYS, try removing it (the
standard versions of ANSI.SYS should not cause this problem, but there
seem to be some non-standard versions of ANSI.SYS floating around that
can cause this problem).




User name is too long or contains invalid characters.

Explanation:  The user name parameter you specified is invalid.

Recommended Action:  Edit the initialization file and correct the user
name.




Password is too long or contains invalid characters.

Explanation:  The password parameter you specified is invalid.

Recommended Action:  Edit the initialization file and correct the
password.




Drive mapping string is too long.

Explanation:  One of the drive mapping parameters you specified is too
long.

Recommended Action:  Edit the initialization file and correct the drive
mapping.




Printer mapping string is too long.

Explanation:  One of the printer mapping parameters you specified is too
long.

Recommended Action:  Edit the initialization file and correct the
printer mapping.




Redirector configuration is too big.

Explanation:  You allocated so many resources for the redirector that it
cannot fit into available memory.  This is most likely to happen if you
install the redirector in EMS, because the EMS version of the redirector
is limited to a maximum size of 48K.

Recommended Action:  Try reducing the following redirector parameters:
Sessions, Files, and FCBs.  If you are loading the redirector into EMS,
you can try loading it into shadow RAM or DOS memory instead.




Aborted by user.

Explanation:  You aborted a drive mapping by pressing Esc.

Recommended Action:  None.




Invalid path on server.

Explanation:  The directory you specified in a drive mapping parameter
does not exist on the server's disk.

Recommended Action:  Correct the parameter in the initialization file.




Invalid drive on server.

Explanation:  The drive you specified in a drive mapping parameter does
not exist on the server.

Recommended Action:  Correct the parameter in the initialization file.




Cannot redirect current drive.

Explanation:  You are currently logged in to the drive that you are
trying to redirect.  This is not allowed.

Recommended Action:  Change your current drive before starting Invisible
LAN.




Server not found.

Explanation:  The server name you specified in a drive mapping parameter
could not be found on the network.

Recommended Action:  Check the server name you entered to make sure it
is correct.  Make sure that the server computer has been started.




Server not listening.

Explanation:  The server's limit on network sessions has been exceeded.

Recommended Action:  Increase the server's Sessions parameter.




Server does not have a print spooler.

Explanation:  A printer mapping parameter names a server that does not
have a print spooler.

Recommended Action:  Make sure you entered the correct server name.  If
you want to use the server's printer, you have to configure the server
to allow it.




Access denied.

Explanation:  You do not have security permission to access the
specified drive, shortname, or printer;  or you have not entered the
correct password.

Recommended Action:  Enter the correct password in the initialization
file.  Make sure you have security permission to use the drive,
shortname, or printer.




Invalid shortname.

Explanation:  The shortname you entered in a drive mapping parameter
does not exist at the server.

Recommended Action:  Correct the shortname in the initialization file.




Invalid printer number.

Explanation:  The printer number you entered in a printer mapping
parameter does not exist at the server.

Recommended Action:  Correct the printer number in the initialization
file.




Too many redirections.

Explanation:  You have exceeded the redirector's limit on network
sessions.

Recommended Action:  Increase the redirector's Sessions parameter.




Incorrect password.

Explanation:  You do not have security permission to access the
specified drive, shortname, or printer;  or you have not entered the
correct password in the initialization file.

Recommended Action:  Enter the correct password in the initialization
file.  Make sure you have security permission to use the drive,
shortname, or printer.




Invalid parameter in initialization file.

Explanation:  A drive or printer mapping parameter in the initialization
file has an invalid value.

Recommended Action:  Correct the parameters in the initialization file.




Invalid local drive letter.

Explanation:  The local drive letter you specified for a drive mapping
parameter is invalid.  The drive letter you entered is greater than the
LASTDRIVE value.

Recommended Action:  Check the drive mapping parameter to make sure it
is correct.  Increase the LASTDRIVE value in CONFIG.SYS, if necessary.




Cannot establish redirection.

Explanation:  The drive or printer redirection could not be established,
due to an unexpected error.

Recommended Action:  Check to see that the server is running.




Too many files.

Explanation:  The number of network files supported by the redirector,
plus the number of files specified in CONFIG.SYS, exceeds 250.

Recommended Action:  Reduce the number of network files supported by the
redirector, or reduce the value of FILES= in CONFIG.SYS.



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



7. Mail Installation Error Messages




You must load the Redirector before running MAIL.

Explanation:  You need to install the redirector before installing mail.

Recommended Action:  If you want to use the mail program, install the
redirector.




MAIL is already installed.

Explanation:  You cannot install the mail program, because mail is
already installed.

Recommended Action:  Do not install mail if it is already installed.
Reboot the computer if you want to re-install mail.




Cannot install MAIL - Conflicting program is already installed.

Explanation:  You cannot install mail if you have already installed the
POPMAST program.

Recommended Action:  Do not run POPMAST if you want to use Mail.




Incorrect version of Invisible LAN.

Explanation:  The Mail program's version number does not match the
version number of the installed network software.

Recommended Action:  Use the correct software version.




Redirector has rejected installation of MAIL.

Explanation:  The Mail program could not be installed, due to an
unexpected error in the redirector.

Recommended Action:  Reboot the system and retry the command.




This program requires Expanded Memory version 4.0 or later.

Explanation:  You attempted to load mail into expanded memory, but there
is no expanded memory installed, or the expanded memory is not version
4.0.

Recommended Action:  Install the expanded memory hardware and software,
and make sure your expanded memory software is version 4.0 or higher;
or else load mail into shadow RAM or DOS memory instead of EMS.




Unable to allocate required expanded memory.

Explanation:  You attempted to load mail into expanded memory, but there
is insufficient free expanded memory available.

Recommended Action:  Add more expanded memory;  or else load mail into
shadow RAM or DOS memory instead of EMS.
