____________

Introduction

This file contains a list of error messages generated by the Eicon Technology
WAN Services for Windows NT software. The messages are organized by program and
error
code number as follows:

Code Category
--------------------------------------------------------------
AC ECMODULE error messages
AD ECDIALER error messages
EC Error messages common to many Eicon Technology programs
FA ECTEST error messages
LT SLP error messages
NI MPR error messages
NI MPRCCT error messages
NI IPMAP error messages
NI General Router error messages
NI Event Viewer error messages
PD ECCARD error messages
SN ECSNMP error messages
XR X.PAD error messages
_______________________
Error Message Structure

All error messages returned by Eicon Technology drivers and command-line

utilities follow a standard structure:

MODULENAME: Error #AA999.

General description of problem. Suggested user remedy (ECNB code if
applicable).

Each error message documented in this chapter provides you with a simple
explanation of the problem you are facing, and suggests a solution. Detailed
technical information is sometimes included: this helps the Customer Services
personnel at Eicon Technology or your representative to diagnose the
situation.

Please note that xxxxxxxx represents an alphabetic variable, and that nn

represents a numeric variable.

________
ECMODULE

@AC001

Parameter entry error. The port number you specify must fall between 1 and
48.

The port number specified on the command line fell outside the range of valid
port numbers.

@AC002
Parameter entry error. The connection number that you specified is not in
use.

The connection number provided on the command line does not correspond to a
connection currently in use. Refer to the reference guide for information
about using ECMODULE correctly.

@AC003

Memory shortage. Unload programs, or reduce the number of allocated sessions.

There is not enough available memory in the computer to run the Eicon
Technology software. Free memory by removing unnecessary resident programs
and drivers. Reducing the number of allocated sessions will also free memory.

@AC004

Parameter entry error. The station number that you specified (nn) is not in
use.

The station number provided on the command line does not correspond to a
station currently in use. Repeat the procedure with a valid station number.

@AC005

Required protocol missing or not configured for the specified port. Load the
protocol xxxxxxxx with ECCARD and try again.

The protocol identified by xxxxxxxx has not yet been loaded on the EiconCard.
Use ECCARD START to load the protocol, and try again. Ensure that the
protocol has already been configured.

@AC006

Parameter entry error. The LU Name xxxxxxxx that you specified does not
exist.

The Logical Unit (LU) specified on the command line could not be found by the
Eicon Technology software. The LU name may have been misspelled or contain
invalid characters. Check to see that the LU name has been entered in the
table of valid LU's. If necessary, configure or create the LU with the
configuration program.

@AC007

Parameter entry error. The Session ID number specified (nn) does not exist.

The Session ID number that was specified on the command line does not
correspond to a session that is currently active. Thus, no action can be
taken by the Eicon Technology software.

A session is a single conversation between a PC or terminal, and a host

computer. These sessions are identified by WAN Services with
unique identification numbers. Use the ECMODULE command to view the Session
ID number for each connection.

@AC008

Parameter entry error. The mode that you specified (xxxxxxxx) does not exist.

The mode you specified on the ECMODULE command line is invalid. Type ECMODULE
/? for a list of valid modes.

@AC009

File not found: xxxxxxxx.

The Eicon Technology software was unable to find the file represented by
filename xxxxxxxx. Check that the file is on the computer's hard disk, and is
in the same directory as the software that produced this message.

@AC010

Parameter entry error. Invalid trace filter (xxxxxxxx).

The trace filter that you specified (represented by xxxxxxxx) was not
recognized by the Eicon Technology software. Verify that the command line was
correctly typed.

@AC011

Parameter entry error. Invalid trace size. Range is 0 to 65534 (xxxxxxx).

The value you entered for the trace size was outside the proper range. Enter
a value between 0 and 65534.

@AC012

Parameter entry error. Invalid trace truncation length.

The value you entered for truncating the trace buffer was incorrect. The
value for the trancation parameter must be at least 16. If a lower value is
entered, then the above error message is issued, and the value of 16 is used.
There is no upper limit.
@AC013

Trace not started

You cannot stop the trace because the trace is not running. The command was
ignored.

@AC014

DIALER option is not suported by this version of ECMODULE.

The current version of ECMODULE does not allow you to use the DIAlER option.
Contact Eicon Customer Services for more information.

@AC015

ECEXIT.NLM resource unavailable. Attempt running program until resource

becomes available.

Resources used by ECEXIT are busy. Try running your program again after a
short time. The resources will become available eventually.

@AC016

The xxxxxxx module did not return control to ECMODULE in time(nn). Please
UNLOAD the xxxxxxx module.

ECMODULE is having difficulty communicating with the module referred to by

xxxxxxx. Control was supposed to be passed back to ECMODULE within a certain
period (nn), but it was not. Use the UNLOAD command to remove the module
from memory. You may reload it later.

@AC017

Could not run xxxxxxx. (nn)

The module referred to by xxxxxxx was not able to run. This may indicate a
serious internal software error. Try restarting the system, and if that does
not work, try reinstalling the software. Make note of the error code (nn) and
contact Eicon Customer Support if the problem continues.

@AC021

Bad output file name. Name "xxxxxxx" is a directory.

The system cannot write data to the specified filename -- the name is a
directory, not a file.
@AC022

Gateway or Router options not supported by ECBIOS for this version.

The current version of ECMODULE does not allow you to use the gateway or
router options. Contact Eicon Customer Services for more information.

@AC018

Invalid board name for ECEXIT.NLM.

@AC019

Internal software error: PFspawnvp_signal() (nn)

This indicates an serious internal error. If it persists, try reinstalling

the software. If the problem persists, make note of the error code (nn),
and contact Eicon Customer Services.

@AC020

Parameter entry error. The EiconCard number you specify must fall
between 1 and 6.

You cannot have more than six EiconCards in a given PC. You must specify a
value from 1 to 6 for the EiconCard number.

@AC100

Required driver or redirector missing. Load the driver with ECCARD or the
redirector with ECLAN.

A critical driver has not yet been loaded into memory. Check the reference
guide for information about using the ECCARD and ECLAN commands.

@AC101

Server not responding. Check to see if the server's redirector is loaded.

The PC acting as the gateway server is not acknowledging calls placed to it

through the LAN. The gateway PC may be disconnected, not running its gateway
software, have a configuration error, or its name may simply be incorrectly
typed. Check the gateway status by running the ECLAN STATUS SERVER /S command
on the Server or the ECLAN STATUS SERVER /S command on a client workstation.
@AC102

Resource shortage. Too many sessions are active on the redirector or on the
server.

There are not enough ECBIOS sessions available for the requested operation.
This shortage could be occurring on the redirector (workstation) or on the
server (gateway). Try increasing the number of ECBIOS sessions available on
the workstation and/or on the gateway.

@AC103

Internal software error: xxxxxxxx (nn). Contact your Eicon Technology

representative (see manual for instructions).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Make a backup copy of your
configuration files by copying the *.CFG files to another directory,
re-install the Eicon Technology software from the original distribution
disks, and copy the *.CFG files back to the directory which contains the
Eicon Technology software.

@AC104

Port ID error. EiconCard may not be installed; port may not exist or be
configured; required protocols may not have been loaded.

A general error occurred when the Eicon Technology software attempted to

communicate with the specified Port ID. This error condition could have been
triggered by a number of factors. Check to see that the card is properly
inserted into the computer's expansion slot. Verify that all of the required
steps have been performed to load the necessary drivers.

@AC105

EiconCard in halted state. Re-start the card with ECCARD START.

The command ECCARD STOP was previously issued. Reactivate the card by issuing
the ECCARD START command, and re-issue the previous command.

@AC108

EiconCard not configured. Start the card with ECCARD START.

The EiconCard you are attempting to use has not yet been configured. Run the
WAN Services Configuration program. Then, activate the card by issuing the command
ECCARD START on the server.
________
ECDIALER

@AD000

File not found: xxxxxxxx. The modem script file is not in the required
directory.

The specified script file could not be found. You may have entered an
incorrect file and/or pathname, or the file may not exist. Locate or create
the file, and issue the command again using the correct file and pathname.

@AD001

Script error: jump label xxxxxxxx specified in script file is undefined or

can't be found.

The script specifies a JUMP to a non-existent label. A label is a defined

point in a script that contains a series of instructions to be executed under
certain circumstances.

@AD002

Script error: unable to jump to specified label xxxxxxxx found.

The JUMP was improperly constructed. Look up ECDIALER in your InterConnect

Server for NetWare Reference Guide for more information.

@AD003

Script error: MATCH String xxxxxxxx is too long. The maximum length for a
MATCH string is nn.

MATCH strings cannot exceed the maximum length specified in the on-screen
message. Reduce the MATCH string to the maximum alllowable length.

@AD004

Script error: invalid value of 0 specified in TIMEOUT keyword.

The TIMEOUT value must be greater than 0.

@AD005

Script error: invalid value of 0 specified in WAIT keyword.

The WAIT value must be greater than 0.

@AD006

Script error: command timed out. Unable to complete command in the time
specified.

The command specified in the script could not be completed within the time
specified in the TIMEOUT value. Reset the TIMEOUT keyword to a greater value.

@AD007

Script error: SEND string too long. The SEND string must not exceed nn
characters.

SEND strings cannot exceed the maximum length specified in the on screen
message. Reduce the SEND String to the maximum allowable length.

@AD008

Script error: DIAL string too long. DIAL string must not exceed nn
characters.

DIAL strings cannot exceed the maximum length specified in the on screen
message. Reduce the DIAL string to the maximum allowable length.

@AD009

Script error: SET_DATA_BITS. Invalid value specified for number of data bits.
Allowable values are 5, 6, 7, or 8.

You may only specify the values 5,6,7, or 8 for SET_DATA_BITS. Set this
parameter to the allowable values.

@AD010

Script error: The string to be printed exceeds the maximum length of nn.

ECDIALER's scripts can only print strings up to this finite length. Reduce
the string to the maximum allowable length.

@AD011

Script error: SET_STOP_BITS. Invalid value specified for number of STOP bits.
Allowable values are 1 or 2.

You may only specify the values 1 or 2 for SET_STOP_BITS. Set this parameter
to one of the allowed values.
@AD012

Script error: SET_SPEED. Invalid value specified for AT bit rate. Allowable
values are 1200, 2400, 4800 and 9600 bits per second.

You may only specify the values 1200, 2400, 4800, or 9600 for SET_SPEED. Set
this parameter to one of the allowed values.

@AD013

Script error: SET_PARITY. Invalid value specified for the type (if any) of
parity checking to use. Allowed settings are NO_PARITY, ODD_PARITY or
EVEN_PARITY.

You may only specify the values NO_PARITY, ODD_PARITY or EVEN_PARITY for
SET_PARITY. Set this parameter to the allowed values.

@AD015

Script error: Invalid value specified for SET_PORT. Allowable range is 1 to

48.

The value specified for SET_PORT must fall within the range of 1 to 48. Set
this parameter to an allowable value.

@AD016

Script error: Syntax error or invalid command.

A line in your script file cannot be understood by the Eicon Technology

software. Check that all lines in the file are typed correctly.

@AD020

Dial error: bps rate/configuration pair invalid or mismatched. Refer to the

V.32bis section of the EiconCard configuration program chapter in the manual.

With V.32bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifying the parameters for your V.32 bis modem.

@AD021

Dial error: phone number string too long. Phone number cannot exceed nn
digits.
DIAL strings cannot exceed the maximum length specified in the on-screen
message. Reduce the phone number string to the maximum allowable length.

@AD022

Dial error: invalid bit rate specified nn. Refer to the V.32bis section of
the EiconCard configuration program chapter in the Gateway manual.

With V.32 bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifying the parameters for your V.32 bis modem.

@AD023

Dial error: invalid configuration specified xxxxxxxx Refer to the V.32bis

section of the EiconCard configuration program chapter in the manual.

With V.32 bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifying the parameters for your V.32 bis modem.

@AD024

Dial error: AT phone number string too long. Phone number cannot exceed nn
digits.

DIAL strings cannot exceed the maximum length specified in the on screen
message. Reduce the phone number string to the maximum allowable length.

@AD025

Dial error: Configuration and bit rates can only be specified for V.32
modems.

You have attempted to set a parameter allowed only on V.32 bis modems.

@AD026

Dial error: if a phone number is specified for V.32 modems the bit rate and
the configuration must also be specified.

V.32 modem will use the previous bit rate and configuration settings only
when repeating a previous phone number. Specifying a telephone number resets
these registers and necessitates that these parameters be provided again.

@AD027
Dial error: Directory number string too long. Directory number cannot exceed
nn digits.

The Directory number that you specified is too long. Reduce the directory
number to the maximum allowable length. Consult the information that came
with your ISDN subscription.

@AD028

Dial error: Subaddress string too long. Subaddress cannot exceed nn digits.

The Subaddress string that you specified is too long. Reduce the Subaddress
string to the maximum allowable length. Consult the information that came
with your ISDN subscription.

@AD029

Dial error: Transit Network Selection string too long. Transit Network
Selection cannot exceed nn digits.

The Transit Network Selection string that you specified is too long. Reduce
the Transit Network Selection string to the maximum allowable length. Consult
the information that came with your ISDN subscription.

@AD030

Parameter entry error: invalid configuration or bit rate is not allowed with
the specified configuration.

The bit rate that you specified is not compatible with the configuration
information contained in the configuration program.

@AD031

Dial error: invalid xxxxxxxx parameter specified.

One of the parameters that you specified was not recognized by ECDIALER. This
may be due to a typing error.

@AD032

Dial error: xxxxxxxx parameter required.

There is no default value for the parameter represented by xxxxxxxx. You must
include a value for this parameter.

@AD033
Dial error: xxxxxxxx parameter not compatible with the current dialer.

Some ECDIALER parameters are only appropriate for certain kinds of

connections.

@AD037

Answer error: modem is currently set to the specified state.

The request to set the modem state was ignored, since the modem was already
in answer mode.

@AD040

Store error: invalid bit rate specified for primary. Refer to the V.32bis
section of the EiconCard configuration program chapter in the manual.

With V.32 bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifiying the parameters for your V.32 bis modem.

@AD041

Store error: invalid configuration specified for primary number. Refer to the
V.32bis section of the EiconCard configuration program chapter in the manual.

With V.32 bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifying the parameters for your V.32 bis modem.

@AD042

Store error: invalid bit rate specified for alternate number. Refer to the
V.32bis section of the EiconCard configuration program chapter in the manual.

With V.32 bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifiying the parameters for your V.32bis modem.

@AD043

Store error: invalid configuration specified for alternate number. Refer to

the V.32bis section of the EiconCard configuration program chapter in the
manual.

With V.32 bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifiying the parameters for your V.32 bis modem.

@AD044

Store error: AT phone number string too long. Phone number cannot
exceed %d digits.

The AT phone number string is too long for the dialer. This usually
indicates that you are making an error in entering information.

@AD045

Store error: Configuration and bit rates can only be specified

for V.32 modems.

With V.32 bis modems, the bits per second (bps) rate dictates what
configurations are possible. In other words, you must follow a set of rules
when specifiying the parameters for your V.32 bis modem.

@AD046

Store error: if a phone number is specified for V.32 modems the bit
rate and the configuration must also be specified.

Make sure that you provide all necessary information on the command line when
you issue an ECDIALER command. When you specify a new telephone number for
dialing, you must also provide the bit rate and configuration information.

@AD047

Store error: Directory number string too long. Directory number

cannot exceed nn digits.

The Directory number that you specified is too long. Reduce the directory
number to the maximum allowable length. Consult the information that came
with your ISDN subscription.

@AD048

Store error: Subaddress string too long. Subaddress cannot exceed

nn digits.

