                   NETWORK INITIALIZATION FILE SYNTAX

                Copyright 1993 Invisible Software, Inc.



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




     All Invisible LAN parameters are stored in an initialization file.
The easiest way to create the initialization file is to use the
Invisible LAN Setup program.  However, you can also create the
initialization file with a text editor.  The following is a description
of the syntax that must be followed when creating an initialization file
with a text editor.




====== PARAMETER SYNTAX ===============================================




     All the network parameters are stored in an initialization file.
The initialization file is an ASCII text file.  It may be edited with
any text editor or word processor that is able to handle ASCII text
files.

     The initialization file contains one parameter on each line.
Parameters have the following general form:


        program.keyword = value  comment


     As shown above, each parameter has four parts:

     *  The "program" is the name of the particular program that is
        affected by the parameter.  For example, SERVER for the file
        server, or CACHE for the disk cache.

     *  The "keyword" identifies the particular parameter.  For example,
        SESSIONS for the number of network sessions, or FILES for the
        number of files.

     *  The "value" is the value you want to assign to the parameter.
        It can be a number or a text string, depending on the particular
        parameter.

     *  The "comment" is an optional comment.  Invisible LAN ignores the
        comment.

     You may optionally include spaces before and after the equal sign.
 Spaces are not allowed before or after the period, or within the
"program", "keyword", or "value".

     Parameters may be specified in any order.  All parameters are
case-insensitive, that is, you can use uppercase and lowercase letters
interchangeably.  The network loader program, NET30.EXE, automatically
loads programs in the correct order regardless of the order in which
parameters appear in the initialization file.

     The following notations are used to describe the parameters:

     *  Words in uppercase must be entered into the initialization file
        exactly as shown.

     *  Words in lowercase must be replaced with the desired value.

     *  Where there are two or more alternative values for a parameter,
        the alternatives are separated by a vertical bar (|).  In this
        case, you must enter one of the alternatives into the
        initialization file.

     Most parameters have a default value.  If a parameter is omitted,
Invisible LAN automatically uses the default value.

     No abbreviations are allowed, with one exception:  YES or NO may be
abbreviated to Y or N.




====== GENERAL PARAMETERS =============================================




These parameters control the overall system configuration, or else
provide information used by more than one network program.



NET30.HARDWARE = hardware_type

     The type of network hardware you are using.  The following hardware
types are supported in the unserialized version of Invisible LAN:

Value                   Hardware
-----                   --------
NONE                    No network hardware.
MODEL_100               Invisible Network Model 100.
MODEL_200               Invisible Network Model 200.
MODEL_300               Invisible Network Model 300.
MODEL_200/A             Invisible Network Model 200/A (Micro Channel).
MODEL_300/A             Invisible Network Model 300/A (Micro Channel).
ETHERNET_8              Invisible Ethernet (8-bit card with 32K RAM).
ETHERNET_16_16K         Invisible Ethernet-16 with 16K RAM.
ETHERNET_16_64K         Invisible Ethernet-16 with 64K RAM.
ETHERNET/A_16K          Invisible Ethernet/A (Micro Channel), 16K RAM.
ETHERNET/A_64K          Invisible Ethernet/A (Micro Channel), 64K RAM.
ETHERNET_1000           Invisible Ethernet 1000 (8-bit card).
ETHERNET_2000           Invisible Ethernet 2000 (16-bit card).
ETHERNET_2/A            Invisible Ethernet 2/A (Micro Channel).
ETHERNET_VL_16K         Invisible Ethernet VL (32-bit VESA), 16K RAM.
ETHERNET_VL_32K         Invisible Ethernet VL (32-bit VESA), 32K RAM.
ETHERNET_8003_8K        Invisible Ethernet 8003 (8-bit WD) with 8K.
ETHERNET_8003_32K       Invisible Ethernet 8003 (8-bit WD) with 32K.
ETHERNET_8013_16K       Invisible Ethernet 8013 (16-bit WD) with 16K.
ETHERNET_8013_64K       Invisible Ethernet 8013 (16-bit WD) with 64K.

The serialized version of Invisible LAN supports:

Value                      Hardware
-----                      --------
ACCTON_POCKET_ETHERNET     Accton parallel port Ethernet.
COMPEX_PARAPORT_COAX       Compex Paraport Ethernet, coaxial cable.
COMPEX_PARAPORT_TP         Compex Paraport Ethernet, twisted pair.
DLINK_1000                 D-Link 8-bit Ethernet with D-Link chip.
DLINK_2000                 D-Link 16-bit Ethernet with D-Link chip.
IBM_TOKEN_RING             IBM Token Ring (using LAN Support Program).
INVISIBLE_ETHERNET_16_16K  Invisible Ethernet-16 with 16K RAM.
INVISIBLE_ETHERNET_16_64K  Invisible Ethernet-16 with 64K RAM.
INVISIBLE_ETHERNET_8_32K   Invisible Ethernet (8-bit with 32K RAM).
INVISIBLE_ETHERNET/A_16K   Invisible Ethernet/A (Micro Channel), 16K.
INVISIBLE_ETHERNET/A_64K   Invisible Ethernet/A (Micro Channel), 64K.
INVISIBLE_ETHERNET_VL_16K  Invisible Ethernet VL (32-bit VESA), 16K RAM.
INVISIBLE_ETHERNET_VL_32K  Invisible Ethernet VL (32-bit VESA), 32K RAM.
INVISIBLE_PORT_ETHERNET    Portable Invisible Ethernet (printer port).
INVISIBLE_THRUPORT_COAX    Invisible Thruport Ethernet, coaxial cable.
INVISIBLE_THRUPORT_TP      Invisible Thruport Ethernet, twisted pair.
NDIS                       NDIS Ethernet or Token Ring.
NE/2                       Micro Channel NE/2-compatible Ethernet.
NE1000                     8-bit NE1000-compatible Ethernet.
NE2000                     16-bit NE2000-compatible Ethernet.
NO_HARDWARE                No network hardware.
OLD_NE1000_WITH_8390B      Old NE1000 boards with 8390B Ethernet chip.
OLD_NE2000_WITH_8390B      Old NE2000 boards with 8390B Ethernet chip.
WD8003_8K                  Western Digital/SMC 8-bit Ethernet with 8K.
WD8003_32K                 Western Digital/SMC 8-bit Ethernet with 32K.
WD8013_16K                 Western Digital/SMC 16-bit Ethernet with 16K.
WD8013_64K                 Western Digital/SMC 16-bit Ethernet with 64K.



NET30.NAME = user_name

     Specifies your name on the network.  Each user must have a
different name.  The name can range from 1 to 15 characters.

     Example:  If your user name is MIKE, enter NET30.NAME=MIKE.



NET30.SERVER = YES | NO
NET30.REDIRECTOR = YES | NO
NET30.SHARE = YES | NO
NET30.CACHE = YES | NO
NET30.MAIL = YES | NO

     Specifies which Invisible LAN modules to install:  file server,
redirector, DOS SHARE program, disk cache, and/or electronic mail
program.  In each case, the default is NO.



NET30.MEMORY = memory_type

     Specifies which of the Invisible RAM memory management programs you
want to use.  The default value is NONE.  The following memory types are
supported:

Value                 Memory Manager
-----                 --------------
NONE                  No memory manager.

NEAT_CHIPSET          Invisible RAM for the NEAT chipset.  Requires a
                        286 or 386SX with the NEAT chipset and at least
                        1MB RAM.

AT/386_CHIPSET        Invisible RAM for the AT/386 chipset.  Requires a
                        386 with the AT/386 chipset and at least 1MB
                        RAM.

386_VIRTUAL           Invisible RAM 386, for the 386 virtual mode.
                        Requires a 386, 386SX, or 486 with at least 2MB
                        RAM.

INVISIBLE_EMS         Invisible RAM for the Invisible EMS memory board.

GENERIC_EMS           Invisible RAM Generic.  Requires a computer with
                        expanded memory, compatible with EMS 4.0.

SCAT_CHIPSET          Invisible RAM for the SCAT chipset.  Requires a
                        286 with the SCAT chipset and at least 1MB RAM.

PEAK_CHIPSET          Invisible RAM for the PEAK chipset.  Requires a
                        386 or 486 with the PEAK chipset and at least
                        1MB RAM.



NET30.WINDOWS = YES | NO

     Specifies whether or not to load the Windows version of the network
software.  The default is NO.  You must specify YES for this parameter
if you want to run Microsoft Windows.



