Computer Shopper 108/gp2demo.iso/business/mshare/disk2/MSRFILES.2/CLIENT.CON

Text File | 1996-06-27 | 34.5 KB | 834 lines

@@Main Menu Choices
From the Main menu you must select either a parameter file
type (ModemShare server or ModemShare client) or choose
the Quit option to exit from the Parameter Editor.

Choosing a parameter file type will automatically begin an
editing session for the parameter type you selected.
@@Client Edit Menu Choices
From the Client Edit menu you select one of the general
categories shown to change the values. To end the edit
session, select the File option and choose either Quit
(which discards any changes) or Save (which saves any
changes that you have made).
@@Done
Choose this option when you have finished editing all of
the categories for the object you have selected.
@@Buffer Size
Specify the amount of space (in bytes) to be reserved for
buffers. Buffers are used to hold information sent to and
received from the ModemShare server. Generally, the
movement of information across the network (between the
server and ModemShare client) is much faster than the
movement of data across communication lines. Data is
therefore saved in buffers until it can be sent by the
server or received by the communications program being
run in the client. Providing more buffer space in a client
allows the system to more efficiently process your
communication data since there will be fewer conditions in
which the system will need to wait for buffer space. The
default value is 8192 bytes and the minimum value is 6144
bytes.
@@Client Communications Parameters
Specify communications parameters (baud rate, parity,
data bits, and stop bits) and select the type of flow
control desired. While the type of flow control desired
should always be specified, the remaining communications
parameters should not be supplied if you want to use the
default parameters provided by the ModemShare server.

Communications values specified by the ModemShare client
will override the server values when a connection is made.
@@Client Flow Control
Specify whether or not you want to use flow control and,
if so, the type of flow control desired. You shouldn't
specify flow control if you want to use the default flow
control provided by the ModemShare server, as any value
you specify here will override the server value when a
connection is made.
@@Client Server Name
In ModemShare, servers are not separated by name.
Any ModemShare server that has a line available which
matches the ModemShare client request can make the
connection.

Server names can have a maximum of 16 characters unless
you're using the NASI interface, in which case the server
name can have a maximum of eight characters.

IMPORTANT NOTE for NASI users - the NASI architecture
expects that each server will have a different name. In
addition, NASI expects that -

  o  Every line will belong to at least one group
  o  You will not have duplicate group/line pair names
     on different Servers

INSYNC ModemShare permits duplicate group/line pair names
to exist. Having duplicate group/line pair names may
cause problems for communications programs using the NASI
interface.

You can avoid any problems using the NASI interface if you

  o  Ensure that server, group, and line names don't
     exceed the maximum lengths for the NASI interface
  o  Make sure that each line name is unique across all
     servers
  o  Make sure that each line belongs to at least one
     group
@@Client Connection Values
Specify the information used to request a connection from
a ModemShare server. This information includes the name of
the server, the name of a group of lines or a specific
line name requested. You also select whether or not you
want:
  o  The ModemShare client to automatically retry the
     connection request if no server answers
  o  A server to queue the request if all the lines that
     could be used to satisfy the request are in use.

A connection can also be requested by passing a string
(usually a phone number) which will be automatically sent
to the modem (the modem must be Hayes-compatible).
@@Client Network Parameters
Specify various parameters that control such things as how
long a ModemShare client will wait for a response for
service, and the size of and frequency of sending packets
(blocks of data) over the network. All parameters in this
area have default values and you shouldn't specify any of
these parameters unless you have a specific reason to do
so.
@@Client Inbound Service
Specify the default service name that the ModemShare
client will respond to (accept) if a ModemShare server
requests a client to accept an incoming call. The name
supplied here is used only if the client is conditioned
to accept an incoming call using the INHOST program
without specifying a service name.

Note that the inbound facility isn't the same as a client
using a modem to auto-answer an incoming phone call.
@@Client Group/Line Name
This name is used when requesting a port from a
ModemShare server.

