ThunderLAN(tm) - Novell NetWare OS/2 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. 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 OS/2 ODI Client Driver conforms to Novell's 16 Bit OS/2 Client HSM specification, version 2.1. It enables OS/2 2.x and OS/2 Warp 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 OS/2 ODI Client systems. The driver files are provided on the ThunderLAN Driver Diskette in the following subdirectories: Directory / Files Contents ------------------------- --------------------------------------------- netware\ os2odi\ readme.txt This file tlanodi.sys ThunderLAN ODI OS/2 Client Driver net.cfg Sample net.cfg 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. HOW TO SETUP NETWARE CLIENTS ============================ The ThunderLAN NetWare OS/2 ODI Client Driver is loaded and started at workstation boot time. If the Netware Client software is already installed on the workstation... 1. Add the following line to the section in config.sys delimited by the comment "ODI-Driver Files Begin": DEVICE=C:\NETWARE\TLANODI.SYS 2. Copy the file "\netware\os2odi\tlanodi.sys" from the ThunderLAN(tm) Driver Diskette to "C:\NETWARE\TLANODI.SYS". 3. Reboot the workstation. If the Netware Client software has not been installed... 1. Follow the instructions given during the Netware Client installation program to install a driver not included with Netware's Client software. When prompted for the name of the driver, enter "tlanodi.sys". How to install from OS/2 Warp Connect CD. NOTE: The following instructions assume the user will be accessing only a Novell Netware LAN. If the user will need access to a Netware LAN and a LAN running IBM's Lan Server, we recommend installing the OS/2 NDIS 2 driver. To install the OS/2 NDIS 2 driver, see the file \ndis2\os2\readme.txt on this diskette. 1. Install OS/2 following the instructions in the documentation that accompanies the Warp Connect CD. However, DO NOT choose to install Networking Products. When the Networking Products Installation window appears, choose No. 2. The operating system installation will continue. Do not remove the Warp Connect CD from the CDROM drive after the system reboots and OS/2 starts. 3. Open an OS/2 window. You now run an installation program from the CD. If your CDROM drive is d:, type: d:\prodinst 4. From the list of products to install, highlight Netware Client for OS/2 and select [Install]. 5. The Netware installation program runs. From the Installation menu, choose the "Requester on Workstation..." option. 6. A series of Dialog boxes appears: a.) Set Target Directory The default locations of the target and source are probably correct, but make any changes necessary and select [OK]. b.) Requester Installation The default option is "Edit CONFIG.SYS and Copy All Files". This is correct. Select [OK]. c.) Step 1 - Choose the ODI LAN Driver Type in: TLANODI.SYS and select [Continue]. d.) Step 2 - Choose Netware Support for DOS and Windows Applications The default is No IPX Support for DOS and Windows. Unless the user will be running DOS or Windows applications which require access to the Netware network, the default is correct. Select [Continue]. e.) Step 3 - Choose Optional Protocols Again, this is configurable, but no other protocols are necessary for access to a Netware network. Select [Save]. f.) Save Changes to CONFIG.SYS The default is "Save File as: C:\CONFIG.SYS". Unless special configuration has been done, this is correct. Select [OK]. g.) Copy Requester Files No changes can be made at this point. Select [Copy]. h.) Copy ODI LAN Driver Files The installation program does not allow the user to specify the drive and path to search for driver files. Select [Cancel]. 7. The Novell Netware installation program will complete sucessfully. Exit the installation program. To install the driver, type: copy a:\netware\os2odi\tlanodi.sys c:\netware in an OS/2 window. The above command assumes the driver is being installed from floppy drive a: and that the Netware installation program placed the netware files in c:\netware. 8. The machine must be rebooted to start the networking software. NOTE ABOUT USING MULTIPLE ADAPTER CARDS: ======================================== OS/2 ODI clients do not support interrupt sharing. If the driver detects more than one adapter card assigned to the same interrupt line, only the first card detected will be initialized. The driver uses PCI BIOS routines to determine which interrupt lines are assigned to which slots. In order to change a configuration in which the same interrupt line is assigned to more than one PCI slot, use the SETUP/DIAG program provided by the workstation manufacturer. RELEASE NOTES ============= This section describes the revision history and known problems/issues with the driver. Issue / problem Resolution / status ---------------------------------------------- ------------------------- Revision history --------------------------------------------------------------------- Rev 1.03 - 13Dec95 a.) Added changes necessary for TLAN ECN all000. Driver now halts the transmitter whenever a carrier loss event is detected and the transmitter is idle. Cures the UTP cable connect/disconnect problem. Rev 1.02 - 30Oct95 a.) Fixed bit settings for GEN_CTL register when operating in full duplex mode b.) Added support for the Network Keyword and removed support for the Fullduplex Keyword c.) Added functionality to correctly report line speed for NWAY compliant phys (we support autonegotiation now). Functionality includes support for NWAY compliant phys that are connected to non-NWAY compliat link partners. d.) Fixed msm.txt file so that driver specific keywords actually work...also fixed the driver keyword functions. Rev 1.01 - 12Oct95 a) Changed Driver Initialization code to check that interrupt line is valid (0 < x < 16) b) Major changes to phy power up routines to support adapter cards with crystals Rev 1.00 - 07Sep95 [First production] a) Added link disconnect fix for National Tx phy Rev 0.02 - 23Aug95 a) Passes Netware multicast test b) Forwards packets received on multicast address. Problem reported to Novell. Novell has duplicated the problem in their labs, with their card. c) Driver no longer accepts packets sent from local host d) Corrected errors freeing memory on perm shutdown e) Corrected VG training problem (resulting from correction c) f) Added test for detecting possible shared interrupts Rev 0.01 - 08Aug95 [Initial beta release] --- 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.