ThunderLAN(tm) - FTP Packet 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 Class 1 Packet Driver conforms to the PC/TCP Packet Driver
Specification, Revision 1.09, for a Class 1 (ethernet) device. For
compatibility with 802.3, this driver also supports Class 11 access
requests.
This text file describes how to install and use the ThunderLAN driver
for use with FTP software.
The driver files are provided on the ThunderLAN Driver Diskette in the
following subdirectories:
Directory / Files Contents
------------------------- -----------------------------------------
\packet
tlanpkt.exe ThunderLAN packet driver
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 FTP Software applications
INSTALLING THE DRIVER
---------------------
1. Install FTP Software as desired.
2. Type "cd \pctcp", where "\pctcp" is the directory where you
installed FTP.
3. Copy the file "\packet\TLANPKT.EXE" from the ThunderLAN driver
disk.
The use of a packet driver is described in the FTP product documentation.
Instructions for configuring the ThunderLAN driver are given in the
following section.
DRIVER COMMAND LINE ARGUMENTS
=============================
Several operational parameters of the ThunderLAN driver can be specified
at driver initialization time through the use of command line arguments.
This section describes the ThunderLAN driver specific options.
The command line arguments are supplied on the command line (in any order)
when the driver file PKT_TLAN is first invoked. On options where a
numerical value is required, the value may be supllied in either decimal
(e.g. "s=10") or in standard 'C' hex form (e.g. "s=0xa").
H or ? Help Option
-------------------
Displays a quick reference screen with a summary of the options
described here.
I=<n> Driver Interrupt Level
-----------------------------
Although normally installed at interrupt 0x60, the packet driver
may be installed at any interrupt level (0x60 to 0x7F) by
supplying this parameter. Otherwise; the default of 0x60 is used.
S=<n> PCI Card Slot
---------------------
The SLOT options 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 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:
S = (PCI Bus Number * 32) + PCI Device Number
If the the PCI Card Slot is not specified, then the driver will
auto select the network adapter, using the first ThunderLAN
adapter found.
P=<n> 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.
4. When in Phy auto-detect mode, it is not necessary to re-load the
driver if switching network types. When a link is lost on one
phy, the auto-selection process automatically restarts.
N=<n> Network Type
--------------------
The NETWORK option 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 the network parameter is set to 0, or not supplied, ThunderLAN
will auto configure the speed and duplex settings.
N(etwork) = 0 - Auto Configuration
1 - 10Mbit
2 - 100Mbit
3 - 10Mbit / FullDuplex
4 - 100Mbit / FullDuplex
V=<n> VendorID
----------------
The VendorID keyword is used to override the default PCI VendorID
which the driver uses to search for Tlan based hardware. The valid
range for the VendorID is 0x0000 to 0xFFFF. The default value for a
Racore ThunderLAN adapter is 0x104C.
D=<n> DeviceID
----------------
The DeviceID keyword is used to override the default PCI DeviceID
which the driver uses to search for Tlan based hardware. The valid
range for the DeviceID is 0x0000 to 0xFFFF. The default value for
a Racore ThunderLAN adapter is 0x0500.
A="xxxxxxxxxxxx" Netcard Address
----------------------------------
The netcard address option 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 option with caution. Unpredictable results will occur if a
conflicting or non-standard address is specified.
If the netcard address (A) paramter is not specified, then the network
address stored in the ThunderLAN adapter's ROM is used.
Example
-------
The following command line,
pkt_tlan i=0x61 n=1 p=31 a="002233445566"
tells driver to install at interrupt 0x61, using PHY 31
(ThunderLAN(tm) internal PHY) at 10Mb, Half Duplex, with a net
address of "002233445566".
RELEASE NOTES
=============
This section describes the revision history and known problems/issues
with the driver.
Revision history
---------------------------------------------------------------------
Rev 1.01 [Beta5] - Test Release - 05Dec96 [Internal Phy Ints]
- Corrected setting of NetMask (no functional change)
Rev 1.01 [Beta4] - Test Release - 17Nov96
- ASM Engine bug in disabling Tlan Ints fixed (only showed up in
the NDIS2 driver).
- Added support for uLin Phy
Rev 1.01 [Beta3] - Test Release - 17Oct96
- Added support for Tlan 3.1
- Hook MS POWER.EXE to put power down PHY and put Tlan 3.1 in
D1 on software suspend.
- Added command line arguments to allow setting VendorID and
ProductID.
Rev 1.01 [Beta] - Test Release - 11Oct96
- Increased receive buffers to 4
- Added support for ICS Phy
- Fixed bug in autonegotiating full duplex
- Fixed bug in renegotiating when Phy search is disabled
Rev 1.00 - First Production Release - 18Oct96
ASM Engine Code Revs 0.00 to 0.05 [ Internal Releases ]
- Test versions of the packet driver using the common ASM engine
code, which includes the following enhancements:
o Continuous Phy auto-detect
o Continuous re-negotiation ability
o Power-down capability (not used in packet driver)
Rev 0.10 - 23Aug96
- Modified to enable build with either MASM 5.10b and MASM 6.11c
Rev 0.09 - 23Jul96 [Internal Release]
- Allowed for specifying "slot" on bus numbers other than 0.
- Inverted polarity fix
- Fixed bug which corrupted a different part of the driver
on each of the below versions.
- No longer disable Full Duplex in advertisement reg
Rev 0.07 - 11Jun96 [Beta release 3]
- Altered packet queueing mechanism to allow for multiple back
to back sends when interupts are disabled, or during a
packet receive indication.
Rev 0.06 - 05Jun96 [Beta release 2]
- Stopped using handle 0xFFFF as request-all-packet-type handle
- Fixed bug in setting MAC address using a="" command line option
Rev 0.04 - 02May96 [Beta release 1]
- Added ability to accept requests for Class 11 packets
- Fixed bug in handling requests for multiple packet types
Rev 0.03 - 29Feb96 [Alpha release]
- Minor cleanup
- Command line arg processing
- Startup after adapter reset
Rev 0.01 - 23Jan96 [Initial Alpha 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.