The name can be either the name of a group, which is a
collection of lines having common characteristics so
that they are interchangeable from the user point of view,
or the name of a specific line being requested.

You may not specify this value if you supply a value for
the Phone connect option.

The maximum length of a group or line name for
installations that don't use the NASI interface is 16
characters. If you use the NASI interface, group names
are limited to eight characters and line names must not
be longer than 14 characters.
@@Client Phone String
This value is used when you want to automatically dial the
specified number on making a connection with a ModemShare
server. In order to use this feature-

 o Your server must support a group name of NULL

 o You must have a Hayes-compatible modem connected to the
   line selected by the server

 o You must not supply a value for the ModemShare client
   group/line option
@@Save or Quit
Select "Save" to save any changes that you've made or
"Quit" to abandon this edit session without saving your
changes.
@@Station Type
You must select a parameter file type (ModemShare server
or ModemShare client) to create or edit.
@@Save Changes
This option will save any changes that you've made to the
parameter file and then exit from the edit session.
@@Flat Network
A flat network is one that has only one leg (no bridges or
routers) or uses transparent bridges. During
initialization, all stations attempt to dynamically
locate any bridges on the network by sending broadcast
messages. This process is repeated until all bridges have
been located;it may require many broadcast messages to be
sent over the network. If your network has only one leg,
the process is unnecessary. If your network uses
transparent bridges, the process is also not necessary
since a transparent bridge doesn't require special
handling to send packets to the other side of the bridge.

The value specified here has no meaning for the Lite
version since the Lite version supports only a single
network leg.
@@Abandon Edit
This option will provide exit from your edit session
without saving any changes you have made to the parameter
file.
@@Quit Program
Selecting this option will cause the Parameter Editor
to return to DOS.
@@Server
Choose this option if you want to edit a Parameter Set for
use by a ModemShare server.
@@Client
Choose this option if you want to edit a Parameter Set for
use by a ModemShare client.
@@File Name
This is the DOS file name for the parameter file. Be sure
to use a fully qualified name (a name that includes the
path) if the file you're editing doesn't exist in the
current directory.

If you're creating a new parameter file, you should also
specify a fully qualified name if you don't want the file
created in the current directory.
@@Parameter Set
Parameter files can contain up to 99 different collections
of parameters, called parameter sets. When you start a
ModemShare server or ModemShare client, you can select
both the name of the parameter file and the parameter set
within the parameter file to use for initialization.
@@Line Speed
The baud rate desired for the communication line being
used.
@@Parity
The parity value desired for the communication line being
used.
@@Data Bits
The number of data bits desired for the communication line
being used. Only certain combinations of data bits and
stop bits are allowed. The valid combinations are:

Data Bits     Stop Bits

    5          1 or 1.5
    6          1 or 2
    7          1 or 2
    8          1 or 2
@@Stop Bits
The number of stop bits desired for the communication line
being used. Only certain combinations of data bits and
stop bits are allowed. The valid combinations are:

Data Bits     Stop Bits

    5          1 or 1.5
    6          1 or 2
    7          1 or 2
    8          1 or 2
