+-------------------------------------------------------------+
| EP100TX driver for Novell ODI Server |
| V1.13 |
+-------------------------------------------------------------+
1. Overview:
This Readme file explains how to install the Novell NetWare
Odi server driver. This driver is currently supported for the
SURECOM EtherPerfect 100TX Board.
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 NetWare version 3.11 or above.
o Novell MSM.NLM version 2.22 or above.
o Novell ETHERTSM.NLM version 2.22 or above.
3. Supplied Files:
Table 1: The Novell NetWare ODI Server Directory Files
---------------------------------------------------------------------
README.TXT This File
---------------------------------------------------
RELEASE.TXT Provides a description of updates to the new driver.
---------------------------------------------------
EP100TX.LAN EP100TX Novell NetWare ODI server driver.
---------------------------------------------------
EP100TX.LDI Novell network installation file for this driver
---------------------------------------------------
ETHERTSM.NLM Novell TSM needed to run the ODI server driver
---------------------------------------------------
MSM.NLM Novell MSM needed to run the ODI server driver
---------------------------------------------------
MSM31X.NLM Novell MSM needed to run the ODI server driver with
NetWare v3.11
---------------------------------------------------
PATCHMAN.NLM Novell module needed in NetWare v3.11 in addition
to MSM31X.NLM
---------------------------------------------------
LSLENH.NLM Novell module needed in NetWare v3.11 in addition
to MSM31X.NLM
---------------------------------------------------
AUTOEXEC.NCF Sample AUTOEXEC.NCF files for NetWare 3.1X and 4.X
---------------------------------------------------
MONITOR.NLM NetWare server MONITOR module for NetWare v3.11
---------------------------------------------------------------------
4. Installing Software:
To install the Novell NetWare ODI Server Device Driver:
EP100TX.LAN is the Novell NetWare ODI server driver for
EP100TX Ethernet adapter.
1. NetWare v3.1x installation:
1.1 Copy The EP100TX.LAN to the SYS:\SYSTEM directory on
the NetWare server.
1.2 Add to your AUTOEXEC.NCF the line required to load
the EP100TX.LAN and bind it. Refer to the sample
AUTOEXEC.NCF for more information (according to the
type of NetWare you are using, i.e. v3.1x or 4.x).
2. NetWare v4.x installation:
2.1 Have ready a diskette with EP100TX.LAN and EP100TX.LDI
both from the driver's kit.
2.2 On the server's prompt type: LOAD INSTALL
2.3 When the install program comes up, choose the menu
item that refers to NETWORK DRIVERS.
Note that this menu item is on different place on
different NetWare versions (i.e. v4.0x vs. 4.1x).
2.4 Install the network driver EP100TX.LAN according to
the NetWare manual, or use the on-line instructions
and help.
5. Parameters
The following parameters belong on the server's command line, or in
the load line inside the AUTOEXEC.NCF. The general way of using these
parameters is:
LOAD <driver name> <PARAMETER NAME>... <PARAMETER NAME[=VALUE]>
Example:
LOAD <driver name> TURBO SLOT=16 FRAME=Ethernet_802.2
Driver specific parameters list (as for NetWare standard parameters,
please see the NetWare user's manual):
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 the problem of multiple transmit
underflows and receive overflows (i.e. lose of
packets) in systems that use certain PCI
chipsets.
BIOS16 instructs the driver to access the PCI BIOS
using 16-bit real mode calls, instead of the
PCI32 mechanism.
This is not recommended, and should be used
ONLY! on motherboards that have a known problem
in the PCI BIOS implementation.
LINE_SPEED selects line speed between 10MPBs and 100MBPs
on network cards.
Format: LINE_SPEED=<value>
Allowed values are: 10,100
GENERAL_PURPOSE_CONTROL user override of the control value in
the GENERAL_PURPOSE register in EP100TX
network cards.
Normally, this value should not be
changed.
Format: GENERAL_PURPOSE_CONTROL=<Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
GENERAL_PURPOSE_DATA user override of the data value in the
GENERAL_PURPOSE register.
Normally, this value should not be
changed.
Format: GENERAL_PURPOSE_DATA=<Hexadecimal Value>
Allowed values: in the range 1FF-0 hex.
SBASE User specified slot base number, i.e. if the user
would like the first PCI slot that has a EP100TX device
to be numbered 37 decimal they should write 'SBASE=37'.
This way the first EP100TX device would have a slot number
of 37 and the other device would be numbered in increments
of 1. A value under 16 would be treated as if the user wrote
SBASE=16.
Format: SBASE=<decimal value>
Allowed values: 16-65535 decimal.
6. Driver Error messages:
Some messages also have a numerical code printed with them. The codes are
given here to the left of the message (when applicable).
50 - No EISA or PCI board found in machine!
Driver could not detect a supported NIC.
73 - Unable to allocate memory
Driver failed to allocate needed memory from the OS (receive/transmit
descriptors or needed transmit buffers).
200 - Timeout when initializing DecChip 21X4 with setup packet!
This happens mainly when the PCI slot does not support DMA accordingly.
Make sure the BIOS setup or motherboard switches are set to enable DMA or
Bus Master operation of this slot.
210 - Driver failed to locate either EISA or PCI bus!
The machine is not identified as EISA (to support EISA based NICs) and
not as PCI (to support PCI NICs).
213 - Unexpected OS behavior. Driver supports 3.11 and later
This identifies a fail of assumption regarding the OS behavior.
217 - Failed to find PCI BIOS
The machine is not identified as PCI (to support PCI NICs). This error is
generated when driver is directed to load PCI NIC (using the 'slot=xx'
keyword, and slot value is a PCI number). If the driver is loaded without
specifying slot number, the driver checks for EISA and PCI support, and
in this case will generate another error message (please refer to error
number 210 - Driver failed to locate either EISA or PCI bus).
218 - 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 - 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.
221 - PCI board disappeared...
PCI BIOS is not consistent with returned values per this NIC.
222 - Unsupported TSM version (need x.yz and above)!
This driver supports EtherTSM.NLM of version as specified and higher.
223 - DC21X4 Tx babbles on slot x. Driver halted this slot's NIC.
This is a watchdog put in the driver to make sure the transmit does not
babble on the cable.
224 - DC21X4 detected PCI bus error on slot x (bus error bits = xh).
Driver halted this slot NIC due to that identified error.
226 - Could not handle Turbo switch successfully
Failed to operate the 'Turbo' mechanism from one of the following
reasons: - Unknown chipset on the motherboard
- PCI BIOS returned a fail status in one of the calls involved
with operating this mechanism.
227 - Internal CRC table corrupted
Driver found an error in internal CRC table.
228 - 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 - This machine Host to PCI bridge has a known bug. Driver limits DC21X4
bursts as a workaround.
230 - 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
This machine Host to PCI bridge has a known bug that might violate system
integrity. Driver cannot be responsible for outcome, therefor it will
not load in this case. Putting the machine in write-through mode (cache)
makes the system safe to work with. Driver will load in that case.
240 - Unable to locate or read the Ethernet ROM address on board!
This might happen due to bad data stored in the IEEE serial ROM, an error
when reading it, or a wrong data structure burnt into the ROM.
244 - Serial ROM - Read failed
Driver failed to read the IEEE serial flash ROM due to hardware handshake
failure. Make sure the IEEE flash ROM on your NIC is operational using
external utility.
245 - The selected media is unsupported
The selected media is unsupported by the device.
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.