The Subaddress string that you specified is too long. Reduce the Subaddress
string to the maximum allowable length. Consult the information that came
with your ISDN subscription.
@AD049

Store error: Transit Network Selection string too long. Transit

Network Selection cannot exceed %d digits.

The Transit Network Selection string that you specified is too long. Reduce
the Transit Network Selection string to the maximum allowable length. Consult
the information that came with your ISDN subscription.

@AD051

Store error: invalid xxxxxxxx parameter specified.

Type xxxxxxxx /? for help.

The parameter represented by xxxxxxxx was not understood by ECDIALER. Please

enter the command followed by /? for online help.

@AD052

Store error: xxxxxxxx parameter required.

Type xxxxxxxx /? for help.

The parameter represented by xxxxxxxx was not understood by ECDIALER. Please

enter the command followed by /? for online help.

@AD053

Store error: xxxxxxxx parameter not compatible with the current dialer.

Some ECDIALER parameters are only appropriate for certain kinds of

connections.

@AD060

Card initialization error: EiconCard port is not initialized. Set AUTO

INITIALIZE to YES in the configuration program, run "ECCARD START /PORT".

The EiconCard must be initialized in order to perform operations. If you

would like initialization to occur automatically each time you enter the
software, add this sequence to the ECICS load sequence. To initialize the
port manually, run ECCARD START /Port.

AD063

Error: xxxxxxxx parameter not valid for this dialer.

Some ECDIALER parameters are only appropriate for certain kinds of

connections.
AD064

Error: xxxxxxxx command not valid for this dialer.

Some ECDIALER parameters are only appropriate for certain kinds of

connections.

@AD100

Internal software error: dialer API (nn). Contact your Eicon Technology
representative for assistance.

This indicates an internal error in the Eicon Technology software. Contact

your Eicon Technology representative for assistance, quoting the message
number and the numeric value returned as (nn).

@AD114

Port ID error. Port may not exist or may not be configured.

An invalid port number has been specified. Verify the port ID in the ICS
Configuration utility.

@AD115

No status to display for direct line.

Direct lines (leased lines) do not provide status information. Only dial-up
lines provide this kind of information.

@AD200

Parameter entry error: bad command syntax.

The Eicon Technology software was unable to understand the command that you
entered. Verify that the command and parameters that you have supplied on the
command line are typed correctly.

@AD201

Resource conflict. Not owner or command still under processing.

This may indicate a a multi-tasking error. You may have already started the
process in another window, or have another process which is using a common
resource. Terminate all processes currently using the common resource before
starting a new process. You may also receive this error message if you make a
dial request while a previous dial request is still in progress.
@AD202

Dial error. Destination did not answer.

The computer that you tried to dial did not answer. Contact personnel at the
remote site and ask them to verify their software and hardware status.

@AD204

Required parameter missing. No telephone number registered.

A telephone number must be provided for the dial operation. Use the /N
parameter with your command.

@AD206

Already in answer mode.

The modem was already in answer mode, so the command was ignored.

@AD207

Invalid parameter value provided: invalid asynchronous speed.

You must set your bits per second rate to one of the industry-standard
settings. You may only specify the values 1200, 2400, 4800, or 9600 for
SET_SPEED.

@AD208

Invalid parameter value provided: invalid parity.

You may only specify the values NO_PARITY, ODD_PARITY or EVEN_PARITY for
SET_PARITY.

@AD209

Invalid parameter value provided: invalid number of bits per transmitted

byte.

You may only specify the values 5,6,7, or 8 for SET_DATA_BITS.

@AD210
Invalid initialization parameter.

One or more of the parameters that you specified on the command line could
not be understood by the Eicon Technology software. Check that the command
line does not contain any typing errors.

@AD212

Modem error. Disconnection received while connecting.

This error may be an isolated incident, the result of line noise, or

incorrectly configured software on the remote site. Try the operation again
before attempting detailed troubleshooting.

@AD213

Modem error. Close received while connecting.

This error may be an isolated incident, the result of line noise, or

incorrectly configured software on the remote site. Try the operation again
before attempting detailed troubleshooting.

@AD214

Modem error. Hangup received while connecting.

This error may be an isolated incident, the result of line noise, or

incorrectly configured software on the remote site. Try the operation again
before attempting detailed troubleshooting.

@AD215

Modem error. Ring indication received while connecting. This error may be an
isolated incident, the result of line noise, or incorrectly configured
software on the remote site.

Try the operation again before attempting detailed troubleshooting. Verify

that you have correctly identified the modem type in the ICS Configuration
utility.

@AD216

Call failure indication (CFI) received.

The host is unable or unwilling to receive the call request that you placed.
Verify that this is not due to a local hardware configuration problem: check
modem cables, etc. If the cause is not local, contact personnel at the host
site. Their system may be down or busy.
@AD217

Delayed call indication (DLC) received.

This indicates that the host system has chosen to block calls from your site.
This may be due to several considerations: password violations, noisy line,
etc. Generally, this is not a permanent ban, but is imposed for fixed periods
of time. Contact personnel at the host site for more information regarding
your status.

@AD218

Invalid indication (INV) received.

This indicates that the host has received a syntax error. Ensure that the
parameters you have specified are correct for this particular host. Verify
your modem hardware. If you are unable to resolve the problem, contact your
Eicon Technology representative for assistance.

@AD223

Dial error: destination busy.

The destination telephone line is busy. Keep trying until the line is free.
If the condition persists, contact personnel at the remote site and ask them
to verify their software and hardware status.

@AD225

Dial error: no carrier.

The computers failed to establish a link, or carrier wave. Verify software

configuration, ask personnel at remote site to do same.

@AD228

Dial error. No dial tone.

There is no dial tone coming from the telephone line. Check the cable that
runs from the modem to the telephone jack.

@AD229

Close request received.

The remote computer has requested that the connection be closed. This message
advises you that the remote computer has closed the session.
@AD230

Disconnect request received.

The remote computer has requested that the link be disconnected. This message
advises you that the remote computer has disconnected the session.

@AD234

Parameter entry error. Phone number contains invalid digit(s).

The telephone number that you specified contains invalid characters. Check to
see that you typed it correctly.

@AD235

Parameter entry error. Invalid phone number structure.

The telephone number that you specified contains invalid characters. Check to
see that you typed it correctly.

@AD236

Command not allowed or already hungup.

The command that you entered is not allowed within the context of current
operations.

@AD237

Invalid parameter value provided: invalid bit rate.

You may only specify the values 5,6,7, or 8 for SET_DATA_BITS.

@AD238

Invalid parameter value provided: invalid configuration mode.

The EiconCard is incorrectly configured for the requested operation.

@AD239

Required parameter missing. No telephone number registered.

A telephone number must be provided for dial operations.

@AD250

Parameter entry error. Invalid Bearer Capability.

Bearer Capability is the speed at which your telephone company's lines can
carry information. For circuit-switched calls, this parameter can be set to
56K or 64K. For packet-switched calls, this parameter must be set to 64K. If
this parameter is not specified, the value defaults to 64. This is
appropriate for most major cities in North America. Refer to the manual for
more information.

@AD251

Parameter entry error. Invalid ISDN Number.

The ISDN Number that you specified is in the wrong format. Consult the
information that came with your ISDN subscription. Remember to use a valid
combination of Number Type and Number Plan.

@AD252

Parameter entry error. Invalid ISDN Subaddress.

The ISDN Subaddress that you specified is in the wrong format or is not
required. Consult the information that came with your ISDN subscription.
Remember to use a valid combination of Number Type and Number Plan.

@AD253

Parameter entry error. Invalid Transit Network Selection.

The Transit Network Selection information that you specified is in the wrong
format. This parameter specifies which long distance carrier you will be
using for your connection. Consult the information that came with your ISDN
subscription. Remember to use a valid combination of Number Type and Number
Plan.

@AD254

Parameter entry error. Invalid or incompatible ISDN Port.

The ISDN Port that you specified either does not exist, or has not been
configured correctly. The EiconCard ISDN can be configured to use one or two
B-channels to carry information. Some countries also permit you to carry X.25
data on the D-channel. Use the configuration program to verify your ISDN
configuration information.
@AD255

Parameter entry error. Invalid structure.

The information that you entered on the command line was not understood by
ECDIALER. This may be due to a typing error, or you may be specifying
parameters in the wrong sequence.

@AD256

Dialer closed or not fully activated.

Verify that the EiconCard has been configured using the configuration program.

@AD257

Invalid or incompatible Dialer state.

Verify that the EiconCard has been configured using the configuration
program. The card may be configured incorrectly.

@AD258

Call Control cannot complete the call.

For ISDN connections only: the call could not be completed through the ISDN
network. Consult the ISDN cause code displayed by ECDIALER status and refer
to the manual for its explanation.

@AD259

Internal Hangup/Disconnect requested.

This may indicate that your software was not configured correctly, or that
some other error has occurred. Another error message may provide a more
detailed diagnosis of the problem.

@AD260

Cannot hangup on X31A.

This kind of connection cannot be hung up.

@AD261
Required parameter missing. No ISDN number registered.

The ISDN number was not specified on the command line, and has not been
registered in the configuration file. Use the configuration program to
register a default number.

@AD280

Dial failed, hangup received or port is not activated.

This refers to a general error in the communications between the Eicon

Technology software and the modem. Verify that the modem is correctly
installed and configured. Check all cables. If these steps fail to resolve
the problem, contact your Eicon Technology representative for more
information.

@AD281

Hangup under processing.

The server still station (gateway) is still processing a previous hangup

request. The command that you just entered cannot be processed until the
hangup is completed.

@AD301

Internal software error: (NCB return code xxxxxxxx). Contact your Eicon
Technology representative (see manual for instructions).

This indicates an internal error in the Eicon Technology software. Contact

your Eicon Technology representative for assistance, quoting the message
number and the NCB return code.

@AD302

Resource conflict: dialer already in use.

The dialer is already in use by another workstation. Find out who is using
the dialer in your work group and make arrangements to use the dialer when
they are finished.

@AD303

Required driver missing. The dialbios has not been opened.

You must have ECLAN client software running in order to use ECDIALER. Refer
to the manual for more information.
@AD308

Onhook or Offhook command invalid.

Either you tried to hangup when there was no connection, or you tried to
start a connection when another one was already active.

______
Common

@EC200

Internal software error: invalid buffer length (ECBIOS: ENETBUFLEN). Contact

your Eicon Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Re-install the software from
the original distribution diskettes.

If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.

@EC201

Network error: invalid command. Verify your network software configuration

(ECBIOS: ENETICMD).

This may indicate a LAN configuration error for the station placing the
request, an error in the Eicon Technology configuration program, or a
conflict between the Eicon Technology software and other applications running
on the PC. Contact your LAN administrator for help. If that person is unable
to resolve the problem, contact your Eicon Technology representative for
assistance.

@EC202

Internal software error: command timeout (ECBIOS: ENETCMDTO) Contact your

Eicon Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Re-install the software from
the original distribution diskettes.

If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.
@EC203

Network error: incomplete message. Verify your network software configuration

(ECBIOS: ENETIMSG).

This may indicate a LAN configuration error for the station placing the
request, an error in the Eicon Technology configuration program, or a
conflict between the Eicon Technology software and other applications running
on the PC. Contact your LAN administrator for help.

@EC204

Parameter entry error: the connection or linkstation number that you

specified is invalid or not in use (ECBIOS: ENETILSN).

The connection or linkstation number that you provided was invalid. Check
that the number was correctly typed.

@EC205

Network error: no circuit available. Wait a few minutes and try again.
(ECBIOS: ENETNOCKT).

All of the virtual circuits (communication paths through the gateway) are
currently in use. A link cannot be established until one of these circuits
becomes available. If the situation persists, contact your gateway
administrator.

@EC206

Call cleared. Your session has been closed. Attempt to re-establish the
connection (ECBIOS: ENETCALLCLR).

The communications link between the PC and the host has been terminated.
Repeat the steps necessary to re-establish the gateway connection.

@EC207

Network error: Command cancelled (ECBIOS: ENETCMDCANC).

This may indicate a LAN configuration error for the station placing the
request, an error in the Eicon Technology configuration, or a conflict
between the Eicon Technology software and other applications running on the
PC. Contact your LAN administrator for help.

@EC208

Node name already exists (ECBIOS: ENETPUEXIST).

An attempt was made to add a Node name to a table that already contains that
entry. Choose another node name, or remove the node name from the table
before adding it.

@EC209

Nodes/PUs configured have all been used or number of PUs free is not enough
to start the specified node (ECBIOS: ENETPUFULL).

The table that holds nodes (Physical Unit names) has a finite amount of
space. Remove an existing node name before attempting to insert another one.

@EC210

Session table full. Close a session and try again (ECBIOS: ENETNOSESS).

There is a finite number of sessions available. Before trying to invoke a new

session, an existing session must be closed.

@EC211

Internal software error: unable to establish a local session (ECBIOS:

ENETUCALL) Contact your Eicon Technology representative (see manual for
instructions).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Make a backup of the Eicon
configuration files and re-install the software from the original
distribution diskettes.

If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.

@EC212

Card initialization error. You must first download the protocol to the
EiconCard port with ECCARD START (ECBIOS: ENETNAMENF).

A critical driver has not yet been loaded into memory. Review the procedure
listed in the reference manual for the action being attempted, add the
required driver, and try again.

@EC213

Network error: circuit in use. Wait a few minutes and try again (ECBIOS:
ENETINUSE).
All of the virtual circuits (communication paths through the gateway) are
currently in use. A link cannot be established until one of these circuits
becomes available. If the situation persists, contact your gateway
administrator.

@EC214

An invalid port number has been specified. Check the port configuration and
try again.

Verify the software configuration and ensure that the correct port has been
specified configure for your hardware installation.

@EC215

Network event: session reset (ECBIOS: ENETSRESET).

The X.25 network has reset the session between the PC and the host. Repeat
the steps necessary to re-establish the session.

@EC216

Network condition: trace not started (ECBIOS: ENETNOTRACE).

The requested trace could not be executed by the X.25 network. If repeated
attempts fail, contact your Eicon Technology representative.

@EC217

EiconCard memory shortage. Use the configuration program to reduce the number
of reserved resources and restart the card. (ECBIOS: ENETNOMEM).

The EiconCard is a sophisticated communications coprocessor, with its own CPU

and RAM (Random Access Memory). The amount of available RAM on an EiconCard
depends on its model. An error occurred because you tried to load too many
images (EiconCard programs) and/or you tried to reserve too many resources
(buffers, etc.). Use the Eicon configuration program to reduce the amount of
resources that you request so that it fits within the EiconCard's memory
capacity.

@EC218

Internal software error: too many outstanding commands (ECBIOS: ENET2MANYC).

Contact your Eicon Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Re-install the software from
the original distribution diskettes.

If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.

@EC219

Parameter entry error. Specified port number is invalid (ECBIOS:

ENETBADPORT).

The port number specified on the command line is invalid. Re-issue the
command with the correct port number.

@EC220

Required parameter missing. A phone number must be specified for dialing.

(ECBIOS: ENETNONUMBER).

A telephone number must be provided on the command line. Enter the telephone
number that you wish to dial using the /N parameter.

@EC221

Modem error: no dial tone. Check your modem hardware (ECBIOS: ENETNOTONE).

The modem is not functioning properly. This might be because the modem is
turned off, because its cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working modem is connected to
the EiconCard. If you are using a null-modem cable it could be defective:
check the cable's pin outs.

@EC222

Modem error: modem test failed. Check your modem hardware (ECBIOS:
ENETMDFAILED).

The modem is not functioning properly. This might be because the modem is
turned off, because its cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working modem is connected to
the EiconCard. If you are using a null-modem cable it could be defective:
check the cable's pin outs.

@EC223

