ThunderLAN(tm) - OS/2 NDIS 2 Driver
Installation and usage instructions
CONTENTS
========
Introduction .................. Provides a brief description of the
driver and associated files.
Installing the Driver ......... Step-by-step instruction on how to
install the ThunderLAN driver.
1) Using OS/2 WARP Connect Network
support or LAN Server 4.0 LAPS
installation.
2) Using MPTS or LAPS installation
3) Manual installation.
Driver Keywords ............... Describes the ThunderLAN specific driver
keywords.
More Than One Adapter Support . Driver support for more than one ThunderLAN
Network adapters.
Release Notes ................. Provides information on driver revision
history and any known driver problems.
INTRODUCTION
============
The ThunderLAN OS/2 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.
The driver files are provided on the ThunderLAN Driver Diskette in the
following subdirectories:
Directory / Files Contents
------------------------- ---------------------------------------------
\os2ndis2
tln.msg Driver message file
tlnh.msg Help message file
tlan.nif Network Installation File
tlan.os2 Driver
protocol.smp Sample protocol.ini file
readme.txt This file
INSTALLING THE DRIVER
=====================
NOTE: The following instructions assume the user requires access to
an IBM Lan Server and/or TCP/IP networks. If the user only requires access
to a Novell Netware LAN, then we recommend installing the Netware OS/2 ODI
client driver. To install the Netware OS/2 ODI client driver, see the
file \netware\os2odi\readme.txt on this diskette.
NETWORK SUPPORT INSTALLATION
----------------------------
This installation process occurs during the installation of OS/2 Warp
Connect Network Support. The Network Support option must be selected
along with at least one of the following services: IBM Peers for OS/2,
Novell Netware Client for OS/2, or Internet Access using Modem.
To install ThunderLAN NDIS MAC driver:
At the Select Network Adapter panel
_ Select CHANGE ADAPTER then, after a list of available adapter
drivers is listed, select OTHER ADAPTER.
_ Put the "ThunderLAN Driver Diskette" into drive A:, and enter
A:\NDIS2\OS2. The installation program now copies the following
files:
TLAN.OS2 ---> IBMCOM\MACS
TLAN.NIF ---> IBMCOM\MACS
TLN.MSG ---> IBMCOM
TLNH.MSG ---> IBMCOM
_ Choose Ethernet as the Type of LAN in the Drivers Found panel.
The adapter configurable parameters are displayed with their default
values, press OK to accept these values.
Note: In order for the Novell Netware Client to work correctly,
the following parameters for IBM Netware Requester Support must be
configured:
Netword Adapter Address : ThunderLAN adapter network address
(12 alphanumeric characters).
Ethernet Frame Header Support : Yes
USING MPTS or LAPS INSTALLATION
-------------------------------
NOTE: Assuming that OS/2 Warp is already installed. This procedure is
used to install or replace just the network adapter used for the MAC and
Transport layer interface.
1) Type MPTS or LAPS at the command prompt (or select the MPTS folder).
2) Select "configure".
3) Select "configure" "LAN Adapters and Protocols".
4) Select "Others" from "Network Adapters" list box.
5) Enter "a:\os2ndis2".
6) Insert the ThunderLAN Driver diskettes into drive A:
7) Select "ok".
Once the driver files are copied from the diskette.
8) Select "TI ThunderLAN(tm) NDIS Ethernet Adapter (TLAN.OS2)" from
the "Network Adapters" list box.
9) Select "add".
10) Select appropriate protocols from the "Protocols" list box such as
TCP/IP, NETBIOS, or Netware Support.
11) Select "ok".
The config.sys and protocol.ini files are automatically updated. a reboot
of the system is necessary for changes to take effect.
MANUAL INSTALLATION
-------------------
This section describes how to MANUALLY install the ThunderLAN MAC driver.
To install the driver with IBM LAN Server LAPS or MPTS facility, please
refer to their respective documentations.
The following files are copied:
TLAN.OS2 ----> X:\IBMCOM\MACS
TLAN.NIF ----> X:\IBMCOM\MACS
TLN.MSG ----> X:\IBMCOM
TLNH.MSG ----> X:\IBMCOM
The CONFIG.SYS file should include:
DEVICE = X:\IBMCOM\MACS\TLAN.OS2
DPATH points to X:\IBMCOM so the operating system could find
ThunderLAN message and message help files.
Note :
X: is the drive letter containing the IBMCOM directory
TLAN.OS2 must be included after PROTMAN.OS2 in the config.sys
file
The PROTOCOL.INI file should contain:
[TLAN_nif]
DriverName = TLAN$
MAXTRANSMITS = 12 (range from 6 to 18, default 12)
NETWORK = 0 (range from 0 to 4, default 0)
AUTODETECT = 1 (0 or 1, default 1)
SLOT = OPTIONAL (range from 0 to 31, default not specified)
NETADDRESS = OPTIONAL (if specified, address must be 12 hex ascii)
NOMGTMIIPHY = 0 (0 or 1, default 0)
AUICONNECTOR = 0 (0 or 1, default 0)
For each protocol that wants to use ThunderLAN as the transport
MAC driver, it must specifies the binding statement below in its own
section in the PROTOCOL.INI file.
Bindings = TLAN_nif
All the keywords are optional except DriverName keyword. If
optional keywords are not specified, the default values are assumed.
Please refer to below for a detail description of specific
keywords.
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.
AUICONNECTOR=<0/1>
------------------
This keyword (AUICONNECTOR = 1) specifies that the AUI network interface
is to be used for ThunderLAN's internal 10BaseT PHY or a bit-rate
10 Mbps PHY.
If this keyword (AUICONNECTOR = 0), then the 10BaseT network interface
is used. The default is AUICONNECTOR = 0.
MAXTRANSMITS=<n>
------------
The MAXTRANSMITS=<n> keyword specifies the number <n> of transmit
packet headers that can be queued by the driver. The value of <n> can
range from 6 to 18 inclusive, the default value is 12.
Each transmit header requires approximately 128 bytes of memory.
Reducing the value of MAXTRANSMITS will save memory used by the
driver, but may result in an increased number of "out of resource"
conditions, resulting in decreased performance. Increasing MAXTRANSMITS
will reduce these "out of resource" conditions.
SLOT=<n>
--------
The SLOT keyword specifies the PCI slot where the ThunderLAN Network
adapter is installed. Specify this parameter only when more than one
ThunderLAN network adapter is present in the same workstation.
The value of <n> can range from 0 to 31 inclusive, the default is not
specified.
AUTODETECT=<0/1>
----------------
The AUTODETECT keyword disables/enables the PHY auto-detection mechanism.
The default (AUTODETECT = 1) is to automatically detect the PHY to use
by testing for a valid link. Specifying AUTODETECT = 0 disables
auto-detect mechanism, and causes the driver to select the first PHY
device encountered, regardless of link status.
NETADDRESS="xxxxxxxxxxxx"
-------------------------
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.
If the NETADDRESS keyword is not specified, then the network address
stored in the ThunderLAN adapter's Read-Only-Memory (ROM) is used.
NOMGTMIIPHY=<0/1>
-----------------
The keyword NOMGTMIIPHY=1 specifies that an MII compliant PHY device
which does not provide a management MII interface is to be used.
Specifies this keyword disables the use of ThunderLAN internal 10BaseT
PHY and other management capable MII PHYs.
The default value (NOMGTMIIPHY = 0) is to use ThunderLAN internal 10BaseT
PHY.
NETWORK=<n>
-----------
The keyword NETWORK allows the user to specify the type (speed and
duplex) of the target network. The available options are:
NETWORK=0 - Default, auto-detect. The driver uses the
auto-detection mechanism to determine the speed and
duplex mode of the current network.
NETWORK=1 - 10 Megabit, half duplex mode.
NETWORK=2 - 100 Megabit, half duplex mode.
NETWORK=3 - 10 Megabit, full duplex mode.
NETWORK=3 - 100 Megabit, full duplex mode.
MULTI-ADAPTER SUPPORT
=============================
ThunderLAN NDIS Ethernet MAC driver supports up to 4 network adapters
installed in the same workstation. Separate driver instance is loaded for
each network adapter card, and the mechanism to pair-up a driver instance
with a network adapter card is by the SLOT keyword. If the SLOT keyword is
specified for each and every adapter card, then a driver instance
will use the adapter card in the specified slot. If the SLOT keyword
is not specified for any of the adapter card, then the first
driver instance will use the lowest-numbered pci slot found, the second
driver instance will use the next lowest-number pci slot, and so on. The
SLOT keyword is either specified for all the adapters or not specified at
all. Please do not specified a SLOT keyword for one adapter card and not
for the next, this will produce unpredictable results.
RELEASE NOTES
=============
This section describes the revision history and known problems/issues
with the driver.
Issue / problem Resolution / status
---------------------------------------------- ----------------------
1) This driver has been tested under the
following environment. Additional testing
is in progress for other OS/2 versions:
- OS/2 WARP operating system
- LAN Server and Requester version 4.0
- Novell Netware client for OS/2 Warp Connect
- IBM TCP/IP version 2.0 for OS/2
- IBM NFS File Server version 2.0 for OS/2
2) 802.2 protocol driver complaints of duplicate Investigation
node addresses during binding.
Revision history
---------------------------------------------------------------------
Rev 1.01 - 24May96
a) Fixed the Open adapter problem during binding for Novell Netware
Client support using OS/2's ODI2NDI.OS2 driver, and 802.2 driver
that comes with OS/2 Warp Connect.
b) Remove optional ResetAdapter request because (1) MAC driver is in
better position to know if something wrong with the adapter and
to reset it. (2) every protocol driver tries to reset the adapter
when it first binds to MAC driver, in a multi-protocol
environment, this amounts multiple resets during initialization.
(3) to be conformed with our TLAN DOS driver.
Rev 1.00 - 4Jan96 First production
a) Added support for Network Keyword.
b) Changed driver Initialization code to check for valid interrupt
line between 1 and 15 inclusive, 0 < IRQ < 16.
c) Fixed link disconnect problem for National TX Phy.
d) Added support for Autonegotiation.
Rev 0.01 - 27Nov95 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.