ThunderLAN(tm) - DOS NDIS 2 Driver Installation and usage instructions CONTENTS ======== Introduction .................. Provides a brief description of the driver and associated files. Before Installing the Driver .. Things to do before installing the driver. Installing the Driver ......... Step-by-step instruction on how to install the ThunderLAN driver. Driver Keywords ............... Describes the ThunderLAN specific driver keywords. Release Notes ................. Provides information on driver revision history and any known driver problems. INTRODUCTION ============ The ThunderLAN DOS NDIS 2 Driver conforms to the Microsoft/3COM Network Device Interface Specification (NDIS), version 2.0.1. This text file describes how to install and use the ThunderLAN driver for Microsoft LAN Manager 2.0 and 2.2. The driver files are provided on the ThunderLAN Driver Diskette in the following subdirectories: Directory / Files Contents ------------------------- ----------------------------------------- \mslanman.dos \drivers \ethernet \tlan tlan.dos ThunderLAN DOS NDIS 2 driver protocol.ini Protocol.ini information \nif tlan.nif Network Information File readme.txt This file 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. INSTALLING THE DRIVER ===================== This section provides instruction on how to install the driver for the following Network Operating Systems: o Microsoft LAN Manager 2.2 o Microsoft LAN Manager 2.0 INSTALLING THE DRIVER FOR USE WITH MICROSOFT LAN MANAGER 2.2 ------------------------------------------------------------ 1. Install Microsoft LAN Manager 2.2. 2. Type "cd \lanman". 3. Run the network setup program "setup". 4. Select "configuration". 5. Select "network drivers". 6. Select "add new configuration". 7. Select "other driver". 8. Insert the ThunderLAN Driver Diskette in drive A: 9. Select "ok". Once the driver is copied from the diskette, you will be asked to select the network protocol. Once the protocol has been selected, the driver installation is complete. The "config.sys" and "protocol.ini" files are automatically updated. You will be prompted to save the configuration changes, exit setup, and restart the system for changes to take effect. INSTALLING THE DRIVER FOR USE WITH MICROSOFT LAN MANAGER 2.0 ------------------------------------------------------------ 1. Install Microsoft LAN Manager 2.0. 2. Type "cd \lanman.dos". 3. Run the network setup program "setup". 4. Select "action". 5. Select "import network drivers". 6. Insert the ThunderLAN Driver Diskette in drive A: when prompted to do so. 7. Select the "Racore ThunderLAN(tm) adapter". The driver will then be copied. 8. Select "action". 9. Select "view/modify". 10. Continue through screens until you get to "network drivers". 11. Select "network adapter cards". 12. Scroll down the adapter card list until you reach the "Racore ThunderLAN(tm) adapter". 13. Select "add driver". 14. Select "add protocol" to select desired protocols. 15. Remove any unwanted configurations using the "remove" command. 16. Select "done". 17. Select "action". 18. Select "save" to save changes. 19. Select "exit" to exit the setup program. Reboot your system for the changes to take effect. 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 manually added into the [TLAN_NIF] section of the "protocol.ini" file. SLOT=<n> PCI Card Slot ------------------------ The PCI Card Slot option specifies the PCI card slot number where the ThunderLAN(tm) adapter is installed. The SLOT number can be specified to identify the specific ThunderLAN(tm) adapter to use if more than one adapter is installed. The value of <n> can range from 0 to 8191 inclusive. The correct value for the the slot keyword is calculated by combining the PCI device number (sometimes called slot) with the PCI bus number in the following manner: Slot = (PCI Bus Number * 32) + PCI Device Number If the PCI Card Slot is not specified, then the driver will auto select the network adapter, using the first (or second in a second driver instance) ThunderLAN adapter found. PHYSELECT=(0 to 31, 32, 33, or 34) Phy Selection ------------------------------------------------ The PHYSELECT keyword specifies the PHY for ThunderLAN(tm) to use in attemping a network connection. The legal values are as follows: PHYSELECT = 0 to 31 - TLAN PHY Bus Index of target PHY device 32 - Enables PHY Auto Select 33 - Enables TLAN or bit-level AUI Selection 34 - Enables Non-Managed MII PHY Selection AUI Selection ------------- The AUI selection specifies that the AUI network interface is to be used for ThunderLAN's internal 10BaseT PHY, or an attached bit-level PHY. Non-Managed MII Phy ------------------- The Non-Managed MII Phy mode specifies that an MII compliant PHY device which does not provide a management MII interface is to be used. Auto Select ----------- The auto select mode enables the PHY auto-detection mechanism. In auto select mode, the driver attempts to automatically detect the PHY to use by testing for a valid link. 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 non-managed MII PHY mode is specified, 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, the driver checks for a valid link on this PHY. If a valid link is found, then this PHY is used. If a PHY index is specified (0-31), then only that particular PHY is checked. NETWORK=(0 or 1 to 4) Network Type ---------------------------------- The NETWORK keyword is used to force ThunderLAN to use the speed and duplex settings as shown below. Note that in order for speed and duplex support to operate properly, ThunderLAN must be connected to a HUB capable of setting supplied. The NETWORK keyword is ignored if a 100VG PHY is used. If NETWORK is set to 0, ThunderLAN will auto configure the speed and duplex settings. NETWORK = 0 - Auto Configuration 1 - 10Mbit 2 - 100Mbit 3 - 10Mbit / FullDuplex 4 - 100Mbit / FullDuplex VENDORID=<n> Vendor ID ---------------------- The VENDORID keyword is supplied to allow an OEM to alter the PCI Vendor ID of the target network device. If set incorrectly, the driver will not find the network adapter. DEVICEID=<n> Device ID ---------------------- The DEVICEID keyword is supplied to allow an OEM to alter the PCI Device ID of the target network device. If set incorrectly, the driver will not find the network adapter. NETADDRESS="xxxxxxxxxxxx" Netcard Address - Use quotes -------------------------------------------------------- The NETADDRESS keyword allows an alternative network adapter address to be specified for the ThunderLAN adapter. The 12 character address must be specified within double quotes. Use this keyword with caution. Unpredictable results will occur if a conflicting or non-standard address is specified. If the NETADDRESS keyword is not specified, then the network address stored in the ThunderLAN adapter's ROM is used. RELEASE NOTES ============= This section describes the revision history and known problems/issues with the driver. Revision history --------------------------------------------------------------------- Rev 1.11 - 30Dec96 [Size and WFW] a) Corrected bug which made driver allocate significantly more memory than it required. b) Corrected bug which prevented driver from initializing with WFW. Rev 1.10 [Beta2] - 05Dec96 [Internal Phy Ints] a) Corrected setting of NetMask (no functional change) Rev 1.10 [Beta] - 17Nov96 [Power, Tlan 3.1] a) ASM Engine bug in disabling Tlan Ints fixed (only showed up in the NDIS2 driver). b) Added support for Tlan 3.1 c) Hook MS POWER.EXE to put power down PHY and put Tlan 3.1 in D1 on software suspend. d) Re-enabled support for setting VendorID and ProductID. e) Added support for uLin phy f) Bumped rev so first common engine code release will have minor rev increase. Rev 1.08 [Beta] - 31Oct96 [Power, Common ASM Engine, ICS, Negotiation] a) Fixed to use common engine code with assembly packet driver, which implements phy searching, renegotiation, etc. b) Increased receive buffers to 4 c) Added support for ICS Phy d) Fixed bug in autonegotiating full duplex e) Fixed bug in renegotiating when Phy search is disabled f) Added IOCLT to support TLPWR16 application, which can turn net driver on and off. Rev 1.07 - 23Jul96 [Slot and Polarity] a) Allowed for specifying "slot" on bus numbers other than 0. b) Inverted polarity fix c) No longer disable Full Duplex in advertisement reg Rev 1.06 - 11Mar96 [Fatal Error Recovery] a) Fixed startup sequence bug in fatal error recovery, which was introduced in v1.04. Fatal error sequences do not occur during normal adapter operation. Rev 1.05 - 08Feb96 [VDS] a) Added "don't alloc buffer flag" to VDS call Rev 1.04 - 13Dec95 [Keywords / NDIS3 Companion Release] a) Integrated AUTODETECT, NOMGTMIIPHY, and AUICONNETOR keywords into a single PHYSELECT keyword, allowing for greater flexibility in specifying a particular PHY - NOT BACKWARDS COMPATIBLE b) Added VENDORID and DEVICEID keywords to allow OEM to select the appropriate values for the target hardware. c) Enabled IRQ sharing with other TLAN and PCI devices. d) Added Carrier Sense Error recovery Rev 1.03 - 30Oct95 [Keywords] a) Changed FULLDUPLEX keyword to NETWORK, and integrated speed selection - NOT BACKWARDS COMPATIBLE b) Disabled Autonegotiation support for internal 10BaseT PHY. Rev 1.02 - 13Oct95 [Minor Cleanup / PHY Support / NDIS3 Keywords] a) General Cleanup b) Revised INT8 Trapping - Modifed WaitHalfSec to use new ISR c) Itegrated a new PHY power-up sequence d) Changed Tlan Max Frame RX from 1536 to 1514. e) Checked for invalid IRQ's above 15 f) Revised keywords to match NDIS3 driver - NOT BACKWARDS COMPATIBLE Rev 1.01 - 06Sep95 [Minor Cleanup / Additional Phy Support] a) Minor cleanup and removal of some unused data variables b) Added support for both normal and fast MII start delimiter c) Removed support for NDIS request Reset function d) Added support for NOAUTODETECT and NOMGTMIIPHY keywords, while retaining old versions for backwards compatibility. e) Revised InitNIC to disable Full Duplex auto-negotiation. f) Added bug fix for Link disconnect on National Phy Rev 1.00 - 11Aug95 [Initial production release] Rev 0.30 - 07Aug95 a) Do not load driver in the case where a single interrupt is shared by more than one ThunderLAN board when multiple TLAN boards are installed in the same system. b) Set receive and transmit buffer allocation block size and buffer capacity in the service-specific characteristics table to be multiple of 1514. Rev 0.21 - 03Aug95 a) Revised 386 code to fix forward pointer problems on receive list buffers. Rev 0.20 - (Not released) a) Reduced memory requirements of driver by using only 1 transmit buffer, and queueing from 6 to 18 transmit packet headers. Added MAXTRANSMITS keyword to specify number of transmit packets headers to queue. b) Forced number of receive buffers to 3. c) Eliminated RECVBUFS and XMITBUFS keywords (see above). d) Added support to recover from adapter checks. e) Fixed problem with 100BaseTX PHY auto-detection. Rev 0.10 - 25Jul95 [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.