Modem error: modem not ready. Check your modem hardware (ECBIOS: ENETMDNR).

The modem is not functioning properly. This might be because the modem is
turned off, because its cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working modem is connected to
the EiconCard. If you are using a null-modem cable it could be defective:
check the cable's pin outs.

@EC224

Modem error: modem not ready (no DSR). Check your modem hardware (ECBIOS:
ENETMDDSR).

The modem is not functioning properly. This might be because the modem is
turned off, because its cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working modem is connected to
the EiconCard. If you are using a null-modem cable it could be defective:
check the cable's pin outs.

If you receive this message while using a DPNA card, ensure that the
interface is set to X.21 (RS-232).

@EC225

Modem error: modem not ready (no CTS). Check your modem hardware (ECBIOS:
ENETMDCTS).

The modem is not functioning properly. This might be because the modem is
turned off, because its cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working modem is connected to
the EiconCard. If you are using a null-modem cable it could be defective:
check the cable's pin outs.

@EC226

Modem error: modem not ready (no clock) (ECBIOS: ENETMDCLK).

The modem is not functioning properly. This might be because the modem is
turned off, because its cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working modem is connected to
the EiconCard. If you are using a null-modem cable it could be defective:
check the cable's pin outs.

If you receive this message while using a DPNA card, ensure that the
interface is set to X.21 (RS-232).

@EC227

Remote line busy. Wait a few minutes and try again (ECBIOS: ENETBUSY).

The telephone number that you are dialing is returning a busy signal. If
repeated attempts fail, contact personnel at that site and ask them to
investigate the problem.
@EC228

Remote not answering. Contact personnel at remote site (ECBIOS:

ENETNOANSWER).

The modem at the remote end is not answering the telephone line. Contact
personnel at that site and ask them to investigate the problem.

@EC229

Phone line error: no line available. Check the cable which runs from the
modem to the telephone jack (ECBIOS: ENETNOLINE).

The modem is unable to obtain a dial tone. Check to see that the cable is
properly connected to the modem and to the telephone jack.

@EC230

Modem already in use. Check to see if someone in your workgroup is already

using the modem (ECBIOS: ENETMDUSED).

Another station may be using the modem. In such a case, you may simply have
to wait your turn.

@EC231

Parameter entry error: bad phone number syntax. Phone numbers should follow
format #-###-###-#### (ECBIOS: ENETMDSYNTAX).

The phone number provided was in an invalid format or contained invalid

characters. Retype the phone number using the format above.

@EC233

Internal software error: link level not ready. Verify your network
configuration (ECBIOS: ENETLINKNR). If attempts fail, contact your Eicon
Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Make a backup of your
initialization files, and re-install the software from the original
distribution diskettes.

If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.
@EC234

Internal software error: packet level not ready. Verify your network
configuration (ECBIOS: ENETPKTLNR). If attempts fail, contact your Eicon
Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Make a backup of your
initialization files, and re-install the software from the original
distribution diskettes.

If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.

@EC235

Restart indication received (ECBIOS: ENETRESTART).

The X.25 network has re-started its link with the gateway. Repeat the steps
necessary to re-establish the gateway connection.

@EC245

General card failure. Attempt a system restart. (ECBIOS: ENETSNARK).

The EiconCard has experienced a critical failure. Verify that the EiconCard
is correctly installed: refer to the EiconCard installation guide for more
information. Shutdown and restart the computer containing the EiconCard.
Reload the gateway software. If repeated attempts fail, contact your Eicon
Technology representative.

@EC246

EiconCard hardware error. (ECBIOS: ENETCARD).

The EiconCard has experienced a critical failure. Verify that the EiconCard
is correctly installed: refer to the EiconCard installation guide for
information. Shutdown and restart the computer containing the EiconCard.
Reload the gateway software. If repeated attempts fail, contact your Eicon
Technology representative.

@EC247

EiconCard hardware error. Verify that the EiconCard is loaded (ECBIOS:

ENETLOAD).

The EiconCard has experienced a critical failure. Verify that the EiconCard
is correctly installed: refer to the EiconCard installation guide for
information. Shutdown and restart the computer containing the EiconCard.
Reload the gateway software. If repeated attempts fail, contact your Eicon
Technology representative.

@EC248

EiconCard in halted state. Re-start the card with ECCARD START (ECBIOS:
ENETHALT).

The card was previously halted with ECCARD STOP. Issue the command ECCARD
START to resume operations.

@EC249

Required driver or redirector missing. Load the driver with ECCARD or the
redirector with ECLAN and try again (ECBIOS: ENETNODRV).

The ECBIOS driver has not been loaded. Ensure that your CONFIG.SYS file has
the line DEVICE=ECBIOS.SYS to load the driver into memory. Then run ECBIOS
START and resume.

@EC250

Command not completed (ECBIOS: ENETPEND).

This refers to a critical failure in the operation of the Eicon Technology

software. The PC's environment may be corrupted. Try rebooting the machine
and re-starting the Eicon Technology software. If the error persists, it may
be an indication of a corrupted program file. Make a backup of your
initialization files, and re-install the software from the original
distribution diskettes.

If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.

@EC251

Internal software error: (NCB return code xxxxxxxx). Contact your Eicon
Technology representative (see manual for instructions).

This refers to a critical error in the Eicon Technology software. Contact

your Eicon Technology representative for assistance.

@EC252

Port ID error. EiconCard may not be installed; port may not exist or be
configured; required protocols may not have been loaded (ENETNOTCONF).

The EiconCard's port has not yet been configured with a protocol. Specify and
configure a protocol using the Eicon configuration program, and try again.
@EC500

Parameter entry error: too many arguments. Remaining arguments will be

ignored. Type xxxxxxxx /? for help.

More parameters were provided on the command line than the Eicon Technology
software was expecting. The excess parameters were not processed. Obtain the
correct syntax by retyping the command with the help parameter /?.

@EC501

Syntax error: invalid option. Type xxxxxxxx /? for help.

An unknown parameter was specified on the command line. Obtain the correct
syntax by retyping the command with the help parameter /?.

@EC502

Required parameter missing. xxxxxxxx must be specified. Type xxxxxxxx /? for

help.

The parameter xxxxxxxx was not provided on the command line and is required
for the desired operation. Re-issue the command using the required parameter.

@EC503

Required parameter missing. You must specify a value for option xxxxxxxx.
Type xxxxxxxx /? for help.

The parameter xxxxxxxx was not provided on the command line and is required
for the desired operation. Re-issue the command using the required parameter.

@EC504

Invalid parameters in command line. Type xxxxxxxx /? for help.

The Eicon Technology software is not able to understand the command line that
you have typed.This usually indicates a typing error or an inappropriate
value. For example, you might have supplied a string (alphabetic) value for a
field that required a numeric value (such as a port number).

@EC505

Ambiguous parameter: xxxxxxxx (xxxxxxxx?). Type xxxxxxxx /? for help.

The Eicon Technology software is not able to understand the command line that
you have typed. This usually indicates a typing error or an inappropriate
value. For example, you might have supplied a string (alphabetic) value for a
field that required a numeric value (such as a port number).

@EC506

Parameter entry error: value is out of range (xx). Type xxxxxxxx/? for help.

The command indicated by xxxxxxxx was accompanied with a parameter that falls
outside the accepted range. Each command and its parameters have different
ranges for their accepted values. Entering a command followed by /? will
provide you with a list of commands and the values acceptable for each
parameter. This help feature goes down several levels: for example, ECLAN USE
/? would provide information on server station (gateway) selection.

@EC900

A DCB (Dos Control Block) was not found.

This probably indicates an error in your PC's DOS configuration. Verify that
you do not have a misbehaving TSR (resident program) that is conflicting with
the Eicon Technology software.

@EC902

The application was unable to perform the specified operation or was unable
to establish a local session. See the diagnostic below.

This message is usually accompanied by more specific error messages. Refer to

those messages for detailed information on the error condition.

______
ECTEST

@FA001

File not found: xxxxxxxx. EiconCard configuration file could not be found.

The specified EiconCard configuration file (*.CFG) could not be found. You
may have entered an incorrect file and/or pathname, or the *.CFG file may not
exist. Locate or create the file, and issue the command again using the
correct file and pathname.

@FA002

File not found: xxxxxxxx. EiconCard Loadable Module file could not be found.

The specified loadable module file (*.ELM) could not be found. Make sure that
it is in the current directory or on the path. If you cannot find the file,
re-install the Eicon Technology software.

@FA003

EiconCard nn not supported by this version of ECTEST. No tests performed.

ECCARD CONFIG allows the selection of a card type that is not currently
supported by the ECTEST program. EiconCards of the specified type can not be
tested.

@FA004

Configuration error: EiconCard #nn could not be found in the configuration

file.

EiconCard #nn was not configured using ICS Configuration or the card number
specified is incorrect.

@FA005

Memory shortage: Unload programs, or reduce the number of allocated sessions.

The file server PC requires a certain amount of free memory to run ECTEST.
Unload unnecessary programs from memory, and run ECTEST again.

@FA006

Version mismatch: Invalid version of the EiconCard Configuration file

xxxxxxxx.

The file ECTEST is trying to read is an incompatible version. This usually

appears when ECTEST tries to read an old EiconCard configuration file
(*.CFG). This problem is most likely to occur after you have upgraded your
software to a new version, and did not regenerate the EiconCard configuration
files using the new version of the EiconCard configuration program (ICS
Configuration).

@FA008

Card identification error. The type of the EiconCard is xxxxxxxx. The card
name to select in the ECCARD CONFIG program is xxxxxxxx instead of xxxxxxxx.

The Card Type specified in EiconCard configuration program is not of the same
type as the EiconCard installed in the file server PC. Run the ICS
Configuration program and set the correct Card Type.
@FA009

Invalid I/O port address, invalid memory segment address, Card nn is not an
EiconCard, or hardware failure.

This occurs when the I/O port address and memory segment address validity
tests pass, but the EiconCard is still not responding. It is possible that
there is a configuration conflict (I/O port address and/or memory segment
address) either between two EiconCards or between an EiconCard and another
adapter that could not be detected by the configuration validity tests. If
there are no configuration conflicts, then there may be a hardware failure
with the board. Try alternate I/O port addresses and memory segm ent
addresses. For assistance, refer to the installation guide that came with
your EiconCard.

@FA010

Selected Interrupt Request Level is not supported by the xxxxxxxx card.

Select another one.

You have chosen an interrupt request level (IRQ) that is not supported by
this version of EiconCard. Run EiconCard configuration program and select an
IRQ smaller than 8. Refer to your EiconCard documentation for more
information on valid IRQ settings.

@FA011

EiconCard is in an XT slot (8 bits) in which the extended interrupt request

levels (8 to 15) are not supported. Either place the EiconCard in an AT slot
(16 bits) or select an interrupt request level smaller than 8.

You have installed the EiconCard in an inappropriate slot. Move the EiconCard
into one of the long 16 bit slots in the gateway PC, or run EiconCard
configuration program and select an IRQ number lower than 8 for the
EiconCard.

@FA012

No interrupts received from the EiconCard. Invalid Interrupt Request Level or

hardware failure.

You may have set the EiconCard to an incorrect Interrupt Request Level, or
there may be a hardware problem with the EiconCard. Run the EiconCard
configuration program and change the IRQ settings. If this does not work,
then there may be a problem with your EiconCard.

@FA013

EiconCard xxxxxxxx nnnnK is not supported by this version of ECTEST. No test

performed.
The specified EiconCard is an old version of the board and cannot be tested
by this version of ECTEST.

@FA014

Invalid interface type selection. The machine type to select in the Eicon
configuration program is /MC instead of /PC.

You have a Micro-Channel EiconCard installed in your machine but you are
attempting to use the ISA bus structure. Run the ICS Configuration program,
and on the hardware configuration screen select Micro Channel Architecture
instead of Industry Standard Architecture as the bus type.

@FA015

Invalid interface type selection. The machine type to select in the Eicon
configuration program is /PC instead of /MC.

You have a PC EiconCard installed in your machine but you are attempting to
use the Micro-Channel bus structure. Run the ICS Configuration program, and
on the hardware configuration screen select Industry Standard Architecture
instead of Micro Channel Architecture as the bus type.

@FA016

Parameter entry error. Card number must be within the 1 to nn range.

The specified card number is invalid. Valid card numbers range from 1 to nn.

@FA017

The interface type according to the EiconCard device driver differs from the
one selected in the EiconCard configuration file. If interface type selected
in file is incorrect, select appropriate interface type. Otherwise, re-boot
system.

This indicates that an Eicon Technolgy OS/2 program was run using a
configuration file with an interface type different from the interface type
selected in the configuration file to be used by ECTEST. If the interface
type selected for ECTEST is incorrect, run ICS Configuration to select the
appropriate type. If the type is correct, the OS/2 gateway must be rebooted.
Bear in mind that because of the nature of the OS/2 environment, the Eicon
Technology software is unable to automatically detect which bus typ e that
your computer has.

@FA018

Resource conflict: required EiconCard device driver resource currently

unavailable. Attempt running ECTEST until the resource is free.
On OS/2 computers, this message appears when another program is using one of
the EiconCard device driver's resources. Wait until the necessary resource is
free, and run ECTEST again.

@FA019

Memory segment xxxxxxxx not supported by this version of xxxxxxxx. Select a

memory segment address equal to or smaller than xxxxxxxx.

The EiconCard cannot be tested using the selected memory segment address in
the current version of ECTEST. Run the EiconCard configuration program to
select a memory segment value in the specified range.

@FA020

Version mismatch: Invalid version of the Eicon Loadable Module file xxxxxxxx.

This is an invalid version of a *.ELM file. The file may have been corrupted,
or belong to a version which is not compatible with this version of ECTEST.
Use the ECVER command to determine the version of the Eicon software you are
running. Contact your Eicon Technology representative to obtain the most
recent software.

@FA021

Hardware failure: I/O Interface test failure.

There may be a hardware failure on the EiconCard.

@FA022

Extended memory not supported by EiconCard. Select a memory segment address

smaller than 0x10000.

This message does not require any further explanation.

@FA023

EiconCard is in an XT slot (8 bits) in which extended memory is not

accessible. Either place the EiconCard in an AT slot (16 bits) or select a
memory segment address smaller than 0x10000.

This message does not require any further explanation.

@FA024
No extended memory present at the selected memory segment address. Select a
memory segment address equal to or smaller than xxxxxx.

This message does not require any further explanation.

@FA025

Invalid I/O port address, invalid EiconCard type, card is not an EiconCard,
invalid interface type (OS/2 only) or hardware failure.

* One or more of the following problems may have triggered this error:

* The I/O port address selected in the EiconCard configuration file may be
invalid (conflicting with another adapter), and/or the I/O port address
jumpers or switches may not correspond to the value selected in the
configuration file.

* The EiconCard type may be wrong.

* The card using the specified I/O port address may not be an EiconCard.

* (under OS/2 only) The interface type may be incorrect.

* There may be a hardware failure on the EiconCard.

* Verify jumpers or switch settings. Verify accuracy of the card type. If

those items are correct, try alternate I/O port address in case of a possible
conflict with another device. If no valid I/O port address can be found,
there may be no more I/O port addresses available on your host system or
there may be a hardware failure on the EiconCard.

* It is impossible under OS/2 to determine the bus type of the host

machine. The configured bus type is assumed correct. If the bus type is
incorrect, boot the system and run the EiconCard Configuration program to
select the correct bus type.

@FA026

Invalid memory segment address and/or invalid I/O port address, or hardware
failure.

The memory segment address selected in the EiconCard configuration file may
be invalid, and/or the memory segment address jumper settings on the
EiconCard (if any) may not correspond to the value selected in the EiconCard
configuration file. If no valid memory segment address can be found, it is
possible that it is the I/O port address that is invalid (invalid I/O ports
cannot always be detected).