@@XON
The Xon character (used only with Xon/Xoff protocols) is
used to indicate that sending or receiving should be
resumed. The character specified can be a decimal
number, or you can specify the value as a hexadecimal
number by adding the character "h" after the number.
For example, the values 17 and 11h are the same.
@@XOFF
The Xoff character (used only with Xon/Xoff protocols) is
used to indicate that sending or receiving should be
suspended. The character specified can be a decimal
number, or you can specify the value as a hexadecimal
number by adding the character "h" after the number.
For example, the values 19 and 13h are the same.
@@Server Edit Menu Choices
From the Server Edit menu you select one of the general
categories shown to change the values. To end the edit
session select the File option and choose either Quit
(which discards any changes) or Save (which saves any
changes that you have made).
@@Inactivity Timer
This value, specified in minutes, indicates that a
connection should be released if the ModemShare client is
inactive (hasn't sent or received any data) for the period
specified. Setting this value to zero indicates that no
inactivity timer should be used.
@@Server Timeout
This value, specified in seconds, indicates how long the
ModemShare client should wait after requesting a
connection for a response. This value need be adjusted
only if your network contains multiple "bridges" or
special configurations which cause the network response to
be delayed.
@@Packet Size
Specifies the size of individual network transmissions.
Unless you have a specific need to do so, you shouldn't
specify this value.

Since packets are always sent when they're full,
specifying a lower value will cause more frequent network
transmissions (which may make a computer more responsive)
at the cost of higher network overhead. Setting the value
to a number greater than the physical packet size on a
network will result in packets being split, which requires
multiple transmissions for a single packet.

If you choose to adjust the packet size you should also
review the value for the Packet Timer.
@@Character Timer
This value, specified in milliseconds, forces packet
(network) transmission if the time elapses without a
character being sent. This can be useful in improving the
responsiveness of the system when a terminal user is
typing data, but it will be at the cost of increasing
network overhead.

Network packets are always sent when they're filled, or if
the Packet Timer expires (see Packet Timer for more
information). To have any effect, this value must be lower
than the Packet Timer.
@@Packet Timer
This value, specified in milliseconds, forces packet
(network) transmission if the time elapses without a
packet being filled. This time starts when the first
character is placed in a packet and can be useful in
improving the responsiveness of the system when the
typical data transmissions are smaller than a packet.

When transmitting a file, this timer will also force
transmission of the last packet (if it isn't full).
@@NASI Level
Selects the NASI API specification to use. A value of 2
indicates that the NASI interface should return data as
specified in the Novell NASI API Reference published in
September, 1988. A value of 3 indicates that the NASI
interface should return data to conform to the Novell
version 3 documentation.

The default value is 2. If you are having trouble with
your communications programs correctly recognizing modem
status (such as the CTS or DSR signals), try running
with a value of 3.
@@Trigger Character
Trigger characters are any set (up to 16) of characters
that are to cause transmission of network packets. You
might, for example, want to specify the carriage return
character (0DH) to force packet transmission if you are
working in an interactive mode. This will cause packets to
be sent when you hit the ENTER key, rather than waiting
for a Packet Timeout or Character Timeout to occur. Note,
however, that trigger characters are bi-directional. That
is, they cause network transmission both from the
ModemShare client to the ModemShare server and from the
server to the client.
@@No Line Parameters in Client
The ModemShare client shouldn't have line parameters if
you want to use the default line parameters supplied by
the ModemShare server which provides a line for your
connection. If the client has line parameters they're
always used for establishing a connection.
@@Server Name
Specify the name to which this ModemShare server should
respond for the Remote Monitor program. Each server should
have a unique name.

If you're using the NASI interface, server names are
limited to eight characters; otherwise server names can
be up to 16 characters long.

IMPORTANT NOTE for NASI users - the NASI architecture
expects that each server has a different name. In
addition, NASI expects that -

  o Every line belongs to at least one group
  o You do not have duplicate group/line pair names
    on different servers

INSYNC ModemShare permits duplicate group/line pair names
to exist. Having duplicate group/line pair names may
cause problems for communications programs using the NASI
interface.

You can avoid any problems using the NASI interface if you

  o  Ensure that server, group, and line names don't
     exceed the maximum lengths for the NASI interface
  o  Make sure that each line name is unique across all
     servers
  o  Make sure that each line belongs to at least one group
@@Server Transmit Sets
Each transmit set is named and contains communications
parameters that can be applied as default settings to line
and group definitions. The information defined here
includes items such as line speed, parity, data bits,
and stop bits. In addition, information that controls
network transmission such as packet size, network
transmission timers and trigger characters is also
specified.

When you define a line or group, you can reference a
complete set of communication and network parameters
simply by giving the transmit set name. The parameters
associated with a line or group are used as the default
values for both communications and network transmission if
a ModemShare client doesn't provide these parameters when
requesting a connection. See the Help topic "Server
Values For a Connection" for a description of how the
complete set of communication and network parameters is
selected when a connection is made.

You should define a transmission set for each unique
combination of these (communication/network) parameters
that you want to apply to individual lines or line group
definitions.

For example, suppose that you have two physical ports on
the ModemShare server, one with a 4800-baud modem and the
other with a 9600-baud modem. You'll need two transmission
sets (one reflecting a 4800-baud line speed and the other
for the 9600-baud line). If both of the lines have the
same speed modem and you want to supply identical values
for both lines, only one transmission parameter set needs
to be defined.
@@Server Lines (Ports)
Each physical line that is to be shared by the ModemShare
server must be defined. This definition includes the
hardware address of the line and the interrupt level that
will be used to service the line. If you use standard
computer communications (async) ports, you'll be limited
to two lines because each needs a separate interrupt level
to operate properly. This is true even though most current
boards are capable of being addressed at one of four
different addresses.

Common name  Address   Interrupt level

   COM1        3F8          4
   COM2        2F8          3
   COM3        3E8          4
   COM4        2E8          3

Notice that even though four different addresses are used,
only two interrupt levels (3 and 4) are used. This means
that, for example, you could not use COM1 and COM3
together on the server.

Optionally, you can use a multiport board which contains
either four or eight external connections. A multiport
board uses only one interrupt level and, because two
interrupt levels are normally reserved for asynchronous
ports (actually, you can use any interrupt level that is
not in use), you can install two in each server.

In any case, you must know the correct hardware address
and interrupt level for each line (port) or the server will
not function properly. Please consult the hardware manuals
that came with your equipment to determine the proper
values to specify.
@@Server Group
Groups perform two primary functions in the ModemShare
server. The first is to give a name (which can then be
used by ModemShare clients to request connections) to a
set of lines that can supply a common service. For
example, you define a group of all lines which are
attached to a 4800-baud modem. Similarly, you could define
a group of lines attached to a 9600-baud modem. Since
almost all 9600-baud modems are capable of running at
4800-baud, you could include all of the 9600-baud lines in
the 4800-baud line group. This grouping allows clients to
request connections based on a general requirement (such
as line speed) and increases the likelihood that a line
will be available when requested. You can define any line
grouping that suits your requirements based on any
criteria that you choose.

The second use of a group is to apply different default
values to the same line or set of lines based only on the
name used in the connection request. You could, for
example, define a group called "DOWJONES" that contained
the proper communications parameters (speed, parity, flow
control, etc.) for accessing this service.

A group contains one or more lines and a single line may
belong to many groups.

IMPORTANT NOTE for NASI users - the NASI architecture
expects that each server will have a different name. In
addition, NASI expects that -

  o Every line will belong to at least one group
  o You don't have duplicate group/line pair names
    on different servers

INSYNC ModemShare permits duplicate group/line pair names
to exist. Having duplicate group/line pair names may
cause problems for communications programs using the NASI
interface.

You can avoid any problems using the NASI interface if you

  o  Ensure that server, group, and line names do not
     exceed the maximum lengths for the NASI interface
  o  Make sure that each line name is unique across all
     servers
  o  Make sure that each line belongs to at least one
     group
@@Server Inbound Service
Lines are marked as eligible for Inbound Service using the
group function.

Note that the inbound facility is not the same as a
ModemShare client using a modem to auto-answer an incoming
phone call. The advantage of the inbound facility is that
the line and modem can continue to be used for outgoing
calls. If a client allocates a line and modem, and sets
the modem in auto-answer mode, the line and modem are
unavailable for other use until the client releases the
connection.
@@Call Forward Name
Call Forward allows you to bypass the normal
conversation that the ModemShare server has with an
off-network caller and automatically runs the communication
program you selected when you ran the INHOST program. This
permits the communication program to see a full call
sequence since the server doesn't answer the phone.

For Call Forward to be active, the following conditions
must be met:

  o One or more ModemShare clients must have used the
    INHOST program using the same service name that you
    specify as the Call Forward name.
  o The group must have at least one line selected as an
    inbound line (see Help topic "Server Inbound Service").

If the above conditions are met, the server doesn't answer
the phone when a ring is detected. The service name is used
for a connection request as if the caller had typed it in
during the standard inbound conversation. If the request
fails, then standard inbound processing is started.

This function allows a communication program to answer the
phone rather than the server. That program could then take
different actions depending on the type of call. For
example, one use is to allow FAX/data/voice recognition by
a communications program.
@@Server Group Name
Group names are one to sixteen characters in length,
unless you're using the NASI interface, in which case the
names can't be longer than eight characters.

ModemShare clients can request a connection using either a
line name or a group name. Group names must be unique
within a ModemShare server (different servers can have the
same group name) and must not be the same as a line name.

IMPORTANT NOTE for NASI users - the NASI architecture
expects that each server has a different name. In
addition, NASI expects that -

  o Every line will belong to at least one group
  o You won't have duplicate group/line pair names
    on different servers

INSYNC ModemShare permits duplicate group/line pair names
to exist. Having duplicate group/line pair names may
cause problems for communications programs using the NASI
interface.

You can avoid any problems using the NASI interface if you

  o  Ensure that server, group, and line names don't
     exceed the maximum lengths for the NASI interface
  o  Make sure that each line name is unique across all
     servers
  o  Make sure that each line belongs to at least one group
@@Server Conference
The conference attribute can be associated with the lines
in a group and allows multiple ModemShare clients to connect
to the same line. This is a very powerful facility for users
who all want to see the same information, since only one
external connection is required. All users in the
conference are allowed to input data, so care must be
exercised to avoid interspersed data from being sent
to the off-network device. Conference is specified as either
half (H) or full (F) duplex which controls the echo of
characters input from one computer to all other computers
in the conference. H specifies that the off-network device
won't echo characters and causes the server to echo
input characters to all computers. F specifies that the
off-network device echoes characters and that the server
need not echo input characters to all computers.
@@Server Group Lines
You must specify which lines (ports) belong to each
group. Since 16 lines are supported, each group can have
16 lines. Lines are allocated by the ModemShare server in
the same order that you specify them.
@@Server Group Transmit
Just as a transmit set can be (and usually is) associated
with a line, a transmit set can also be associated with a
group. If you associate a transmit set with a group, the
parameters from the set specified are used as the default
values for connections made using the group name. If
no transmit set is associated with the group, the transmit
set associated with the line selected by the ModemShare
server will be used for default values.
@@Server Inbound Lines
Some or all of the lines in a group can be marked as
inbound service lines. Inbound lines will be set up by the
ModemShare server to answer incoming calls, interact with
the caller to determine what service is requested, and
attempt to locate a ModemShare client that is able to
accept the call. Lines that are set up as inbound lines are
still eligible to service outgoing calls.

The number you specify is the number of lines (starting
with the first line specified) that are to be set up for
inbound service. If you specify a number greater than the
number of lines in the group, all lines are set up for
inbound service.
@@Server Group Phone
A phone number can be associated with the lines in a group
which will cause the ModemShare server to automatically
dial the number specified when a connection is made using
the group name. The necessary Hayes-compatible control
characters are added to the number given.
@@Server Buffer Size
Specify the amount of space (in bytes) to be reserved for
buffers. Buffers are used to hold information sent to and
received from the ModemShare server. Generally, the
movement of information across the network (between the
server and client) is much faster than the movement of
data across communications lines. Data is therefore saved
in buffers until it can be sent by the server or received
by the communications program being run in the
client. Providing more buffer space in a
client allows the system to more efficiently
process your communication data since there will be
fewer conditions in which the system will need wait for
buffer space. The default value is 65536 bytes. The
minimum value for this parameter is 10240 bytes.
@@Server Log Size
Specify the amount of space (in bytes) to be reserved for
the activity log. The amount specified is taken from the
buffer and reduces the amount of available buffer space.
The activity log is used to record information about the
resources used by each connection. A connection record is
about 40 bytes long and the minimum size is 400 bytes
(enough space for 10 connection entries.) You must run
MONITOR to remove the entries from the
activity log and place the data in a file. The size of the
log required depends on the rate of connections and the
overall load on the system. See the INSYNC ModemShare
manual for information on collecting the activity log
records.
The default value is 0 bytes (no logging.)
@@Server Remote Monitor Password
You can require that a user on another computer running
the Remote Server Monitor enter a password for control
functions.
Control functions include actions such as breaking
connections and removing lines from service. The password
can be from one to 16 characters long and is encrypted in a
separate file which is read when the ModemShare server is
started. If you don't specify a password or set the
password to blanks, no password is required for issuing
control functions from the Remote Server Monitor.
@@Flow Control
Flow control is used to pace the interchange of data
between the ModemShare client and off-network device (or
program). Pacing is required since both sides are allowed
to transmit at the same time and some mechanism is needed
to prevent data from arriving faster than it can be
processed.
Three options are available -

Xon/Xoff uses "reserved" characters to signal the other
side when to suspend/resume transmission. This mechanism
works only when the data being transmitted doesn't
contain the values selected for the Xon or Xoff character.
In standard text interaction this works fine, but for
operations such as file transfers, Xon/Xoff can't be used
as any characters might be in the transmitted data.

No flow control is used when pacing is performed by a
"file transmission" protocol, such as XMODEM, YMODEM,
KERMIT, etc. These protocols are synchronous;
only one side is allowed to transmit at a time.

Hardware flow control is implemented by setting and testing
a hardware signal. This type of flow control can be used
for any type of transmission and is the preferred method.
This requires that your hardware (modem) and software
(communications package) support hardware flow control.
@@Server Transmit Set Name
Each transmit set has a name (up to four characters long)
that you must use in other definitions (such as line
definitions) to apply default communications parameters.
When you define lines and groups, you can reference a
complete set of communications and network parameters
simply by giving the transmit set name.
@@Server Permit Sets
Permit sets allow you to restrict access to a line. The
only computers that will be granted access to the line
named are those in the set of computers that you list.
Computers are identified by their 12 hexadecimal digit
network names assigned to the network adaptor card.
@@Server Values For a Connection
When a ModemShare server allocates a line to a ModemShare
client (makes a connection), a complete set of
communications and network parameters is required. The
order for collection of these parameters is -

 1) any value supplied by the client

 2) any value not supplied by a client but obtained from
    the server parameter file for the allocated line

 3) any value not supplied in either parameter file but
    defaulted based on values internally kept in the
    server program
