ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ PLANET ENW-9501 Plus ³
³ Installation for NetWare Server ODI ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
A. Software Revision Requirements:
o NetWare version 3.11 or above.
o Novell support modules as supplied in kit directories.
B. Supplied Files:
Table 1: The Novell NetWare ODI Server Directory Files
---------------------------------------------------------------------
DC21X4.LAN DC21X4 Novell NetWare ODI server driver.
---------------------------------------------------
DC21X4.LDI Novell network installation file for this driver
---------------------------------------------------
DC21X4.INF Novell network Windows 95 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
---------------------------------------------------
NBI.NLM Novell NBI needed to run the ODI server driver
---------------------------------------------------
MSM31X.NLM Novell MSM needed to run the ODI server driver with
NetWare v3.1x
---------------------------------------------------
NBI31X.NLM Novell NBI needed to run the ODI server driver with
NetWare v3.12
---------------------------------------------------
PATCHMAN.NLM Novell module needed in NetWare v3.11 in addition
to MSM31X.NLM
---------------------------------------------------
A3112.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
---------------------------------------------------
MONITOR.NLM NetWare server MONITOR module for NetWare v3.11
---------------------------------------------------
LSWAP.EXE For Netware 3.12 you must copy the LOADER.EXE and
LOADER.EXE LSWAP.EXE to the NWSERVER directory and run the
LSWAP.EXE to update the loader segment in the
server.exe file. This is required by Novell in order
for the NBI31X/MSM31X to function correctly.
--------------------------------------------------------------------
C. Installing Software:
1. NetWare v3.1x installation: (use respective directory \NWSERVER\311
or \NWSERVER\312)
1.1 Copy The DC21X4.LAN to the SYS:\SYSTEM directory on the NetWare
server.
1.2 Add to your AUTOEXEC.NCF the line required to load the
DC21X4.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).
1.3 For Netware 3.12 ONLY you must copy the LOADER.EXE and LSWAP.EXE
to the NWSERVER directory and run the LSWAP.EXE to update the
loader segment in the server.exe file. This is required by Novell
in order for the NBI31X/MSM31X to function correctly.
2. NetWare v4.x installation:
2.1 Have ready a diskette with DC21X4.LAN and DC21X4.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 DC21X4.LAN according to the NetWare
manual, or use the on-line instructions and help.
NOTE: The slot numbers in Netware 3.11 are different from the
ones in Netware 3.12 and 4.x. This is due to the fact that
the 3.12 and 4.x driver (one and the same) use the NBI layer
from Novell, and the 3.11 driver does not. Novell DO NOT and
will NOT supply an NBI layer for 3.11.
D. 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
------------------------------------------------------------------
NOTE that wrong values (such as 'line_speed=128') are IGNORED, and
a default value is taken instead.
------------------------------------------------------------------
Driver specific parameters list (as for NetWare standard parameters,
please see the NetWare user's manual):
AUI selects AUI port.
TP selects TP port.
BNC selects BNC port.
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.
LINE_SPEED selects line speed between 10MPBs and 100MBPs.
Format: LINE_SPEED=<value>
Allowed values are: 10,100
GENERAL_PURPOSE_CONTROL
user override of the control value in the
GENERAL_PURPOSE register.
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.
T4 run in T4 100Mbps mode
NT run under NT requester
OS2 run in NetWare for OS/2
Unixware run in UnixWare
Client32Win run in Client32 environment for windows
Client32Win95 run in Client32 environment for Windows95
Client32DOS run in Client32 environment for DOS
E. 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 PCI board found in machine!
Driver could not detect a supported NIC.
53 - Board is disabled for no apparent reason!
Board is not enabled. Normally BIOS & ECU should enable the board.
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.
209 - Do not support DC21041 in DC21040 mode
The DC21041 MODE_SELECT pin is connected to VSS making it work
in MODE_0, i.e. as a virtual DC21040 in all respects. The driver
does NOT support this mode.
210 - Driver failed to locate PCI bus!
The machine is not identified as PCI (to support PCI NICs).
211 - Failed to locate DecChip 21X4 on board
Failed to identify a DecChip 21x4 signature in an PCI board.
212 - Unsupported DC21140 chip version
The DC21X4 drivers do not support DC21140 rev 1.0 chip.
If you receive this message, please make sure you have an updated
rev of your NIC.
213 - Unexpected OS behavior. Driver supports 3.11 and later
This identifies a fail of assumption regarding the OS behavior.
214 - Read bad mask value from EISA configuration
An assumption regarding data read from EISA ECU (for EISA based
NICs) failed. This might happen because of incorrect ECU file for
that NIC.
215 - Read bad port size value from EISA configuration
An assumption regarding data read from EISA ECU (for EISA based
NICs) failed. This might happen because of incorrect ECU file for
that NIC.
216 - Failed to read EISA configuration
An assumption regarding data read from EISA ECU (for EISA based
NICs) failed. This might happen because of incorrect ECU file for
that NIC.
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 PCI support, and in this case will generate another
error message (please refer to error number 210 - Driver failed
to locate 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.
220 - PCI BIOS failed to initialize DecChip 21040 CBIO reg!
PCI BIOS has initialized a DWORD register in the NIC's
configuration space (at offset 10Hex) with illegal value. Please
check the BIOS version and BIOS correctness using an external
utility. Also verify that your BIOS setup enables I/O and
initialize correctly the device in this PCI slot.
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.
225 - PCI BIOS assigned DecChip 21040 an illegal interrupt number
PCI BIOS has initialized a byte register in the NIC's
configuration space (at offset 3CHex) with illegal value. Please
check the BIOS version and BIOS correctness using an external
utility. Also verify that your BIOS setup enables interrupt,
assigns a reasonable interrupt value and initialize correctly
the device in this PCI slot.
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.
246 - Cannot initalize the network card (CreateNIC failed)
Cannot initalize the network card (CreateNIC failed)
The CreateNIC routine failed, and we cannot initalize the nic
247 - NOT USED.
248 - This machine PCI chipset has a problem that might cause
excessive transmit underflows. Driver works around this, but
performance may be affected.
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.