Try alternate values for the I/O port. Make sure to modify jumper/switch
settings according to the new I/O port values. If this does not work, there
may be no more available resources (I/O port address and/or memory segment
address) on your host system, or there may be a hardware failure on the
EiconCard.
@FA027

Micro-Channel EiconCard not detected. Invalid slot number, invalid interface

type (OS/2 only) or hardware failure.

The adapter in slot n, if any, was not recognized as being an EiconCard.

Either the configured slot number is incorrect, or there is a hardware
failure on the EiconCard. Check the EiconCard slot position and update ICS
Configuration accordingly.

Under OS/2, this error may also occur if the selected interface type is /MC
but the host machine is a /PC machine.

If the slot number is correct and the interface type is correct (relevant
uder OS/2 only) but the problem still persists, contact your Eicon Technology
representative for assistance.

@FA028

Configuration error: EiconCard device driver not installed.

ECBIOS has not been installed. The EiconCard device driver ECBIOS.SYS must be
specified in your CONFIG.SYS file before you can test the EiconCard. This
message only applies to OS/2 systems.

@FA029

Security conflict: Insufficient user privilege. Contact your system

administrator.

You do not have sufficient privileges to run in this control mode. Contact
your system administrator for the proper access rights.

@FA030

Internal software error: There was an error sending a system call to the
EiconCard driver. Contact your Eicon Technology representative (see manual
for instructions).

This may indicate an error in the Eicon Technology software. Other error
messages may provide a more detailed diagnosis of the problem. If you unable
to resolve this problem yourself, contact your Eicon Techology representative
for assistance.

@FA031

Configuration error: ECBIOS Driver or redirector not installed.

The EiconCard driver has not been loaded. Run the ECBIOS command before
issuing any further commands on the EiconCard.
@FA032

Network error: Cannot reach server.

The command failed due to an error on the network. Ensure that the network is
functioning properly before reissuing the command.

@FA033

Internal software error: EiconCard driver internal error (xxxxxxxx: nn).

Contact your Eicon Technology representative (see manual for instructions).

This may indicate an error in the Eicon Technology software. Other error
messages may provide a more detailed diagnosis of the problem. If you unable
to resolve this problem yourself, contact your Eicon Techology representative
for assistance.

@FA034

Resource conflict: Interrupt request level nn already used by another

adapter. Select another Interrupt Request Level.

You have chosen an interrupt request level (IRQ) that is already in use by
another adapter. Select a different IRQ for the adapter and leave your
EiconCard IRQ setting to nn, or vice versa.

@FA035

Hardware failure: EiconCard not responding.

Refer to FA025 for possible solutions. If problems still persist, contact

your Eicon Technology representative for assistance.

@FA036

Hardware failure: 4K Memory Window test failed.

Refer to FA025 for possible solutions. If problems still persist contact your
Eicon Technology representative for assistance.

@FA037

Hardware failure.

Refer to FA025 for possible solutions. If problems still persist contact your
Eicon Technology representative for assistance.

@FA038

Invalid interface type or hardware failure.

Verify the accuracy of the interface type selected in the Eicon Configuration
program. If incorrect, rectify the interface type and reboot the system.
Otherwise, there is a hardware failure on the EiconCard.

@FA039

Invalid interface type selection. The Parallel Port Interface is not

supported by this version of ECTEST. Select another one.

The parallel port interface type is not supported by this version of ECTEST.
Select another interface using the Eicon configuration program.

@FA040

xxxxxxxx is not a valid value for the /Loopback option. The valid values are
V24V35 and X21.

The value you specified cannot be tested. You can only perform V24 and X21
driver tests.

@FA041

Improper hardware setup for driver test(s) and/or hardware failure.

There is a conflict between the configured values for the EiconCard and the
hardware itself. Verify that the EiconCard has been configured correctly and
that the proper options are being issued with the ECTEST command.

@FA042

xxxx EiconCard category not supported by this version of ECTEST.

The Eicon configuration program used to generate the system configuration

file allows the selection of the xxxx EiconCard category but the version of
ECTEST used does not recognize the specified category.

Contact your Eicon Technology representative to obtain the latest version of

the ECTEST program.

@FA043
EiconCard not present on Parallel Port #nn, power supply missing, invalid
adapter type, or hardware failure.

The EiconCard you configured for the parallel port specified does not exist
or an invalid adapter type was specified. Check your hardware parallel port
for the correct port where your EiconCard was installed.

You may also have a problem with your power supply.

If you have checked all possible error sources, and you are still
experiencing problems, contact your Eicon Technology representative for
assistance.

@FA044

Invalid interface type selection. The EISA interface is not supported by this
version of xxxxxxxx. Select another one.

You have selected an invalid interface for your bus architecture. Verify your
setting before retrying this command.

@FA045

Parallel Port nn not enabled or does not exist.

The parallel port you specified for testing has not been configured.

@FA047

More than one adapter card configured to use the 0x0x I/O port address. Run
the Eicon configuration program to configure the EiconCard port address to a
value that is uniquely used.

The I/O port you configured is in conflict with another adapter card in your
system. Verify the positions of all adapter cards installed in your machine
and then set the appropriate I/O address for the EiconCard.

@FA048

More than one adapter card configured to use the 0x1x Memory Segment address.
Run the Eicon configuration program to configure the EiconCard memory segment
address to a value that is uniquely used.

The memory segment address you configured is in conflict with another adapter
card in your system. Verify the positions of all adapter cards installed in
your machine and then set the appropriate address for the EiconCard.

@FA049
More than one adapter card configured to use the nn Interrupt Request Level.
Run the Eicon configuration program to configure the EiconCard Interrupt
Request Level to a value that is uniquely used.

The IRQ you configured is in conflict with another adapter card in your
system. Verify the positions of all adapter cards installed in your machine
and then set the appropriate IRQ for the EiconCard.

@FA050

Micro-Channel EiconCard nn could not be detected. No installed EiconCard in

the HOST machine configured to use the hardware configuration parameters
selected by the Eicon configuration program for card #nn.

You do not have an EiconCard installed in the machine that you are running
the ECTEST command on. Determine where the EiconCard is installed and verify
the interface type (Micro-channel or PC) against your configuration settings.

@FA062

Option module identification error or hardware failure. The type of the

detected module is xxxxxxxx.

The option module selected in the Eicon configuration program does not
correspond to the type of Option module detected on the EiconCard. Run the
configuration program and select Option Module M1 instead of module M2.

If the Configured option module type does not correspond to the Option module
present on the board that this error is reported, it may be because of a
hardware failure on the EiconCard causing the Option module type to be
errorneously identified. Contact your Eicon Technology representative for
assistance.

@FA063

Modem module missing from EiconCard, modem module not recognized or hardware
failure.

This message applies to the EC IMC/PC and EC IMC/MC boards only. These boards
cannot operate without a modem module. The modem module configured using the
Eicon configuration program could not be detected. There may be no module on
the EiconCard. Verify that a modem module is present on the EiconCard, that
it is correctly positioned and that it's type corresponds to the Dialer
selection field of the Eicon configuration program.

If the modem module is correctly placed on the EiconCard but this error is
still reported, contact your Eicon Technology representative. You may have a
version of the program that does not recognize the module that is present on
the EiconCard or there may be a hardware failure keeping the program from
detecting the right module type.
@FA064

xxxxxxxx module detected on EiconCard but not configured. The option module
name to select in the ECCARD CONFIG program is xxxxxxxx.

An Option module on the EiconCard was detected by the program but it was not
configured using the Eicon configuration program. If not configured, the
Option module capacities are not going to be used by the software.

Run the Eicon configuration program and select the specified Option module.

@FA065

The configured xxxxxxxx module is missing from the EiconCard, module type not
recogized or hardware failure.

The specified Option module was selected in the Eicon configuration program
but could not be detected on teh EiconCard. The Option module may be missing.
Verify that the configured module is present on the EiconCard. If you do not
have such a module, simply remove the module selection using the Eicon
configuration program.

After doing so, if the error is still reported, a hardware failure may be
keeping the program from determining the correct type of module. Consult your
Eicon Technology representative for assistance.

@FA066

Modem module identification error or hardware failure. The type of the

detected module is xxxxxxx. (Dialer selection xxxxxxx in eccard config
program instead of xxxxxxx).

The type of modem module present on the EiconCard does not correspond to the
module type selected in the Eicon configuration program. Run the Eicon
configuration program and select M1 instead of M2 in the Dialer selection
field.

If the type of the configured module corresponds to the type configured in

the Eicon configuration program but this error is still reported, there may
be a hardware failure keeping the program from detecting the right modem
module type. Consult your Eicon Technology representative.

@FA200

Error reading xxxxxxxx file.

The file specified above could not be read correctly or is possibly

corrupted.

@FA201
File xxxxxxxx cannot be opened.

The file specified above could not be opened. Check to see that you have
sufficient privileges on the file or the directory that it is located in. If
the problem persists, contact your Eicon Technology representative for
assistance.

@FA202

File xxxxxxxx cannot be closed.

The specified file could not be closed due to an internal software error. Try
rebooting your machine and restarting the software. If the problem persists,
contact your Eicon Technology representative for assistance.

@FA203

Error positioning handle of xxxxxxxx file.

The specified file has encountered an internal software error. Try rebooting
your machine and restarting the software. If the problem persists, contact
your Eicon Technology representative for assistance.

@FA300

Resource conflict. An application software is already running on the

EiconCard located in slot nn. No tests performed.

This message applies to Micro Channel EiconCards only. An application is

currently running on an EiconCard located in slot #nn of your PS/2 host
system. Run ECCARD STATUS to identify the number of the EiconCard using the
slot #nn. Run ECCARD STOP /Eiconcard x, where x is the identified card
number. This will halt the application running on that EiconCard, and allow
ECTEST to run on that EiconCard.

@FA301

Resource conflict. An application software is already running on an EiconCard

using the xxxxxxxx I/O port address. No tests performed.

An application is currently running on an EiconCard using I/O port address

xxxxxxxx. Run ECCARD STATUS to identify the number of the EiconCard using the
I/O port address xxxxxxxx. Run ECCARD STOP /Eiconcard x, where x is the
identified card number. This will halt the application running on that
EiconCard, and allow ECTEST to run on that EiconCard.

@FA302
Resource conflict. An application software is already running on an EiconCard
using the nn interrupt request level. No tests performed.

An application is currently running on an EiconCard using interrupt request

level nn. Run ECCARD STATUS to identify the number of the EiconCard using the
interrupt request level nn. Run ECCARD STOP /Eiconcard nn, where nn is the
identified card number. This will halt the application running on that
EiconCard, and allow ECTEST to run on that EiconCard.

@FA303

Resource conflict. An application is already running on EiconCard #nn. No

test performed. Specify /FOrce option on command line to force tests
execution.

An application is currently running on EiconCard #nn. Specify the /FOrce

option on the command line to halt the application running on the EiconCard
and allow testing using ECTEST.

@FA305

Module type not supported by this version of ECTEST. No test will be

performed on the module.

The module type was not recognized by ECTEST. It may be a module type for
which there are no tests available or there may be a hardware failure on the
module.

@FA306

Version mismatch. Eicon Technology xxxxxxxx is not supported by this version

of ECTEST. No test performed.

There are no tests available in the current version of ECTEST for the
specified module type. If displayed module type is correct, there may be a
hardware failure on the module. Run the ECVER command to list the Eicon
Technology software you have loaded on your system. If necessary, contact
your Eicon Technology representative to obtain the most recent version of
this file.

@FA307

Unknown EiconCard model. Either new EiconCard not recognized by ECTEST or I/O
port address conflict between two EiconCards. In case of conflict or
incorrect card type selection, card diagnostic results may be erroneous.

ECTEST was not able to identify the EiconCard. This may be due to either the
fact that the board is a new revision of an EiconCard that is not yet known
recognized by the ECTEST program, or due to the fact that two different
EiconCards are configured to use the same I/O port address.
I/O port addressing problems: if two EiconCards are configured to use the
same I/O port address, select a different I/O port address for one of the
EiconCards and run program again. Note that if this was the case, the
diagnostic result was erroneous and must be ignored.

If there is no I/O port conflict between two EiconCards, this means that the
board revision was not recognized by the ECTEST program. For the purposes of
its diagnostic routines, ECTEST will assume that the EiconCard type specified
in the EiconCard configuration program is correct. In effect, ECTEST assumes
that the unidentified card will have similar characteristics to the known
properties of the card indicated in the EiconCard configuration program. This
may lead to incorrect results, and ECTEST's conclusions are to be treated
with suspicion in such a case.

@FA308

The application running on EiconCard #nn could not be stopped properly.

This error indicates a complex problem with the Eicon Technology software.
Contact your Eicon Technology representative for assistance.

@FA309

Resource conflict. An application is already running on an EiconCard using

the xxxx memory segment address. No tests performed.

An application is currently running on an EiconCard located using memory

segment address xxxx. Run ECCARD STATUS to identify the number of the
EiconCard using the memory segment address xxxx. Run ECCARD STOP /Eiconcard
nn, where nn is the identified card number. This will halt the application
running on that EiconCard, and allow ECTEST to run on that EiconCard.

@FA405

Parallel Port nn not enabled or inexistent.

Parallel Port nn does not exist on the HOST machine or is not enabled. Use
an alternate Parallel Port or enable Parallel Port #x.

_____
ECLAN

@LT087

SLP xxxxxxx aborted: specified transport protocol(s) not loaded.

One or more protocols specified in TSP.INI are not available. Check the file
ECICS.INI to see if the specified protocols are loaded properly. Also check
TSP.INI for invalid information.
@LT088

SLP startup aborted: no protocols configured.

The file TSP.INI doesn't specify any protocols to be used. At least one
protocol must be specified.

@LT089

SLP xxxxxxx aborted: not enough memory for RCB's.

TSPSLP wasn't able to create any Request Control Blocks because there was not
enough free memory. You can create more space by removing unnecessary
programs from the system, or by reducing the maximum number of sessions.

@LT090

SLP xxxxxxx aborted: not enough memory for SCB's.

TSPSLP wasn't able to create any Service Control Blocks because there was not
enough free memory. You can create more space by removing unnecessary
programs from the system, or by reducing the maximum number of sessions.

@LT091

SLP xxxxxxx aborted: can't start Request Manager.

This is an internal system error. It may indicate a lack of free memory. You
can create more space by removing unnecessary programs from the system, or by
reducing the maximum number of sessions.

@LT092

SLP xxxxxxx aborted: can't start Timer Manager.

This is an internal system error. Contact Eicon Technical Support for

Assistance.

@LT093

SLP stopped successfully.

This is a simple status message. It indicates that TSPSLP has stopped

properly.
@LT094

SLP startup aborted: already started.

TSPSLP was already running. The startup command was ignored. This applies
only to OS/2.

@LT095

SLP startup aborted: error nn spawning .EXE.

This is an OS/2 error. The software may be corrupted. Try reinstalling.

Contact Eicon Technical Support for more assistance.

@LT096

Unable to start advertising on xxxxxxx.

This is an internal software error which applies for protocols which support
a server advertising facility. Contact Eicon Technical Support for
Assistance.

@LT097

Unable to initialize TSP for xxxxxxx LISTENER.

This is an internal software error. Contact Eicon Technical Support for

Assistance.

@LT098

Invalid .INI mode, using default (agent).

There is a problem with the .INI file. The information on the "MODE=" line is
invalid. Check the file for error in syntax.

@LT099

.INI poll interval nn out of range, using nn.

The value specified on the "POLL=" line in the .INI file is either too small
or too large. It should be between 5 and 300.

@LT100

Unknown protocol xxxxxxx found in .INI.