NET30.VERSION = software_version

     Specifies which version of the Invisible LAN software you want to
use.  The default value is STANDARD.  The following versions are
supported:

Value                 Software Version
-----                 --------------
STANDARD              The normal software that can be used on all
                        computers running DOS or Windows.

ULTRA_SERVER          The high-performance file server, intended mainly
                        for dedicated server applications.  It requires
                        a 386 or 486 with extended memory.




====== TRANSBIOS PARAMETERS ===========================================




     These parameters control the configuration of the TransBIOS
software.  The parameters have no effect if TransBIOS is loaded from
ROM, except for TRANSBIOS.RETRY_LIMIT and TRANSBIOS.DATA_LOCATION.

     TransBIOS is the basic network communication software used by
Invisible LAN.  All Invisible LAN programs communicate over the network
by calling TransBIOS.  Therefore, you must configure TransBIOS to
provide enough resources for all your network programs.



TRANSBIOS.DATA_LOCATION = DOS | SHADOW

     Specifies the type of memory to use for TransBIOS data tables and
packet buffers.  The default is DOS.

     If you are loading TransBIOS from ROM, this parameter is effective
only in the case where an Invisible RAM memory manager is loaded by
NET30.EXE (not by CONFIG.SYS).  For the RAM version of TransBIOS, this
parameter is always effective

     Example:  To install the TransBIOS data segment into shadow RAM,
use TRANSBIOS.DATA_LOCATION=SHADOW.



TRANSBIOS.CODE_LOCATION = DOS | SHADOW | EMS

     Specifies the type of memory to use for TransBIOS program code.
The default is DOS.

     Note that using EMS will substantially slow down the performance of
the network.  If possible, use SHADOW rather than EMS.

     Example:  To install the TransBIOS code segment into expanded
memory, use TRANSBIOS.CODE_LOCATION=EMS.



TRANSBIOS.DATA_SIZE = nn

     The amount of memory to use for TransBIOS data tables and packet
buffers, in kilobytes.

     The default value depends on the type of network hardware in use.
For all Ethernet hardware, the default is 24 kilobytes.  For the
Invisible Model 200 and 300 series, the default is 32 kilobytes.

     Example:  To provide 64K for the TransBIOS data segment, use
TRANSBIOS.DATA_SIZE=64.



TRANSBIOS.SESSIONS = nn

     The number of concurrent network sessions supported by TransBIOS.
The value can range from 4 to 256, and defaults to 32.

     A server consumes one session for each workstation that is
connected to it.  A redirector consumes one session for each server that
it is connected to.  A remote program load server consumes one session
for each diskless workstation.  An application program that uses NetBIOS
consumes one TransBIOS session for each NetBIOS session that it creates.
In addition, at least two extra sessions are required for network
management and mail functions.

     Example:  To provide 64 sessions, use TRANSBIOS.SESSIONS=64.



TRANSBIOS.NAMES = nn

     The number of network names supported by TransBIOS.  The value can
range from 4 to 256, and defaults to 18.

     TransBIOS consumes 2 names internally, and Invisible LAN consumes 4
additional names.  In addition, and application program that uses
NetBIOS consumes one TransBIOS name for each NetBIOS name that it
creates.

     Example:  To provide 32 names, use TRANSBIOS.NAMES=32.



TRANSBIOS.POLLS = nn

     The number of concurrent network polling operations supported by
TransBIOS.  The value can range from 2 to 16, and defaults to 4.

     There is no known reason to change this parameter.



TRANSBIOS.RESPONSES = nn

     The number of network responses that can be pending at one time in
TransBIOS.  Allowed values are 4 to 256, with a default of 16.

     There is no known reason to change this parameter.



TRANSBIOS.APPLICATIONS = nn

     The number of different TransBIOS applications that can be
installed at one time.  Allowed values are 4 to 256, with a default of
16.

     TransBIOS consumes 2 applications internally, and Invisible LAN
consumes 3 additional applications.



TRANSBIOS.RETRY_LIMIT = nn

     The number of times TransBIOS retries a data transmission before
aborting a network session.  Each retry takes 1 or 2 seconds.  The
default value is 32.  The range of allowed values varies depending on
the type of network hardware in use;  however, if you specify a value
invalid for the hardware in use, the closest valid value is used.  This
parameter is effective for both ROM and RAM versions of TransBIOS.

     This parameter lets you control the amount of time it takes for a
session to die.  If you have enabled automatic re-mapping of drives and
printers, this parameter determines how long it takes for the re-mapping
to occur.

     Example:  To specify a retry limit of 5, which causes sessions to
die in 5 to 10 seconds, use TRANSBIOS.RETRY_LIMIT=5.



TRANSBIOS.PORT = nnn

     Hardware I/O port address, in hexadecimal.  Default is auto-detect.

     Refer to HARDWARE.TXT for information on what values are allowed
for each type of network hardware.

     Example:  To specify an I/O port address of 340 hex, use
TRANSBIOS.PORT=340.



TRANSBIOS.IRQ = nn

     Hardware interrupt level.  It can be a decimal number from 2 to 15
(or 2 to 7 on XT-type computers).  Default is auto-detect.

     Refer to HARDWARE.TXT for information on what values are allowed
for each type of network hardware.

     Example:  To specify interrupt level 4, use TRANSBIOS.IRQ=4.



TRANSBIOS.DMA = nn

     Hardware DMA (direct memory access) channel.  It can be a decimal
number from 0 to 7 (or 1 to 3 on XT-type computers).  Default is
auto-detect.

     Not all hardware uses DMA.  Refer to HARDWARE.TXT for information
on what values are allowed for each type of network hardware.

     Example:  To specify DMA channel 3, use TRANSBIOS.DMA=3.



TRANSBIOS.MEMORY = nnnn

     Segment address of shared memory, in hexadecimal.  Default is
auto-detect.

     Not all hardware uses shared memory.  Refer to HARDWARE.TXT for
information on what values are allowed for each type of network
hardware.

     Example:  To specify that shared memory is located in memory
segment D000, use TRANSBIOS.MEMORY=D000.



TRANSBIOS.PACKET_SIZE = nnnn

     Maximum network packet size, in bytes.  The default is to use the
largest possible packets.

     This parameter can only reduce the packet size, it cannot increase
the packet size.  Reducing the packet size may be useful if your network
contains bridges or routers that cannot handle large packets.

     On Ethernet, TransBIOS normally uses packets larger than the
official Ethernet specification allows.  Set the packet size to 1514 if
you want TransBIOS to adhere strictly to the Ethernet standard.

     Example:  To specify a packet size of 1514 bytes, use
TRANSBIOS.PACKET_SIZE=1514.




====== NETBIOS PARAMETERS =============================================




     These parameters control the configuration of the NetBIOS software.
NetBIOS is a standard network communication interface defined by IBM.
Invisible LAN itself does not use NetBIOS (except for the Remote Program
Load function), however many network application programs use NetBIOS.

     Note that NetBIOS is a TransBIOS application, so each NetBIOS
activity consumes TransBIOS resources.  For example, each NetBIOS name
consumes one TransBIOS name.

     These parameters have no effect if NetBIOS is loaded from ROM.



NETBIOS.SESSIONS = nn

     The number of concurrent network sessions supported by NetBIOS.
Allowed values are 4 to 254, with a default of 32.

     A Remote Program Load Server consumes one NetBIOS session for each
diskless workstation.  A diskless workstation uses one NetBIOS session
to communicate with the RPL Server.

     If you increase the value of this parameter, you should also
increase the value of TRANSBIOS.SESSIONS.

     Example:  To provide 64 sessions, use NETBIOS.SESSIONS=64.



NETBIOS.NAMES = nn

     The number of network names supported by NetBIOS.  Allowed values
are 4 to 253, with a default of 16.  This number does not include the
NetBIOS permanent node name.

     Invisible LAN always uses one or two NetBIOS names.

     If you increase the value of this parameter, you should also
increase the value of TRANSBIOS.NAMES.

     Example:  To provide 32 names, use NETBIOS.NAMES=32.



NETBIOS.COMMANDS = nn

     The maximum number of NetBIOS commands (also called "NCBs" or
"Network Control Blocks") that can be outstanding at one time.  Allowed
values are 4 to 254, with a default of 32.

     A Remote Program Load Server consumes two NetBIOS commands.  A
diskless workstation uses one NetBIOS command to communicate with the
RPL Server.

     Example:  To provide 64 commands, use NETBIOS.COMMANDS=64.




