ThunderLAN(tm) - Novell NetWare DOS ODI Client 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. Before Installing the Driver .. Things to do before installing the driver. How To Setup Netware Clients .. 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 DOS ODI Client Driver conforms to Novell's 16 Bit DOS Client HSM specification, version 4.0. It enables MS-DOS and Windows 3.x based workstations to connect to NetWare 3.11, 3.12, and 4.x servers. This text file describes how to install and use the ThunderLAN(tm) driver for Novell NetWare DOS ODI Client systems. The driver files are provided on the ThunderLAN Driver Diskette in the following subdirectories: Directory / Files Contents ------------------------- --------------------------------------------- netware\ dosodi\ Supports NetWare Workstations 3.11, 3.12, 4.x supfiles\ Netware support files net.cfg Network configuration file readme.txt This file tlanodi.com ThunderLAN ODI DOS Client Driver tlanodi.ins 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 are added into the TLANODI driver section of the NET.CFG file. Keywords are not case-sensitive; they may be specified in either lower-case, upper-case, or a combination. 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. 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. BEFORE INSTALLING THE DRIVER ============================ Before installing the driver, make sure to check the following items: 1. If you are loading "emm386.exe" in your "config.sys" file, make sure it is version 4.48 or later. This version is shipped with MS-DOS v6.20. If an earlier version of emm386 is used, your computer will hang when loading the ThunderLAN driver. HOW TO SETUP NETWARE CLIENTS ============================ The following instructions describe how to manually install the ThunderLAN NetWare DOS ODI Client Driver. Depending on the version of NetWare you are using, an automated installation program may be provided. Check your Novell NetWare documentation's installation instructions for more details. 1. Create a directory on your hard drive (i.e. "c:\tlan"). 2. Copy all of the files from the directory "a:\netware\dosodi" on the ThunderLAN(tm) Driver Disk to "c:\tlan". 3. Copy the following files from the Novell NetWare package to "c:\tlan": - lsl.com - ipxodi.com - vlm.exe - required *.vlm files If you encounter problems using the support files from your copy of Novell Netware, you may copy the support files from the \netware\dosodi\supfiles directory. 3. Modify the NET.CFG file as required to reflect your network environment. To load NetWare and the ThunderLAN driver, type the following from the directory created in step #1 above: lsl tlanodi ipxodi vlm f: Switch to network drive letter (may vary) login {username} RELEASE NOTES ============= This section describes the revision history and known problems/issues with the driver. Issue / problem Resolution / status ---------------------------------------------- ---------------------- Revision history --------------------------------------------------------------------- Rev 1.03 - 14May96 a) Fixed Statistics Version number error due to Rxlist overrun Rev 1.02 - 05Mar96 [Production Release Update 02] a) Added ability to load driver into DOS high memory. Rev 1.01 - 12Dec95 [Production Release Update 01] 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.01 fixes this issue. Rev 1.00 - 26Oct95 [Production Release] a) Removed MaxFrameSize and MAX FRAME SIZE keyword support (they are ignored by MSM) b) The SPEED and FULLDUPLEX keywords have been merged into the NETWORK keyword. NETWORK can be set to AUTO, 10, 100, 10FULLDUPLEX, 100FULLDUPLEX. Rev 0.24 - 24Oct95 a) Add MAX FRAME SIZE Keyword=MAXFRAMESIZE. Rev 0.23 - 23Oct95 a) Add SPEED keyword, and fix GetPhyType to report correct speed for an NWAY compliant Phy, or National 10/100 or BroadCom Phys. Rev 0.22 - 10Oct95 a) Fixes for MII Phy powerup routines. To support Crystal based Phys. Split MiiSync into MiiSync and MiiIsolate for Phy powerup. Add new Phy PowerUp algorithm to InitNIC and GetPhyType. Rev 0.21 - 04Oct95 a) Fix PCI int=0FFh, HPs' no PCI int value is 0FFh, not zero. Rev 0.20 - 26Sep95 a) Upgrade MSM/Ethernet files for Novell DDK v3.02 Rev 0.12 - 05Sep95 a) Add fix for National Link Disconnect (National ECN P019.C) Rev 0.11 - 24Aug95 a) Add support for Phys with slow SDELs like BROADCOM 100T4 Phy, and MII bit 1.6 FAST SDEL indication bit. b) Disable Phys Autonegotiation to Full duplex, must use keyword. Rev 0.10 - 25Jul95 a) Disable the Internal Phy when doing autodetection unless no external valid Phys are detected. This corrects a contention between the Internal PG2.1 Phy and the 100Tx Phy. Rev 0.09 - 06Jul95 a) Added Bit Level Phy AUI Support b) Added Autodetect of multiple Phys c) Add NoAutoDetect Keyword Rev 0.08 - 27Jun95 a) Fix EtherNet.asm(Line 989) in processing MalFormedPackets, the FrameLookAhead pointer had not been setup. This is fixed in the latest EtherNet.asm 1/95 version. b) Added AUI and ThinNet keywords to support using the Internal Phys' AUI interface. c) Add support for future VG PMI revs. Now supports revs 1-F. d) Fix Sign On Message to indicate Driver Type. e) Fix Timeout recovery to recover from unknown VG Hopi Rev 1.0 lockups. f) Report correct speed for Internal Phy selection. Rev 0.07 a) Fix support for Internal Phy on PG 2.1, the Internal Phy Ignores the first write to itself, rendering the FullDuplex/Autonegotiate enabling useless. 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. c) Add MaxRx support for PG 2.0 and up, eliminating the adapter check recovery when frames that are larger than the receive buffer are received. d) Changed the signon message to better suit the driver. Rev 0.06 a) Add support for Internal Phy rev 2.1 and later, required for NoMgtMiiPhy keyword to work on PG 2.1 or later. Rev 0.05 a) Add FullDuplex keyword for 10/100 Mbit Phys, This parm is ignored for VG Mode. b) Add NoMgtMiiPhy Keyword for support of MII complient Phys, that have no IEEE managment interface, On these Phys the MDIO and MDC are used for FullDuplex, and Loopback respectively outputs for the Phy. c) 32 bit bug, caused some 32 bit applications some grief. d) Improve the Internal Phy Read routines for performance e) Detect Internal Phy, and add support code. Rev 0.03 a) Increment Others errors on invalid interrupts b) Fix National specific code from 9501 silicon to 9507 silicon 9501 required hidden register opations to auto switch from 10 to 100Mbit 9507 drops frames if you poll the MII regs. This code no longer supports the 9501 silicon. c) Receive code optimisation. --- 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.