3Com Corporation reserves the right to revise this documentation and to make changes in content
from time to time without obligation on the part of 3Com Corporation to provide notification of
such revision or change.
3Com Corporation provides this documentation without warranty of any kind, either implied or
expressed, including, but not limited to, the implied warranties of merchantability and fitness for a
particular purpose. 3Com may make improvements or changes in the product(s) and/or the
program(s) described in this documentation at any time.
UNITED STATES GOVERNMENT LEGENDS:
If you are a United States government agency, then this documentation and the software described
herein are provided to you subject to the following restricted rights:
For units of the Department of Defense:
Restricted Rights Legend: Use, duplication, or disclosure by the Government is subject to restrictions
as set forth in subparagraph (c) (1) (ii) for Restricted Rights in Technical Data and Computer Software
Clause at 48 C.F.R. 52.227-7013. 3Com Corporation, 5400 Bayfront Plaza, Santa Clara, California
95052-8145.
For civilian agencies:
Restricted Rights Legend: Use, reproduction, or disclosure is subject to restrictions set forth in
subparagraph (a) through (d) of the Commercial Computer Software – Restricted Rights Clause at
48 C.F.R. 52.227-19 and the limitations set forth in 3Com Corporation’s standard commercial
agreement for the software. Unpublished rights reserved under the copyright laws of the United States.
If there is any software on removable media described in this documentation, it is furnished under a
license agreement included with the product as a separate document, in the hard copy
documentation, or on the removable media in a directory file named LICENSE.TXT. If you are unable
to locate a copy, please contact 3Com and a copy will be provided to you.
Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may
or may not be registered in other countries.
3Com, TokenDisk and TokenLink are registered trademarks of 3Com Corporation. Velocity and
NetAge are trademarks of 3Com Corporation. 3ComFacts is a service mark of 3Com Corporation.
Artisoft and LANtastic are registeed trademarks of Artisoft, Inc. Banyan and VINES are registered
trademarks of Banyan Systems Incorporated. CompuServe is a registered trademark of CompuServe, Inc.
DEC and PATHWORKS are registered trademarks of Digital Equipment Corporation. Intel is a registered
trademark of Intel Corporation. AIX, IBM, NetView, and OS/2 are registered trademarks of International
Business Machines Corporation. Microsoft, Windows, and Windows NT are registered trademarks of
Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc.
Other brand and product names may be registered trademarks or trademarks of their respective holders.
5400 Bayfront Plaza
■
Santa Clara, California
■
95052-8145
■
ii
C
ONTENTS
A
BOUT
T
How to Use This Guide 1
Conventions 2
HIS
G
UIDE
1
I
NTRODUCTION
Product Features 1-1
Overview of Point Enablers, Socket Services, Card Services,
and Super Client Drivers 1-2
Point Enablers 1-4
Socket Services 1-5
Card Services 1-5
Super Client Drivers 1-7
Card Services Enabler 1-7
Card and Socket Services Versus Point Enablers 1-7
Autoset Mode 1-8
2
I
NSTALLING
Kit Contents 2-1
Installation Tips 2-1
Installing the 3C389 PC Card 2-1
Removing the 3C389 PC Card 2-5
3
I
NSTALLING
Windows 95 Installation 3-2
Windows 95 OSR 2 Installation 3-4
Windows for Workgroups/NDIS 2 Installation 3-4
Using Memory Management 3-6
Windows NT 3.51 Installation 3-6
Windows NT 4.0 Installation 3-8
Novell NetWare Client 32 for Windows 95 Installation 3-9
THE
THE
T
OKEN
N
ETWORK
L
INK
V
D
ELOCITY
RIVERS
PC C
ARD
iii
OS/2 NDIS 2 Device Driver Using LAN Adapter Protocol Support
(LAPS) 3-9
DOS Client 16 for Novell NetWare 4.01 and
Above Installation 3-11
Using Memory Management 3-12
OS/2 NDIS 2 Device Driver Using Multiprotocol Transport Service
(MPTS) 3-12
IBM LAN Support Program/Native Installation 3-14
Using Memory Management 3-15
4
LANAID
LANAID 4-1
Net Address 4-2
IBM LAN Client 4-2
Installing LANAID 4-3
Using LANAID to Install IBM LAN Client 4-4
Using LANAID to Configure the 3C389 PC Card 4-7
Running LANAID From the Command Line 4-8
5
T
ROUBLESHOOTING
Error Codes 5-3
OS/2 NDIS Error Codes 5-3
DXMCSMOD Error Codes 5-6
Troubleshooting Windows 95 (NDIS 3) 5-7
Troubleshooting Windows NT (NDIS 3) 5-8
Running the Diagnostics Program 5-8
Test Options 5-9
Diagnostics Error Codes and Suggested Actions 5-10
Open Errors 5-11
Open Error Codes 5-11
Transmit Error Codes 5-16
AND
IBM LAN C
Initialization Error Codes 5-10
Phases 5-12
Errors 5-12
Suggested Actions in Response to Open Errors 5-12
LIENT
iv
A
U
SING
A
M
EMORY
Memory Managers with Point Enabler A-1
Memory Managers with Card and Socket Services A-2
Expanded Memory Specification A-4
B
S
YSTEM
S
OFT
C
H
OT
-P
LUGGABILITY
Windows 95 (NDIS 3) C-2
DOS ODI Hot-Pluggability and Suspend/Resume C-3
DOS NDIS Hot-Pluggability C-3
OS/2 NDIS Hot-Pluggability and Suspend/Resume C-4
C
ARD
M
AND
AND
ANAGER
S
OCKET
S
USPEND
S
ERVICES
/R
ESUME
S
PECIFICS
D
T
ECHNICAL
Online Technical Services D-1
World Wide Web Site D-1
3Com Bulletin Board Service D-2
3ComFacts Automated Fax Service D-2
3ComForum on CompuServe Online Service D-3
Support from Your Network Supplier D-4
Support from 3Com D-4
Returning Products for Repair D-6
I
NDEX
3C
OM
FCC C
VCCI C
S
UPPORT
Access by Analog Modem D-2
Access by Digital Modem D-2
C
ORPORATION
LASS
B C
LASS
2 S
L
IMITED
ERTIFICATION
TATEMENT
W
ARRANTY
S
TATEMENT
3C
OM
E
ND
U
SER
S
OFTWARE
L
ICENSE
A
GREEMENT
v
F
IGURES
1-1PC Card Software Interfaces 1-3
2-1Attaching the Cable to the 3C389 PC Card 2-2
2-2Inserting the 3C389 PC Card 2-3
2-3Modular UTP Cable for the 3C389 PC Card 2-4
2-4RJ-45 to STP Connector 2-4
vii
T
ABLES
Notice Icons 2
Text Conventions 2
4-1 Clients and Protocol Descriptions 4-5
1
2
5-1 DOS ODI Error Codes 5-4
5-2 DXMCSMOD Error Codes, Explanation, and Action 5-6
5-3 Phase Nibble Explanations 5-12
5-4 Error Condition Nibble Explanations 5-12
5-5 Actions for Open Errors 5-13
5-6 Recommended Actions Key 5-16
ix
L
IFETIME
ARRANTY
W
3Com’s EtherLink
TokenLink Velocity
FDDILink
Lifetime Limited Warranty. For further details,
please see 3Com’s Limited Warranty statement
in this guide.
To ensure the very best 3Com service and
support, take the time to complete the product
registration card.
™
L
IMITED
®
, Fast EtherLink, TokenLink
™
, ATMLink
network interface cards have a
™
PCI, and
®
,
Customers in the countries or regions shown below should send the
completed registration card to the appropriate address. Customers in
other non-U.S. locations should send the registration card to the U.S.
address on the front of the card.
■
Asia
3Com Asia Ltd., Marketing Department
Room 2506-07, 25/F.
Citibank Tower
Citibank Plaza, Central
Hong Kong
■
Australia, New Zealand
3Com Australia, Marketing Department
99 Walker Street
Level 7
North Sydney
New South Wales 2060
Australia
3Com France, Marketing Department
Immeuble McKinley
BP 965
1, Avenue de l’Atlantique
91976 Les Ulis Courtaboeuf Cedex
France
■
Japan
3Com Japan, Marketing Department
Shinjuku Sumitomo Building 23F
2-6-1 Nishi Shinjuku, Shinjuku-ku
Tokyo 163-02
Japan
■
Sweden, Finland, Norway,
Denmark
3Com Nordic, Marketing Department
Torshamsgatan 39
Box 1110
164 22 KISTA
Sweden
■
United Kingdom, Eire
3Com UK Ltd., Marketing Department
Pacific House
Third Avenue
Globe Park Marlow-on-Thames
Buckinghamshire, SL7 1YL
England
■
Germany, Austria, Switzerland
3Com GmbH, Marketing Department
Gustav-Heinemann-Ring 123
D-81739 Muenchen
Munich
West Germany
■
Italy, Greece, Spain, Portugal,
Malta
3Com Mediterraneo Srl,
Marketing Department
Via Michelangelo Buonarroti, 1
20093 Cologno Monzese MI
Italy
ABOUT THIS GUIDE
This guide describes how to install and configure the
3Com 3C389 TokenLink Velocity PC Card, and is
intended for the token ring network administrator,
operator, or hardware installer. A knowledge of token
ring networks and microcomputer hardware configuration
procedures is required.
If the information in the README.TXT file or the Release
Notes differs from the information in this guide, follow
the information in the README.TXT file first, the Release
Notes second, and the user guide third. The README.TXT
files are on the software diskettes; the printed Release
Notes are placed in the product box or inserted in the
user guide when the product is packed.
How to Use This Guide
This table shows where to find specific information in this
guide.
If you are looking for...Turn to...
Features of the 3C389 TokenLink Velocity PC CardChapter 1
Installing the 3C389 TokenLink Velocity PC CardChapter 2
Installing the network device drivers for a specific operating systemChapter 3
Using LANAID for network device driver configurationChapter 4
Troubleshooting and error codesChapter 5
Using the diagnostic utilityChapter 5
Using a Memory ManagerAppendix A
Specifics about SystemSoft Card and Socket ServicesAppendix B
Hot-Pluggability and Suspend/ResumeAppendix C
Contacting 3Com technical supportAppendix D
2ABOUT THIS GUIDE
Conventions
Table 1 and Table 2 list conventions that are used
throughout this guide.
Table 1 Notice Icons
IconNotice TypeAlerts you to...
Information noteImportant features or instructions
CautionRisk of personal safety, system damage, or loss
WarningRisk of severe personal injury
Table 2 Text Conventions
ConventionDescription
CommandsThe word “command” means you must enter the
Screen displaysThis typeface represents information as it appears on
Words in italicized
type
of data
command exactly as shown in text and press the Return
or Enter key. Example:
To remove the IP address, enter the following
command:
SETDefault !0 -IP NETaddr = 0.0.0.0
This guide always gives the full form of a command in
uppercase and lowercase letters. However, you can
abbreviate commands by entering only the uppercase
letters and the appropriate value. Commands are not
case-sensitive.
the screen.
Italics emphasize a point or denote new terms at the
place where they are defined in the text.
INTRODUCTION
1
The 3Com TokenLink Velocity PC Card (referred to as the
3C389 PC Card) is a network interface card (NIC) that
provides an interface between PCs and token ring
networks. The 3C389 PC Card is designed to operate in
PCs with PC Card slots that comply with the standards of
the Personal Computer Memory Card International
Association (PCMCIA) Release 2.1, Type II slots.
Product Features
■ Fully compatible and up to 90% faster than the
3Com TokenLink III PC Card.
■ Remote Program Load (RPL) capability.
■ Full-duplex ready.
■ Supports the Desktop Management Interface (DMI).
■ Easy to install—variable interrupt levels and I/O
address choices.
■ Choice of Plug and Play automated configuration or
software configurable, with included graphical or
command line tool, for fast and easy installation.
■ RJ-45 cable and shielded twisted pair (STP) media
access adapter for easy connection to either
unshielded twisted pair (UTP) or STP cabling.
■ Hot-Pluggability—conserves power and memory
resources without removing the PC Card.
■ Compliance with PCMCIA and IEEE 802.5 standards,
Revision 2.
■ Support for a variety of network operating systems
and network applications.
■ Auto Ring Speed option that automatically detects the
data rate of the ring.
1-2CHAPTER 1: INTRODUCTION
See the README.TXT files on the TokenDisk diskettes for
information on 3C389 PC Card features not documented
in the user guide.
Overview of Point Enablers, Socket Services,
Card Services, and Super Client Drivers
Computers that support PC Cards have one or more PC
Card slots, known as A, B, C... or 1, 2, 3....
Communication between the LAN device driver and the
PC Card is enabled by a software layer which may include
one or more of the following programs:
■ Point Enablers
■ Card Services
■ Socket Services
■ Super Client Drivers
Figure 1-1 shows how these programs operate relative to
each other. A dotted line means that the program has
fulfilled a temporary function and is no longer operating
or resident in memory.
Overview of Point Enablers, Socket Services, Card Services,
and Super Client Drivers
1-3
PCMCIA 2.1
LAN device
driver
Card
services
Socket
services
Socket
controller
Socket services
enabled
LAN device
driver
Socket services
enabler
Point enabled
LAN device
driver
Point
enabler
Socket
controller
Card services
enabled
LAN device
driver
Card services
enabler
Socket
services
Socket
controller
Figure 1-1 PC Card Software Interfaces
Card
services
Socket
services
Socket
controller
1-4CHAPTER 1: INTRODUCTION
Point Enablers
Windows NT currently uses a point enabler called
PCMCIA.SYS, which currently ships with Windows NT.
OS/2 requires Card Services.
Point enablers are small programs that provide an
interface directly to the PC Card controller; therefore,
they must be written to support a particular type of
controller. For the 3C389 PC Card, there are point
enablers for the Intel chip (most PCs) and for the chip
installed in the Toshiba 3300SL.
In the DOS environment only, you have the option of
using these point enablers instead of Card and Socket
Services.
Two point enablers are supplied for this PC Card:
■ POINTTR.EXE—For PCs with Intel PCMCIA controllers,
including the IBM ThinkPad, Toshiba 4500 and later,
and many other makes.
■ TOSHTR.EXE–For the Toshiba T3300SL.
When using the point enabler, it is vitally important that
you make certain that the system resources used by the
PC Card are different from and do not conflict with the
system resources and any other PC Cards installed in
your PC.
Advantages
Enablers consume no memory—they remove themselves
after configuring the PC Card.
Disadvantages
You must specify the slot number; the point enabler will
enable only that slot. Therefore, the PC Card must always
be in a specific slot.
In some PCs, the slot may not be switched off when the
PC is in suspend mode, so the PC Card will continue to
consume power.
When configuring two or more PC Cards, you must
allocate memory and interrupt resources manually.
Socket Services
This is a BIOS-type interface that provides a way to gain
access to the PC Card sockets (slots) of a PC. It identifies
how many sockets your PC has and detects the insertion or
removal of a PC Card while the PC is switched on. It has
an interface to Card Services. Socket Services is part of the
PCMCIA Specification.
The Socket Services device driver is usually provided by
the manufacturer of the PC, because the driver must
understand the PC's BIOS and PCMCIA controller.
The Socket Services interface enabler shipped on
TokenDisk diskette #2 is TOKENRNG.EXE. It will not work
with Socket Services 2.0 or higher.
The file TOKENRNG.EXE is an MSDOS Socket Services 1.01
interface enabler. It uses the Socket Services that is
included in some PCs to configure the socket and PC Card.
It is used on machines with DATABOOK PC Card controllers
that support the Socket Services 1.01 interface and not
Card Services.
Socket Services
1-5
Card Services
This is a software management interface that allows
system resources (such as memory, interrupts, slots, and
I/O ports) to be allocated automatically when Socket
Services has detected that a PC Card has been inserted.
Client drivers call Card Services to allocate and de-allocate
system resources. When Socket Services detects an
insertion or removal of a PC Card, it sends notification to
Card Services. Card Services then notifies its registered
client drivers, such as IBMTOKCS.OS2, that they should
allocate or de-allocate resources.
1-6CHAPTER 1: INTRODUCTION
If the installation program detects Card and Socket
Services in your PC, it will default to Autoset mode.
Autoset mode allows your LAN driver to negotiate with
Card Services for memory space and interrupts. This helps
to prevent conflicts with other PC Cards that are
installed in your PC; however, you will not know exactly
what memory addresses and interrupts have been given
to you.
Card Services requires Socket Services. The Card Services
interface is usually provided with the operating system.
Advantages
■ Ability to insert and remove PC Cards without PC
reconfiguration and without damaging the electrical
contacts.
■ Automatic allocation of system resources.
■ When used with your token ring software in Autoset
mode, automatic configuration of your PC Card
occurs.
Disadvantage
■ Stay-resident program that uses system memory. The
amount varies according to the type of PC Card
support and the drivers used.
The file CS20TOK.EXE is a DOS Card Services 2.00
interface enabler shipped on TokenDisk diskette #2. It uses
the Card Services interface to configure the socket and
the PC Card. It is used when the token ring device driver is
not a Card Services client driver and a Card Services
environment is desired. It works with DOS Card Services
2.00 and higher.
Super Client Drivers
Many notebook PC vendors are providing customers with
super client drivers that can enable many different PC
Cards. PC-DOS 6.1 includes one called PCMSCD.EXE, for
example.
They are best used for modems and other PC Cards that
do not have a Card Services client driver of their own. If
you use a super client driver, try to disable support for the
PC Card and use the 3Com client driver. 3Com drivers
have been written to take advantage of Card Services.
Look at the documentation for your super client driver to
find out whether you can disable token ring support.
Card Services Enabler
If you want to use a token ring device driver that does
not have built-in Card Services support on a system that
uses Card Services, CS20TOK.EXE is supplied. This
program is a Card Services Enabler that uses Card and
Socket Services to configure the 3C389 PC Card. As with
other enablers, you must specify the resources desired
for the PC Card, and they must agree with the settings of
the token ring device driver for the system to work
correctly.
Super Client Drivers
1-7
Card and Socket Services Versus Point Enablers
In principle, Card and Socket Services is the better
method of connection because it allows you to insert or
remove PC Cards from any slot as you want, even while
the PC is switched on (hot-swapping) and it automatically
allocates resources like memory, I/O ports, interrupt levels,
and slots.
Point Enablers, two of which are provided with the
PC Card, are popular because they remove themselves
from memory after having been loaded—as opposed to
the 30-40 KB needed for Card and Socket Services.
1-8CHAPTER 1: INTRODUCTION
For point enablers, you have to specify the slot in which a
particular PC Card will be used and you have to specify
memory locations, interrupt levels, and other parameters.
This is not difficult unless you use several PC Cards at
different times, in which case you need to make certain
that what you specify does not conflict with any other PC
Cards installed in your PC.
Autoset Mode
Card and Socket Services turns out to be most helpful
when you have a number of PC Cards installed in your
PC. If the installation program detects Card and Socket
Services in your PC, it will default to Autoset mode.
Autoset mode allows your LAN driver to negotiate with
Card and Socket Services for memory space and
interrupts every time you switch on your PC. This helps to
prevent conflicts with other PC Cards that are installed in
your PC; however, you will not know exactly what
memory addresses and interrupts you are using.
INSTALLINGTHE
2
Kit Contents
In addition to this manual, your kit contains the following
items:
■ 3Com 3C389 TokenLink Velocity PC Card
■ Token ring PC Card RJ-45 cable
■ Five TokenDisk diskettes
■ An shielded twisted pair (STP) connector for
connection to STP network wiring
The 3C389 PC Card cable can be purchased separately.
If you want additional cables, contact your 3Com
marketing representative or your place of purchase.
Installation Tips
If you plan to use Card and Socket Services software,
Version 2.0 or higher, install it and reboot your PC. The
software may be provided with your PC or operating
system. See Chapter 1 for a description of these services.
TOKENLINK VELOCITY
PC CARD
The README.TXT file on TokenDisk diskette #2 contains
more information to help you configure and customize
the 3C389 PC Card.
Installing the 3C389 PC Card
The procedures in this section explain how to physically
install the 3C389 PC Card. The installation procedure is
summarized by the following sequence:
■ Attach the RJ-45 cable to the 3C389 PC Card.
■ Insert the 3C389 PC Card into the PC.
■ Plug the cable into the appropriate network port.
2-2CHAPTER 2: INSTALLINGTHE TOKENLINK VELOCITY PC CARD
If you are using Card and Socket Services, you may be
able to use hot-pluggability features with your 3C389
PC Card. See Appendix C, “Hot-Pluggability and
Suspend/Resume” for more information
1 Turn off the power to the PC.
2 Attach the cable to the 3C389 PC Card (Figure 2-1).
Retract the latch by sliding the half-circle latching button
on the connector backwards toward the cable. The cable
cannot be connected or disconnected unless the latch is
retracted.
With the part number facing down, attach the cable
connector to the 3C389 PC Card.
The connector can attach to the 3C389 PC Card in only
one way. If the connector does not seem to fit, turn it
over and gently try again.
The cable for the 3Com 3C689 TokenLink III PC Card is not
compatible with the 3C389 PC Card.
INSERT
THIS SIDE UP
3C389
PC card
TokenLink
16/4 PC Card
Part number
(on bottom)
®
Velocity
™
Latching button
Figure 2-1 Attaching the Cable to the 3C389 PC Card
Installing the 3C389 PC Card2-3
16/4 PC Card
TokenLink
®
Velocity
™
INSERT
THIS SIDE UP
3C389
3 Lock the cable connector to the 3C389 PC Card.
Slide the latching button toward the 3C389 PC Card.
You can leave the latching button retracted, so that if the
cable is yanked, the connector will disconnect from the
PC Card, possibly saving your PC from being pulled off a
table.
4 Insert the 3C389 PC Card in the slot (Figure 2-2).
If you are using a point enabler, note which slot
you use.
The 3C389 PC Card can go in only one way. If you feel
resistance before the 3C389 PC Card is fully inserted,
remove the 3C389 PC Card, turn it over, and reinsert it.
Figure 2-2 Inserting the 3C389 PC Card
2-4CHAPTER 2: INSTALLINGTHE TOKENLINK VELOCITY PC CARD
5 Connect the PC Card cable to the network port.
■ If your network uses unshielded twisted pair (UTP)
cabling, attach the RJ-45 (8-pin modular) connector
on the 3C389 PC Card cable (P/N 38H7044) to the
RJ-45 network port (Figure 2-3).
To RJ-45
network port
RJ-45 connector
Credit card
adapter cable
Figure 2-3 Modular UTP Cable for the 3C389 PC Card
■ If your network uses shielded twisted pair (STP)
cabling, attach the RJ-45 connector on the 3C389
PC Card cable (P/N 38H7044) to the RJ-45 end of the
STP connector (P/N 73G8315). Attach the STP
connector to the STP network port (Figure 2-4).
The STP connector has been specifically designed to
work with the 3C389 PC Card.
network port
Code
number
RJ-45
Figure 2-4 RJ-45 to STP Connector
100
STP
Data connector
Verify that you are using the correct STP connector. The
correct STP connector is labeled with the number 100.
6 Turn on the power to the PC.
Proceed to Chapter 3 for instructions on how to install
the network drivers.
Removing the 3C389 PC Card
Removing the cable from the 3C389 PC Card makes the
operating system behave as if the PC Card has been
physically removed from the slot. See Appendix C for
more information.
Follow these steps to remove the 3C389 PC Card:
1 Switch off the power to the PC.
2 With the cable still attached to the 3C389 PC Card,
remove the 3C389 PC Card from the PC.
3 To detach the cable from the 3C389 PC Card, retract
the latching button (the half-circle in the center of
the connector) by sliding it backwards away from
the 3C389 PC Card.
4 Disconnect the cable connector from the 3C389
PC Card.
Removing the 3C389 PC Card2-5
INSTALLINGTHE NETWORK
3
DRIVERS
This chapter describes how to install network LAN drivers
other than IBM LAN Client. After installation, some
network drivers must be configured using LANAID, an
installation and diagnostic utility described in Chapter 5.
If you are installing the IBM LAN Client go directly to
Chapter 5.
Consult the following lists to determine if LANAID is
required to configure your network driver:
LANAID is not required to configure the following
drivers:
■ Windows 95
■ Windows NT 3.51
■ Windows NT 4.0
■ OS/2 NDIS 2 device driver using LAPS
■ OS/2 NDIS 2 device driver using MPTS
■ OS/2 NDIS 2 device driver using other installation
programs
■ Warp Connect
■ Warp Server
■ Novell NetWare Client 32 for Windows 95
LANAID is required to configure the following
drivers:
■ IBM LAN Support Program/Native
■ IBM LAN Client
■ DOS Client 16 for Novell NetWare lower than 3.12
■ DOS Client 16 for Novell NetWare 3.12 and 4.0
3-2CHAPTER 3: INSTALLINGTHE NETWORK DRIVERS
■ DOS Client 16 for Novell NetWare 4.01 and higher
■ OS/2 NetWare Client
■ Artisoft LANtastic 6.0, 7.0
■ Banyan VINES 6.X
■ Microsoft LAN Manager/NDIS
■ Windows for Workgroups\NDIS 2
■ Other DOS NDIS environments
The installation procedures for the following drivers are
found in the README.TXT file shipped on TokenDisk
diskette #1:
■ Microsoft LAN Manager, NDIS
■ ARTISOFT LANtastic Versions 6.0 and 7.0
■ Banyan VINES, NDIS
■ DOS Client-16 for Novell NetWare lower than 3.12
■ DOS Client-16 for Novell NetWare 3.12 and 4.0
■ OS/2 NetWare Client
■ OS/2 NDIS 2 Device Driver Using Other Installation
Programs
The most recent 3Com drivers are available from the
3Com World Wide Web site (www.3com.com) or the
3Com Bulletin Board Service. See Appendix D for
information on how to connect with 3Com online
services.
Windows 95 Installation
You will need your Windows 95 diskettes or CD-ROM
during installation, unless you have copied the .CAB files
to your hard disk.
TokenDisk diskette #2 contains the device driver for
Windows 95. It is recommended that you use the
Windows 95 3C389 PC Card support software.
Loading...
+ 60 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.