The system can't identify the protocol specified in the .INI file. The
proper values are "SPC" for SPX/IPX, "TCP" for TCP/IP, "NB" for NetBIOS or
OS/2, and "AT" for AppleTalk running on NetWare.

@LT101

.INI reply timeout nn out of range, using nn.

The value specified on the "timeout=" line in the .INI file is either too
small or too large. It should be between 5 and 300.

@LT102

Unable to resolve xxxxxxx SLP domain server 'xxxxxxx'.

This may not be an error. The above-mentioned SLP agent can't find a
particular server. The server may be down.

@LT168

SLP System Error xxxxxxx (nn).

A system error occurred in ECSLP. You will have to restart your system. If
the problem persists, make note of the error return code (nn) and contact
Eicon Customer Support.

@LT169

SLP startup aborted, see the ERROR LOG file xxxxxxx.

The ECSLP program could not start for an unspecified reason. Check the error
log file for more information.

@LT170

The xxxxxxx configuration file is not found.

The configuration file specified by xxxxxxx could not be found. Check that you
have specified the correct file name, that the file exists, and that it can
be found in the directory specified by the %path% setting. You may have to
create a new configuration file.

@LT171

SLP startup aborted: error nn spawning xxxxxxx.

This is an internal system error. The program specified by xxxxxxx could not
be found. Check that the file exists, and that it can be found in the
directory specified by the %path% setting. Try reinstalling the software.

___
MPR

@NI101

Router already started. The MPR START command was previously issued.

You need only issue the MPR START command at the beginning of each Router
session to use the Router commands and functions.

@NI102

Router was not started. To start the Router, issue the MPR START command.

The Router is not currently active. To begin a new Router session, issue the
MPR START command to enable Router commands and functions.

@NI103

IP stack not bound. Make sure that TCP/IP NetBIOS and TCP/IP Protocol are
bound to the Eicon Router Driver. Use the Bind option in the Network applet.

Network driver bindings necessary for the operation of the Router are missing.
Use the Network applet in Control Panel to verify that the Eicon NDIS Driver
is bound to the proper protocols.

@NI104

Shutdown failure. The MPR STOP command was unsuccessful.

The Router is not accepting the MPR STOP command that you have issued. To
terminate the Router, reboot your system.

@NI201

The circuit name already exists. Specify a different circuit name when you
issue the MPRCCT ADD or IPMAP ADD commands.

Each time you create a new circuit, you must use a unique circuit name. This
error has occurred because you are trying to create a circuit with a circuit
name that is already defined in the MPR.INI file.
@NI202

Parameter entry error: invalid port number. The port number must be within the
valid range.

The number of EiconCard ports available varies depending on the number and
type of EiconCard(s) installed. The maximum valid range for a Port Number is 1
to 48. Only specific EiconCards can support multiple ports; check your
EiconCard Installation Guide for more information.

@NI203

The specified connection could not be found in the MPR.INI file.

This error has occurred because the Router cannot identify the specified
circuit name. Verify the circuit entry parameters and try again.

@NI204

Internal software error: invalid connection ID. Contact your Eicon Technology
representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI205

Invalid connection type. Set the circuit to Incoming, Two-way, or Outgoing

using MPR.INI or MPRCCT .

The X.25 connection type specified does not match any of the valid choices:
Incoming, Two-way, or Outgoing.

@NI206

Invalid Autostart option. In the [CIRCUIT_ENTRY\name] section of the MPR.INI

file, set Auto_Start to Y for yes or N for no.

This error has occurred because you have entered one or more characters other
than Y for yes or N for no. The Autostart option allows you to choose whether
or not you want your Router connections to be activated automatically upon
starting the Router.
@NI207

Invalid compression option. In the [CIRCUIT_ENTRY\name] section of the MPR.INI

file, set Data_Compression to Y for yes or N for no.

This error has occurred because you have entered one or more characters other
than Y to turn on compression or N to turn off compression.

@NI208

Invalid LAN protocol. The Router can only accept the IP protocol type.

In the [CIRCUIT_ENTRY\name] section of the MPR.INI file, the LAN protocol

parameter must be set to IP.

@NI209

Invalid WAN protocol. The Router only operates over X.25 SVC or X.25 PVC.

The WAN protocol parameter must be in the [CIRCUIT_ENTRY\name] section of the

MPR.INI file. This release of the Router only supports X.25 SVC and X.25 PVC
protocols.

@NI210

Inconsistent WAN protocol. The specified connection type is invalid for the
selected WAN protocol.

The connection type you have specified (Incoming, Two-way, Outgoing) is

invalid for the protocol type you want to use (X.25 PVC, X.25 SVC). When
creating a circuit in MPR.INI or through MPRCCT, ensure that the specified
connection type and protocol type can be used together.

@NI211

Invalid circuit name. The circuit name specified does not exist or is invalid.
Ensure that you use 1-15 ASCII characters.

Circuit names are defined in MPR.INI or are specified through MPRCCT and must
contain 1-15 ASCII characters, excluding control characters. It is preferable
to use only alphanumeric characters when defining circuit names.

@NI212

The specified comment line in the [CIRCUIT_ENTRY\name] section of the MPR.INI

file is over the 80 character limit.

You should not enter more than 80 characters when typing a comment line in the
[CIRCUIT_ENTRY\name] section of the MPR.INI file.

@NI213

Unable to save a connection entry in the MPR.INI file. Contact your Eicon
Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI214

The circuit is currently activated; modifications cannot be performed.

Modifying the connection while the WAN connection is active is not permitted.

@NI215

The circuit name already exists in the Router circuit table. Rename and try
again.

Each time you create a new circuit, you must use a unique circuit name. This
error has occurred because you are trying to create a circuit with a circuit
name that is already defined in the Router. Use another circuit name when
issuing the MPRCCT ADD or IPMAP ADD commands.

@NI216

The Router circuit table is full. Delete unused circuit entries currently
active in the Router, or increase the number of circuits permitted by the
Router configuration using the Network applet in Control Panel.

Use MPRCCT DELETE cctName command to delete unused circuit entries currently
active in the Router.

@NI217

The specified EiconCard port could not be initialized. Verify that the
EiconCard and Connection Manager were properly loaded and that you have not
surpassed the maximum number of ports permitted.

Each port on each EiconCard must be correctly configured for your Router
connection. Run the EiconCard configuration program to verify that you have
properly configured the EiconCard. To increase the number of ports, use the
Network applet in Control Panel. You must reboot your PC after you do this for
any changes to take effect.

@NI218

Internal software error: circuit unbind error. Contact your Eicon Technology
representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI219

Circuit name not found in the Router. An active circuit name must be present
to invoke the MPRCCT or IPMAP commands.

This error has occurred because you are trying to delete or obtain status on a
circuit that does not exist. Verify that you are using the correct circuit
name and try again.

@NI220

Circuit name busy in the ECNDIS driver. Pause briefly between entering
commands.

The Router requires a certain amount of time between entering the MPRCCT ADD
command and the MPRCCT DELETE command for the desired action(s) to take
effect. Please pause briefly between entering commands.

@NI221

Subnet not loaded. The EiconCard must be configured for the type of WAN
protocol specified.

Verify that the WAN protocol for the specified circuit matches that loaded on
the EiconCard. This release of the Router only supports the X.25 protocol.

@NI222

Internal software error: unknown code. Contact your Eicon Technology

representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI223

Port nn. This port is already in use by another protocol. Either use another
port or stop the protocol on the current port first.

You are trying to use a port that is already in use. Only one protocol can be
active on a port at a time.

@NI250

The remote DTE address is missing or invalid. This address is required when
you issue the MPRCCT ADD X25 command.

You must specify the remote X.25 DTE Address when you create a circuit. If you
did specify an address, then it is not in the correct format, as specified by
CCITT Recommendation X.121. Verify that you are using the correct DTE address,
and try again.

@NI251

The local DTE address is missing. You must specify the remote X.25 DTE Address
when you create a circuit using a two-way connection type.

When you issue the MPRCCT ADD X.25 command, you will need to enter the correct
local DTE address for a two-way connection type.

@NI252

The local DTE address is invalid. Enter the correct local DTE address when you
issue the MPRCCT ADD X25 command.

The local DTE address you specified is not in the correct format, as specified
by CCITT Recommendation X.121. Verify that you are using the correct DTE
address and try again.

@NI253

The Permanent Virtual Circuit (PVC) number is missing or invalid. Enter the
correct X.25 PVC number when you issue the MPRCCT ADD X25 -V pvcnum command.

You must specify the PVC number when you create a circuit that will use an
X.25 permanent virtual circuit. If you did specify a PVC number, it is not in
the valid range. The number of PVCs available is specified on the X.25
Configuration screen of the EiconCard Configuration Program.

@NI254

X.25 inactivity timeout is not within the valid range.

The valid range for the X.25 inactivity timeout is 0 to 86400 seconds. The
default value is 60 seconds. Timeout refers to the amount of time a computer
waits for a response before disconnecting the line.

@NI255

The X.25 retry number value specified is not within the valid range.

The valid range for an X.25 retry number is 0 to 100. The default value is 0
retries before the Router abandons the data transfer.

@NI256

The X.25 retry delay value specified is not within the valid range.

The valid range for an X.25 retry delay value is 5 to 65535 seconds. The
default is 5 seconds before the Router abandons the data transfer.

@NI257

The asterisk wildcard character (*) is not accepted when indicating an X.25
DTE address for this connection type.

This error has occurred because you are using a wildcard character for an
Outgoing X.25 circuit. You can use wildcard characters to specify the remote
DTE Address for Incoming circuits only.

@NI258

Invalid user data length. The X.25 user data entry must be within the valid
range.

The maximum or minimum user data length varies depending on your X.25 network.
Ensure that you have entered the correct data. Contact your X.25 network for
details.

@NI259

Invalid format of user data. Use ASCII characters to specify X.25 user data:
control characters are invalid.
You cannot include control characters when specifying user data. Ensure that
you have entered the correct data. Contact your X.25 network for details.

@NI260

Invalid user facilities. X.25 user facilities must follow CCITT standards.
Contact your X.25 network for more information.

Verify that you have entered the correct user facilities. For more information
on CCITT user facilities, consult the CCITT Recommendation International User
Services and Facilities in Public Data Networks, Vol. VIII, Fascicle VIII.2,
Rec. X.2.

@NI261

Connection not started.

This is a simple status message.

@NI262

Port binding Error.

This is a status message, usful only to Eicon Technology personnel.

@NI270

The DLCI number is missing or invalid. Specify the correct DLCI for this
Frame Relay Circuit.

Make sure that you have specified a value for the DLCI. The correct range is
between 16 and 1007.

@NI290

EiconCard memory shortage. Not enough memory to enable compression for the
specified circuit. Reduce the number of allocated sessions or restart the
connection without compression.

There is insufficient memory on the EiconCard to turn on the compression

option. You must either do without compression or reduce the number of
sessions to free up more memory.

@NI291

Node was not started. Ensure that the specified node used by this circuit is
loaded on the EiconCard before the circuit is activated.
The specified Node must be loaded onto the EiconCard and started before it
can be used by this curcuit.

@NI292

LU name already defined. The local LU name used for the specified circuit is
already defined on the EiconCard. Change the local LU name used for the
connection and try again.

The router cannot have two Local LUs with the same name. Use a different
name.

@NI301

The specified mapping could not be found in the MPR.INI file.

This error has occurred because the Router cannot identify the specified
mapping. Verify the mapper entry parameters and try again.

@NI302

IP address (next hop) is missing. The IP address specified through IPMAP does
not exist or is invalid. Enter the correct IP address and try again.

In the [MAPPER_ENTRY\ipaddress] section of the MPR.INI or through IPMAP,

verify that the Next Hop (IP Address) is specified in the following format:
xxx.xxx.xxx.xxx where xxx is a number between 1 to 254.

@NI303

Invalid broadcast setting in MPR.INI. In the [MAPPER_ENTRY\ipaddress] section

of the MPR.INI file, set Broadcast to Y for yes or N for no.

This error has occurred because you have entered one or more characters other
than Y to turn on the Broadcast function or N to turn off the Broadcast
function. The Broadcast function indicates whether broadcasts of IP protocol
are active on the current circuit. When broadcasts are off, applications that
rely on broadcasts, such as TCP/IP's ROUTE, cannot be used over the WAN.

@NI304

Unable to save a mapper entry to the MPR.INI file. Contact your Eicon
Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI305

Mapping table full in Router. Remove unnecessary mappings currently active in

the Router, or increase the maximum number of mappings using the Network
applet in Control Panel.

Use the IPMAP DELETE cctName command to delete active mappings. If you want to
change the maximum number of mappings use the Network applet in Control Panel.
You must reboot your PC after you do this for any changes to take effect.

@NI306

Mapping entry not found in the Router. The mapping entry must exist when
issuing the IPMAP DELETE command.

This error has occurred because you are trying to delete a mapping entry that
does not exist. Verify that you are using the correct circuit name and try
again.

@NI307

Map broadcast error. Unable to activate the Broadcast function with the IPMAP
ADD ipaddress /B command.

This error has occurred because the Router cannot recognize the IPMAP ADD
ipaddress /B command that you have issued. You will need to abandon this
attempt and recreate the mapping by reissuing the command.

@NI401

Trace utility was not enabled. Use the Network applet in Control Panel to
enable the trace option for the Eicon NDIS Interface Driver.

The trace utility must be enabled before you can actually

trace a protocol. Use the Network applet to do this.

@NI402

Internal software error: invalid parameter in request. Contact your Eicon

Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment may be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it may be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI501

Internal software error: see MPR.LOG file. Contact your Eicon Technology
representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI502

Internal software error: invalid position number. Contact your Eicon

Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI504

Resource allocation error: memory allocation error in the DLL. Free memory by
removing unnecessary drivers and/or concurrent applications.

The PC requires a certain amount of free memory to successfully run the

software. Unload any unnecessary programs from memory to allow proper memory
allocation in the DLL.

@NI505

Resource allocation error: memory allocation error in the application. Free

memory by removing unnecessary drivers and/or concurrent applications.

The PC requires a certain amount of free memory to successfully run the

software. Unload any unnecessary programs from memory to allow proper memory
allocation in the Router application.

@NI506
Internal software error (SNMP): invalid field to modify.

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI507

Connection Manager session cannot be created. Increase the number of sessions

in the Connection Manager settings for your configuration.

This error has occurred because the maximum number of Connection Manager
sessions has been reached. To add a new entry, increase the Connection Manager
Session value as needed, reload the EiconCard, and try again.

@NI508

EiconCard memory shortage. Not enough memory to enable compression for the
specified circuit. Reduce the number of allocated sessions or restart the
connection without compression.

This error has occurred because there is insufficient memory on the EiconCard
to process the MPRCCT ADD [/K] command. Run the configuration program and
deselect any unnecessary protocols or restart the circuit without compression
enabled.

@NI509

Internal software error: invalid buffer from the ECNDIS driver. Contact your
Eicon Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI510

Internal software error: invalid value from the ECNDIS driver. Contact your
Eicon Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI511

Unable to initialize Eicon Router Driver. Either the Router software is

improperly installed or driver parameters have improper settings.

Verify that you have correctly installed the Router software. If the file
ECNDIS.SYS was deleted this message will appear. Another cause could be
improper settings of the Eicon Router Driver parameters. If this is the case
an error message identifying the offending parameter appears in the Event
Viewer applet.

@NI512

Internal system error: unable to communicate with the ECNDIS driver. Contact
your Eicon Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI513

Internal system error: unable to disconnect from the ECNDIS driver. Contact
your Eicon Technology representative (see manual for instructions).