@@Server Line Name
Each line (port) being shared by a ModemShare server must
havea name that is unique. (Different servers can have the
same line name.) The line name serves as a referent for
the line and can be used by a ModemShare client for a
connection request.

If you're using the NASI interface, line names can't be
longer than 14 characters; otherwise line names can be up
to 16 characters long.

IMPORTANT NOTE for NASI users - the NASI architecture
expects that each server has a different name. In
addition, NASI expects that -

  o Every line will belong to at least one group
  o You won't have duplicate group/line pair names
    on different servers

INSYNC ModemShare permits duplicate group/line pair names
to exist. Having duplicate group/line pair names may
cause problems for communications programs using the NASI
interface.

You can avoid any problems using the NASI interface if you

  o  Ensure that server, group, and line names don't
     exceed the maximum lengths for the NASI interface
  o  Make sure that each line name is unique across all
     servers
  o  Make sure that each line belongs to at least one group
@@Server Line Address
Each line (port) being shared by a ModemShare server must
have a hardware address that is unique and isn't being
used by any other device in the system. The address can be
specified either as a decimal or hexadecimal number
followed by the character h.

The standard "COM" addresses are shown below.


Common name  Address   Interrupt level

   COM1        3F8          4
   COM2        2F8          3
   COM3        3E8          4
   COM4        2E8          3