====== SERVER AND PRINT SPOOLER PARAMETERS ============================




     These parameters control the configuration of the Invisible file
server and print spooler.  These parameters are ignored if the server is
not loaded.



SERVER.SHADOW = YES | NO

     Specifies whether or not to use shadow RAM for the server software.
Default is NO.



SERVER.EMS = YES | NO

     Specifies whether or not to use expanded memory for the server
software.  If YES is specified, then most of the server software is
placed in expanded memory, and the remainder is placed in either DOS
memory or shadow RAM (as specified by the SERVER.SHADOW parameter).
Default is NO.

     Note that EMS slows the server significantly.



SERVER.BUFFERS = nn

     The number of network communication buffers used by the server.
Each buffer is 2K bytes.  The value can range from 2 to 64, with a
default of 4.

     Increasing this parameter can improve the performance of the
server.  However, there is no benefit to providing more than 4 buffers
per workstation.

     Example:  To provide 16 buffers, use SERVER.BUFFERS=16.



SERVER.SESSIONS = nn

     The number of network sessions supported by the server.  Each
workstation connected to the server requires one session.  Allowed
values range from 2 to 256, with a default of 8.

     If you make this value larger than 30, you should also increase the
value of TRANSBIOS.SESSIONS.

     Example:  To provide 16 sessions, use SERVER.SESSIONS=16.



SERVER.LOCKS = nn

     The maximum number of concurrent record locks supported by the
server.  The value can range from 20 to 1000, and 20 is the default.

     Note that the number of record locks is limited both by this
parameter, and by SHARE.LOCKS.  If you increase this parameter, you
should also increase SHARE.LOCKS.

     Example:  To allow 100 record locks, use SERVER.LOCKS=100.



SERVER.FILES = nn

     The maximum number of files that can be open concurrently.  Legal
values are 20 to 1000, and the default is 50.

     Note that the number of files that can be open concurrenly is
limited by this parameter, by SHARE.FILESPACE, and by the FILES=
statement in the server's CONFIG.SYS.  If you increase this parameter,
you should also make appropriate adjustments in SHARE.FILESPACE and
FILES=.  (Exception:  If you specify SERVER.PRIVATE_FILES=YES, then the
number of files is not limited by the FILES= statement in CONFIG.SYS.)

     Example:  To allow 100 open files, use SERVER.FILES=100.



SERVER.PRIVATE_FILES = YES | NO

     Specifies whether the server should allocate a private file table.
Default is NO.  If you specify YES, then the number of network files is
not limited by the FILES statement in the CONFIG.SYS file, thereby
allowing the server to support up to 1000 network files.

     Note that if you allocate a private file table, then Windows cannot
be run in 386 enhanced mode on the server.  (You can run Windows in
standard mode.)



SERVER.WRITE_PIPELINE = YES | NO

     This specifies whether the server can use pipelined writes during
file I/O.  This means that write data is cached in the server, and the
workstation is immediately given permission to proceed while the data is
written to the file at a later time.  This may prevent some error
conditions (like a completely full hard disk) from being reported to the
workstation.  Also, it is conceivable that some software may not work
correctly with the write pipeline enabled (although we are not aware of
any such software).  The default is YES.

     Note that this parameter is completely independent from the disk
cache parameter CACHE.WRITE_POLICY.



SERVER.RPL = d:\path\filename

     If this parameter is specified, the server will act as a Remote
Program Load Server.  The value is the name of a disk file that contains
a boot diskette image file (created by the MAKEIMG program).  A full
drive and path specification is required.

     If this parameter is omitted, the server does not act as a Remote
Program Load Server.

     Example:  To activate a Remote Program Load Server using the boot
diskette image in file C:\NET30\BOOT.IMG, enter the parameter value
SERVER.RPL=C:\NET30\BOOT.IMG.



SERVER.PRINTER_1 = NONE | LPT1 | LPT2 | LPT3 | COM1 | COM2
SERVER.PRINTER_2 = NONE | LPT1 | LPT2 | LPT3 | COM1 | COM2

     The devices to use for network printers #1 and #2.  Default is
NONE.  Note that when you share a printer(s), you should always
establish a mapping to your printer(s), so that your own printer output
goes through the print spooler.

     Example:  If you want to share LPT2 as network printer #1, enter
the parameter SERVER.PRINTER_1=LPT2.

     Example:  If you want to share COM1 as network printer #2, enter
the parameter SERVER.PRINTER_2=COM1.



SERVER.FEED_1 = YES | NO
SERVER.FEED_2 = YES | NO

     Specifies whether or not to add a form-feed command at the end of
each print job.  Default is YES.  Note that this is specified separately
for each network printer.

     Enabling form-feeds causes each print job to begin at the top of a
new page.  However, you may want to disable form-feeds if your
application programs already add form-feeds, or if you are using a page
description language such as PostScript.

     This parameter determines the initial setting of the form-feed
state.  After the network is started, you can change the form-feed state
with the PQ or MENU command.



SERVER.FLOW_1 = DTR | XON
SERVER.FLOW_2 = DTR | XON

     Specifies the flow control method to use for a serial printer.  You
can select DTR flow control or Xon/Xoff flow control.  Default is DTR.
Note that this is specified separately for each network printer.

     For parallel printers, this parameter is ignored.

     This parameter determines the initial flow control setting.  After
the network is started, you can change the flow control setting with the
PQ or MENU command.

     Example:  To select DTR flow control for network printer #1, enter
SERVER.FLOW_1=DTR.



SERVER.BREAK_1 = NONE | ASCII | POSTSCRIPT | PCL
SERVER.BREAK_2 = NONE | ASCII | POSTSCRIPT | PCL

     Specifies whether to print a break page at the start of each print
job.  Default is NONE.  If the break page is enabled, this parameter
specifies if the break page should be printed in ASCII, PostScript, or
PCL.  Note that this is specified separately for each network printer.

     The design of the ASCII break page is stored in the file
BP_ASCII.DAT, the design of the PostScript break page is stored in the
file BP_PSCPT.DAT, and the design of the PCL break page is stored in the
file BP_PCL.DAT.  You can use the MAKEBP program to change the break
page design.



SERVER.SPOOL_FILES = nn

     The maximum number of files that can be queued up in the print
queue.  The value can range from 10 to 1000, and defaults to 50.

     Example:  To allow 500 files in the print queue, use the parameter
value SERVER.SPOOL_FILES=500.



SERVER.SPOOL_BUFFER_SIZE = nn

     The size of the buffer used to transfer data from the print queue
to the printer, in bytes.  The value can range from 64 to 2048, with a
default of 128.  The default value is adequate for printing ASCII files.
Larger values should be used for graphics or page description languages.

     Example:  To set the spool buffer size to 2048, use the parameter
value SERVER.SPOOL_BUFFER_SIZE=2048.



SERVER.SPOOL_DIRECTORY = d:\path

     The disk directory used to hold print spooler files.  A complete
drive and path are required.  If omitted, the default is the directory
where the Invisible LAN program files are stored.

     It is often possible to speed up printing by placing the spooler
files into a RAM Disk.

     Example:  If you want the print spool files to be stored in
directory E:\SPOOLER, enter SERVER.SPOOL_DIRECTORY=E:\SPOOLER.



SERVER.AUDIT = YES | NO

     Specifies whether the server should maintain an audit trail.  The
audit trail is a log of server activity.  Default is NO.



SERVER.AUDIT_SIZE = nnnn

     The size, in records, of the audit trail file (AUDIT.DAT).  Each
record requires 48 bytes of disk space.  Allowed values are 500 to
50000, with a default of 5000.  This parameter is only used when the
server creates a new AUDIT.DAT file.  If there is an existing AUDIT.DAT
file, the server uses the size of the existing file.



SERVER.DIRECT_PRINT = YES | NO

     Specifies whether the print spooler can send a job to the printer
at the same time it is being spooled.  Default is NO.  Note this setting
can be changed with the PQ program.



SERVER.SPOOL_PRIORITY = LOW | MEDIUM | HIGH

     Specifies whether priority for sending data to the printer.
Default is MEDIUM.  Note that this setting can be changed with the PQ
program.



SERVER.SUPERUSER = YES | NO

     Specifies whether a user working locally at the server is a
superuser, who can perform any operation on the server regardless of
security permissions.  Default is YES.



SERVER.BLOCK_CADEL = YES | NO

     Specifies whether the server should deactivate the Ctrl-Alt-Del
key, so the server cannot be rebooted.  Default is NO.