This refers to a critical failure in the operation of the Router software. The
PC's environment might be corrupted. Try rebooting the machine and re-starting
the Router software. If the error persists, it might be an indication of a
corrupted program file. Make a backup copy of your configuration files by
copying the *.CFG and *.INI files to another directory, re-install the Router
software from the original distribution diskettes, and copy the *.CFG and
*.INI files back to the directory which contains the Router software.

@NI514

Unable to open the MPR.INI configuration file. Ensure that the MPR.INI file is
not a system file, missing, read-only, or hidden. Locate and/or adjust the
file and retry.

The IP Router for Windows NT software cannot read the MPR.INI if the file
attributes have been changed to system, read-only, or hidden. Another cause
might be that the MPR.INI cannot be located or is missing. The Router software
must be in the current directory or in the environment's PATH=variable.

@NI515

Invalid parameter in the MPR.INI file. Verify that all specified parameter
entries in MPR.INI are valid.

During manual editing of the MPR.INI file, syntax errors may have caused the
file to become unreadable. Another cause might be that the file itself has
been damaged. To resolve this situation, you will have to delete the MPR.INI
file and recreate the circuits by invoking the MPRCCT and IPMAP commands.

@NI516

Unable to update the MPR.INI configuration file. Ensure that the MPR.INI file
is not a system file, missing, read-only, or hidden. Locate and/or adjust the
file and retry.

The IP Router for Windows NT software cannot read the MPR.INI if the file
attributes have been changed to system, read-only, or hidden. Another cause
might be that the MPR.INI cannot be located or is missing. The Router software
must be in the current directory or in the environment's PATH=variable.

@NI517

Unable to create a temporary MPR.INI file. Ensure that the MPR.INI file is not
a system file, missing, read-only, or hidden. Locate and/or adjust the file
and retry.

The IP Router for Windows NT software cannot read the MPR.INI if the file
attributes have been changed to system, read-only, or hidden. Another cause
might be that the MPR.INI cannot be located or is missing. The Router software
must be in the current directory or in the environment's PATH=variable.

@NI601

Invalid or missing Action parameter. Ensure that action must be DROP or

FORWARD.

This is a syntax error. The Action parameter should be either DROP or

FORWARD. Check the correct usage of the command with the /? switch.

@NI602

Invalid or missing Direction parameter. Ensure that direction must be IN or

OUT or ALL.

This is a syntax error. The Direction parameter should be either IN, OUT, or
ALL.

@NI603

Invalid or missing Port Type parameter. Ensure that port type must be TCP or
UDP or ALL.

This is a syntax error. The Port Type parameter should be either TCP, UDP,
or ALL.

@NI604

Invalid or missing Low Port number parameter. Ensure that low port number be
less than the High Port number and within the valid range.

This is a syntax error. The range of the Low Port parameter is from 0 to
65535. The value for the Low Port must be less than or equal to the value
for the High Port.

@NI605

Invalid or missing High Port number parameter. Ensure that the high port
number be greater than the low port number and within the valid range.

This is a syntax error. The range of the High Port parameter is from 0 to
65535. The value for the High Port must be greater than the value for the
Low Port.

@NI606

Invalid or missing Source address parameter.

This is a syntax error. The Source IP address must be present, and must be
in the form of nnn.nnn.nnn.nnn.

@NI607

Invalid or missing Destination address parameter.

This is a syntax error. The Destination IP address must be present and must
be in the form of nnn.nnn.nnn.nnn.

@NI608

Invalid or missing filter identification parameter.

This is a syntax error. The filter ID parameter can have a number of values.
A value of 0 means this IP filter is the first filter entered in the list
associated with a given circuit; any other number is the filter ID; 99 means
the filter ID is in last on the list.

@NI609

Invalid or missing filter name in the configuration file.

This is a syntax error. The filter name is either missing from the
configuration file or not specified correctly. Check the list of filter
names.

@NI610

Invalid or missing Source Mask address parameter.

The Source Mask is either missing or not specified correctly. It must have
same form as an IP address (i.e. nnn.nnn.nnn.nnn).

@NI611

Invalid or missing Destination Mask address parameter.

The Destination Mask is either missing or not specified correctly. It must

have same form as an IP address (i.e. nnn.nnn.nnn.nnn).

@NI612

Filter is currently active and cannot be replaced (SNMP).

This specified filter is already in use and cannot be replaced until it is

deactivated.

@NI613

Invalid or missing Usage parameter. Ensure that the usage specified be either
PRIMARY or BACKUP.

This is a syntax error. The Usage parameter should be either PRIMARY or

BACKUP. If using the command line, check the correct usage of the command
with the /? switch. Otherwise, check the "connection_usage" parameter in the
NPR.INI file.

@NI614

The primary circuit specified could not be found.

This is a syntax error. Check the name specified for the primary circuit.

@NI615

A backup entry already exists for the specified circuit.

You cannot have two backup circuits for the same primary circuit. Choose
another.

@NI616

The backup circuit is not loaded because the associated primary circuit is
not bound.

Something is wrong with the primary circuit -- it may be down. Check its
status before trying to assign a backup circuit to it.

@NI617

Invalid or missing Primary Name parameter. Make sure that you provide a
valid primary circuit name whenever creating a backup entry.

This may be a syntax error -- you may be specifying an improper primary

circuit name. Or, the primary circuit you specified simply may not exist.

@NI618

The specified protocol has not been activated.

Check your EiconCard configuration, and make sure auto-activate is turned on.

@NI619

The router's filter table is full. Delete unnessary filter entries and
re-issue the command.

There is no more room on the filter name for new filter names. If any
loaded filters are not being used, they should be removed from the table.

@NI620

The specified filter could not be found in the router's filter table.

The system cannot find the specified. It does not appear to be loaded.
Check your configuration.
@NI621

The router does not have any filter chains available.

There is not enough memory assigned to filters. Check your ECNDIS

configuration, and increase the number of filters.

@NI622

The specified filter is already active.

You tried to activate a filter that was already on.

@NI623

The specified filter is already inactive.

You tried to deactivate a filter than was already off.

@NI624

The backup entry can't be created because the WAN protocol is not the same as
the one from the specified primary circuit.

The WAN protocol for the primary and backup circuits must be the same. Run
the config program or check out your NPR.INI file for a mismatched protocol.

@NI625

Invalid WAN protocol. The specified WAN protocol does not match the one that
is currently loaded on this port.

The port requires a different WAN protocol than the one specified. Check
your configuration.

@NI626

The filter specified could not be found in the filter table.

@NI627

Invalid or missing IP Port Filter parameter. The specified value is not

within the valid range.
@NI628

Unable to save the IP Port Filter entry. Contact your Customer Services
representative (see manual for instructions).

@NI629

Filter already in use. The value specified is already in the filter table.

NI630=1;Connection Manager session cannot be created. Increase the number of

sessions in the Connection Manager settings for your configuration.

@NI801

Router software incorrectly installed. Re-install according to the directions

in this manual.

Certain internal parameter settings could not be found by the Router software.
This indicates a possible problem with your Router installation or that the
PC's environment may be corrupt. Try rebooting the machine and re-starting the
Router software. If the error persists, it may be an indication of a corrupted
program file, or Windows NT Registry database. Make a backup copy of your
configuration files by copying the *.CFG and *.INI files to another directory,
re-install the Router software from the original distribution diskettes, and
copy the *.CFG and *.INI files back to the directory which contains the Router
software. See your Windows NT manual for instructions on backing up and
restoring the Registry database.

@NI802

The Core Services software is not installed. Re-install the Core Services
software.

Verify that you have correctly installed the Eicon Core Services software.
This message will also appear if you delete the file ECNB.SYS.

@NI803

Invalid parameter setting. Use the Network applet to correct the setting for
the Eicon Router Driver parameter: nnnnnnnnn

There is insufficient memory to support the configuration you have defined.

Reduce the setting for the indicated parameter remedy the situation.

@NI804

Memory shortage. Use the Network applet to alter the setting for the Eicon
Router Driver parameter: nnnnnnnnn

There is insufficient memory to support the configuration you have defined.

Reduce the setting for the indicated parameter remedy the situation.

@NI805

Port number conflict. Ensure that each Eicon NDIS Logical Adapter is assigned
as unique port number.

One or more Eicon NDIS Logical Adapters share the same port number. Use the
Network applet in Control Panel to give each Adapter its own unique port
number. You can only have one Eicon NDIS Logical Adapter per EiconCard port.

______
ECCARD

@PD001

Syntax error. Command aborted.

The command was not executed because of an error in the way parameters were
specified on the command line. Obtain the correct syntax by retyping the
command with the help parameter /?.

@PD002

Required driver missing: EiconCard device driver not installed.

ECBIOS has not been installed. The device driver ECBIOS is the link between
your PC and the EiconCard. Install and start the ECBIOS driver before you try
to execute this command.

@PD003

Memory shortage. Unload programs, or reduce the number of allocated sessions.

There is not enough memory available in the computer to run ECCARD. Unload
unnecessary programs from memory, and run ECCARD again.

@PD004

Parameter entry error: invalid card number.

The card number that you specified is incorrect. Make sure that a card by
that number exists. Note that DOS machines can support up to six EiconCards
but OS/2 machines can only support up to four.
@PD005

Parameter entry error: invalid port number.

The port number specified is incorrect. Run ECCARD STATUS for a list of valid
port numbers.

@PD006

Parameter entry error: invalid port name.

The port name specified is incorrect. Run ECCARD STATUS to determine if a

port by that name exists, and that the port name specified is a valid
alphanumeric sequence.

@PD007

Required file missing. Configuration file could not be found.

The EiconCard configuration file could not be found. This may be because an
incorrect name or path was specified for the file. If you cannot find the
EC.CFG file, recreate it using the ECCARD CONFIG command.

@PD008

Invalid, corrupt, or bad version of configuration file.

The EiconCard configuration file *.CFG could not be read by ECCARD. The file
may have been created with an outdated version of ECCARD or ECCFG, or have
been corrupted. Delete the file and recreate it with a version of ECCARD
(CONFIG) or ECCFG that matches the rest of your software.

@PD009

Internal software error. xxxxxxxx(nn).

There was an error with ECCARD. This could indicate that ECCARD has been
corrupted. You may need to re-install the Eicon Technology Gateway software.
If you are unable to resolve the problem, contact your Eicon Technology
representative for assistance.

@PD010

Size of Mail trace on EiconCard is invalid, must be between 1 and 64K.

The EiconCard software cannot allocate a memory size greater than 64K. Enter
a number from 1 to 64.
@PD011

Size of NCB trace on EiconCard is invalid, must be between 1 and 64K.

The EiconCard software cannot allocate a memory size greater than 64K. Enter
a number from 1 to 64.

@PD012

Required file missing. Executable file xxxxxxxx could not be found.

The specified EiconCard executable file could not be found. The file is not
in the same path as the ECCARD module. Locate or re-load the file from the
distribution diskettes, and place it in the proper location.

@PD013

Cannot open file xxxxxxxx: invalid directory or write access denied.

The specified file could not be opened. You may have entered an incorrect
file and/or pathname, the file may not exist, or you may not have write
privileges on the file. Try and locate the file under a different pathname.
This may be be a binary dump file that was specified with ECCARD DUMP /b
dumpfile. If the file does not exist and is part of the Eicon Technology
software package, consider reloading the file from the install program. To
check the file status, use the DOS attrib command and ensure that the file is
not read-only.

@PD014

Invalid, corrupt, or bad version of test file xxxxxxxx.

The test file xxxxxxxx (usually VERIFCFG.ELM) could not be read by the
EiconCard program. Delete the file and reload the original file from the
distribution diskettes.

@PD015

Required driver or redirector missing: EiconCard device driver or redirector

not installed.

The ECBIOS or LAN support driver cannot be found. The EiconCard device driver
ECBIOS is the link between your PC and the EiconCard. The redirector links
the workstation to the gateway. These drivers must be started before you try
and load the EiconCard.
@PD016

Parameter entry error: invalid drive or path specified.

The pathname you specified with the ECVER command was incorrect. Obtain the
correct syntax by retyping the command using the help parameter /?.

@PD017

Failed to write to output file xxxxxxxx. Verify if there is still space left
on the I/O device.

The specified EiconCard binary dump file could not be opened. You are
probably out of disk space on your drive. If the problem is due to a space
limitation, delete any unnecessary files to free some space on the drive.

@PD018

Cannot read the file xxxxxxxx. Verify the file integrity or the I/O device
condition.

The test file xxxxxxxx (usually VERIFCFG.ELM) could not be read by the
EiconCard program. If the file is corrupted, delete the file and reload it
from the original distribution diskettes.

@PD019

Server not responding. Make sure that the server's redirector is loaded.

The EiconCard could not reach the gateway specified in your command. Make
sure that the LAN support software (ECLAN) has been loaded on your machine,
check the gateway name and spelling, and check all your connections.

@PD020

Resource shortage. Too many sessions are active on the redirector or on the
server.

There are not enough sessions available for normal operations. Verify that
you have allocated enough sessions with ECCARD CONFIG. See if unnecessary
sessions on this or another workstation can be discontinued to free
resources.

@PD021

Command not supported on workstation. Type ECCARD /? for help.

The command that you entered can only be executed on the gateway PC.
@PD022

Resource shortage. Too many applications are using ECBIOS.

The computer as run out of free memory to manage system rousources. Try
quitting some applications.

@PD023

The xxxxxxxx file for output redirection could not be opened. Invalid file or
write access denied.

The specified file could not be opened. You may have entered an incorrect
file and/or pathname, the file may not exist, you may not have write
privileges on the file, or your disk may be full. Try and locate the file
under a different pathname.

@PD024

Invalid EiconCard memory window tuning delay, must be between 0 and 1024.

Specify a value between 0 and 1024 for delay period.

@PD025

Invalid EiconCard state for this command. EiconCard must be xxxxxxxx.

The ECCARD OPTION command was issued without first loading the EiconCard with
the delay option. Issue the following command first:

[LOAD] ECCARD START [/E n] [/Zwait delay]

@PD101

Card initialization error: EiconCard nn. Card not stopped. Cannot start.

The ECCARD START /E nn command was issued, but could not be executed because
the EiconCard is still running. Run ECCARD STOP before running ECCARD START.

@PD102

Configuration error: EiconCard nn. Card not defined in configuration file.

You have not defined a configuration for the EiconCard you are trying to
load. Use the Eicon configuration program to define your card.
@PD103

Configuration error: EiconCard nn. Test loadable module xxxxxxxx could not be
found.

The Eicon Loadable Module file represented by xxxxxxxx (usually VERIFCFG.ELM)

could not be found in the expected drive and directory. Make sure that it is
in the correct location. The VERIFCFG.ELM file is used to test the
EiconCards.

@PD104

Configuration error: EiconCard nn. Invalid card type in configuration file.

The type of card detected does not correspond to the card type defined in the
configuration file. Use the EiconCard configuration program ECCARD CONFIG
(see the reference manual) to verify your card type.

@PD105

Configuration error: EiconCard nn. Hardware configuration failed. Bad or

conflicting I/O port address.

The I/O Address jumpers on your EiconCard do not match the values you
specified in the configuration file. This message could also mean that you
are trying to access an EiconCard that does not exist, or that the wrong card
was specified during configuration. Ensure that the I/O Address jumpers on
your EiconCard match. If they do, then verify that no other adapter card
installed in your PC is set to the same I/O Address. This error can also
indicate that you specified the wrong card during configuration.

@PD106

Configuration error: EiconCard nn. Hardware configuration failed. Bad or

conflicting segment address.

The Memory Segment Address jumpers on your EiconCard do not match the values
you specified in the configuration file. This message could also mean that
you are trying to access an EiconCard that does not exist. Ensure that the
Memory Segment Address jumpers on your EiconCard match. If they do, then
verify that no other adapter card installed in your PC is set to the same
Memory Segment Address.

