ThunderLAN(tm) driver - SCO Unix 3.2v5.00 MDI version 1.00
(SCO OpenServer Release 5)
Installation and usage instructions
CONTENTS
========
Introduction ................... Provides a brief description of the
driver and associated files.
How to Install the Driver ...... Step-by-step instructions for
installing the ThunderLAN driver.
Netconfig(ADM) Advanced Options Describes the ThunderLAN specific driver
options.
Release Notes .................. Provides information on driver revision
history and any known driver problems.
INTRODUCTION
============
The ThunderLAN SCO Unix Driver conforms to the SCO MDI network driver
specification. The driver will load and run correctly on SCO Unix
3.2v5.00 (OpenServer Release 5), but not on previous SCO releases.
The driver has been extensively tested on machines running SCO
OpenServer Release 5 with Release Supplement 5.00d available via
anonymous ftp from ftp.sco.com. If a TCP/IP protocol stack will be
configured on top of the driver, it is recommended that the Networking
Supplement Release (currently at version 1.0.0) also be installed.
The supplement is available via anonymous ftp from ftp.sco.com.
This text file describes how to install and use the ThunderLAN(tm) driver
with SCO OpenServer Release 5.
The driver files are provided on the ThunderLAN Driver Diskette in the
following subdirectories:
Directory / Files Contents
------------------------- ---------------------------------------------
sco\
custom.dst ThunderLAN SCO OpenServer Release 5 Driver
readme.txt This file
HOW TO INSTALL THE DRIVER
=========================
The ThunderLAN SCO OpenServer Driver is installable via the SCO "custom"
utility. These instructions assume the operating system is installed
and is running in multiuser mode and that the software is being
installed from the local machine. For network installation instructions,
see the SCO OpenServer documentation regarding installing software over
a network. The driver can only be installed by superuser (root).
1.) Insert the floppy into the floppy drive.
2.) Install the software using one of the following two methods:
A.) Software Manager
----------------
1.) Start the Software Manager by double clicking on the
Software Manager icon.
2.) Choose Install New... from the Software menu.
3.) Click on the Continue button of the following two
popup dialog windows titled "Begin Installation" and
"Select Media".
4.) Click on the "Full" button in the Install Preference
popup window.
B.) Command Line
------------
Type the following at the prompt, replacing <floppy device> with
the name of your floppy device (typically /dev/fd0).
custom -p tlan -i -m <floppy device>
3.) Once the software is installed, the driver must be configured for the
installed network interface cards (NICs). To configure the driver,
use the netconfig(ADM) utility. If the NICs have not yet been
installed, it is recommended that driver configuration be postponed
until they are installed.
4.) The netconfig(ADM) utility can either be started by typing
"netconfig" at a command prompt, or by double clicking on the
Network Configuration Manager icon in the Networks folder of the
System Administration desktop folder icon. For complete instructions
regarding network configuration, see the SCO OpenServer documentation.
NETCONFIG (ADM) ADVANCED OPTIONS
================================
The following remarks can also be found in the on-line documentation
in the Networking Documentation Set of the SCO Documentation Library.
The driver provides limited sanity checking of the Advanced Options
selections. Ift is recommended that only users with both an in-depth
knowledge of both the Network Interface Card (NIC) and the attached
Local Area Network (LAN) modify the driver configuration.
Media Option
------------
Auto(default) IEEE 802.3 Media Auto-Negotiation. Many physical
layer devices offer support form more than one
wire speed and/or offer full versus half duplex
transmission capabilities. If such a physical
layer is detected by the driver, the driver will
attempt to auto-negotiate speed and duplex
capabilities with an attached hub.
100MBPS Force 100 Mbps/Half Duplex operation of the physical
layer device. Note: if the attached hub cannot
support such a configuration, network operation may
fail.
10MBPS Force 10 Mbps/Half Duplex operation of the physical
layer device.
100FULLDUPLEX Force 100 Mbps/Full Duplex operation of the physical
layer device. Note: if full duplex capability is
not supported by the attached hub, network
communication will fail if this mode is used by the
card.
10FULLDUPLEX Force 10 Mbps/Full Duplex operation of the physical
layer device. Note: if full duplex capability is not
supported by the attached hub, network communication
will fail.
AUI Force use of the AUI network interface for
ThunderLAN's internal 10BaseT phy or an attached
bit-rate 10 Mbps physical layer device.
No Management MII PHY
---------------------
No(default)/Yes Selecting 'Yes' for this option forces the driver
to assume that an MII compliant physical layer
device exists on the controller. The driver will
disable ThunderLAN's internal 10BaseT phy and try
to use the alternate device.
Physical Layer Device Auto-detection
------------------------------------
Yes(default)/No The default operation of the driver is to
automatically detect the physical layer device to
use by testing for a valid link. Selecting 'No'
for this option deisables this feature and forces
the dirver to use the first physical layer device
it encounters on the NIC, regardless of whether or
not a valid link can be detected. The following
is a brief outline of the physical layer device
detection scheme:
1.) If a "bit-level" physical layer device is
detected (e.g. the Level-One device) it is used.
2.) If the No Management MII Phy option is set to
'Yes', an MII compliant physcial layer device which
does not provide a management interface is used.
3.) All MII compliant physical layer devices are
scanned.
A.) If the Physical Layer Device Auto-detection
option is set to 'Yes' (default), each device is
activated as it is discovered and a test is made
for a valid link. The first device at which a
valid link is discovered is used. (If no device
on the NIC can detect a link, all devices are
rescanned until a valid link is found. A message
is periodically printed to notify the user about
the absence of a network connection).
B.) If the Physical Layer Device Auto-detection
option is set to 'No', the first MII compliant
device found is used.
MAC ADDRESS CONFIGURATION
=========================
The ThnderLAN (tm) Ethernet Controller driver will read the factory
programmed MAC address from EEPROM druing driver initialization. If,
however, it is necessary to use a MAC address other than that configured
by the manufacturer, the driver will override the MAC address read from
EEPROM with an address hard coded into the driver's link kit. See the
file:
/etc/conf/pack.d/tlan/space.c
for more information.
RELEASE NOTES
=============
This section describes the revision history and known problems/issues
with the driver.
Issue / problem Resolution / status
---------------------------------------------- -------------------------
Revision history
---------------------------------------------------------------------
Rev 1.00 04Mar96 [Initial Production release]
Rev 0.01 - 05Feb96 [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.