@@Modem Presence
Each line must specify whether or not a Hayes-compatible
modem is attached. If you indicate that a modem is
attached, the ModemShare server will check for the presence
of the modem and, if no modem is attached, will reset this
value.

Modems are required for lines that either have a phone
number associated (for automatic dialing) or are being
used with the inbound feature.

If you're using the INSYNC ModemShare inbound calling
feature, you must indicate that the line has a modem
attached, you may specify a setup string for the modem
and you can choose to set the port speed to the line
speed when an inbound call is detected. The alternative
to matching speeds is to fix the port speed at the value
selected in the server parameter file regardless of the
line speed detected when an incoming call is answered.
@@Inbound Setup String
Used only for inbound lines, this specifies the modem
initialization string that is to be used to condition
the modem to accept incoming calls. Lines that you
indicate have a modem but aren't marked as inbound lines
are reset with the string ATZ when a connection is
terminated.

The string can be up to 32 characters long and must begin
with the characters AT. A carriage return character is
always appended to the string.

The default setup string is ATQ0E1X1V1S0=0

The default string, for most Hayes-compatible modems, will
satisfy the ModemShare server requirements for inbound modem
conditioning. In order for inbound service to work
properly, your modem must be set to the following state:

 o  Commands must be echoed (E1 in the default string)
 o  Command responses must be returned (Q0)
 o  Verbal command responses must be returned (V1)
 o  Minimum set of command responses and trans-
      mission speed must be returned when a connection is
      made (X1)
 o  Auto answer must be disabled (S0=0)

