ThunderLAN(tm) - NDIS 4 Miniport 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.
Configuration Options ......... Describes the ThunderLAN driver
configuration as seen by the user.
Driver Keywords ............... Describes the ThunderLAN specific driver
keywords.
Release Notes ................. Provides information on driver revision
history and any known driver problems.
INTRODUCTION
============
The ThunderLAN NDIS 4 Miniport Driver is desinged to provide NDIS4
functionality to Microsoft Windows NT 4.0.
This text file describes how to install and use the ThunderLAN driver
for Microsoft Windows NT 4.0.
The driver files are provided on the ThunderLAN Driver Diskette in the
following subdirectories:
Directory / Files Contents
------------------------- ---------------------------------------------
\ndis4
oemsetup.inf Installation script file
tlan.dll Contains Windows NT setup program information
tlan.hlp Help file for Windows NT configuration dialog
tlan4.sys ThunderLAN(tm) NDIS4 Miniport Driver file
readme.txt This file
BEFORE INSTALLING THE DRIVER
============================
INSTALLING THE DRIVER
=====================
This section provides instructions on how to install the driver for
Microsoft Windows NT 4.0.
If you have a previous version of the ThunderLAN(tm) Driver installed in
Windows NT, perform the following steps to remove it before proceeding to
step 1 below:
a. Run "Network" from Control Panel.
b. Highlight the "Racore ThunderLAN(tm)" entry in the
"Installed Adapter Cards" list box and click "Remove".
Then, click "OK".
c. Close the Network Settings dialog and restart Windows NT when
prompted.
1. From Windows, click on the "Network" icon from the Control Panel.
2. Click on "Add Adapter...".
3. When prompted for the name of the network adapter, select
"<Other> Requires disk from manufacturer". Under NT 4.0, click the
"Have Disk" button.
4. Insert the "ThunderLAN(tm) Driver Diskette" in drive A:.
5. When prompted for the pathname of the vendor-provided network
driver disk, enter "A:\NDIS4"
6. Select the "Racore ThunderLAN(tm) Adapter" adapter and
click "OK".
7. After some file copying, you will see the Texas Intstrument
ThunderLAN(tm) Adapter Setup dialog box. This dialog is used
to configure the driver options; PCI slot, network interface,
network type, and network address. See the driver configuration
section below for a detailed description of these options.
Once you have configured the driver, select 'OK'.
8. You will then be prompted for the bus type and bus number where
your ThunderLAN(tm) card is installed. In most cases, the
displayed settings will be correct. Make any necessary
corrections and press 'OK'.
9. Close the Network Settings dialog and restart Windows NT when
prompted.
To change driver settings, you may run the network control panel
application at any time. Highlight the "Racore ThunderLAN(tm)"
entry in the "Installed Adapter Cards" list box and click "Configure..".
CONFIGURATION OPTIONS
=====================
Several operational parameters of the ThunderLAN driver can be specified
at driver initialization time through the use of driver keywords. These
keywords are configured through the Network control panel applet in
Windows NT.
This section describes ThunderLAN(tm) driver setup options as seen from
from the network control panel applet. The section following contains
a more technical description of the keyword values.
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 can range from 0 to 31 inclusive.
If the "Auto Detect" option is selected, then the driver will
auto select the network adapter.
Network Interface
-----------------
The Network Interface parameter allows the user to choose among a
potential variety of network interface options available on the
network adapter card. The possible settings will vary according
to the hardware used, and in some cases only a single option may
be presented. The following include the most common options:
Auto Select
-----------
The Auto Select setting instructs the driver to search all
possible interfaces in an attempt to find the currently
active interface. On NDIS2, this requires the adapter to be
connected to an active network during driver start-up.
Expansion Module
----------------
The Expansion Module setting tells the driver to use the
optional expansion module on the ThunderLAN(tm) adapter.
TLAN 10BaseT
------------
The target adapter has a built-in PHY capable of connecting
to a 10BaseT network (if the connecter is supplied on the board).
This option specifies the use of this TLAN 10BaseT PHY.
TLAN/BitLevel AUI
-----------------
In the event the adapter is using an AUI or Thinnet connector,
connected to either the TLAN built-in PHY or a BitLevel PHY,
this option is used to specify to the driver to use the AUI
connector.
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.
Network Type
------------
The Network Type parameter allows the user to specify the type
(speed and duplex) of the target network. The available options
are as follows:
Auto Negotiate - Attempt to negotiate speed and duplex.
10Mbit - Use a 10Mbit network
100Mbit - Use a 100Mbit network
10Mbit/FullDuplex - Use a 10Mbit full duplex network
100Mbit/FullDuplex - Use a 100Mbit full duplex network
Network Address
---------------
The Network Address parameter allows the user to specify an
alternative network adapter address for the ThunderLAN adapter.
Use this option with caution. Unpredictable results will occur if a
conflicting or non-standard address is specified.
If the entry is blank in Windows NT, then the network address
stored in the ThunderLAN adapter's ROM is used.
DRIVER KEYWORDS
===============
TO CONFIGURE THE THUNDERLAN DRIVER, SEE THE PREVIOUS SECTION.
Several operational parameters of the ThunderLAN driver can be specified
at driver initialization time through the use of driver keywords. This
section describes the definitions of some of the ThunderLAN driver
specific keywords.
These keywords can be manually edited in the registry, but the procedure
required for this operation is beyond the scope of this document.
SLOT=<n> PCI Card Slot
------------------------
The SLOT keyword specifies the PCI card slot number where the
ThunderLAN adapter is installed. The SLOT number can be specified to
identify the specific ThunderLAN adapter to use if more than one
ThunderLAN adapter is installed.
The value of <n> can range from 0 to 32 inclusive.
A value of 32 will cause the driver to choose the first card
it finds, the same as if the SLOT keyword were not supplied.
PHYSELECT=(0 to 31, 32, 33, or 34) Phy Selection
------------------------------------------------
The PHYSELECT keyword specifies the PHY for ThunderLAN(tm) to
use in attempting 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
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 / Full Duplex
4 - 100Mbit / Full Duplex
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.
PROMISCUOUS=(0 or 1) Promiscuous mode
------------------------------------
Setting this to 1 causes the driver to always set the promiscuous
bits in 802.12 training frames to 0x10 (IEEE Draft Std. 802.12,
23 March 95, section 10.6.3.2). This requests all packets be
forwarded to the driver, which keeps the driver from having to
retrain the hub when a client sets promiscuous mode. This was
added as a workaround for a bug in the Microsoft NT/Win95 driver
test suite which caused the test to timeout while the driver was
dynamically retraining. The default value is 0 (not in registry)
which means the driver will retrain the hub as necessary.
RELEASE NOTES
=============
This section describes the revision history and known problems/issues
with the driver.
Revision history
---------------------------------------------------------------------
Rev 1.03 - 12Dec96
a) Fixed problem in setting D0 power state on start-up
b) Clear NetMask on shutdown to enable MII wake events
Rev 1.02 - 22Nov96
a) Added support for uLin Phy
b) Changed the way negotiation in handled on autonegotiating PHYs,
where PHY searching is disabled.
c) Improved support to TLPOWER
d) Support added for the D1 power state on Tlan 3.1
Rev 1.00 - 11Sep96 [1st Production 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.