@PD107

Configuration error: EiconCard nn. Hardware configuration failed. Invalid IRQ

setting.

The IRQ jumpers on your EiconCard do not match the values you specified in
the configuration file. Ensure that the IRQ jumpers match. If they do, then
verify that no other adapter card installed in your PC is set to the same IRQ
value. If they do not, then run the EiconCard configuration program and
select the correct IRQ values for the EiconCard. If you try to configure an
extended (ISA) IRQ (10-12, 14-15), be sure the EiconCard supports it and it
is installed in a 16-bit slot. Use the command ECTEST /v in order to obtain
diagnostic information.

@PD108

Card Identification error: EiconCard nn. Hardware configuration failed: card

in slot is not an EiconCard.

The ECCARD software has been unable to find or identify the EiconCard that
you specified. Check to see that the EiconCard is properly installed. On
Micro Channel machines, ensure that the card is in the correct slot.

@PD109

Resource conflict: EiconCard nn. Hardware configuration failed. I/O port

address already used.

The I/O port address that you specified is already in use. This may indicate
that the EiconCard was already configured using another card number, or that
another device is using that I/O port address. Change the I/O port used by
the EiconCard to a different address, using the EiconCard configuration
program.

@PD110

Resource conflict: EiconCard nn. Hardware configuration failed. Memory window

address already used.

This message indicates that another adapter card installed in your PC is

using the same Memory Segment Address as your EiconCard. Change the memory
segment used by the EiconCard to a different address using the EiconCard
configuration program.

@PD111

Resource conflict: EiconCard nn. Hardware configuration failed. IRQ setting

already used.

This message indicates that another adapter card installed in your PC is

using the same IRQ (Interrupt Request Level) as your EiconCard. Change the
IRQ used by the EiconCard to a different one, using the EiconCard
configuration program.

@PD112
Resource conflict: EiconCard nn. Hardware configuration failed. Slot number
already in use by another EiconCard.

The slot number that you specified in the EiconCard configuration program for
this EiconCard is already in use by another EiconCard. Confirm which slot
belongs to which card, and correct your configuration using the EiconCard
configuration program.

@PD113

Hardware error: EiconCard nn. Hardware configuration failed. Cannot evaluate

EiconCard memory size.

ECCARD is unable to evaluate the EiconCard's memory size. This may be because
the card is not installed properly, or because the configuration refers to an
incorrect location for the EiconCard. You should verify that the card has
been installed correctly using the most recent copy of VERIFCFG.ELM. If
problems persist, contact your Eicon Technology representative for
assistance.

@PD114

Configuration error: EiconCard nn. Invalid or unsupported card type or card

interface type.

The card type detected is not supported by the version of software you are
using. Run the ECVER command to list all the Eicon Technology software you
are using. Contact your Eicon Technology representative to obtain the correct
version of the software.

@PD120

Configuration error: EiconCard nn. Card is not configured.

The EiconCard configuration has not yet been detected by the driver. You must
first ensure that the ECBIOS driver has been loaded into memory and the card
has been started using ECCARD START.

@PD121

EiconCard Configuration: No card configured.

The EiconCard configuration has not yet been detected by the driver. You must
first ensure that the ECBIOS driver has been loaded into memory and the card
has been started using ECCARD START.

@PD122
EiconCard nn: The configured protocol does not require activation. You should
change AUTO ACTIVATE PORT option to NO in the configuration file.

When Auto Activate is on, then all configured X.25 and Frame Relay ports are
automatically activated as soon as you start the gateway. Note that all other
protocols (SDLC, HDLC, etc.) cannot be automatically activated. Run the
ECCARD CONFIG program and on the Hardware Configuration Screen select N for
Auto activate ports if any protocols other than X.25 or Frame Relay have been
selected.

@PD123

EiconCard associated to the port name xxxxxxxx is not configured or invalid

port name.

The card has not been started or, the software cannot find a matching port
name in the ECCARD CONFIG file. Use the EiconCard configuration program
ECCARD CONFIG to redefine your port.

@PD124

EiconCard nn. Configuration error: EiconCard nn. Cannot detect Notebook

EiconCard.

Verify the connection between the parallel port and the Notebook EiconCard.
Also verify the connection EiconCard and the power source.

@PD125

EiconCard nn. Configuration error: EiconCard nn. No parallel port detected on

LPTx.

Verify the configuration (LOT1, LPT2, LPT3) of the parallel port.

@PD126

Configuration error: EiconCard nn. The xxxxxxx option is not supported by the
underlying software modules (DLL and/or driver).

@PD127

Configuration error: EiconCard nn. The xxxxxxx option is not supported by the
EiconCard.

@PD201

File not found: module order file xxxxxxxx. EiconCard nn: Load has failed.
The specified EiconCard module order file could not be found. The file may be
located in a different directory, or it may not exist. Locate the file, or
reload it from the distribution diskettes, and issue the command again.

@PD202

File not found: loadable module file xxxxxxxx. EiconCard nn: Load has failed.

The specified EiconCard loadable module file could not be found. The Eicon
Loadable Module file represented by xxxxxxxx could not be found in the
expected drive and directory. Make sure that it is in the correct location.
The loadable module is necessary for the operation of the protocol.

@PD203

EiconCard Memory shortage. EiconCard nn: load has failed. Not enough memory
on the EiconCard to load the requested configuration.

The EiconCard was unable to load the protocol software onto the specified
EiconCard. This may be because of insufficient memory on the EiconCard, or
because of a hardware problem with the EiconCard itself. Run ECTEST to verify
the integrity of the EiconCard hardware or run ECCARD CONFIG and unselect any
unecessary protocols. This error commonly occurs on DNA 512K EiconCards.
Although the ECCARD CONFIG program allows configuration of two ports, in
reality only one can be loaded onto the card. A memory overflow occurs when
trying to load the second port's configuration.

@PD204

EiconCard nn. Load has failed. Invalid loadable module file xxxxxxxx. File
checksum failed.

The loadable module file has been corrupted, and cannot be used. You may have
to re-install the Eicon Technology software. Make a backup of your *.CFG
files by copying them to another directory on the hard disk, and re-install
the software from your original distribution diskettes. You should then copy
the backup *.CFG files into the same directory as the re-installed software.

@PD205

EiconCard nn: Load has failed. Internal EiconCard software error

(ECBIOS:xxxxxxxx).

The EiconCard was unable to load the specified protocol software. This may be
because of a hardware problem with the EiconCard itself, or because of
corrupted files. Run ECTEST to verify the integrity of the EiconCard
hardware. If the problem persists, reload the software from the distribution
diskettes.
@PD206

EiconCard nn. Load has failed. Invalid loadable module file xxxxxxxx. Mail
trace signature was not found.

The Eicon Loadable Module file represented by xxxxxxxx has been altered and
is invalid due to a missing MAIL trace parameter. Reload the gateway software
from the distribution diskettes and try again.

@PD207

EiconCard nn. Load has failed. Invalid loadable module file xxxxxxxx. NCB
trace signature was not found.

The Eicon Loadable Module file represented by xxxxxxxx (usually VERIFCFG.ELM)

is invalid due to a missing NCB trace parameter. Reload the gateway software
from the distribution diskettes and try again.

@PD208

EiconCard nn. Load has failed. Fatal EiconCard software error. (xxxxxxxxx).

An application terminated abnormally and any previous commands issued to the

card were not carried out. There could also be a possible memory or interrupt
conflict with another adapter installed in your machine. Determine the
application/adapter that caused the EiconCard to halt and remove it from
memory.

@PD209

EiconCard nn. An operation has failed. Time-out occured.

If you are using a Notebook EiconCard, verify all your connections. If you
are using a cable between the parallel port and the Notebook EiconCard, try
using a shorter cable or no cable at all.

@PD251

File not found: loadable module file xxxxxxxx. EiconCard nn.

The specified EiconCard loadable module file could not be found. The Eicon
Loadable Module file represented by xxxxxxxx could not be found in the
expected drive and directory. Make sure that it is in the correct location.

@PD301

Port nn. The xxxxxxxx protocol is not loaded.

You cannot perform the specified action on this protocol because it has not
been loaded onto the EiconCard. Run the EiconCard install program in order to
load the protocol module. Then run the ECCARD CONFIG program and configure
the protocol.

@PD302

Port nn. The xxxxxxxx protocol is not configured.

This protocol has not been properly configured or the card has not been
started. Run the EiconCard Configuration program and configure the protocol,
or run ECCARD START /P nn to activate the port.

@PD303

Port nn. EiconCard memory shortage. Not enough memory on the EiconCard to
load the requested configuration.

The EiconCard was unable to load the specified protocol software. This may be
because of insufficient memory on the EiconCard, or because of a hardware
problem with the EiconCard itself. Run ECCARD CONFIG and deselect any
unecessary protocols, or run ECTEST to verify the integrity of the EiconCard
hardware.

@PD304

Port nn. No protocol to activate or, if applicable, use a protocol-specific

START command to activate the port (E.G.:ECPAD START /P,...).

The line protocol configured for this port is not an activable protocol (X.25
or Frame Relay), or is a protocol which does not requre activation. (see
PD122).

@PD305

Port nn. The xxxxxxxx protocol is already activated.

The ECCARD START /P command was issued but could not be executed because the
port was already active. Run the EiconCard configuration program and select a
new protocol or run ECCARD STOP /P nn to first stop the port. This could also
indicate that AUTO ACTIVATE has been set to YES in ECCARD CONFIG, making the
command line invocation unnecessary.

@PD306

Port nn. The xxxxxxxx protocol is already deactivated.

The request to deactivate a port was ignored since the port has already been
stopped.
@PD307

All ports: No protocol(s) activated.

None of the EiconCards have been started. Run the ECCARD START /E command.

@PD308

Port nn. No protocol to deactivate.

The line protocol configured for this port is not a stoppable protocol (X.25
or Frame Relay), or is a protocol which does not requre stopping. (see
PD122).

@PD309

Undefined NCB return code (0xxx) sent by card.

A diagnostic code returned by the software on the EiconCard is undefined.

This may be caused by an invalid or altered module order file. Stop the
EiconCard with ECCARD STOP and restart it again. If the problem persists, it
may be an indication of a corrupted module. Reload the original software from
the distribution diskettes.

@PD321

Port nn. The xxxxxxxx protocol could not be started. Modem not ready (no
DSR).

Your modem is not functioning properly. This might be because the modem is
turned off, because your cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working synchronous,
full-duplex modem is connected to the EiconCard. If you are using a
null-modem cable it could be defective: check the cable's pin outs. Refer to
the Modemless Connections appendix of the Gateway Reference Guide for more
information on null-modem connections.

If you receive this message while using a DPNA card, check that the jumper is
set to the right interface: X.21 (RS-232).

@PD322

Port nn. The xxxxxxxx protocol could not be started. Modem not ready (no
CTS).

Your modem is not functioning properly. This might be because the modem is
turned off, because your cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working synchronous,
full-duplex modem is connected to the EiconCard. If you are using a
null-modem cable it could be defective: check the cable's pin outs. Refer to
the Modemless Connections appendix of the Gateway Reference Guide for more
information on null-modem connections.

If you receive this message while using a DPNA card, check that the jumper is
set to the right interface: X.21 (RS-232). This may also indicate a clocking
problem. Verify that the INTERNAL/EXTERNAL CLOCKING setting has been set
correctly.

@PD323

Port nn. The xxxxxxxx protocol could not be started. Modem not ready (no
clock).

The protocol port could not be started because your modem is not functioning
properly. This might be because the modem is turned off, because your cable
is disconnected, or because there is something wrong with the cable itself.
Make sure that a working synchronous, full-duplex modem is connected to the
EiconCard. If your EiconCard is configured for External Clocking, make sure
the other end is providing the clocking. If it is configured for Internal
Clocking, make sure the other end is not providing the clocking. If you are
using a null-modem cable it could be defective: check the cable's pin outs.
Refer to the Modemless Connections appendix of the Gateway Reference Guide
for more information on null-modem connections.

@PD324

Port nn. The xxxxxxxx protocol could not be started. Remote line busy.

Communications cannot be established because the remote line is busy. If

repeated attempts fail, contact the operators of the remote system.

@PD325

Port nn. The xxxxxxxx protocol could not be started. Remote not answering.

Communications cannot be established because the remote computer is not

answering. Contact the operators of the remote system.

@PD326

Port nn. The xxxxxxxx protocol could not be started. No line available.

There is no line available for the requested operation. Free a line and
repeat the operation.

@PD327
Port nn. The xxxxxxxx protocol could not be started. ECBIOS error nn.

The ECBIOS driver has possibly been corrupted. Retry the command. If you
still do not have any success, unload the ECBIOS driver and reload it again.
If you are running on an OS/2 system, check that the ECBIOS.SYS driver has
been specified in the CONFIG.SYS file.

@PD328

Port nn. The xxxxxxxx protocol could not be started. Timeout expired. Port
activation cancelled.

During attempts to make a port connection, the timeout period has expired and
port activation cancelled. If problems still persist, have your system
administrator check the network status.

@PD341

Port nn. Network status xxxxxxxx. Modem is not ready.

Your modem is not functioning properly. This might be because the modem is
turned off, because your cable is disconnected, or because there is something
wrong with the cable itself. Make sure that a working synchronous,
full-duplex modem is connected to the EiconCard. If you are using a
null-modem cable it could be defective: check the cable's pin outs. Refer to
the Modemless Connections appendix of the Gateway Reference Guide for more
information on null-modem connections.

@PD342

Port nn. Network status xxxxxxxx. Link level is not ready.

The remote side of the connection is not ready, or both the local and remote
are configured as DCE or DTE. Verify your configuration and change it if
necessary.

@PD343

Port nn. Network status xxxxxxxx. The EiconCard's settings do not match the
configuration.

The jumpers on your EiconCard do not match the values you specified in the
configuration file. This message could also mean that you are trying to
access an EiconCard that does not exist. Ensure that the jumpers on your
EiconCard match. If they do, then verify that no other adapter card installed
in your PC is set to the same I/O, IRQ, or memory addresses.

@PD350
Port nn. XID exchange failed.

The XID you specified in the EiconCard configuration file is invalid. Check
the XID value with your X.25 Network Subscription.

@PD351

Port nn. Packet level is not ready.

The remote side of the connection is not ready, or both the local and remote
are configured as DCE or DTE. Verify your configuration and change it if
necessary.

@PD401

Load aborted: Cannot attach to Micro EiconCard.

The Micro EiconCard is a complex device, and is dependent on the parallel

port of a computer to make a connection. Verify the connection between the
Micro EiconCard and the parallel port. Verify that the parallel port number
(LPT1, LP2, LPT3) corresponds to the physical connector you are using. Ensure
that the parallel port is not being intercepted by another program (e.g. a
network print spooler).

@PD500

Cannot open file xxxxxxxx: invalid directory or permission denied.

The specified file could not be opened. You may have entered an incorrect
file and/or pathname, the file may not exist, or you may not have write
privileges on the file. Try and locate the file under a different pathname.
This may be be a binary dump file that was specified with ECCARD DUMP /b
dumpfile. If the file does not exist and is part of the Eicon Technology
software package, consider reloading the file from the install program.

@PD501

Parameter entry error: invalid path specified.

The pathname you specified with the ECVER command was incorrect. Obtain the
correct syntax by retyping the command using the help parameter /?.

@PD502

Command not supported on a workstation. Type eccard -h for help.

The command can only be run on a machine acting as the gateway.

@PD503

Configuration error: EiconCard nn. Card not defined in configuration file.

Run eccard config.

You have not defined a configuration for the EiconCard you are trying to
load. Use the WAN Services Configuration program to define your
card.

@PD504

EiconCard nn: load has failed.

