ThunderLAN(tm) - Novell Netware Server ODI Driver
Installation and usage instructions
CONTENTS
========
Introduction .................. Provides a brief description of the
driver and associated files.
Driver Keywords ............... Describes the ThunderLAN specific driver
keywords.
How To Setup Netware Servers .. Step-by-step instruction on how to
install the ThunderLAN driver.
Release Notes ................. Provides information on driver revision
history and any known driver problems.
INTRODUCTION
============
The ThunderLAN Novell NetWare Server ODI Driver conforms to
Novell's NetWare Server Driver HSM specification, version 3.2. This
driver can be used with NetWare 3.11, 3.12, and 4.x server software.
This text file describes how to install and use the ThunderLAN Novell
NetWare Server ODI Driver.
The driver files are contained on the ThunderLAN Driver Diskette in the
following subdirectories:
Directory / Files Contents
------------------------- ---------------------------------------------
netware\
server\ Supports NetWare 3.11, 3.12 or 4.0 server
3_11\ Support files for Netware 3.11
3_12\ Support files for Netware 3.12
4_x\ Support files for Netware 4.x
readme.txt This file
tlan32x.lan ThunderLAN Server ODI Driver
tlan32x.ldi Installation script file
DRIVER KEYWORDS
===============
Several operational parameters of the ThunderLAN driver can be specified
at driver initialization time through the use of driver keywords. This
section describes the ThunderLAN driver specific keywords.
These keywords can be specified on the command line when loading the
ThunderLAN Netware Server ODI driver using the LOAD command.
Alternatively, they may also be specified in a Driver Configuration File.
Keywords are not case-sensitive; they may be specified in either
lower-case, upper-case, or a combination. Consult your Novell
documentation for more information.
Network
-------
The Network keyword takes a parameter that describes the link
capabilities of the network ThunderLAN will be using. The
parameters are:
AUTO
Signifies autonegotiation of network speed and duplex
capabilities (if the Network keyword is not specified,
this is the default mode of operation)
100
100 Mbps link speed, half duplex
10
10 Mbps link speed, half duplex
100FULLDUPLEX
100 Mbps link speed, full duplex
10FULLDUPLEX
10 Mbps link speed, full duplex
NoAutoDetect
------------
The default operation of the driver is to automatically detect the
PHY to use by testing for a valid link. Specifying the NoAutoDetect
keyword disables this feature, and causes the driver to select the
first PHY device encountered, regardless of link status. This is
used to support peer-peer links, or other load driver with no cable
situations. The following is brief outline of the PHY detection
scheme:
1. If a bit-level PHY is detected (i.e. Level-One), it is used.
2. If the NoMgtMiiPhy keyword is specified in "net.cfg" (see below
for a description), then an MII compliant PHY device which does
not provide a management MII interface is used.
3. All MII PHY ID's are scanned. If an MII PHY is found, and the
NoAutoDetect keyword is not specified in "net.cfg", then the
driver checks for a valid link on this PHY. If a valid link is
found, then this PHY is used. Otherwise, the next PHY is checked.
If the NoAutoDetect keyword is specified, then no link checking is
done and this PHY is used.
IMAX <value>
------------
The IMAX keyword specifies the maximum interrupts per second that the
driver will issue to the Server. Valid values for <value> are between
1000 and 32000 inclusive. If IMAX is not specified, the default value
of 32000 is used.
TBURST <burst size>
-------------------
The TBURST keyword specifies the maximum number of bytes to be
transferred in any one transmit DMA data burst. Valid values for
<burst size> are 16, 32, 64, 128, 256, and 512. If TBURST is not
specified, the default value of 64 bytes is used.
HOW TO SETUP NETWARE SERVERS
============================
1. Load INSTALL.NLM from the netware server.
2. Select LAN DRIVER OPTION (CONFIGURE, LOAD, UNLOAD).
3. Select from the listed LAN Drivers,
or
type <INSERT> to add an unlisted driver from diskette. Press <F3> to
specify a different path,
For the TLAN Driver Diskette, Netware Server Driver, specify:
A:\netware\server
4. At the Driver TLAN32x PARAMETER SCREEN, press <F10> to accept all
default values.
5. Binding IPX to LAN Driver
Netware will sense if the cable segment attached already has an
address. If so, Netware will sense the address and bind IPX to
that address. If no address is sensed, Netware will generate
a network address or allow you to enter your own.
6. Once a network address is specified for each frame type, the driver
installation is complete. An autoexec.ncf file must then be created
to reflect these changes after bootup.
The autoexec.ncf is created using the INSTALL.NLM option CREATE/EDIT
AUTOEXEC.NCF. The autoexec.ncf should look like the following:
file server name Houlan401
ipx internal net 3017AD7E
load TLAN32X Slot=14 Frame=ethernet_802.3 Name=TLAN32X_1E_802.3
bind IPX to TLAN32X_1E_802.3 net=000129fd
load TLAN32X Slot=14 Frame=ethernet_802.2 Name=TLAN32X_1E_802.2
bind IPX to TLAN32X_1E_802.2 net=00012bfd
load TLAN32X Slot=14 Frame=ethernet_802.snap Name=TLAN32X_1E_802.snap
bind IPX to TLAN32X_1E_802.snap net=00012afd
load TLAN32X Slot=14 Frame=ethernet_802.ii Name=TLAN32X_1E_802.ii
bind IPX to TLAN32X_1E_802.ii net=000128fd
Refer to the appropriate Netware manual for more information.
RELEASE NOTES
=============
This section describes the revision history and known problems/issues
with the driver.
Issue / problem Resolution / status
---------------------------------------------- ----------------------
Revision history
---------------------------------------------------------------------
Rev 1.03 - 04Nov96
a) Removed int 3 on unconfigured devices.
Rev 1.02 - 28May96
a) Resolved "Outdated API call" msg on driver load by replacing direct
call to cReschelulelast with MSM function MSMYieldWithDelay.
b) Removed all debug statements
Rev 1.00 - 14Dec95 [Production Release]
a) Add Carrier Sense fix to reset FIFO pointers after CarrierLoss errors.
If the cable was unplugged repeatedly, during high traffic, a
slow-down was observed. Version 1.00 fixes this issue.
Rev 0.10 - 03Nov95 [Production Release Candidate]
a) The SPEED and FULLDUPLEX keywords have been merged into the NETWORK
keyword. NETWORK can be set to AUTO, 10, 100, 10FULLDUPLEX,
100FULLDUPLEX.
Rev 0.08 - 12Oct95
a) Novell DDK 3.02 TestCon driver certification fixes:
- Fixed DriverReset for AdapterResetCount statistics.
- Correct DriverModeFlag to eliminate obsolete bits.
- Correct MLDIFlags to eliminate obsolete bits.
- Cleanup Rx Active Queue during DriverReset.
- Eliminate interrupts required in DriverReset, to fix driver load and
unload test.
b) Enhanced 100VG-AnyLAN Training under high CPU utilization.
c) Fix Open Errors and No Interrupt messages.
Rev 0.07 - 05Sep95
a) Add fix for National Link Disconnect (National ECN P019.C)
Rev 0.06 - 28Aug95
a) Add support for the internal Phy.
b) Add Phy auto-detection algorithm.
c) Add support for Slow Mii devices (Broadcom & Others),
d) Add NoAutoDetect keyword to disable link detection.
e) Add Internal Phy AUI support.
f) Add Aui and ThinNet keywords for bit level/Internal Phys.
g) Add NoMgtMiiPhy keyword for Phys with no MII I/F.
h) Fix Single board detection, to not require Slot keyword.
i) Fix No ThunderLAN found error message.
j) Add Message for no Valid link detected during autodetection when no
usable Phys are detected.
k) Set LineSpeed for 10Mbit only Phys.
l) Add Support for PG 2.1 Internal Phy.
m) Disable Phys AutoNegotiate to Full Duplex, must use FULLDUPLEX keyword.
Rev 0.05
a) Improve performance of support routines.
b) Improve VG recovery during high errors.
Rev 0.04
a) Added support for ThunderLAN internal 10BaseT PHY
b) Fix training to support training on very heavily loaded VG Hubs, these
Hubs were causing erronious training frame timeouts causing training to
retry continously until a traffic load reduced momentarily.
Rev 0.03
a) Added IMAX and TBURST keywords for performance tuning
b) Added FULLDUPLEX keyword and associated support
c) Fixed Interrupt sharing for multiple boards. The PCI interface likes
similar devices to share interrupts.
--- End of readme.txt ---
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.