+-------------------------------------------------------------+
| EP100TX driver for Novell ODI DOS Client |
| V2.13 |
+-------------------------------------------------------------+
1. Overview:
This Readme file explains how to install the Novell NetWare
DOS ODI Client driver.
This driver is currently supported for the SURECOM EtherPerfect
100TX adapter.
2. Preinstallation Hardware and Software Requirements:
A. Hardware Requirements:
o An IBM-compatible personal computer with 80386 or higher
microprocessor and PCI bus.
o A EP100TX Ethernet adapter.
B. Firmware Requirements:
o Fully compliant Rev. 2.0 or above PCI BIOS supplied with the PC.
C. Software Revision Requirements:
o MS-DOS version 3.0 or above.
o Novell LSL.COM version 2.11 or above.
o Novell IPXODI.COM version 2.20 or above.
o Novell NETX.COM version 1.11 or above.
or
o Novell VLM.EXE version 1.11 or above.
For getting the most updated revisions of Novell's files, please
contact Novell at:
Novell, Inc.
Novell Labs Administration
MS E-13-1
122 East 1700 South
Provo, UT 84606
Tel: 801-429-7000
Fax: 801-429-5224
3. Supplied Files:
Table 1: The Novell NetWare ODI Client Directory Files
---------------------------------------------------------------------
README.TXT This File
---------------------------------------------------
RELEASE.TXT Provides a description of updates to the new driver.
---------------------------------------------------
EP100TX.COM EP100TX Novell NetWare ODI Client driver.
---------------------------------------------------
NET.CFG Novell network configuration file for this driver
---------------------------------------------------------------------
4. Installing Software:
To install the Novell NetWare ODI Client Device Driver:
EP100TX.COM is the Novell NetWare ODI client driver for the EP100TX
This Readme file explains how to install the Novell NetWare DOS
ODI Client driver.
1. Copy the following files to a user specified directory:
copy a:\NOVELL\WKSTN\*.*
2. Copy the following files provided by Novell to a user
specified directory:
LSL.COM
IPXODI.COM
NETX.COM or VLM.EXE
3. Edit the NET.CFG file if necessary to select protocol and
media type options.
NOTICE:
o NO NEED TO SPECIFY SLOT NUMBER, BUS ID OR INTERRUPT NUMBER!
o If you specify Bus ID please notice that for PCI bus you
write
BUS ID PCI 4
in NET.CFG
o If you specify Slot Number please notice that SLOT 1 means
in PCI : The first board found in system.
4. To connect to a server, use the following loading sequence:
LSL
EP100TX
IPXODI
NETX or VLM
LOGIN
5. Parameters
The following parameters can be used in order to control part of
the driver's operation.
These parameters are added to the driver's entry in NET.CFG
For NetWare standard parameters, please refer to NetWare user's
manual.
AUTOSENSE enables autosensing of media type when driver
is loading (Also called Power-Up Autosense) on all
types of supported cards
and run-time autosensing of media type on cards
based on DC21140 chip designed for supporting
Run-time Autosensing.
TP_NO_LINK_TEST selects twisted pair connection, but disables
the LINK test for specific HUBs that do not
support LINK.
TP_FULL_DUPLEX selects twisted pair connection to work in
full duplex mode.
TURBO Fixes a problem of multiple transmit
underflow and receive overflow (i.e.
loss of packets) in systems that use
certain PCI chipsets.
LINE_SPEED selects line speed between 10MPBs and
100MBPs on network cards based on DC21140.
Format: LINE_SPEED <value>
Allowed values are: 10,100
GENERAL_PURPOSE_CONTROL the user can override the control value
in the GENERAL_PURPOSE register on
network cards based on DC21140. Normally,
this value should not be changed.
Format: GENERAL_PURPOSE_CONTROL <Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
GENERAL_PURPOSE_DATA the user can override the data value
in the GENERAL_PURPOSE register on
network cards based on DC21140. Normally,
this value should not be changed.
Format: GENERAL_PURPOSE_DATA <Hexadecimal Value>
Allowed values: in the range FF-0 hex.
RX_BUFFERS Allows the user to select the number of
receive buffers which are allocated.
A larger number of buffers results in a
larger driver resident in memory and
can result in better driver performance.
Format: RX_BUFFERS <Hexadecimal Value>
Allowed values: in the range 2-10 hex.
Default values: 16 (10hex) for DC21140 based cards.
6. Driver Error messages:
- FATAL: Failed to lock system memory
Driver call to OS memory support routines for locking its
internal buffers and descriptors failed.
- FATAL: DC21X4 driver works only with 386 or above!
The driver failed to identify the CPU as a 386 or above the
driver can run on 386 (or above) machines only.
- FATAL: Slot value error!
The user has specified an illegal slot number in NET.CFG
50 - FATAL: Board not found in system
Driver could not detect a supported NIC in the system.
53 - FATAL: Board is disabled for no apparent reason!
EISA board is not enabled. Normally BIOS & ECU should enable
the board.
200 - FATAL: Timeout when initializing DC21X4 with setup packet!
This happens mainly when the PCI slot does not support DMA.
Make sure the BIOS setup or motherboard switches are set to
enable DMA or Bus Master operation of this slot.
210 - FATAL: DC21X4 Does not support this bus type
The machine is not identified as a PCI machine or the user has
specified BUS ID which is not PCI.
217 - FATAL: Failed to find PCI BIOS
The machine is not identified as a PCI machine (to support PCI
NICs). This error is generated when the driver is directed to
load a PCI NIC using the BUS ID keyword (in DC21X4.COM v2.0 and
above) and PCI 4 is specified, or SLOT keyword (in DC21X4 V1.02
and below), and slot value is a PCI slot number (16 and above).
218 - FATAL: Bad PCI BIOS status
PCI BIOS returned a fail status in one of the calls. Please
check the BIOS version and BIOS correctness using an external
utility.
219 - FATAL: Bad PCI BIOS Register err
PCI BIOS returned a fail status in one of the calls. Please
check the BIOS version and BIOS correctness using an external
utility.
220 - FATAL: PCI BIOS failed to initialize DECchip 21x40 CBIO reg!
PCI BIOS has initialized a DWORD register in the NIC's
configuration space (at offset 10Hex) with illegal value (in x86
machines this value is between 0 to FFFFHex). Please check the
BIOS using an external utility. Also verify that your BIOS setup
enables the slot the NIC is plugged in, allocates I/O addresses
to it and initializes correctly the device in this PCI slot.
222 - WARNING: KWD RXD No param
The user added the RX_BUFFERS key word in NET.CFG but did not
specify the number of buffers required.
Add the number of buffers to the KWD (such as: RX_BUFFERS 9)
222 - WARNING: KWD RXD Param too small
The number of Rx buffers specified by the user is too small
for proper driver's work.
Please increase the amount of Rx buffers in RX_BUFFERS KWD in
NET.CFG
The minimum number of rx buffers is 2.
222 - WARNING: KWD RXD Param too big
The user had specified more rx buffers than the driver can handle
Please decrease the amount of Rx buffers in RX_BUFFERS KWD in
NET.CFG
The maximum number of rx buffers is 16 but it may be less depending
on the driver's size.
225 - FATAL: PCI BIOS allocated an illegal Interrupt to DECchip 21x40!
PCI BIOS has initialized a byte register in the NIC's
configuration space (at offset 3CHex) with illegal value (in x86
machines legal values are between 1 to 15). Please check the
BIOS using an external utility. Also verify that your BIOS setup
enables the slot the NIC is located in, enables interrupts to
this slot and assigns a legal interrupt number to it.
226 - WARNING: Failed to handle Turbo switch
Failed to operate the 'Turbo' mechanism from one of the
following reasons:
- The chipset on the motherboard does not support TURBO mode.
- PCI BIOS returned a fail status in one of the calls involved
with operating this mechanism.
227 - FATAL: Internal CRC table corrupted
Driver found an error in internal CRC table either because the
driver file is corrupted or someone has changed the table's
contents.
228 - FATAL: Could not handle chipset bug workaround successfully
Failed to operate chipset bug workaround because PCI BIOS
returned a fail status in one of the calls involved with
operating this mechanism.
229 - WARNING: This machine Host to PCI bridge has a known bug.
Driver limits DC21X4 bursts as a workaround.
230 - FATAL: This machine Host to PCI bridge has a known bug when
using cache in WB mode which may cause data corruption
or system hang. Please change the cache mode to WT
(Write Through) as a workaround.
240 - FATAL: Unable to locate Adapter ROM!
Driver failed either to locate the address ROM or read it. This
might happen due to bad data stored in the serial ROM.
240 - FATAL: Failed to read ROM!
Driver failed to read the serial flash ROM due to a hardware
failure. Make sure the IEEE flash ROM on your NIC is operational
using external utility.
240 - FATAL: Unsupported ROM Version
The version (and hence the format) of the data read from the
SROM is not supported by the driver. Please run an external
utility to upgrade the Serial ROM's data.
241 - FATAL: Unsupported media selection
The NIC or device do not support the requested media selection.
Please check the available media types on the NIC and use one of
them.
242 - FATAL: Unsupported Line Speed
The device does not support the requested line speed. This
happens when line speed of 100MBps is specified while using an
Ethernet device. Please remove the Line_Speed key-word or
change its value to 10.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.