The EiconCard was unable to load the specified protocol software. This may be
because of a hardware problem with the EiconCard itself, or because of
corrupted files. Run ECTEST to verify the integrity of the EiconCard
hardware. If the problem persists, reload the software from the distribution
diskettes.

@PD505

Port nn. No protocol to activate or, if applicable, use a protocol-specific

start command to activate the port (e.g.: eccard start -p ...).

The line protocol configured for this port is not an activable protocol (X.25
or Frame Relay), or is a protocol which does not requre activation. (see
PD122).

@PD506

Port nn. No xxxxxxxx protocol could not be started. EtECs error nn. Verify
your protocol software configuration in eccard config.

The EtECs driver has possibly been corrupted. Retry the command. If you
still do not have any success, unload the EtECs driver and reload it again.

______
ECSNMP

@SN011

The MIBs must be defined in ascending order in the ECSNMP.INI file.

Refer to the [MIB] section of the ECSNMP.INI file. If you have changed the
order of the files, and cannot remember the correct sequence, you will have
to resave the EiconCard configuration file and make it current. This process
generates a new ECSNMP.INI file and places the MIB files in the correct
loading order.
@SN012

Internal error: Refer to the ECSNMP.LOG file for details.

This refers to a failure in the operation of the SNMP Agent. Refer to the
ECSNMP.LOG file for a more precise description of this error message.

@SN013

Error while reading ECSNMP.INI or *.DAT MIB file.

An invalid entry may have been made in the ECSNMP.INI file or one of the MIB
*.DAT files that the SNMP Agent was trying to instrument. Check your
configuration file and ensure that the correct references are used.

You may also be running low on the amount of free memory required to
successfully run the software. Unload any unnecessary programs from memory to
allow proper memory allocation for the SNMP sub-agent.

@SN101

Error on EcbiosOpen xxxxxxx.

The Eicon Technology SNMP Agent cannot register to the EiconCard driver
(ECBIOS). You will have to reset the PC and reload the software modules in
the order specified in the reference guide. If problems persist, contact
your Eicon Technology representative for assistance.

@SN201

ECSNMPD is not loaded.

You must load the Eicon Technology SNMP Sub-Agent (ECSNMPD) that provides the
interface to the IBM SNMP Agent.

@SN202

ECSNMPD is already loaded.

The Eicon Technology SNMP Sub-Agent has already been loaded. the load
command was ignored.

@SN203

Unable to connect with ECSNMPD.

Requests being issued to the Eicon Technology Sub-Agent are not being
executed. Try issuing the command without the /v option. If the problem still
persists, you will have to terminate the Eicon SNMP sub-agent with an OS/2
utility, or reboot your PC. Restart the SNMP Agent programs and try resending
your command.

@SN204

Unable to load ECSNMPD, return code = nn.

The Eicon Technology Sub-Agent failed to load due to one of the following
reasons:

- Insufficient memory on the PC.

Make sure that you have enough memory to load the ECSNMP sub-agent. If not,
you must unload any unnecessary TSRs from memory or unload any other Eicon
modules that are not in use.

- Too many files are open.

You have exceeded the number of files that can be concurrently open. Try
increasing the number of files in your CONFIG.SYS file.

- There is sharing violation on the file.

This file is already in use. Check to make sure that you do not already have
ECSNMPD open in another window.

- Access to this file was denied.

You do not have sufficient privileges to load this file. Check with your
administrator for security restrictions.

@SN205

ECSNMP is already in use in another window.

You are attempting to use the Eicon Technology Sub-Agent command while the
sub-agent is still being loaded. Check to see that you have no other windows
running ECSNMP.

@SN206

Internal error: xxxxx (), return code nn.

The error listed indicates critical failure of the Eicon Technology software.
Contact your Eicon Technology representative for assistance.

@SN207
Internal error: Number of characters sent to ECSNMPD is nn.

The Eicon SNMP sub-agent is not receiving complete command requests from the
command line. Try resending the command. If the problem still persists, you
will have to terminate the Eicon sub-agent with an OS/2 utility, or reboot
your PC. Restart the SNMP Agent programs and try resending your command.

@SN208

Internal error: Invalid command "xxxxxxx" received from ECSNMPD.

An invalid response was returned by the Eicon SNMP sub-agent. Resend the
command. If the problem still persists, you will have to terminate the Eicon
SNMP sub-agent with an OS/2 utility, or reboot your PC. Restart the SNMP
Agent programs and try resending your command.

@SN209

Unable to load ECSNMPD. The file xxxxxxxx was not found.

The DLL file xxxxxxxx could not be located. Make sure that it can be accessed
using the LIBPATH.

@SN212

Error while registering to the IBM SNMP Agent.

This refers to a failed attempt to connect to the IBM SNMP Agent. Re-issue
the ECSNMP START command. If problems still persist, contact your Eicon
Technology representative for assistance.

@SN213

The IBM SNMP Agent is not loaded or the community name is not valid.

The ECSNMP command could be executed as it could not detect the IBM SNMP
Agent. Make sure that you have activated the IBM SNMP Agent and configured it
according to the instructions presented in the Eicon Technology operator's
guide.

You should also check that the community name specified with the ECSNMP.INI
command matches that specified by the IBM SNMP Agent.

@SN214

Error while reading ECSNMP.INI, refer to the ECSNMP.LOG file for details.

This refers to a failure in the operation of the SNMP Agent. Refer to the
ECSNMP.LOG file for a more precise description of this error message.

@SN215

The Eicon SNMP sub-agent could not find any IP interface on the server.

ECSNMPD could not find any IP address for your server. Check to make sure
that TCP/IP support has been initialized and that the IP address has been
configured by the TCP/IP program. You should also make sure any batch files
that activate TCP/IP support (e.g. TCPSTART.CMD) have been executed.

@SN216

The Sub-Agent is not advertising, refer to the ECSNMP.LOG file for details.

This is an OS/2 error. An unspecified error has ocurred with the Eicon Sub-
Agent. You may be able to determine the cause of the error from the log
file.

@SN217

The Sub-Agent is not advertising, because ECSLP is not started.

This is an OS/2 error. The Eicon Sub-Agent did not start because it requires
ECSLP to be running first. Issue the ECSLP START command from the command-
line, and then continue.

@SN301

Invalid parameter. Use /v to enable verbose debug output.

An invalid parameter was specified with the LOAD ECNOVAPI command.

@SN302

Error while registering Eicon Technology MIB file with NetWare SNMP Agent.

This refers to a failed attempt to connect to the NetWare SNMP Agent. Make
sure that no other sub-agents are using the Eicon Technology MIBs.

@SN303

Error while initializing TSP Protocol #nn.

The LOAD ECNOVAPI command could not be executed completely as SPX/IPX or

TCP/IP support was not activated. Run the LOAD TSPSPX or LOAD TSPTCP command
to activate the support module for the protocol you require.
@SN401

Cannot open (xxxxxxx) registry. Return Code = (nn).

The above-mentioned entry in the registery could not be accessed. This error
indicates the Windows NT registery data may be corrupted. It it persists,
make note of the return code and contact Eicon Customer Services.

@SN402

Cannot get (xxxxxxx) from registry. Return Code = (nn).

The system could not read information from the above-mentioned entry in the
registery. This error indicates the Windows NT registery data may be
corrupted. It it persists, make note of the return code and contact Eicon
Customer Services.

@SN405

Cannot initialize TSP for (xxxxxxx). Return Code = (nn).

The above-mentioned module could not initialize the Eicon Transport Service
Provider. This may indicate a serious internal problem. if it persists, make
note of the return code, and contact Eicon Customer Support.

@SN406

TSP cannot register (xxxxxxx) service. Return Code = (nn).

The above-mentioned module could not be registered with the Eicon Transport
Service Provider. This may indicate a serious internal problem. if it
persists, make note of the return code, and contact Eicon Customer Support.

@SN407

TSP can't start (xxxxxxx) advertising. Return Code = (nn).

The above-mentioned module could not use the Eicon Transport Service Provider
to begin advertising. This may indicate a serious internal problem. if it
persists, make note of the return code, and contact Eicon Customer Support.

@SN408

Process (xxxxxxx) is already attached.

There appear to be two identical process names entered in the Windows NT

registery database. This condition should not happen. If this error occurs,
contact Eicon Customer Support.

@SN411

Cannot get computer name. Return Code = (nn).

Your computer's name appears to be missing from the Windows NT registery

database. This condition should not happen. If this error occurs, contact
your LAN administrator.

@SN412

Sub-Agent initialized successfully.

This is a simple status message.

@SN413

Initialization of (xxxxxxx) as failed. Return Code = (nn).

The above-mentioned sub-agent did not initialize, thereby cutting off access
to the Eiconcard. This error may indicate corrupted information in a .DAT
file. Check each file with a .DAT extention. Copy the files from the
installation disk.

@SN415

Eicon Sub-Agent (xxxxxxx) not loaded.

The above-mentioned sub-agent was not loaded. This is likely the secondary
result of another error.

________
XPADCNFG

@XR001

Unable to activate help.

The help file (XPADCNFG.HLP) may be missing. Check to see if the file is
missing. Try reinstalling or upgrading the software.

@XR002

Could not start (or restart) the ECXPAD Driver Service. Check the event log
with the Event Viewer.

The file ECNB.SYS could not be loaded, or another application is already

using an XPAD COM port.

@XR003

Unable to locate language file nnnnn. Extended Language Support will not be
enabled for the nnnnn language.

This is a diagnostic message. If it occurrs, check to see that the file

referred to by xxxxx is located in your %SYSTEMROOT% directory. If that is
not the problem, try reinstalling or upgrading the software.

@XR004

Too many messages in Extended Language file.

This is an internal error. The language file(s) may be corrupted. Try

reinstalling or upgrading the software. If you cannot solve the problem,
contact Eicon Customer Support.

@XR005

Extended Language: Format error.

This is an internal error. If is persists, try reinstalling or upgrading the

software. If you cannot solve the problem, contact Eicon Customer Support.

@XR006

Extended Language: Can't add key to registry.

This is an internal error. If is persists, try reinstalling or upgrading the

software. If you cannot solve the problem, contact Eicon Customer Support.

@XR007

Already Running.

This indicates that the program is already running. Switch to that copy of
the program.

@XR008

Could not update registry.

This is an internal error. If is persists, try reinstalling or upgrading the
software. If you cannot solve the problem, contact Eicon Customer Support.

@XR009

Badly formed X.25 Address.

X.25 addresses should contain only decimal digits. They may contain one comma
if you are using both Called and Calling Addresses. They may contain up to
fifteen digits (seventeen if TOA/NPI addressing is enabled).

@XR010

Badly formed X.25 User Data.

User data can be up to 128 bytes, in either hex digits or in ASCII

characters. Hex digits must be separated by commas, ASCII characters by
double-quotes. Example: "password",01,00,00,00.

@XR011

Badly formed X.25 Facilities.

Facilities can be up to 128 bytes (possibly less, depending on your network

configuration). Example: 43,2,2. Refer to your WAN Services manual for more
information.

@XR012

The X.3 field cannot contain non-numeric data.

X.3 parameters must contain decimal digits only up to a value of 255, and
they cannot be left blank.

@XR013

The X.3 Parameter cannot be greater than 255.

X.3 parameters must contain decimal digits only up to a value of 255, and
they cannot be left blank.

@XR014

The X.3 Parameter cannot be blank.

X.3 parameters must contain decimal digits only up to a value of 255, and
they cannot be left blank.
@XR016

Error(s) found in X.3 Field(s).

X.3 parameters must contain decimal digits only up to a value of 255, and
they cannot be left blank.

@XR017

Select at least one COM port.

You must select a COM port before trying to configure it.

@XR018

Add at least one X.PAD COM port.

You must have at least one COM port configured to use the XPAD driver
service.

@XR019

No space available to add new COM ports.

The maximum number of COM ports has already been defined (64). To add a new
port, you must remove another.

@XR020

You must specify an X.25 Address when Auto-Connect Type is set to CALL.

You must specify a calling address when placing a call.

@XR021

An X.25 Address is not required when Auto-Connect Type is set to PVC.

Since the connection is permenantly open, no calling number is needed.

@XR023

Unable to initialize (not enough memory available).

Out of RAM. Shut down any non-essential programs, and try again.
@XR024

Unable to initialize.

This is an internal error. If is persists, try reinstalling or upgrading the

software. If you cannot solve the problem, contact Eicon Customer Support.

@XR025

Unable to initialize ports.

This is an internal error. If is persists, try reinstalling or upgrading the

software. If you cannot solve the problem, contact Eicon Customer Support.

@XR026

Error in profile name.

This is an internal error. If is persists, try reinstalling or upgrading the

software. If you cannot solve the problem, contact Eicon Customer Support.

@XR027

Insufficient memory available to allocate internal storage needed for the

driver.

Out of RAM. Reduce the number of defined XPAD COM ports, or shut down any
unnecessary driver services.

@XR028

The driver will not load because the EiconCard driver ECNB.SYS is either not
installed or not loaded. Make sure the driver is installed properly, or enter
NET START ECNB if it is already installed.

This error may also ocurr if XPAD is installed before Wan Services. Make
sure you have followed the correct installation procedure, as described in
the manual.

@XR029

Errors found in X.3 Parameters - Verify X.3 settings and try again.

X.3 parameters must contain decimal digits only up to a value of 255, and
they cannot be left blank.
@XR030

Errors found in a Profile - Verify the profiles and try again.

This may be an internal error. Run the XPAD configuration program, and
examine your configuration. Try upgrading or re-installing the software.

@XR031

An Illegal Packet Size. Valid range is from 128 to 4096. Correct the Packet
Size and try again.

This may be an internal error. If is persists, try reinstalling or upgrading

the software. If you cannot solve the problem, contact Eicon Customer
Support.

@XR032

The registry key 'XpadParameters' was not found - the driver will unload. Use
the X.PAD configuration program to try again.

The registery may be corrupted, or the XPAD configuration program was not
able to save the key into the registry. Try restarting the system.

@XR033

Unable to create the symbolic link for xxxxx.

This is an internal error. Another driver may be using the same symbolic link
name. If is persists, try reinstalling or upgrading the software. If you
cannot solve the problem, contact Eicon Customer Support.

@XR034

Unable to create the device map entry for xxxxx.

This is an internal error. Another driver may be using the same device map
entry name. If is persists, try reinstalling or upgrading the software. If
you cannot solve the problem, contact Eicon Customer Support.

@XR035

No Pad Profiles are defined.

This is an internal error. If is persists, try reinstalling or upgrading the

software. If you cannot solve the problem, contact Eicon Customer Support.
@XR036

Internal Error #nn occured while initializing xxxxx. The X.PAD driver will
not load. Please contact Eicon Customer Support.

This is a serious internal error. If is persists, try reinstalling or

upgrading the software. If you cannot solve the problem, contact Eicon
Customer Support.

@XR037

Remote DTE cleared the X.25 call on xxxxx.

This is a simple status message.

@XR038

Remote DTE cleared the X.25 call on xxxxx, yyyyy X.25 Return Codes: nn.

This is a simple status message.

@XR039

Network cleared the X.25 call on xxxxx, xxxxx X.25 Return Codes: nn.

This is a simple status message.

@XR041

Not enough room for the Eicon X.PAD Service on drive nnnnn. nn megs needed.

Free some hard drive space.

@XR042

No X.PAD COM Ports are defined. The X.PAD driver will not load. Please add
at least 1 X.PAD COM port in order for the driver to load. Press OK to
re-run X.PAD configuration or CANCEL to skip configuration.

You must have at least one XPAD COM port defined for the ECXPAD driver to
start.

@XR043
You must install the WAN Services for Windows NT Core software before you
can install the Eicon X.PAD Driver.