SERVER.UPS_MONITOR = YES | NO

     Specifies whether the server should monitor a UPS, so it can shut
itself down in the event of a power failure.  Default is NO.



SERVER.UPS_PORT = nnn

     Specifies the I/O port used to monitor the UPS, in hexadecimal.
Default is 231.



SERVER.UPS_SIGNAL = BITn_LO | BITn_HI

     Specifies the signal that the UPS uses to indicate a power failure.
You specify both the bit to test (n = 0 thru 7) and the polarity (LO if
a zero bit indicates a power failure, or HI if a one bit indicates a
power failure).  The default is BIT7_HI.



SERVER.UPS_DISCHARGE = nn

     The amount of time, in minutes, that the server waits after a power
failure before shutting itself down.  The value can range from 1 to 60,
and defaults to 5.



SERVER.UPS_RECHARGE = nn

     The amount of time, in minutes, that the server waits after power
is restored before restarting itself.  The value can range from 1 to 60,
and defaults to 30.




====== ULTRA SERVER PARAMETERS ========================================




     These parameters control the configuration of Ultra Server, the
high-performance file server software.  These parameters are ignored if
Ultra Server is not loaded.



ULTRA_SERVER.FILE_BUFFER_SIZE = nnnn

     The size of each data buffer in extended memory, in bytes.  Default
is 8192.  For best results, this should be a multiple of the disk
cluster size.  It can range from 512 to 65024.

     Example:  To specify a buffer size of 16384, use
ULTRA_SERVER.FILE_BUFFER_SIZE=16384.



ULTRA_SERVER.FILE_HANDLES = nnnn

     Number of network file handles to support.  This is the number of
files that users may open concurrently.  It ranges from 10 to 32768, and
defaults to 500.  Note this is not limited by the FILES= value in
CONFIG.SYS.

     Example:  To allow 5000 open files, use
ULTRA_SERVER.FILE_HANDLES=5000.



ULTRA_SERVER.RECORD_LOCKS = nnnn

     Number of record locks to support.  This is the number of record
locks that users may open concurrently.  It ranges from 10 to 65535, and
defaults to 1000.  Note this is not limited by the LOCKS parameter of
the SHARE program.

     Example:  To allow 20000 record locks, use
ULTRA_SERVER.RECORD_LOCKS=20000.



ULTRA_SERVER.DIRECTORIES = nnnn

     Number of directory entries to store in the cache.  It can range
from 20 to 65535, and defaults to 1000.

     Example:  To retain 4000 directory entries in the cache, use
ULTRA_SERVER.DIRECTORIES=4000.



ULTRA_SERVER.CHANNELS = nn

     Number of DOS file handles that the Ultra Server can use to access
the disk.  It can range from 10 to 240, and defaults to 50.

     Example:  To use 200 DOS file handles for accessing the disk, use
ULTRA_SERVER.CHANNELS=200.



ULTRA_SERVER.PRIVATE_FILES = YES | NO

     Specifies whether or not to allocate a private file table for Ultra
Server.  Default is NO (however, the Setup program defaults this
parameter to YES).  If you specify YES, then the CHANNELS value does not
come out of the FILES= value in CONFIG.SYS.



ULTRA_SERVER.EXTENDED_SIZE = nn

     Amount of extended memory to use, in megabytes.  It can range from
0 to 15, and defaults to 15.

     Example:  To limit Ultra Server to using 8 megabytes of extended
memory, use ULTRA_SERVER.EXTENDED_SIZE=8.



ULTRA_SERVER.HYPER_START = nnnn

     Starting location of hyper-extended memory, in megabytes.  It can
range from 1 to 4095, and defaults to 16.



ULTRA_SERVER.HYPER_SIZE = nnnn

     Size of hyper-extended memory, in megabytes.  It can range from 0
to 4095, and defaults to 0.



ULTRA_SERVER.A = NONE | FIXED_DISK | CD_ROM
ULTRA_SERVER.B = NONE | FIXED_DISK | CD_ROM
ULTRA_SERVER.C = NONE | FIXED_DISK | CD_ROM
...              ...    ...          ...
ULTRA_SERVER.Z = NONE | FIXED_DISK | CD_ROM

     Caching options for drives A: through Z:.  NONE specifies that the
drive is uncached.  FIXED_DISK specifies that the drive is cached as a
read/write drive.  CD_ROM specifies that the drive is cached as a
read-only drive.  By default, drives A: and B: are uncached, each
installed CD-ROM drive from C: to Z: is cached as a read-only drive,
and all other installed drives from C: to Z: are cached as read/write
drives.




====== REDIRECTOR PARAMETERS ==========================================




     These parameters control the configuration of the network
redirector (workstation software).  These parameters are ignored if the
redirector is not loaded.



REDIRECTOR.SHADOW = YES | NO

     Specifies whether or not to use shadow RAM for the redirector
software.  Default is NO.



REDIRECTOR.EMS = YES | NO

     Specifies whether or not to use expanded memory for the redirector
software.  If YES is specified, then most of the redirector software is
placed in expanded memory, and the remainder is placed in either DOS
memory or shadow RAM (as specified by the REDIRECTOR.SHADOW parameter).
Default is NO.

     Note that using EMS slows the redirector significantly.



REDIRECTOR.SESSIONS = nn

     The number of network sessions supported by the redirector.  One
session is required for each server used by the workstation.  The value
can range from 2 to 32, and defaults to 8.

     Example:  To allow 16 network sessions, use REDIRECTOR.SESSIONS=16.



REDIRECTOR.FILES = nn

     The maximum number of network files that can be open concurrently.
The value can range from 10 to 200, and defaults to 50.  The number
specified for this parameter, plus the number specified for the FILES=
statement in CONFIG.SYS, must not exceed 250.

     Example:  For 100 open network files, use REDIRECTOR.FILES=100.



REDIRECTOR.FCBS = nn

     The maximum number of network files that can be open concurrently
using the FCB method.  The value can range from 8 to 200, and defaults
to 16.

     Example:  To allow 50 network files to be opened by the FCB method,
use REDIRECTOR.FCBS=50.



REDIRECTOR.TRUNCATE = nn

     Length of print stream truncation timeout, in seconds.  A value of
0 indicates that print stream truncation is disabled.  The value can
range from 0 to 255, with a default of 0.

     If a nonzero value is given, then the network print streams are
truncated whenever there is no printer activity for the specified time.
This is useful when printing from application programs that do not send
an end-of-file message to the printer.

     This parameter determines the initial value of the print stream
truncation timeout.  After the network is started, the value can be
changed with the TRUNCATE or MENU programs.

     Example:  To specify a print stream truncation timeout of 10
seconds, use REDIRECTOR.TRUNCATE=10.



REDIRECTOR.PASSWORD = password | *

     Specifies the user password.  If the value "*" is used, then you
are prompted to enter the password when the redirector is loaded.  If
this parameter is omitted, the default is no password.

     This parameter determines the initial user password;  it is the
password used in establishing the initial drive and printer mappings.
After Invisible LAN is started, the password can be changed with the
PASSWORD command.

     Example:  To specify a password of MYPASS, use
REDIRECTOR.PASSWORD=MYPASS.

     Example:  If you don'w want to put your password into the
initialization file, use REDIRECTOR.PASSWORD=*.  When you start the
network, it prompts you to type in your password.



REDIRECTOR.AUDIO = YES | NO

     Specifies whether the redirector should beep the speaker when the
server is slow in responding to a network request.  Default is YES.

     This parameter determines the initial audio setting.  After the
network is started, the audio setting can be changed with the NW
command.



REDIRECTOR.AUTO_REMAP = YES | NO

     Specifies whether the redirector should automatically re-establish
its drive and printer mappings when the server is rebooted.  Default is
YES.



REDIRECTOR.BUFFERS = nnn

     Number of buffers to allocate.  These buffers are used to cache
network files.  Allocating buffers may improve the performance of
programs that perform sequential file access with a small record size.
The value can range from 0 to 16, and defaults to 0.



REDIRECTOR.BUFFER_SIZE = nnnn

     Size of buffers to allocate for caching network files.  The value
can range from 128 to 1536, and defaults to 1536.



REDIRECTOR.PRINT_BUFFER_SIZE = nnnn

     Size of buffers to allocate for caching output to network printers.
The redirector always allocates three of these buffers, one each for
LPT1, LPT2, and LPT3.  The value can range from 128 to 1536, and
defaults to 128.