In addition, you may need to set parameters to ensure:

 o  The modem is in DTR normal mode (drops a connection
    and returns to command state when DTR is dropped)

 o  Returns the port (not the line) speed when a
    connection is made, preceded by the characters
    CONNECT, for example: CONNECT 9600

The port speed returned is used only if you choose to
match speeds (see the description that follows). If
you aren't matching speeds, it doesn't matter what
speed is reported in the CONNECT string as the server
will ignore the information.

In addition to specifying an initialization string, you can
choose to have the port speed set to the line speed when an
inbound call is detected. The alternative to matching
speeds is to fix the port speed at the value selected in
the server parameter file regardless of the line speed
detected when an incoming call is answered.
@@Server Line Interrupt Level
You must specify the interrupt level being used by the
line. Care must be exercised to ensure that a single
interrupt level isn't used by more than one board or
the system won't operate properly. The possible
interrupt levels (and most common uses) are shown below.
The lower the number, the higher the priority (handled
first) in the system.

Level    Standard use

  0    Not available, used for timer
  1    Not available, used for keyboard
  2    Available, generally used for network cards and
    devices such as tape drives. If possible, you
    shouldn't run your network at a higher priority
    than your lines as the network activity could
    cause data overruns to occur in high-activity
    systems.
  3    Available, the "standard" COM2/COM4 level
  4    Available, the "standard" COM1/COM3 level
  5    In a PC (8088, 8086), not available if you have a
    hard disk
    In an AT (286/386/486), available if you aren't
    using LPT2 (the second parallel port). This is a
    good choice for your network card.
  6    If you have a floppy disk, not available
    Available for systems without a floppy disk
  7    Available if you are not using LPT1 (the primary
    parallel port)

Remember that standard "COM" boards each use an interrupt
level and that multiport boards can share a single
interrupt level.
@