====== MAPPING PARAMETERS =============================================




     These parameters control the initial drive and printer mappings.
They are ignored if the redirector is not loaded.

     These mappings are established automatically when Invisible LAN is
started.  After the network is started, the mappings can be changed
using the MAP or MENU commands.



MAP.A = \\server\d:[\path]  |  \\server\shortname[\path]
MAP.B = \\server\d:[\path]  |  \\server\shortname[\path]
MAP.C = \\server\d:[\path]  |  \\server\shortname[\path]
...     ...                    ...
MAP.Z = \\server\d:[\path]  |  \\server\shortname[\path]

     Initial drive mappings for drives A: through Z:.  Any drive not
mapped remains local.

     The value of the parameter can be given in either of two forms.
The first form uses a drive and path to specify the destination
directory on the server's disk.  The square brackets indicate that
<BI>\path<D> is optional;  if omitted, it defaults to the root directory
on the server's disk.

     The second form uses a shortname.  The shortname is the network
name for a directory on the server's disk;  you can map to the
shortname's directory, or to any subdirectory.  The square brackets
indicate that the subdirectory <BI>\path<D> is optional;  if omitted, it
defaults to the shortname's directory on the server's disk.

     Example:  To map drive K: to the root directory of drive C: on
server ROBERT, use MAP.K=\\ROBERT\C:.

     Example:  To map drive R: to directory D:\ACCTS on server MAIN,
enter MAP.R=\\MAIN\D:\ACCTS.

     Example:  To map drive M: to the directory with shortname TEXT on
server ALICE, use MAP.M=\\ALICE\TEXT.

     Example:  Server MIKE has a directory with shortname ORDERS.  There
is a subdirectory named OVERDUE within this directory.  To map drive T:
to the OVERDUE subdirectory, enter MAP.T=\\MIKE\ORDERS\OVERDUE.



MAP.LPT1 = \\server\[#]
MAP.LPT2 = \\server\[#]
MAP.LPT3 = \\server\[#]

     Initial mappings for printers LPT1 through LPT3.  Any printer not
mapped remains local.

     The "#" can be 1 or 2.  The square brackets indicate that "#" is
optional;  if omitted, it defaults to 1.

     Example:  To map device LPT2 to network printer #1 on server VINCE,
use MAP.LPT2=\\VINCE\.

     Example:  To map device LPT3 to network printer #2 on server
REGINA, use MAP.LPT2=\\REGINA\2.



MAP.WAIT = YES | NO

     This parameter specifies what action to take if the server is not
on the network when the initial drive and printer mappings are
established.  If you enter YES, then the redirector waits for the server
to be started.  If you enter NO, then the mapping is aborted and an
error message is displayed.  The default value for this parameter is
YES.




====== DISK CACHE PARAMETERS ==========================================




     These parameters control the configuration of the Invisible LAN
disk cache.  These parameters are ignored if the cache is not loaded.



CACHE.DATA_LOCATION = EMS | EXTENDED | XMS

     Specifies the type of memory to use for cached disk data.  EMS
selects expanded memory, and requires an expanded memory system
compatible with EMS 4.0.  EXTENDED selectes extended memory accessed
through the computer's BIOS (using INT 15).  XMS selects extended memory
accessed through an XMS interface, and requires an XMS device driver
such as HIMEM.SYS.

     There is no default for this parameter;  if the cache is loaded,
then this parameter is mandatory.

     If you want to run Microsoft Windows, then the cache data location
must be EMS or XMS.



CACHE.DATA_SIZE = nnnn

     Size of the cache data, in kilobytes.  If the value is 0, then all
available memory is used for cache data.  Default is 0.

     Example:  To use 1024K for the cache data, enter the parameter
value CACHE.DATA_SIZE=1024.



CACHE.CODE_LOCATION = DOS | SHADOW

     The type of memory to use for the cache program code and track
buffer.  Default is DOS.

     Example:  To use shadow RAM for the cache program code and track
buffer, enter CACHE.CODE_LOCATION=SHADOW.



CACHE.EXTENDED_TRANSFER_SIZE = nn

     The number of disk sectors that can be transferred to or from
extended memory in one operation.  Allowed values are 1 to 64, with a
default of 9.

     Since interrupts are disabled during transfers to or from extended
memory, entering too large a value may cause the system to miss
interrupts.

     This parameter is ignored if the cache data is installed in EMS or
XMS memory.

     Example:  To allow 17 sectors to be transferred to or from extended
memory, use CACHE.EXTENDED_TRANSFER_SIZE=17.



CACHE.BIOS_PATCH = YES | NO

     If you enter YES for this parameter, the cache installs a patch for
BIOS interrupt 15H.  The patch corrects a BIOS bug that may affect the
ability of the cache to access extended memory.  It may also improve
performance, because the BIOS patch is faster than many computer's
built-in BIOS.  The default for this parameter is YES.



CACHE.WRITE_POLICY = WRITE_BACK | WRITE_THROUGH | DELAYED_WRITE

     The write policy employed by the cache.  WRITE_BACK specifies that
write data is stored in the cache and then quickly written to disk in
background.  WRITE_THROUGH specifies that write data is immediately
written to disk.  DELAYED_WRITE specifies that data is not written to
disk until after several seconds have elapsed.  The default value is
WRITE_BACK.

     This parameter specifies the initial write policy.  After starting
the network, you can use the CACHE program can change the write policy.



CACHE.ASSOCIATIVITY = nn

     Associativity of the cache.  The value can range from 1 to 64, and
defaults to 4.

     The cache data is organized into "associations", each of which
contains a small number of buffers.  This parameter determines the
number of buffers in each association.

     Example:  To specify 6 buffers per association, enter
CACHE.ASSOCIATIVITY=6.



CACHE.BACKGROUND_TASKS = nn

     Number of background tasks.  This is the maximum number of disk
tracks that can be waiting to be written to the disk.  Allowed values
are 4 to 256, and the default is 64.  Increasing this parameter may
improve performance slightly.

     Example:  For 128 background tasks, use CACHE.BACKGROUND_TASKS=128.



CACHE.DELAY_TIME = nn

     The amount of time that the cache waits before beginning a disk
write when the write policy is delayed-write.  The time is measured in
units of 1/18 second.  Allowed values are 2 to 255.  Default is 54 (3
seconds).



CACHE.SEEK_HORIZON = nn

     The number of disk operations that the cache searches through when
reordering operations.  This allows the cache to minimize the time
required for disk seeks.  Allowed values are 1 to 16, with a default
value of 8.




====== SHARE PARAMETERS ===============================================




     These parameters control the DOS SHARE program.  They are ignored
if SHARE is not loaded, or if SHARE is loaded from the DOS command line
(or a batch file).



SHARE.SHADOW = YES | NO

     Specifies whether to use shadow RAM for the SHARE program.  Default
is NO.



SHARE.FILESPACE = nnnn

     The amount of memory to allocate for the names of open files, in
bytes.  The value can range from 2048 to 20000, and the default value is
2048.

     This parameter is exactly equivalent to the "/F:" parameter on the
SHARE command line.

     Note that on a file server, the number of network files is limited
by this parameter, by the SERVER.FILES parameter, and by the FILES=
statement in the CONFIG.SYS file.

     Example:  To specify a filespace of 5000 bytes, use the parameter
value SHARE.FILESPACE=5000.



SHARE.LOCKS = nn

     The number of concurrent record locks supported by SHARE.  The
default value is 20.

     This parameter is exactly equivalent to the "/L:" parameter on the
SHARE command line.

     Note that on a file server, the number of record locks is limited
by this parameter, and by the SERVER.LOCKS parameter.

     Example:  To allow 1000 record locks, enter SHARE.LOCKS=1000.




====== MAIL PARAMETERS ================================================




     These parameters control the configuration of the mail program.
They are ignored if mail is not loaded.



MAIL.SHADOW = YES | NO

     Specifies whether or not to use shadow RAM for the mail program.
Default is NO.



MAIL.EMS = YES | NO

     Specifies whether or not to use expanded memory for the mail
program.  If YES is specified, then most of the mail program is placed
in expanded memory, and the remainder is placed in either DOS memory or
shadow RAM (as specified by the MAIL.SHADOW parameter).  Default is NO.




====== INVISIBLE RAM MEMORY MANAGER PARAMETERS ========================




     These parameters control the Invisible RAM memory managers.  They
are ignored if no memory management is requested by the NET30.MEMORY
parameter, or if Invisible RAM is installed in CONFIG.SYS.

     Not all parameters are valid for every type of hardware.  The
following table shows which parameters are valid for each type of
hardware;  an X indicates a valid combination.


        PEAK Chipset ---------------------------------------------+
                                                                  |
        SCAT Chipset --------------------------------------+      |
                                                           |      |
        Generic EMS --------------------------------+      |      |
                                                    |      |      |
        Invisible EMS -----------------------+      |      |      |
                                             |      |      |      |
        386 Virtual ------------------+      |      |      |      |
                                      |      |      |      |      |
        AT/386 Chipset --------+      |      |      |      |      |
                               |      |      |      |      |      |
        NEAT Chipset ---+      |      |      |      |      |      |
                        |      |      |      |      |      |      |
                        |      |      |      |      |      |      |

EMM.CODE_LOCATION       X      X      X      X      X      X      X

EMM.CONFIGURATION       X      X      X      X      X      X      X

EMM.CONTEXTS            X             X      X             X

EMM.DEFAULT_RAM         X      X      X      X      X      X      X

EMM.EXCLUDE             X      X      X      X      X      X      X

EMM.EXTENDED_EMULATE                         X

EMM.FRAME_ADDRESS                     X      X             X

EMM.FRAME_SIZE                        X      X             X

EMM.FRONTFILL_SIZE      X      X      X      X      X      X      X

EMM.HANDLES             X             X      X             X

EMM.HIGH_RAM            X      X      X      X      X      X      X

EMM.INCLUDE                           X      X             X

EMM.NONSTANDARD_PAGE                  X      X             X

EMM.PORT                                     X

EMM.ROM_COPY            X      X      X                    X      X

EMM.SHADOW_RAM          X      X      X      X      X      X      X

EMM.TEST_LEVEL          X      X      X      X      X      X      X

EMM.VGA                 X      X      X      X      X      X      X


     The memory managers allocate memory in 16K-byte "page frames".
There are a total of 64 such page frames.  The first page frame covers
segments 0000-03FF, the second page frame covers segments 0400-07FF, and
so on;  the last (sixty-fourth) page frame covers segments FC00-FFFF.

     Each page frame has five possible uses:

     1.  Excluded.  The page frame is not used by the memory manager.
The page frame contains whatever was originally there before the memory
manager was loaded.

     2.  Paged EMS.  The page frame can be used by programs designed for
expanded memory ("EMS" stands for Expanded Memory Specification).  Paged
EMS memory can be located both inside and outside of the DOS memory
space.  The paged EMS memory is further divided into "standard EMS page
frames" and "enhanced EMS page frames";  most expanded memory programs
only use the standard EMS page frames.

     3.  Shadow RAM.  The page frame can be used to hold memory resident
programs and device drivers.  Shadow RAM is always located outside of
the DOS memory space.

     4.  High RAM.  This is RAM located outside of the DOS memory space.
This memory can be used only by specially-designed applications.

     5.  ROM Copy.  The page frame is RAM that contains a copy of a ROM.
The RAM is always located at the same address where the ROM was
originally located.  The advantage of ROM Copy is that it can speed up
the execution of ROM code.

     Some of the parameters let you control the usage of individual page
frames.  These parameters accept a single hexadecimal address, or a
range of hexadecimal addresses.  If you specify a single hexadecimal
address, then the entire 16K page frame containing that address is
affected (for example, EMM.EXCLUDE=CA00 excludes the entire page frame
from C800 to CBFF).  If you specify a range of hexadecimal addresses,
then all page frames that overlap any part of the specified range are
affected (for example, EMM.SHADOW_RAM=D000-E000 creates shadow RAM in
the five page frames at addresses D000 to E3FF;  if you only wanted to
create shadow RAM in the four page frames at addresses D000 to DFFF you
would use EMM.SHADOW_RAM=D000-DFFF).



EMM.CONFIGURATION = EMS_ONLY | EMS_AND_SHADOW | SHADOW_ONLY

     Controls the overall configuration of the expanded memory and
shadow RAM manager.  This parameter determines the default usage of page
frames.  It can be overridden for any particular page frame with the
EMM.INCLUDE, EMM.HIGH_RAM, or EMM.SHADOW parameters.

     EMS_ONLY makes the memory manager use all available page frames for
paged EMS memory.  No shadow RAM is created.

     EMS_AND_SHADOW allocates as many page frames as possible for shadow
RAM, while still supporting expanded memory.  Some page frames are still
used for paged EMS memory, but as few as possible.

     SHADOW_ONLY makes the memory manager use all available page frames
for shadow RAM.  No expanded memory support is provided.  If you specify
SHADOW_ONLY, then the following parameters cannot be used:
EMM.FRAME_ADDRESS, EMM.CONTEXTS, EMM.EXTENDED_EMULATE, EMM.HANDLES,
EMM.INCLUDE, EMM.FRAME_SIZE, EMM.NONSTANDARD_PAGE.

     The default value for this parameter is EMS_ONLY.

     Exception:  For Generic EMS, the value must be EMS_AND_SHADOW or
SHADOW_ONLY;  the default value is EMS_AND_SHADOW.

     Exception:  For the AT/386 or PEAK chipset, the only allowed value
of this parameter is SHADOW_ONLY, and SHADOW_ONLY is the default.



EMM.FRAME_ADDRESS = xxxx

     Desired starting address of the standard EMS page frames.  The
value is a segment address in hexadecimal, and must be on a 16K
boundary.  If this parameter is omitted, the memory manager
automatically determines an appropriate default value based on the
system's hardware configuration.

     Note:  This parameter is not valid for the NEAT chipset.  With the
NEAT chipset, you use your computer's setup program to select the
standard EMS page frame address.

     Example:  To specify a frame address of D000, use
EMM.FRAME_ADDRESS=D000.



EMM.FRAME_SIZE = nn

     The desired number of 16K page frames in the standard EMS area.
The value can range from 2 to 12, and defaults to 4.

     Caution:  Many programs will not work correctly if the value of
this parameter is different than 4.  You should not use this parameter
unless you know what you're doing.



EMM.CONTEXTS = nn

     Number of expanded memory context save areas.  The value can range
from 32 to 255, and defaults to the value of EMM.HANDLES.

     This parameter controls an internal resource of the expanded memory
manager.  The default value should be adequate for almost any purpose.

     Example:  To allocate 128 contexts, use EMM.CONTEXTS=128.



EMM.HANDLES = nn

     Number of expanded memory handles.  The value can range from 32 to
255, and defaults to 64.

     This parameter controls an internal resource of the expanded memory
manager.  The default value should be adequate for almost any purpose.

     Example:  To allocate 128 handles, use EMM.HANDLES=128.



EMM.FRONTFILL_SIZE = nnn

     The desired size of DOS memory, in kilobytes.  The value 0 can be
used to request that the size of DOS memory not be changed.  Default is
to make DOS memory as large as possible.

     This parameter cannot be used to reduce the size of DOS memory
below its initial value.

     Example:  To make DOS memory 672K in size, use the parameter
EMM.FRONTFILL_SIZE=672.



EMM.VGA = ON | OFF

     Specifies the initial state of EGA or VGA graphics.  Default is ON.
This parameter is ignored if you don't have an EGA or VGA, or if DOS
memory is not frontfilled into the EGA/VGA graphics memory area.

     The EGA and VGA video cards use memory locations A000-AFFF to hold
video RAM for the high-resolution graphics modes.  Unfortunately, these
are the same memory locations required to frontfill (increase the size
of) DOS memory.  Therefore, Invisible RAM gives you the ability to
enable or disable the high-resolution graphics modes.  When
high-resolution graphics is enabled, DOS memory size is limited to 640K.
When high-resolution graphics is disabled, DOS memory size can be
increased to 736K (for a color system) or 704K (for a monochrome
system).

     This parameter determines the initial state of EGA/VGA graphics.
ON means that high-resolution graphics is enabled, while OFF means that
high-resolution graphics is disabled.  After Invisible RAM is started,
you can use the VGAON and VGAOFF programs to enable or disable EGA/VGA
graphics.

     Example:  If you want to disable high-resolution graphics, allowing
DOS memory to increase to 736K, use EMM.VGA=OFF.



EMM.CODE_LOCATION = DOS | SHADOW

     Specifies the type of memory to be used for the memory manager
program code.  Default is SHADOW.

     Example:  To keep the memory manager program code in DOS memory,
enter EMM.CODE_LOCATION=DOS.



EMM.TEST_LEVEL = SHORT | LONG | DEFAULT

     Specifies the type of test to be performed on the memory hardware.
Default is DEFAULT.  The DEFAULT test consists of a LONG test following
a cold boot (power-on), or a SHORT test following a warm boot
(Ctrl-Alt-Del).

     This parameter is provided because the LONG memory test can take a
lot of time.

     Example:  If you always want to use the fast memory test, enter
EMM.TEST_LEVEL=SHORT.



EMM.PORT = xxx

     The I/O port address for the Invisible EMS memory board, in
hexadecimal.  Allowed values are 208, 218, 248, 258, 2A8, 2B8, 2E8, and
2F8.  The default is 208.

     This parameter is valid only for the Invisible EMS memory board.
Refer to the Invisible EMS instruction manual for additional
information.

     Example:  If the port address on the Invisible EMS memory board is
set to 218, you would use EMM.PORT=218.



EMM.EXTENDED_EMULATE = nnnn

     If this parameter is included, Invisible RAM uses part of your
expanded memory to emulate extended memory.  The value is the desired
size of extended memory, in kilobytes.  The value can range from 0 to
14336, and defaults to 0.

     Note:  This parameter is not valid for the 386 virtual mode memory
manager (Invisible RAM 386).  For 386 virtual mode, use CP386.EXTENDED
instead.

     Example:  To emulate 2048K of expanded memory, use
EMM.EXTENDED_EMULATE=2048.



EMM.NONSTANDARD_PAGE = nnn

     Directs the expanded memory manager to create a non-standard
physical page.  The allowed values are 254 and 255.  This parameter may
appear in the initialization file more than once, if you need more than
one non-standard page.

     This parameter is useful only with IBM DOS 4.0 (<MI>not<D> MS-DOS
4.0), when using the expanded memory features of IBM DOS 4.0.



EMM.EXCLUDE = xxxx  |  xxxx-yyyy

     Specifies one or more 16K page frames that are not to be used.  The
value can be either a single hexadecimal segment address, or a range of
hexadecimal segment addresses.  This parameter may appear in the
initialization file more than once, if you need to exclude more than one
range of addresses.

     This parameter prevents Invisible RAM from using page frames that
it would otherwise use.  A common application of this parameter is to
prevent a conflict with installed hardware, in cases where Invisible RAM
cannot automatically detect the hardware.

     Example:  VGA video systems can support both color and monochrome
text modes, regardless of whether you have a color or monochrome
monitor.  In color text modes, memory locations B800-BFFF are used for
video RAM, while memory locations B000-B7FF are empty.  In monochrome
text modes, memory locations B000-B7FF are used for video RAM, while
memory locations B800-BFFF are empty.  When Invisible RAM initially
loads, it would normally use the "empty" memory locations for paged EMS
memory or shadow RAM.  This will create a conflict, causing the system
to crash, when you switch from color to monochrome or vice-versa.  To
prevent this, you can exclude the entire range of memory from B000 to
BFFF by entering EMM.EXCLUDE=B000-BFFF.



EMM.INCLUDE = xxxx  |  xxxx-yyyy

     Specifies one or more 16K page frames that are to be used as paged
EMS memory.  The value can be either a single hexadecimal segment
address, or a range of hexadecimal segment addresses.  This parameter
may appear in the initialization file more than once, if you want to
create paged EMS memory in more than one range of addresses.

     Caution:  With some memory hardware (NEAT chipset, AT/386 chipset,
SCAT chipset, PEAK chipset, or 386 virtual mode), specifying a page
frame that overlaps a ROM will cause the ROM to be disabled.  This
should only be done if you are certain that the ROM is not needed.

     Example:  This example applies only to the NEAT chipset, AT/386
chipset, SCAT chipset, PEAK chipset, and 386 virtual mode memory
managers.  Many color video boards have video RAM at memory locations
BC00-BFFF which is never used.  You can disable this unused video RAM,
and create paged EMS memory in its place, with EMM.INCLUDE=BC00.



EMM.DEFAULT_RAM = xxxx  |  xxxx-yyyy

     Specifies one or more 16K page frames which are to be used in the
default manner (either shadow RAM or paged EMS memory, according to the
value of EMM.CONFIGURATION).  The value can be either a single
hexadecimal segment address, or a range of hexadecimal segment
addresses.

     This parameter forces Invisible RAM to use page frames that it
would otherwise not use.  This parameter may appear in the
initialization file more than once, if you want to force Invisible RAM
to use more than one range of addresses.

     If you wish to force a particular usage for the page frames, you
should specify EMM.INCLUDE, EMM.SHADOW_RAM, or EMM.HIGH_RAM instead of
EMM.DEFAULT_RAM.

     Caution:  With some memory hardware (NEAT chipset, AT/386 chipset,
SCAT chipset, PEAK chipset, or 386 virtual mode), specifying a page
frame that overlaps a ROM will cause the ROM to be disabled.  This
should only be done if you are certain that the ROM is not needed.

     Example:  This example applies only to the NEAT chipset, AT/386
chipset, SCAT chipset, PEAK chipset, and 386 virtual mode memory
managers.  Many computers have a setup program located in ROM at
addresses F000-F7FF.  Once the computer is started, the setup program is
no longer needed.  You can disable the setup program ROM, and make an
extra 32K of memory available, with the parameter
EMM.DEFAULT_RAM=F000-F7FF.

     Example:  This example applies only to the Invisible EMS memory
board.  On AT-class computers, the memory from E000 to EFFF may or may
not be available.  The memory manager cannot tell if it is available,
and so by default it does not use the page frames in E000-EFFF.  If this
memory is available on your computer, you can make the memory manager
use it with EMM.DEFAULT_RAM=E000-EFFF.  This makes an extra 64K of
memory available.



EMM.SHADOW_RAM = xxxx  |  xxxx-yyyy

     Specifies one or more 16K page frames that are to be used as
unpaged shadow RAM.  The value can be either a single hexadecimal
segment address, or a range of hexadecimal segment addresses.  This
parameter may appear in the initialization file more than once, if you
want to create shadow RAM in more than one range of addresses.

     Shadow RAM can be used to hold memory-resident programs and device
drivers.  The Invisible LAN programs are loaded into shadow RAM by
setting appropriate parameters in the initialization file (for example,
REDIRECTOR.SHADOW=YES to put the redirector program into shadow RAM).
Other programs are loaded into shadow RAM with the LSHADOW utilities.

     Caution:  With some memory hardware (NEAT chipset, AT/386 chipset,
SCAT chipset, PEAK chipset, or 386 virtual mode), specifying a page
frame that overlaps a ROM will cause the ROM to be disabled.  This
should only be done if you are certain that the ROM is not needed.

     Example:  This example applies only to the NEAT chipset, AT/386
chipset, SCAT chipset, PEAK chipset, and 386 virtual mode memory
managers.  Many monochrome video boards have video RAM at memory
locations B400-B7FF which is never used.  You can disable this unused
video RAM, and create 16K of shadow RAM in its place, with
EMM.SHADOW_RAM=B400.



EMM.HIGH_RAM = xxxx  |  xxxx-yyyy

     Specifies one or more 16K page frames that are to be used as
unpaged high RAM.  The value can be either a single hexadecimal segment
address, or a range of hexadecimal segment addresses.  This parameter
may appear in the initialization file more than once, if you want to
create high RAM in more than one address range.

     High RAM is not actually very useful, since only specially-designed
programs can use it.

     Caution:  With some memory hardware (NEAT chipset, AT/386 chipset,
SCAT chipset, PEAK chipset, or 386 virtual mode), specifying a page
frame that overlaps a ROM will cause the ROM to be disabled.  This
should only be done if you are certain that the ROM is not needed.



EMM.ROM_COPY = xxxx  |  xxxx-yyyy

     Specifies one or more 16K page frames which are to be filled with
RAM that contains a copy of any ROM within the page frame(s).  This can
result in faster execution of ROM code, because RAM is faster than ROM.
The value can be either a single hexadecimal segment address, or a range
of hexadecimal segment addresses.  This parameter may appear in the
initialization file more than once, if you want to copy ROMs in more
than one range of addresses.

     This parameter is ignored if the memory hardware cannot perform the
ROM copy.  (If you are using the TransBIOS ROM, the memory manager
automatically detects it and performs the ROM copy, without any need to
specify a ROM_COPY parameter.  If you want to suppress the copying of
the TransBIOS ROM, use EMM.EXCLUDE.)

     Example:  Most EGA and VGA video boards have a ROM occupying
addresses C000-C5FF.  To copy the ROM into RAM, thereby speeding up
video operations, use EMM.ROM_COPY=C000-C5FF.




====== INVISIBLE RAM 386 CONTROL PROGRAM PARAMETERS ===================




     Invisible RAM 386 (the memory manager for 386 virtual mode) is
structured differently than the other memory managers.  Invisible RAM
386 actually consists of two programs:  a "386 control program" and a
"memory manager program".  The memory manager is configured with the
memory manager parameters that are described in the previous section.
However, the 386 control program has its own separate set of parameters,
which are described in this section.

     These parameters control the Invisible RAM 386 control program.
They are ignored if Invisible RAM 386 is not requested by the
NET30.MEMORY=386_VIRTUAL parameter, or if Invisible RAM 386 is installed
in CONFIG.SYS.



CP386.EXTENDED = nnnn

     The amount of extended memory to reserve for extended memory
applications, such as VDISK.  The value is given in kilobytes.  The
default is 0 if CP386.XMS=NO is specified, or 64 if CP386.XMS=YES is
specified.

     This parameter is also used to reserve extended memory for the
Invisible disk cache.  This is highly recommended, since extended memory
gives better performance for the cache than expanded memory.

     Caution:  If you are using VDISK (a RAM disk program that uses
extended memory), make sure the value specified with this parameter is
greater or equal to the amount of extended memory used by VDISK.

     Example:  To reserve 2048K of extended memory for the disk cache,
use CP386.EXTENDED=2048.



CP386.XMS = YES | NO

     Specifies whether the control program should provide an
XMS-compatible interface to the first 64K of extended memory.  Default
is NO.

     XMS stands for "Extended Memory Specification".  It is an interface
defined by Microsoft, that lets DOS programs use the first 64K of
extended memory.  Microsoft supplies a device driver called HIMEM.SYS,
that provides the XMS interface.  With Invisible RAM 386, you cannot use
HIMEM.SYS.  Instead, you use CP386.XMS=YES to install an XMS interface
compatible with HIMEM.SYS.



CP386.HMAMIN = nn

     Specifies the smallest program, in kilobytes, that can use the XMS
interface.  The value can range from 0 to 63, and defaults to 0.  If
CP386.XMS=NO is specified, this parameter is ignored.

     Example:  Only one program at a time can use the XMS interface, so
it is a good idea to select a program that can use it efficiently.  If
you enter CP386.HMAMIN=32, then a program will be able to use the XMS
interface only if it can use at least half of the available 64K.

     Note:  This parameter is equivalent to the "/HMAMIN=" parameter
that is supported by Microsoft's HIMEM.SYS device driver.



CP386.REGISTER_SETS = nn

     The number of alternate EMS register sets to be supported.  The
value can range from 0 to 255, and defaults to 7.

     EMS register sets are used by multitasking programs, such as
Quarterdeck's Desqview.  They provide a quick way to change the mappings
of all the EMS page frames.  Generally, you should allow one register
set for each concurrent task, plus two or three extra sets.

     Example:  To allocate 32 alternate register sets, use
CP386.REGISTER_SETS=32.



CP386.STACKS = nn

     The number of stack frames to be allocated for processing hardware
interrupts.  The value can range from 8 to 64, and defaults to 16.

     Note:  This parameter is equivalent to the first number appearing
in the STACKS command of CONFIG.SYS.  When using Invisible RAM 386, we
recommend putting STACKS=0,0 in the CONFIG.SYS file, and using
CP386.STACKS and CP386.STACK_SIZE instead.



CP386.STACKSIZE = nnn

     The size, in bytes, of the stack frames that are used for
processing hardware interrupts.  The value can range from 32 to 512, and
defaults to 128.

     Note:  This parameter is equivalent to the second number appearing
in the STACKS command of CONFIG.SYS.  When using Invisible RAM 386, we
recommend putting STACKS=0,0 in the CONFIG.SYS file, and using
CP386.STACKS and CP386.STACK_SIZE instead.

     Example:  To set the interupt stack size to 256 bytes, use the
parameter CP386.STACK_SIZE=256.



CP386.BIOS_SIZE = nnn

     The size, in kilobytes, of the computer's BIOS ROM.  The value can
range from 8 to 128, and defaults to the actual physical size of the
BIOS ROM.

     Some BIOS ROMs have a setup program located in the lower portion of
the BIOS ROM.  With this parameter, you can tell Invisible RAM 386 to
disregard the lower portion of the BIOS ROM, thereby freeing up more
space for shadow RAM.

     Note:  Much the same effect can be achieved using the
EMM.DEFAULT_RAM parameter for the memory manager.

     Example:  For this example, assume your computer has 64K BIOS ROM
at addresses F000-FFFF.  The lower 32K (at addresses F000-F7FF) contains
a setup program that is not needed during normal computer operation.
You can use CP386.BIOS_SIZE=32 to tell Invisible RAM 386 to treat the
BIOS ROM as if it were only 32K in size.



CP386.DMA_0_BUFFER_SIZE = nnn
CP386.DMA_1_BUFFER_SIZE = nnn
CP386.DMA_2_BUFFER_SIZE = nnn
CP386.DMA_3_BUFFER_SIZE = nnn
CP386.DMA_4_BUFFER_SIZE = nnn
CP386.DMA_5_BUFFER_SIZE = nnn
CP386.DMA_6_BUFFER_SIZE = nnn
CP386.DMA_7_BUFFER_SIZE = nnn

     The size, in kilobytes, of the data buffers used for DMA.  In
general, values can range from 0 to 128, with a default of 12.  However,
the actual minimum, maximum, and default values vary with the system's
hardware.

     DMA ("direct memory access") is a way of transferring data between
the computer system and a high-speed peripheral device, such as a disk
drive or network.  With Invisible RAM 386, DMA cannot transfer data
directly to or from an application program's buffer.  Instead, DMA is
performed as follows:

     1.  Peripheral to Memory.  To transfer data from a peripheral
device to an application, Invisible RAM 386 first uses DMA to transfer
data from the peripheral device to the DMA data buffer.  Then Invisible
RAM 386 copies the data from the DMA data buffer to the application
program's buffer.

     2.  Memory to Peripheral.  To transfer data from an application to
a peripheral device, Invisible RAM 386 first copies the data from the
application program's buffer to the DMA data buffer.  Then Invisible RAM
386 uses DMA to transfer data from the DMA data buffer to the peripheral
device.

     Each DMA channel has a separate buffer.  The buffer must be as
large as the largest DMA operation that is ever performed on the
corresponding DMA channel.  The DMA data buffers are located in extended
memory, so they do not take any memory away from DOS.

     Example:  You can save memory by specifying a buffer size of zero
for unused DMA channels.  For example, if DMA channel 7 is not used in
your computer, you can save memory with CP386.DMA_7_BUFFER_SIZE=0.

     Example:  Some (but not all) computers need 64K of DMA to format a
floppy diskette.  Since the floppy diskette uses DMA channel 2, you
would specify CP386.DMA_2_BUFFER_SIZE=64.




====== SETUP PROGRAM PARAMETERS =======================================




The following parameters are used internally by the network Setup program.
They have no effect on any other part of Invisible LAN.



SETUP30.EASY = YES | NO

     Specifies whether or not the initialization file was created with
the "Easy Configuration" section of the Setup program.  YES means that
the initialization was created by "Easy Configuration", and NO means
that the file was created by "Advanced Configuration" or a text editor.
Default is NO.

     When you enter the "Easy Configuration" section of the Setup
program, it checks the value of this parameter.  If the SETUP30.EASY
parameter has the value NO (or if the parameter is omitted), then the
Setup program issues a warning message.  The warning message says that
if you use "Easy Configuration", all the advanced parameters will be set
back to their default values.  The purpose of this warning is to prevent
you from accidentally erasing the parameters that you established by
using "Advanced Configuration" or by editing the initialization file.

     If you edit the initialization file with a text editor, you should
always set this parameter to NO (or delete the parameter).



SETUP30.EMS = YES | NO

     If the initialization file is created by the "Easy Configuration"
section of the Setup program, this parameter records the setting of the
"USE EMS" field.  This parameter is used internally by the Setup
program, it has no effect on any other program.



SETUP30.SHADOW = YES | NO

     If the initialization file is created by the "Easy Configuration"
section of the Setup program, this parameter records the setting of the
"USE SHADOW" field.  This parameter is used internally by the Setup
program, it has no effect on any other program.
