3COM TokenLink VelocityTM XL PCI User Manual

Download

TokenLink® Velocity™ XL PCI Network Interface Card User Guide

A member of the high-performance TokenLink Velocity family

http://www.3com.com/

Part No. 09-1116-000 Published November 1997

3Com Corporation ■ 5400 Bayfront Plaza ■ Santa Clara, California ■ 95052-8145

Copyright © 1997, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.

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 notiﬁcation 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 ﬁtness 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:

United States Government Legend:

and developed solely at private expense. Software is delivered as Commercial Computer Software as deﬁned in DFARS 252.227-7014 (June 1995) or as a commercial item as deﬁned in FAR 2.101(a) and as such is provided with only such rights as are provided in 3Com’s standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this User Guide.

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries.

3Com, the 3Com logo, Net Age, Parallel Tasking, TokenDisk, TokenLink, and Transcend are registered trademarks of 3Com Corporation. AutoLink, DynamicAccess, and Velocity are trademarks of 3Com Corporation. 3ComFacts is a service mark of 3Com Corporation.

Artisoft and LANtastic are registered trademarks of Artisoft, Inc. Banyan and VINES are registered trademarks of Banyan Systems Incorporated. Compaq is a trademark of Compaq Computer Corporation. CompuServe is a registered trademark of CompuServe, Inc. DEC and PATHWORKS are registered trademarks of Digital Equipment Corporation. Intel and Pentium are registered trademarks of Intel Corporation. IBM, NetView, and OS/2 are registered trademarks and Warp is a trademark of International Business Machines Corporation. BootWare is a registered trademark of LANWorks, Inc. Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. TROPIC is a trademark of National Semiconductor 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. Guide written by Phillip Schlueter. Edited by Nancy Kurahashi. Illustrated by Mary Inden. Produced by

Georgi Felix.

All technical data and computer software is commercial in nature

Lifetime Limited Warranty

3Com’s EtherLink®, Fast EtherLink, TokenLink®, TokenLink Velocity™, ATMLink™ PCI, and FDDILink™ network interface cards have a 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.

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

■

Belgium, Netherlands, Luxembourg

3Com Benelux B.V., Marketing Department Nevelgaarde 8-9 3436 ZZ Nieuwegein Netherlands

■

France, Israel

3Com France, Marketing Department Immeuble McKinley BP 965 1, Avenue de l’Atlantique 91976 Les Ulis Courtaboeuf Cedex France

■

Italy, Greece, Spain, Portugal, Malta

3Com Mediterraneo Srl, Marketing Department Via Michelangelo Buonarroti, 1 20093 Cologno Monzese MI Italy

■

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

ONTENTS

BOUT THIS GUIDE

Finding Speciﬁc Information in This Guide 1 Conventions 2

NTRODUCTION

High-Performance Features of the 3C359 NIC 1-2

Parallel Tasking II Performance 1-2 DynamicAccess Class of Service 1-2

Support for Full-Duplex/Dedicated Token Ring 1-3 Wake-up On LAN Capability 1-3 Other Features of the 3C359 NIC 1-3 Installation Overview 1-4

NSTALLING THE

Installation Requirements 2-1 Safety Precautions 2-1 Unpacking and Inspecting the 3C359 NIC 2-2 Inserting the 3C359 NIC 2-3

3C359 NIC

OVELL NETWARE ENVIRONMENTS

Installing a DOS 16-Bit Client Driver 3-1

Installing a DOS 16-Bit Client Automatically 3-1

AutoLink Software Functions 3-1 Before Using the AutoLink Conﬁguration Utility 3-2 Modifying AutoLink Default Settings 3-2 Running the AutoLink Program 3-2

AutoLink Troubleshooting 3-4 Installing a DOS 16-Bit Client Manually 3-4 Conﬁguring the DOS 16-Bit client Driver 3-5

iii

Installing DOS Client32 3-6 Installing an OS/2 Client Driver for NetWare 3-7

Selecting the Appropriate NIC Address 3-8 Displaying the Universal Address 3-8 Installing the Novell OS/2 Requester 3-9 Conﬁguring the Novell OS/2 Requester 3-11

Installing a NetWare Server Driver 3-12

Driver Support 3-12 Installation Instructions 3-13

Installing the Driver in an Existing NetWare Environment 3-13

Installing the Driver as Part of a New Server Installation or Upgrade to NetWare 4.1x 3-20

ICROSOFT WINDOWS ENVIRONMENT

Drivers Available for Windows 4-1

NDIS 4 Miniport Driver 4-1 NDIS 3 Miniport Driver 4-2

Installing a 3C359 NIC Driver for Windows Environments 4-2

Before Installing a Windows Driver 4-2 Installing a Driver for Windows 95 4-3

About Microsoft Windows 95 Versions 4-3

Installing a Driver for Windows 95 Version 950 4-4

Installing a Driver for Windows 95 Version 950b,

OSR2 4-5 Installing a Driver for Windows NT 4.0 4-6 Installing a Driver for Windows NT 3.51 4-7

Selecting Ring Speed 4-8

Setting Ring Speed for Windows 95 4-8 Setting Ring Speed for Windows NT 4.0 4-12

Deﬁning a Locally Administered Network Address 4-14

Deﬁning the LAA Address for Windows 95 4-14

Displaying the Current Network Address for

Windows 95 4-14

Setting the LAA Address for Windows 95 4-15 Deﬁning the LAA Address for Windows NT 4-18

Conﬁguring Class of Service 4-19

Before Starting Class of Service Conﬁguration 4-20 Enabling Class of Service 4-20 Adding Class of Service Ranges and Protocols 4-23 Using Class of Service Advanced Options 4-25 Class of Service Advanced Options Settings 4-26

IBM E

Installing a Driver for Various IBM Environments 5-1

Conﬁguring IBM Host Connectivity 5-5

3C359 NIC LEDs 6-1 Using the Diagnostic Program 6-2

NVIRONMENTS

Installing the IBM LAN Support Program (DXMAID) and the DOS NDIS 2.01 Driver 5-1

Installing a Driver for IBM DOS LAN Services 5-2 Using IBM MPTS to Install a Driver for OS/2 5-3

Adding the MS-DLC Network Protocol for Windows for Workgroups 5-6

Adding the 32-Bit DLC Network Protocol for Windows 95 5-7

Adding the 32-Bit DLC Network Protocol for Windows NT 5-9

ROUBLESHOOTING

DOS Diagnostic Tests 6-2

Register Write/Read Test 6-2 Local RAM Write/Read Test 6-2 Timer Test 6-2 Open NIC for Ring Operation Test 6-3 Ring Operations Test 6-3

Close NIC Test 6-3 Running the DOS Diagnostic Tests 6-3 Changing the DOS Test Setup 6-5

PECIFICATIONS

3C359 NIC Speciﬁcations A-1 Connector Pin Assignments A-3

DB-9 Connector Pin Assignments A-3 RJ-45 Connector Pin Assignments A-3

Cable Requirements A-4

HANGING CONFIGURATION SETTINGS

Using the Conﬁguration Program B-1 Adjusting Conﬁguration Settings B-4

Ring Speed B-4 Boot ROM B-5 Memory Limit of 1 Megabyte B-5

Changing Conﬁguration for Multiple NICs B-5

ECHNICAL SUPPORT

Online Technical Services C-1

World Wide Web Site C-1 3Com Bulletin Board Service C-1

Access by Analog Modem C-2

Access by Digital Modem C-2 3ComFacts Automated Fax Service C-2 3ComForum on CompuServe Online Service C-3

Support from Your Network Supplier C-3 Support from 3Com C-4 Returning Products for Repair C-6

LOSSARY

NDEX

3COM C

ORPORATION LIMITED WARRANTY

FCC C

LASS

B S

TATEMENT

FCC D

ECLARATION OF CONFORMITY

3COM END U

SER SOFTWARE LICENSE AGREEMENT

vii

IGURES

1-1

TokenLink Velocity XL PCI 3C359 NIC 1-1

2-1

Removing the Expansion Slot Cover 2-3

2-2

Inserting the 3C359 NIC 2-4

3-1

Diagnostic and Manual Conﬁguration Program Window 3-9

4-1

Network Window 4-9

4-2

PCI Token Ring Adapter Properties Window: Driver Tab 4-10

4-3

Displaying Ring Speed Setting 4-10

4-4

Manually Setting Ring Speed 4-11

4-5

3Com TokenLink Velocity XL PCI Adapter Dialog Box 4-13

4-6

Conﬁguration and Diagnostic Program Window 4-15

4-7

Network Window 4-16

4-8

PCI Token Ring Adapter Properties Window: Driver Tab 4-17

4-9

Entering Current Network Address 4-17

4-10

3Com TokenLink Velocity XL PCI Adapter Dialog Box 4-19

4-11

DynamicAccess: Select Adapter Window 4-21

4-12

3Com Class of Service Setup Window 4-22

4-13

Class of Service Additional Ranges Window 4-24

4-14

Additional Ranges Window Showing Data 4-25

4-15

Class of Service Advanced Options Window 4-26

6-1

NIC LEDs 6-1

6-2

Test Menu 6-4

6-3

DOS Diagnostic Program Run Tests Dialog Box 6-4

6-4

DOS Diagnostic Program Test Setup Dialog Box 6-5

A-1

DB-9 Connector Pin Assignments A-3

A-2

RJ-45 Connector Pin Assignments A-4

B-1 Conﬁguration and Diagnostic Program Screen B-2 B-2 Install Menu B-2 B-3 NIC Conﬁguration Screen B-3 B-4 Conﬁguration Option Setting Dialog Box B-3

TABLES

1 Notice Icons 2 2 Text Conventions 2

3-1 Location of NetWare Support Modules 3-13 3-2 TLNKPODI.LAN Load Parameters 3-16

B-1 Initial Settings of 3C359 NIC Conﬁguration Options B-4

ABOUT THIS GUIDE

About This Guide provides an overview of this guide, describes guide conventions, and tells you where to look for speciﬁc information.

This guide describes how to install, conﬁgure, and troubleshoot the 3C359 TokenLink® Velocity™ XL PCI network interface card (NIC). This NIC is referred to as the 3C359 NIC in this guide.

The HELP directory on TokenDisk® diskette #1 contains the latest technical information.

This guide is intended for network installers who are familiar with local area networking (LAN) technology, token ring technology, and network interface card installation.

If the information in the release notes shipped with your product differs from the information in this guide, follow the instructions in the release notes.

Finding Speciﬁc Information in This Guide

This table shows the location of speciﬁc information in this guide.

If you are looking for Turn to

3C359 NIC features and product overview Chapter 1 3C359 NIC installation overview Chapter 1 3C359 NIC installation and cabling procedures Chapter 2 Driver installation procedures for Novell NetWare environments Chapter 3 Driver installation procedures for Microsoft Windows environments Chapter 4 Class of Service (also known as Traffic Prioritization)

configuration procedures Auto ring speed detection information Chapter 4 Driver installation procedures for IBM environments Chapter 5

(continued)

Chapter 4

2 ABOUT THIS GUIDE

If you are looking for Turn to

Host connectivity configuration procedures for IBM environments Chapter 5 Troubleshooting tips and procedures Chapter 6 Specifications for cabling and connector pin assignments Appendix A Instructions about changing configuration settings for the 3C359 NIC

through the DOS Configuration and Diagnostic Program Technical support information Appendix C

Appendix B

Conventions

Table 1 and Table 2 list conventions that are used throughout this guide.

Table 1 Notice Icons

Icon Notice Type Description

Information note Important features or instructions

Caution Information to alert you to potential damage to a

Warning Information to alert you to potential personal injury

Table 2 Text Conventions

Convention Description

Syntax The word “syntax” means you must evaluate the syntax

Screen displays This typeface represents information as it appears on

(continued)

program, system, or device

provided and supply the appropriate values. Placeholders for values you must supply appear in angle brackets. Example:

Enable RIPIP by using the following syntax:

SETDefault !<port> -RIPIP CONTrol = Listen

In this example, you must supply a port number for <port>.

the screen.

Table 2 Text Conventions (continued)

Convention Description

The words “enter” and “type”

Menu commands and buttons

Words in italicized type

When you see the word “enter” in this guide, you must type something, and then press the Return or Enter key. Do not press the Return or Enter key when an instruction simply says “type.”

Menu commands or button names appear in italics. Example:

From the Help menu, select Contents.

Italics emphasize a point or denote new terms at the place where they are defined in the text.

Conventions 3

INTRODUCTION

The 3Com TokenLink® Velocity™ XL PCI network interface card (NIC) is a high-performance token ring network adapter for personal computers (PCs) with a Peripheral Component Interconnect (PCI) bus.

The 3C359 NIC provides a high-performance 32-bit PCI local bus interface with bus mastering that runs at a clock speed of 33 MHz.

Data

Figure 1-1 TokenLink Velocity XL PCI 3C359 NIC

1-2 CHAPTER 1: INTRODUCTION

High-Performance Features of the 3C359 NIC

The 3C359 NIC delivers the token ring industry’s highest performance for the lowest cost, and is designed to provide years of trouble-free operation. This section describes the NIC’s high-performance features.

Parallel Tasking II Performance

The 3C359 NIC’s design incorporates new Parallel Tasking® II performance, which takes advantage of the latest developments in PCI bus design to deliver the fastest data throughput and lowest CPU utilization of any token ring NIC.

Parallel Tasking II performance is built upon a solid foundation of proven Parallel Tasking architecture, which introduced data pipelining and overlapping task processing to improve throughput and achieve the industry’s fastest data transmission and reception speeds.

DynamicAccess Class of Service

™

3Com’s DynamicAccess 3C359 NIC for optimized performance and control. With DynamicAccess Class of Service (Trafﬁc Prioritization), you can select time-critical applications that require the highest-priority access to your network—such as multimedia sessions. Based on your selection, the network device driver recognizes high-priority applications, prioritizes their data transmissions, and accelerates their data transmissions in the following ways:

■ The NIC implements dual queues, allowing high-priority

trafﬁc to be queued for transmission before normal-priority trafﬁc.

■ High-priority trafﬁc is allowed to request and use

high-priority tokens (as speciﬁed in the IEEE 802.5 standard). This tends to reduce the latency experienced in acquiring a suitable token for transmission onto the network.

Class of Service (Trafﬁc Prioritization) is available only with the NDIS 4.0 miniport driver supporting the following operating systems: Windows NT 4.0 and Windows 98.

software adds intelligence to the

Wake-up On LAN Capability 1-3

Support for Full-Duplex/Dedicated Token Ring

Full-duplex/Dedicated Token Ring (DTR) is an enhancement to the IEEE 802.5 standard that allows a token ring switch port to be dedicated to a station.

In full-duplex mode, a station can simultaneously transmit and receive independent data streams for potential data throughput of 32 Mbps. The 3C359 NIC can operate in full-duplex mode when attached to a DTR switch.

Wake-up On LAN Capability

The 3C359 NIC provides Wake-up On LAN (WOL) capability, which, with the appropriate applications, lets you remotely perform installations, software upgrades, and other management tasks from a central location, even if the PCs in your network have been turned off.

The 3C359 NIC’s WOL support conforms to the Advanced Conﬁguration and Power Interface OnNow/(ACPI) speciﬁcation, and applies only to PCs conforming to PCI Bus Power Management Interface Speciﬁcation 1.0 that have power management capabilities running under Microsoft Windows 98 or Windows NT 5.0.

Other Features of the 3C359 NIC

The 3C359 NIC supports the following features:

■ Completely automatic hardware conﬁguration through

PCI registration.

■ Auto ring speed detection option that permits the

3C359 NIC drivers for all supported environments to detect and operate at the current ring data rate.

■ LED ring speed indicators.

■ Boot ROM socket that supports the 3C359-TRIROM,

an optional token ring boot ROM with BootWare for TCP/IP, NetWare, and RPL environments. The TriROM allows you to boot PCs (with or without hard drives) remotely from a LAN server. (The TriROM is sold and documented separately. Contact your local reseller for further details.)

1-4 CHAPTER 1: INTRODUCTION

■ AutoLink

™

16-bit client drivers.

■ Plug and Play for worry-free installation.

■ Promiscuous mode support for Windows 95,

Windows NT, and Novell NetWare drivers. While operating in this mode, the NIC receives and forwards all network packets that arrive (regardless of the node to which they are addressed), allowing you to easily identify and resolve problems on the network.

■ DOS diagnostic programs to aid problem solving.

■ Full connectivity with IBM AS/400 and mainframe

computers, and compatibility with legacy IBM applications.

■ Multicast ﬁltering.

■ CISPR B and FCC B certiﬁcation for reduced

electromagnetic interference when using either STP or UTP cables.

■ On-board RJ-45 and DB-9 ports for connecting UTP or

STP cables without using an external media ﬁlter.

Installation Overview

This section outlines the major steps for completing a 3C359 NIC installation. It also indicates the sections in this guide that can help you at each stage.

Follow these steps to successfully install and conﬁgure the 3C359 NIC.

1 Insert the 3C359 NIC in a PCI bus master slot in

your PC. Connect the NIC to a compatible network component using the appropriate cables.

See Chapter 2, “Installing the 3C359 NIC,” for detailed instructions.

2 Install the network driver that is appropriate for

your PC’s operating system environment from the TokenDisk diskettes or from the TokenDisk CD.

Driver installation instructions in this guide are organized by operating system environment. See the table of contents to locate the chapter containing the installation instructions appropriate for your environment.

software for easy installation of NetWare

Installation Overview 1-5

3 Conﬁgure features that are appropriate for your

installation, if necessary. For example:

■ Auto Ring Speed Detection:

Automatically enabled for all drivers, this feature can be disabled (recommended for servers) if necessary.

■ Class of Service:

Automatically disabled, this feature can be enabled for the NDIS 4 driver running under Windows NT or Windows 98.

■ Locally Administered Address (LAA):

You can manually deﬁne an LAA that overrides the NIC’s universal address encoded during manufacturing.

See feature conﬁguration instructions in the chapter for your operating system environment.

4 Run diagnostics, if necessary.

If you experience problems during the installation process, you can check the conﬁguration setup and test for physical NIC problems by running the DOS Conﬁguration and Diagnostic Program, located on TokenDisk diskette #1 or on the TokenDisk CD.

See Chapter 6, “Troubleshooting,” for instructions on using the Conﬁguration and Diagnostic Program. This chapter also describes how to isolate and solve various hardware and network cabling problems.

INSTALLING THE

3C359 NIC

This chapter describes inserting the 3C359 NIC in a PC and connecting the PC to a network.

Installation Requirements

Installing the 3C359 NIC requires the following:

■ A PCI-bus personal computer with an 80486, Pentium,

or other Intel-compatible processor

■ A 32-bit or 64-bit PCI expansion slot that supports

bus mastering

■ A high-density 3.5-inch disk drive or CD-ROM drive

■ Category 3, 4, or 5 UTP cables, or type 1 or 6 STP cables

■ TokenDisk diskettes #1 and #2 (or TokenDisk CD)

containing the AutoLink installation program, network driver software, the DOS Conﬁguration and Diagnostic Program, and online user documentation (CD only)

Safety Precautions

WARNING: PCs operate with voltages that can be lethal. Before removing the cover, follow these steps to protect yourself and the PC.

1 Remove any diskettes and CDs from the computer’s

disk drives.

2 Turn off the PC and unplug it.

CAUTION: To avoid permanent damage to the NIC or other computer circuitry, always turn off the computer’s power when inserting or removing the NIC.

3 Disconnect all cables that are connected to

the computer.

4 Remove jewelry from your hands and wrists.

2-2 CHAPTER 2: INSTALLING THE 3C359 NIC

5 Reduce any static electricity on your body.

Each NIC is packed in an antistatic container to protect it during shipment. To avoid damaging any static-sensitive components after removal from the container, be sure to reduce any static electricity on your body.

One way to reduce static electricity is to touch an unpainted part of the computer’s metal chassis. You can maintain grounding by wearing an antistatic wrist strap attached to the chassis.

6 Verify that your tools are nonconducting or insulated.

Your tools should include a ﬂat-head screwdriver and a Phillips-head screwdriver. To avoid permanent damage to the NIC or other computer circuitry, use only insulated or nonconducting tools.

Unpacking and Inspecting the 3C359 NIC

The contents of the 3C359 NIC package follow. If items are missing, contact your authorized network supplier immediately.

■ TokenLink Velocity XL PCI 3C359 NIC

■ TokenDisk diskettes #1 and #2

■ TokenDisk CD

■ TokenLink Velocity XL PCI Network Interface Card User

Guide and Quick Start Guide

1 Unpack the 3C359 NIC and remove it from its

antistatic container. 2 Lay the NIC on its antistatic container. 3 Inspect the NIC for visible signs of damage.

If you ﬁnd damage, immediately notify your authorized

network supplier and the carrier that delivered the NIC.

4 If you have purchased the separate TriROM accessory,

install it in the 3C359 NIC’s boot ROM socket

according to instructions supplied with the TriROM.

Complete the Product Registration Card and return it to

3Com, or call 1-800-NET-3Com for immediate registration.

Inserting the 3C359 NIC

32-bit PCI slots

ISA/EISA slots

Follow these steps to insert the 3C359 NIC:

1 Remove the computer’s cover and select a PCI

expansion slot that supports bus mastering.

You can install the 3C359 NIC in either a standard bus master 32-bit slot, as shown in Figure 2-1, or a newer bus master 64-bit slot. If both slot types are available in your PC, place the NIC in the 32-bit slot.

Inserting the 3C359 NIC 2-3

Mounting screw

Expansion slot cover

Figure 2-1 Removing the Expansion Slot Cover

Verify that the selected slot is a PCI bus master slot by consulting your computer documentation, manufacturer, or vendor.

2 Unfasten and remove the expansion slot cover

(Figure 2-1) from the selected bus master PCI slot.

Store the expansion slot cover for future use, but retain the mounting screw for securing the NIC.

2-4 CHAPTER 2: INSTALLING THE 3C359 NIC

3 Insert the 3C359 NIC in an empty PCI bus master slot

and secure the mounting screw, as shown in

Figure 2-2.

Make sure the NIC is completely seated in the slot by

pushing down ﬁrmly on both ends of the NIC. When the

NIC is correctly seated, the gold connecting ﬁngers inserted

in the slot do not show.

Note the slot number of the NIC. You may need it during

driver installation.

Mounting screw

32-bit PCI slots

Figure 2-2 Inserting the 3C359 NIC

ISA/EISA slots

4 Replace the unit’s cover and reconnect any cables that

you may have disconnected from other devices (see

“Safety Precautions”). 5 Turn the power on.

When power is turned on, the PCI system automatically

conﬁgures the NIC.

Inserting the 3C359 NIC 2-5

6 Connect one of the following network cable types to

the 3C359 NIC:

■ Shielded twisted-pair (STP) cable with a DB-9 connector

■ Unshielded twisted-pair (UTP) cable with an RJ-45

connector

TokenLink Velocity NICs support industry-standard token ring Category 3, 4 or 5 UTP or types 1 or 6 STP cabling. These cables meet IEEE 802.5 speciﬁcations. (See Appendix A, “Speciﬁcations,” for detailed information regarding cable requirements and connector pin assignments for the 3C359 NIC.)

7 Connect the other end of the cable to a network dual

access unit (DAU), a multistation access unit (MAU), controlled access unit (CAU), or a token ring switch.

The 3C359 NIC can operate in full-duplex mode when attached to a Dedicated Token Ring (DTR)-enabled switch. Full-duplex mode is enabled automatically.

8 Return all packing materials to the shipping container.

If it is necessary to return the 3C359 NIC to 3Com, pack it in the original (or equivalent) packing material to maintain the warranty.

NOVELL NETWARE

ENVIRONMENTS

This chapter describes how to install a 3C359 NIC network device driver for various Novell NetWare network operating system environments.

Before you install a NetWare driver, make sure that the 3C359 NIC is inserted in the PC as described in Chapter 2.

Installing a DOS 16-Bit Client Driver

This section describes installing the DOS 16-bit client driver using two methods:

■ Automatically, using the 3Com AutoLink software utility

■ Manually, using a NetWare installation utility and

TokenDisk diskette or CD

Installing a DOS 16-Bit Client Automatically

The 3Com AutoLink software utility automatically conﬁgures one 3C359 NIC and installs the DOS 16-bit ODI client network driver for NetWare 3.12 and 4.1x systems. This section describes running the AutoLink program.

AutoLink Software Functions

AutoLink software conﬁgures your PC as a NetWare DOS ODI client. The AutoLink installation utility performs the following functions:

■ Installs a DOS NetWare Universal Client Virtual Loadable

Module (VLM) from TokenDisk diskette #1, or from the TokenDisk CD.

The AutoLink installation utility cannot be used to install multiple 3C359 NICs.

■ Modiﬁes the CONFIG.SYS, AUTOEXEC.BAT, and NET.CFG

ﬁles. (The previous versions of these ﬁles are renamed CONFIG.3CM, AUTOEXEC.3CM, and NET.3CM.)

3-2 CHAPTER 3: NOVELL NETWARE ENVIRONMENTS

The AutoLink installation utility is a DOS application. It cannot

run in a Windows NT or Windows 95 DOS window, and

it cannot be used to install an OS/2, Windows NT, or

Windows 95 client. For these operating systems, use the

manual installation procedure described later in this chapter.

Before Using the AutoLink Conﬁguration Utility

Make sure that the following steps have been performed

before using the AutoLink installation utility:

■ The 3C359 NIC is installed in your DOS-based PC and is

connected to the network.

■ NetWare version 3.12 or 4.1x is installed on the server.

■ A NetWare user account is available with a user ID

and password.

■ DOS version 3.2 or later is installed on the client PC, and

the PC has been booted under DOS.

■ The PC has at least 1 MB of free hard disk space.

Modifying AutoLink Default Settings

Use the AUTOLINK.CFG ﬁle to modify the AutoLink

installation process. The AUTOLINK.CFG ﬁle in the

\AUTOLINK directory on TokenDisk diskette #1 (or on

the TokenDisk CD) contains default settings and descriptions

of the AUTOLINK parameters.

See the AUTOLINK.TXT ﬁle in the \AUTOLINK directory for

information on customizing AutoLink and server support.

Running the AutoLink Program

The AutoLink program loads the NetWare DOS ODI 16-bit

client driver. To run the AutoLink program, follow these steps:

1 Install the 3C359 NIC and connect it to the network as

described in Chapter 2. 2 Restart the PC from DOS, verifying that no network

drivers are loaded.

If you are using DOS version 6.x, press F5 after the “Starting

MS-DOS...” message is displayed as DOS loads. This prevents

any drivers or memory managers from loading. If you are

using an earlier version of DOS, boot from a DOS diskette

that does not contain drivers.

Installing a DOS 16-Bit Client Driver 3-3

3 If you are using the 3.5-inch diskettes, insert

TokenDisk diskette #1 in the drive and enter:

If you are using the TokenDisk CD, insert it in the CD-ROM drive and enter the drive letter. For example:

4 Enter:

autolink

An AutoLink information window is displayed.

5 From the AutoLink Information window, press Enter.

The ﬁrst time you use AutoLink, the 3Com software license appears.

6 To accept the terms and conditions, enter:

To view the full text of the license agreement, press F1.

7 When the information window appears, press Enter

to continue.

A status message appears, followed by a prompt for the ring speed of your network.

8 Enter the ring speed. 9 When the auto installation process is ﬁnished,

remove the TokenDisk diskette or TokenDisk CD and restart your PC.

The login prompt for a NetWare server appears.

10 Log in to the NetWare server with your ID and

password.

Your PC is now conﬁgured as a NetWare DOS ODI client. If you experience problems using AutoLink, see the

next section, “AutoLink Troubleshooting.” If you cannot connect to the NetWare server after running AutoLink, see Chapter 6, “Troubleshooting.”

3-4 CHAPTER 3: NOVELL NETWARE ENVIRONMENTS

AutoLink Troubleshooting

If you experience problems when using the AutoLink

program, display or print the AUTOLINK.LOG ﬁle, which

contains a log of the events that occurred during the

AutoLink installation and conﬁguration process.

1 To display the ﬁle, enter the following DOS

command:

type autolink.log | more

2 To print the ﬁle, connect to a local printer and enter:

copy autolink.log prn

print autolink.log

Installing a DOS 16-Bit Client Manually

If you did not use the AutoLink conﬁguration utility, follow

these steps to install the DOS 16-bit client driver for NetWare:

1 Insert the Novell NetWare Client for DOS and

Microsoft Windows Disk 1 and make that drive the

active drive. For example, enter:

2 Enter the following command:

install

Follow the displayed instructions as they appear.

3 When prompted to select the driver for your network

board, scroll down through the list titled Network

Boards. Select Other Drivers, and press Enter. 4 If you are using the 3.5-inch TokenDisk diskettes,

insert TokenDisk diskette #1 in the drive and make

that drive the active drive. For example, enter:

If you are using the TokenDisk CD, insert it in the

CD-ROM drive and enter the location of the DOS

16-bit client driver:

<drive>\netware\nwclient

5 Select 3Com TokenLink Velocity XL PCI and press Enter.

The program copies all relevant ﬁles and makes required

changes to the AUTOEXEC.BAT and CONFIG.SYS ﬁles.

Installing a DOS 16-Bit Client Driver 3-5

6 Copy the microcode ﬁle TLNKP.MAC to the NetWare

client directory on the hard drive. For example, if you are using the 3.5-inch TokenDisk diskettes, enter:

copy a:\tlnkp.mac c:\nwclient

If you are using the TokenDisk CD, substitute the appropriate drive in the path.

7 Restart your PC to start the NetWare 16-bit client.

This completes the procedure for manually installing a NetWare DOS 16-bit client driver.

Conﬁguring the DOS 16-Bit Client Driver

You can edit the NET.CFG ﬁle to change the ring speed or transmit/receive mode. Follow these steps:

1 Using a word processor or text editor, such as the

DOS Editor, open the C:\NWCLIENT\NET.CFG ﬁle.

2 Scroll through the ﬁle and locate the following lines:

LINK DRIVER TLNKPODI

3 Add the appropriate keywords as shown below.

LINK DRIVER TLNKPODI

ringspeed <auto | 4 | 16> <classic | dtr>

where RINGSPEED AUTO forces the driver to detect the current ring speed and to connect at that speed. The default setting is AUTO. You do not need to specify the AUTO setting; it is automatically enabled. If the connection fails, try one of the other speed settings: 4 or 16. A setting of 4 forces the driver to always open the connection at 4 Mbps; a setting of 16 forces the driver to always open the connection at 16 Mbps.

The keyword CLASSIC sets the transmit/receive mode to the half-duplex Token Passing Protocol (TKP). The keyword DTR sets the transmit/receive mode to the full-duplex Transmit Immediate Protocol (TXI). Operating in TXI mode is recommended; if full-duplex mode fails, try TKP mode.

3-6 CHAPTER 3: NOVELL NETWARE ENVIRONMENTS

Installing DOS Client32

This section describes installing the TLNKPODI.LAN DOS

Client32 driver for a NetWare Client32 environment. For

the driver installation procedure, you need the Novell

Client32 diskettes and either the TokenDisk CD or

TokenDisk diskette #1.

1 Insert the Novell Client32 setup diskette #1 into a drive,

switch to that drive, and enter the Install command. For

example, if the diskette is in drive A, enter:

a:\install

2 Read the Novell information window and press Enter.

The displayed window lists installation options.

3 Use the arrow keys to move to the options you need.

Press the spacebar to select the option.

The system prompts you for conﬁguration information.

4 Conﬁrm the conﬁguration and press Enter. 5 If your conﬁguration requires TCP/IP, supply the

IP Address, Router, Subnetmask, DNS Domain, and

Domain Name Server Address. Press Enter. 6 When prompted for the LAN Driver type, select 32-bit

and press Enter.

The 32-bit Network Board Drivers window is displayed.

7 When prompted to select the driver, scroll to User

speciﬁed 32-bit driver. 8 Insert TokenDisk diskette #1 in the drive or the

TokenDisk CD in the CD-ROM drive. Enter the

following path:

<drive>:\netware\client32

9 Select TokenLink Velocity XL PCI and press Enter.

The system allows you to change the conﬁguration.

10 To change a parameter, select it and press Enter. Type

the new value. When you are ﬁnished changing

parameters, press Enter.

Installing an OS/2 Client Driver for NetWare 3-7

11 When the path for the conﬁguration ﬁles is

displayed, verify that the path is correct and press Enter.

12 Press Enter again to return to DOS and edit the

STARTNET.BAT ﬁle.

13 Add the NIC’s slot number in the STARTNET.BAT ﬁle

as follows:

load c:\novell\client32\tlnkpodi.lan frame=token-ring msb slot=<nnnn>

where <nnnn> is the slot number.

If you do not know your NIC’s slot number, you can turn off your PC, remove the cover, and check the slot.

14 On the same LOAD line, you can set the NIC’s ring

speed as follows.

load c:\novell\client32\tlnkpodi.lan...ringspeed=<auto | 4 | 16>

where <auto | 4 | 16> is the ring speed setting:

■ Auto — Allows the NIC to automatically detect the ring

speed. (This is the default setting.)

■ 4 — Disables auto ring speed detection and sets the

NIC ring speed at 4 Mbps.

■ 16 — Disables auto ring speed detection and sets the

NIC ring speed at 16 Mbps.

15 Restart your workstation to start Client32.

The system prompts you for the 3C359 NIC’s slot when the TLNKPODI.LAN driver is loaded.

Installing an OS/2 Client Driver for NetWare

This section describes installing the driver for an OS/2 client. Before installing the OS/2 ODI driver from the TokenDisk diskette or TokenDisk CD, ensure that the OS/2 operating system is installed and that the computer boots without errors. Install the 3C359 NIC as described in Chapter 2.

The Novell NetWare OS/2 ODI driver (TLNKPODI.SYS) is available on the TokenDisk CD or TokenDisk diskette #1.

3-8 CHAPTER 3: NOVELL NETWARE ENVIRONMENTS

Selecting the Appropriate NIC Address

Before starting the OS/2 ODI client driver installation

process, you should decide whether the 3C359 NIC will use

the universal address or a locally administered address.

■ Universal address (UAA)—A default address for the

NIC. It is encoded on the NIC during manufacturing and is often called the “burned-in” address. For example: 00600891CCA8.

■ Locally administered address (LAA)—A user-assigned

address that overrides the NIC’s universal address. This address must consist of 12 hexadecimal digits in the range from X’4000 0000 0000’ to X’7FFF FFFF FFFF’ and must be unique throughout the network.

Displaying the Universal Address

The Conﬁguration and Diagnostic Program displays the

3C359 NIC’s universal address. Follow these steps to

display the universal address:

1 Boot from a DOS diskette to run the diagnostic

program. Display the DOS prompt. 2 If you are using the 3.5-inch TokenDisk diskettes,

insert TokenDisk diskette #1 in the drive and make

that drive the active drive. For example, enter:

If you are using the TokenDisk CD, insert it and

make the CD-ROM drive the active drive. For

example, enter:

3 Enter the following command:

3pcid

The Conﬁguration and Diagnostic Program window

is displayed as shown in Figure 3-1.

Installing an OS/2 Client Driver for NetWare 3-9

Figure 3-1 Conﬁguration and Diagnostic Program Window

4 Record for future reference the 12-digit universal

token ring address displayed on the Diagnostic and Conﬁguration Program window (Figure 3-1). For example:

Network Addr = 00600891CCA8

Next, continue with the next section to install Novell OS/2 Requester and the ODI LAN driver TLNKPODI.SYS.

Installing the Novell OS/2 Requester

Follow these steps to install Novell OS/2 Requester and the ODI LAN driver TLNKPODI.SYS:

1 Insert the Novell OS/2 Requester diskette, WSOS2_1,

in the drive.

2 At the OS/2 Full Screen prompt, make the drive

containing the diskette the active drive. For example, enter:

3 At the A: prompt, enter:

install

A NetWare Workstation for OS/2 Installation Utility menu appears.

3-10 CHAPTER 3: NOVELL NETWARE ENVIRONMENTS

4 Select Installation from the menu and then Requester

on Workstation. 5 Select a target directory for the Requester ﬁles. The

default is C:\NETWARE. Select OK.

A new menu appears with four options:

■ Edit CONFIG.SYS and Copy All Files (default)

■ Only Edit CONFIG.SYS

■ Only Copy Requester Files

■ Only Copy ODI LAN Driver Files

6 From this menu, select the option Edit CONFIG.SYS

and Copy All Files and then select OK.

A dialog box appears, asking for an ODI LAN driver and

presenting two options:

■ Do not upgrade the currently installed LAN driver

■ Choose from the list or type a driver name

7 Enter the driver name for the TokenLink Velocity

XL PCI NIC:

tlnkpodi.sys

8 When prompted, select the default conﬁguration:

IPX Support for DOS or Windows (OFF)

9 Select CONTINUE.

A new menu appears with three optional protocols:

■ SPX Support for OS/2 Sessions

■ NetBIOS Emulation for OS/2 Sessions

■ Remote Named Pipe Support

10 Select the appropriate protocol and save the

conﬁguration.

If no additional protocols are needed, do not select any

of the three options. Bypass this section by choosing Save

the conﬁguration.

A new menu appears, asking if you want to save changes

to the CONFIG.SYS ﬁle.

11 Save the ﬁle as C:\CONFIG.SYS and click OK

to continue.

A new window appears, conﬁrming that you want all ﬁles

copied to C:\NETWARE.

Installing an OS/2 Client Driver for NetWare 3-11

12 Click COPY and follow the displayed instructions.

Continue the installation and insert the appropriate OS/2 Requester diskettes when prompted.

After the OS/2 Utility diskette is installed, a window appears that requests information about the ODI LAN drivers. The default ODI LAN driver is TLNKPODI.SYS.

13 Insert TokenDisk diskette #1 or the TokenDisk CD in

the appropriate drive. 14 Select Copy Only the Default Driver and click OK. 15 Follow the displayed installation instructions and

insert the appropriate OS/2 Requester diskettes

when prompted.

When the installation is complete, a menu appears with the

following menu bar items:

■ Installation

■ Conﬁguration

■ Utilities

■ Readme

■ Help

A message is displayed, stating that the installation process

is complete. Follow the instructions, and continue with

conﬁguration steps in the following section.

Conﬁguring the Novell OS/2 Requester

When you have followed the displayed instructions at

the end of the Novell OS/2 Requester installation process,

a message appears concerning certain conﬁguration

requirements.

After reading the message regarding conﬁguration

requirements, follow these steps:

1 Click the Conﬁguration menu bar item and select

“This Workstation...” to check the NET.CFG ﬁle for

the proper NIC conﬁguration.

2 Verify the link driver header, node address, and

frame type.

3-12 CHAPTER 3: NOVELL NETWARE ENVIRONMENTS

Your NET.CFG ﬁle should look similar to the following:

LINK DRIVER TLNKPODI

Node Address 00608C112233 Frame Token-Ring MSB Frame Token-Ring_SNAP MSB

The node address should be set to the UAA or the LAA. Modify and save the NET.CFG ﬁle if the node address and frame type are not correct.

3 Remove the OS/2 Requester diskette and restart

the PC.

This completes the procedure for installing the OS/2 client driver for NetWare.

Installing a NetWare Server Driver

This section contains information about installing the TLNKPODI.LAN NetWare server driver for the 3C359 NIC in the following environments:

■ NetWare 3.12

■ NetWare 4.1x

The driver and associated ﬁles are located in the \NETWARE\NWSERVER directory on TokenDisk diskette #1.

Driver Support

The TLNKPODI server driver is a high-performance NetWare 4.1x-compliant server driver. It can be used in the following environments:

■ NetWare 4.1x servers

■ NetWare 3.12 servers

■ NetWare servers running SFT III in NetWare 4.1 (as an

The term “NetWare 4.1x-compliant” server driver in this ﬁle means that the HSM (hardware-speciﬁc module, or server driver) meets the Open Data-Link Interface (ODI) 3.3 speciﬁcation. Netware 3.12 servers using ODI 3.3 drivers need updated ﬁles from Novell. If you are installing the driver in a NetWare 3.12 server, download the LANDR9 and 312PTA.EXE ﬁles from Novell’s Web site.

IPX link, not as a mirrored server link)

Installation Instructions

This section has instructions for installing TLNKPODI in

two ways:

■ On a ﬁle server in an existing NetWare environment

running NetWare 3.12 or 4.1x. These instructions also apply to a new installation or upgrade to NetWare 3.12.

■ As part of a new NetWare 4.1x installation or an

upgrade to NetWare 4.1x.

Instructions in this section are written for TokenDisk

diskettes. If you are using the TokenDisk CD, substitute

the appropriate path where required.

Installing the Driver in an Existing

NetWare Environment

This section explains how to install TLNKPODI on a ﬁle server

already running NetWare 3.12 or 4.1x. The instructions in this

section should also be used for a new NetWare 3.12

installation or an upgrade to NetWare 3.12.

If you are in the process of upgrading to NetWare 4.1x,

proceed to “Installing the Driver as Part of a New Server

Installation or Upgrade to NetWare 4.1x.”

TokenDisk diskette #1 contains the server driver and versions

of Novell NetWare Loadable Modules (NLMs) required for all

NetWare 4.1x-compliant server drivers. You must use these

NLMs, or more recent versions, with TLNKPODI.

Table 3-1 shows the names, locations, and versions of the

support modules.

Table 3-1 Location of NetWare Support Modules

Installing a NetWare Server Driver 3-13

NetWare Version

4.1x \NETWARE\NWSERVER\4.1x\MSM.NLM

3.12 \NETWARE\NWSERVER\3.12\MSM31X.NLM

Drivers Available for Windows

3Com provides the following network device drivers for the 3C359 NIC in these Microsoft Windows environments:

■ NDIS 4 miniport driver

■ NDIS 3 miniport driver

NDIS 4 Miniport Driver

The NDIS 4 driver conforms to Microsoft’s latest NDIS 4.0 miniport speciﬁcation and supports the following Windows environments:

■ Windows 95 (version 950b, OSR2)

■ Windows 98 (PC 97 speciﬁcation)

■ Windows NT 4.0

The NDIS 4 driver provides the following 3C359 NIC capabilities:

■ DynamicAccess Class of Service (Trafﬁc Prioritization)

Although the NDIS 4 miniport driver is compatible with Windows 95 (version 950b, OSR2), it does not currently provide Class of Service support for this version of Windows 95.

■ Auto ring speed detection

■ Promiscuous mode

■ Locally administered network address (LAA) selection

Class of Service is disabled by default. You can enable this DynamicAccess feature during installation.

4-2 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Auto ring speed detection is enabled by default during NDIS 4 driver installation. You can disable this feature during installation if desired.

Promiscuous mode is automatically enabled and controlled for the 3C359 NIC by applications that require this feature. No user control is necessary.

You can assign a locally administered address (LAA) that overrides the NIC’s universal address “burned-in” during manufacturing.

NDIS 3 Miniport Driver

The NDIS 3 miniport driver is compatible with Microsoft’s NDIS 3.x miniport speciﬁcation, and supports the following Windows environments:

■ Windows 95 (version 950 and version 950b, OSR2)

■ Windows NT 3.51

The NDIS 3 driver supports all the 3C359 NIC features listed in the preceding section for the NDIS 4 driver except DynamicAccess Class of Service.

Installing a 3C359 NIC Driver for Windows Environments

This section describes installing drivers for the following operating system environments:

■ Windows 95 version 950

■ Windows 95 version 950b (OSR2)

■ Windows NT 4.0

■ Windows NT 3.51

Before Installing a Windows Driver

Before you install a Windows driver, make sure that the 3C359 NIC is inserted in the PC as described in Chapter 2, and that Windows is installed.

Have the Windows software accessible on diskettes, CD, or hard drive in case the installation utility requests protocol ﬁles from the Windows software library.

Installing a 3C359 NIC Driver for Windows Environments 4-3

If your network environment uses the TCP/IP communications protocol, you must obtain from your network administrator all the information you will need to deﬁne an IP address during the installation process.

Installing a Driver for Windows 95

This section describes installing the 3C359 NIC NDIS 4 driver or NDIS 3 driver for the following Microsoft Windows 95 versions:

■ Version 950 (950a, or “retail” version)

■ Version 950b (OEM Service Release 2, or OSR2)

About Microsoft Windows 95 Versions

The 3C359 NIC NDIS 4 driver installation procedures differ depending on the Windows 95 version installed on your PC.

Version 950 of Windows 95 If your PC did not come with Windows 95 already installed, you must install version 950 of Windows 95 (950a, or “retail” version) before you install the driver. Version 950 of Windows 95 is designed to upgrade Windows 3.x PCs.

Version 950b (OSR2) of Windows 95 Some PCs are sold with a special Windows 95 version already installed. Windows 95 OEM Service Release 2 (OSR2) is version 950b of Windows 95. An OEM Service Release is an updated version of a Microsoft product for PC original equipment manufacturers (OEMs) to preinstall on new PCs. Windows 95 version 950b contains some new hardware support and programs.

Finding the Windows 95 Version To determine which Windows 95 version you are using, open the Control Panel, select System, and read the System information under the General tab. If your release is version 4.00.950 (or

4.00.950a), you are using the “retail” version of Windows 95 (version 950). If your release is version 4.00.950b, you are using the OSR2 version of Windows 95 (version 950b).

4-4 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Installing a Driver for Windows 95 Version 950

Follow these steps to install the NDIS 3 driver for Windows 95 (version 950). It is assumed that you have completed the 3C359 NIC installation procedure described in Chapter 2.

1 Turn on the computer and start Windows 95.

Windows 95 automatically detects the new hardware in the PC. Windows 95 displays the New Hardware Found window.

2 Select Driver from disk provided by hardware

manufacturer and click OK.

Windows 95 displays the Install from Disk dialog box, which prompts you to insert the appropriate disk and to enter the directory location for the NDIS 3 driver.

3 If you are using the 3.5-inch diskettes, insert

TokenDisk diskette #2 in the drive. If you are using the TokenDisk CD, insert it in the CD-ROM drive.

4 At the prompt, enter the appropriate path for the

drive containing your TokenDisk diskette or CD and the NDIS 3 driver. For example:

a:\w95nt351

5 Click OK.

If Windows 95 prompts you to insert the Windows 95 CD or diskettes to obtain ﬁles from the Windows 95 software library, insert the appropriate diskette or CD and continue as directed by the prompts.

6 When the setup ﬁle has been read, select

TokenLink Velocity XL PCI NIC on the list and click OK.

Windows 95 imports the driver, and the driver installation is complete.

7 Remove the TokenDisk diskette or TokenDisk CD and

restart your computer.

This concludes the procedure for installing the NDIS 3 driver for Windows 95 (version 950).

Installing a 3C359 NIC Driver for Windows Environments 4-5

Installing a Driver for Windows 95 Version 950b, OSR2

Follow these steps to install the driver for Windows 95 version 950b, OSR2. It is assumed that you are already running Windows 95.

During installation, have the Windows 95 software accessible on diskettes, CD, or hard drive in case the installation utility requests ﬁles from the Windows 95 software library.

1 Install the 3C359 NIC and start the computer.

Windows 95 detects the new hardware. PCI Token Ring Controller appears in the New Hardware Found dialog notice.

The Update Device Driver Wizard dialog box appears.

2 Click Next. 3 Click Other Locations.

The Select Other Location dialog box appears.

4 If you are using 3.5-inch diskettes, insert TokenDisk

diskette #2 in the drive. If you are using the TokenDisk CD, insert it in the CD-ROM drive.

5 At the prompt, enter the appropriate path for the

drive containing your TokenDisk diskette or CD and the driver you want to install.

For example, use the following path to install the NDIS 4 driver (recommended) from the TokenDisk diskette:

a:\w98nt40

Use the following path to install the NDIS 3 driver from the TokenDisk diskette:

a:\w95nt351

If you are using the TokenDisk CD, substitute the appropriate drive in the path.

6 Verify that the Update Device Driver Wizard dialog

box lists 3Com TokenLink Velocity XL PCI Adapter, and click Finish.

Have the Windows 95 software accessible in case the installation utility requests ﬁles from the Windows 95 software library. Insert the appropriate diskette or CD if prompted to do so.

4-6 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Messages appear while ﬁles are being copied. The System Settings Change dialog box appears.

7 Remove the TokenDisk diskette or CD from the drive. 8 Click Yes to restart the computer.

This concludes the procedure for installing a driver for Windows 95 version 950b, OSR2.

To disable auto ring speed detection and manually select the ring speed, see “Setting Ring Speed for Windows 95” for more details.

To deﬁne a locally administered network address, see “Deﬁning the LAA Address for Windows 95” for more details.

Installing a Driver for Windows NT 4.0

Follow these steps to install the 3Com NDIS 4 driver for Windows NT 4.0.

If your network environment uses the TCP/IP communications protocol, obtain from your network administrator all the information you need to deﬁne an IP address during the installation process before starting.

1 In the My Computer group, double-click the

Control Panel icon.

2 In the Control Panel group, double-click the

Network icon.

3 In the Network dialog box, click the Adapters tab. 4 In the Adapters tab, click Add. 5 In the Select Network Adapter dialog box, click

Have Disk.

The Insert Disk dialog box appears.

6 If you are using the 3.5-inch diskettes, insert

TokenDisk diskette #2 in the drive. If you are using the TokenDisk CD, insert it in the CD-ROM drive.

7 Accept the displayed default path by clicking OK.

For example, if you are using the 3.5-inch diskettes, the following path is displayed:

Installing a 3C359 NIC Driver for Windows Environments 4-7

This path identiﬁes the location of the NDIS 4 driver ﬁles for Windows NT 4.0. The Select OEM Option dialog box appears.

8 Select 3Com TokenLink Velocity XL PCI Adapter and

click OK.

9 Verify that 3Com TokenLink Velocity XL PCI Adapter

appears in the list in the Network Adapters tab and click Close.

If your network environment uses the TCP/IP communications protocol, the Microsoft TCP/IP Properties dialog box is displayed. You must obtain from your network administrator all the information you need to deﬁne an IP address during the installation process. Continue after you have deﬁned the NIC for TCP/IP.

Bindings messages appear, followed by a prompt to restart the computer.

10 Remove the TokenDisk diskette or CD from the drive. 11 Click Yes to restart the computer.

This concludes the procedure for installing the NDIS 4 driver for Windows NT 4.0.

To disable auto ring speed detection and manually select the ring speed, see “Setting Ring Speed for Windows NT 4.0” for more details.

To deﬁne a locally administered network address, see “Deﬁning the LAA Address for Windows NT” for more details.

To select applications for high-priority network access, see “Conﬁguring Class of Service” for more details.

Installing a Driver for Windows NT 3.51

Follow these steps to install the NDIS 3 driver for Windows NT 3.51.

1 If you are using the 3.5-inch diskettes, insert

TokenDisk diskette #2 in the drive. If you are using the TokenDisk CD, insert it in the CD-ROM drive.

2 In the Main group, double-click the Control Panel icon.

4-8 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

3 In the Control Panel group, double-click the

Network icon.

4 In the Network Settings dialog box, click

Add Adapter.

5 In the Add Network Adapter dialog box, scroll to the

bottom of the Network Adapter Card selection list. Select <Other> Requires disk from manufacturer.

6 Click Continue. 7 Accept the displayed default path by clicking OK to

select the NIC.

For example, if you are using the 3.5-inch diskettes, the following path is displayed:

a:\

This path identiﬁes the location of the NDIS 3 driver ﬁles for Windows NT 3.51.

The driver ﬁles are copied to the C drive. A prompt appears, asking if you want to restart your computer.

8 Remove the TokenDisk diskette or CD and click

Restart now.

This concludes the procedure for installing the NDIS 3 driver for Windows NT 3.51.

Selecting Ring Speed

This section describes how to set the ring speed for Windows 95 and Windows NT environments.

Setting Ring Speed for Windows 95

The auto ring speed detection option permits the 3C359 NIC’s NDIS 4 driver to detect and operate at the current ring data rate. Auto ring speed detection is automatically enabled when you load the NDIS 4 driver for Windows 95.

You can choose one of the following ring speed options:

■ Enable auto ring speed detection (default setting)

■ Disable auto ring speed detection and manually set

the NIC ring speed to 16 Mbps or 4 Mbps

Selecting Ring Speed 4-9

To access the ring speed option in a Windows 95 environment, follow these steps:

1 In the My Computer group, double-click the

Control Panel icon.

2 In the Control Panel group, double-click the

Network icon.

The Network window appears, as shown in Figure 4-1.

Figure 4-1 Network Window

3 In the Conﬁguration tab, select 3Com TokenLink

Velocity XL PCI Adapter and click Properties.

The Driver tab of the 3Com PCI Token Ring Adapter Properties window appears, as shown in Figure 4-2.

4-10 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Figure 4-2 PCI Token Ring Adapter Properties Window: Driver Tab

4 Click the Advanced tab.

The Advanced tab of the 3Com PCI Token Ring Adapter Properties window appears, as shown in Figure 4-3.

Figure 4-3 Displaying Ring Speed Setting

Selecting Ring Speed 4-11

The default setting for Ring Speed is Auto.

5 To manually set the ring speed, select Ring Speed in

the Property list.

6 Position the mouse pointer on the down arrow

button in the Value ﬁeld. Press and hold down the left mouse button.

The Advanced tab appears, as shown in Figure 4-4.

Figure 4-4 Manually Setting Ring Speed

7 Select one of the following values:

■ 16 — Disables auto ring speed detection and sets NIC

ring speed at 16 Mbps

■ 4 — Disables auto ring speed detection and sets NIC

ring speed at 4 Mbps

■ Auto — Allows NIC to automatically detect ring speed

Your selection overrides the factory setting for the 3C359 NIC and any setting made through the DOS Conﬁguration and Diagnostic Program.

8 Click OK.

4-12 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Setting Ring Speed for Windows NT 4.0

Auto ring speed detection permits the 3C359 NIC’s NDIS 4 driver to detect and operate at the current ring data rate. Auto ring speed detection is automatically enabled when you load the NDIS 4 driver for Windows NT 4.0.

You can choose the following ring speed options:

■ Enable auto ring speed detection (default setting)

■ Disable auto ring speed detection and manually set the

NIC ring speed to 16 Mbps or 4 Mbps To access the ring speed detection option in a Windows NT

environment, follow these steps:

1 In the My Computer group, double-click the

Control Panel icon.

2 In the Control Panel group, double-click the

Network icon.

3 In the Network dialog box, click the Adapters tab. 4 In the Adapters tab, select 3Com TokenLink Velocity

XL PCI Adapter and click Properties.

The 3Com TokenLink Velocity XL PCI Adapter dialog box appears, as shown in Figure 4-5.

5 To manually set the ring speed, position the mouse

pointer on the down arrow button in the Ring Speed Detection ﬁeld. Press and hold down the left mouse button to display the available options.

The ring speed detection menu displays the current ring speed options, as shown in Figure 4-5.

Selecting Ring Speed 4-13

Figure 4-5 3Com TokenLink Velocity XL PCI Adapter Dialog Box

6 Select one of the following values:

■ 16 — Disables auto ring speed detection and sets NIC

ring speed at 16 Mbps

■ 4 — Disables auto ring speed detection and sets NIC

ring speed at 4 Mbps

■ Auto — Allows NIC to automatically detect ring speed

7 Click OK.

You can click the Priority button to access the DynamicAccess: Select Adapter window (Figure 4-11) to enable and conﬁgure Class of Service. For more information about Class of Service, see “Conﬁguring Class of Service” later in this chapter.

This concludes the procedure for setting the 3C359 NIC ring speed in a Windows NT 4.0 environment.

4-14 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Deﬁning a Locally Administered Network Address

A default network address is encoded for the 3C359 NIC during manufacturing. This address is called the universal address (UAA), or “burned-in” address.

To customize the address for your network administration needs, you can assign a locally administered address (LAA) that overrides the NIC’s universal address. The LAA address must consist of 12 hexadecimal digits in the range from X’4000 0000 0000’ to X’7FFF FFFF FFFF’ and must be unique throughout the network.

In most cases, you will use the preset UAA address and not have to deﬁne an LAA address. Check with your network administrator before using this feature.

Deﬁning the LAA Address for Windows 95

Use the following procedures in this section to perform the following actions in a Windows 95 environment:

■ Display the current network address

■ Set a new LAA address.

Displaying the Current Network Address for Windows 95

Follow these steps to display the current network address:

1 Boot from a DOS diskette to run the diagnostic

program. Display the DOS prompt.

2 If you are using the 3.5-inch TokenDisk diskettes,

insert TokenDisk diskette #1 in the drive and make that drive the active drive. For example, enter:

If you are using the TokenDisk CD, insert it and make the CD-ROM drive the active drive. For example, enter:

Deﬁning a Locally Administered Network Address 4-15

3 Enter the following command:

3pcid

The Conﬁguration and Diagnostic Program window is displayed, as shown in Figure 4-6.

Figure 4-6 Conﬁguration and Diagnostic Program Window

4 Record for future reference the 12-digit universal

token ring address displayed in the Conﬁguration and Diagnostic Program window. For example:

Network Addr = 00600891CCA8

Setting the LAA Address for Windows 95

To set a locally administered address for a Windows 95 environment, follow these steps:

1 In the My Computer group, double-click the

Control Panel icon.

2 In the Control Panel group, double-click the

Network icon.

The Network window appears, as shown in Figure 4-7.

4-16 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Figure 4-7 Network Window

3 In the Conﬁguration tab, select 3Com TokenLink

Velocity XL PCI Adapter and click Properties.

The Driver tab of the 3Com PCI Token Ring Adapter Properties window appears, as shown in Figure 4-8.

4 Click the Advanced tab.

The Advanced tab of the 3Com PCI Token Ring Adapter Properties window appears, as shown in Figure 4-9.

Deﬁning a Locally Administered Network Address 4-17

Figure 4-8 PCI Token Ring Adapter Properties Window: Driver Tab

Figure 4-9 Entering Current Network Address

4-18 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

5 Select Current Network Address in the Property list. 6 Enter a valid 12-digit locally administered address in

the Value ﬁeld.

A valid 12-digit hexadecimal LAA value must fall within the range 400000000000h to 7FFFFFFFFFFFh and must be unique throughout the network. Check with your network administrator for the appropriate LAA address.

7 Click OK. 8 Restart the computer.

Deﬁning the LAA Address for Windows NT

To set a locally administered address for a Windows NT environment, follow these steps:

1 In the My Computer group, double-click the

Control Panel icon.

2 In the Control Panel group, double-click the

Network icon.

3 In the Network dialog box, click the Adapters tab. 4 In the Adapters tab, select 3Com TokenLink Velocity

XL PCI Adapter and click Properties.

The 3Com TokenLink Velocity XL PCI Adapter dialog box appears, as shown in Figure 4-10. Note that the current network address is displayed in the second ﬁeld.

5 Enter a valid 12-digit locally administered address in

the Network Address ﬁeld.

Conﬁguring Class of Service 4-19

Figure 4-10 3Com TokenLink Velocity XL PCI Adapter Dialog Box

6 Click OK.

7 Restart the computer.

Conﬁguring Class of Service

This section describes activating and conﬁguring DynamicAccess Class of Service (Trafﬁc Prioritization) support for Windows NT 4.0.

Class of Service is available only with the 3C359 NIC NDIS 4 driver. This feature is not available with other 3C359 NIC drivers. Although the NDIS 4 miniport driver is compatible with Windows 95 (version 950b, OSR2), it does not currently provide Class of Service support for this version of Windows 95. The NDIS 4 miniport driver does provide Class of Service support for Windows 98.

4-20 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Class of Service (Trafﬁc Prioritization) is an IEEE 802.5 supported feature that lets you select critical applications for high-priority network access. Class of Service prioritization allows stations running critical applications under Windows NT 4.0 or Windows 98 to access network bandwidth before other stations. The NDIS 4 driver requests a priority token when the selected applications transmit data.

The Class of Service feature is disabled by default; if you want to take advantage of this feature, you must manually enable it after installing the NDIS 4 driver.

Before Starting Class of Service Conﬁguration

The 3C359 NIC must be installed before you conﬁgure Class of Service. For NIC installation instructions, see Chapter 2, “Installing the 3C359 NIC.”

The NDIS 4 driver must also be installed before you conﬁgure Class of Service. For installation instructions, see the earlier sections in this chapter.

Finally, you must also have installed the appropriate applications that you want to prioritize through Class of Service conﬁguration.

Enabling Class of Service

The Class of Service feature is disabled by default. To enable Class of Service in a Windows NT 4.0 environment, follow these steps:

1 In the Control Panel group, double-click the

3Com Class of Service icon.

The DynamicAccess: Select Adapter window appears (Figure 4-11).

Conﬁguring Class of Service 4-21

The 3Com Class of Service icon is loaded automatically with the NDIS 4 driver installation. In a Windows NT environment, you can also access the DynamicAccess: Select Adapter window by clicking the Priority button on the 3Com TokenLink Velocity XL PCI Adapter window (Figure 4-5).

2 Select 3Com TokenLink Velocity XL PCI Adapter, as

shown in Figure 4-11.

Figure 4-11 DynamicAccess: Select Adapter Window

3 Click OK.

The Supported Applications tab of the 3Com Class of Service Setup window appears, as shown in Figure 4-12. The Supported Applications tab automatically displays all applications on your PC that support DynamicAccess Class of Service.

4-22 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Figure 4-12 3Com Class of Service Setup Window

If an application is not listed in the Supported Applications tab (Figure 4-12), you can obtain the necessary port or socket range from the application’s manufacturer, and manually enter the information in the Additional Ranges tab (Figure 4-13); or you can set the range to include all applications.

4 Select the Enable radio button.

The default mode is Disable. When Class of Service is disabled, you cannot select applications shown in the Supported Applications Tab for high-priority network access. In addition, you cannot make changes to data shown in the Additional Ranges tab and Advanced Options tab. Selecting Enable gives you access to all three tabs of the 3Com Class of Service Setup window.

Conﬁguring Class of Service 4-23

5 Click the box next to each application that you want

to have high-priority network access.

Class of Service divides applications into two network access priority groups:

■ High-priority

■ Low-priority (normal-priority)

Applications that you select are marked for high-priority network access. Unselected applications are given low-priority (normal-priority) network access.

Based on your selections, the NDIS 4 driver can recognize network trafﬁc as high-priority when that trafﬁc is generated by a chosen application.

6 Click OK. 7 Restart the computer.

Adding Class of Service Ranges and Protocols

You can add information for Class of Service applications that you want to prioritize but which are not listed on the 3Com Class of Service Setup window (Figure 4-12).

You must specify port or socket ranges as well as the network protocol being used. Obtain the information from the application manufacturer.

The Class of Service network driver uses these ranges to determine whether a packet should be treated as high-priority. If you are not able to obtain the range, you can set the entire range to 0000–9999.

To add the Class of Service ranges and protocols, follow these steps:

1 Click the Additional Ranges tab.

The Class of Service Additional Ranges window appears, as shown in Figure 4-13.

4-24 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

Figure 4-13 Class of Service Additional Ranges Window

2 Enter the beginning of the port or socket range for

the application in the Range Start box.

The range start should be a hexadecimal value with a maximum of four digits.

3 Enter the inclusive range end value of the port or

socket range for the application.

The range end should be a hexadecimal number with a maximum of four digits. If only one port or socket is needed, Range End should match Range Start.

4 Select the protocol that the application uses.

The protocol can be TCP, UDP, or IPX.

Some applications support multiple protocols and have port or socket ranges for each protocol. In this case, the range or protocol must match the protocol on the PC. For example, if only TCP/IP is installed, do not enter the socket range for IPX, because doing so will adversely affect driver performance.

Conﬁguring Class of Service 4-25

5 Once the Range Start, Range End, and Protocol are

entered press Add.

The range is added to the list, as shown in Figure 4-14.

Figure 4-14 Additional Ranges Window Showing Data

6 Click OK when you are ﬁnished.

To remove a range, select the range in the list and click Remove.

7 Restart the computer.

Using Class of Service Advanced Options

You can use Class of Service Advanced Options to adjust the network driver’s handling of certain types of Class of Service trafﬁc. The advanced options are set to certain default values recommended by 3Com. In general, you do not need to change these values, but you can do so if you wish. Contact network administration before changing these options.

4-26 CHAPTER 4: MICROSOFT WINDOWS ENVIRONMENT

To access the advanced options, follow these steps:

1 Click the Advanced Options tab.

The Class of Service Advanced Options window appears, as shown in Figure 4-15.

Figure 4-15 Class of Service Advanced Options Window

2 Enter new information as required. 3 Click OK to set the new value. 4 Restart the computer to activate changes.

Class of Service Advanced Options Settings

This section provides a detailed description of each Advanced Values ﬁeld shown on the Class of Service Advanced Options window.

FIFO Packet Threshold This setting controls the number of non–Class of Service bytes the network driver will allow in the FIFO ahead of any Class of Service packets. A smaller number decreases the time between Class of Service packets but can adversely affect performance. The default value of 20,000 is the recommended setting.

Conﬁguring Class of Service 4-27

Concurrent UDP Streams This option controls the number of simultaneous multimedia UDP packet streams the network driver can handle at any time. For many applications, the number of UDP streams is the same as the number of connections.

For example, for videoconferencing with three people, applications use three UDP streams for the video data. The value must be a power of 2 (2, 4, 8) but the optimal value may vary depending on the PC and application.

A video server may support 32 connections, but a client may only want to conference with four other people at a time.

The default value of 16 is the recommended setting for most applications.

Low-Priority Ratio When Class of Service support is enabled, high-priority packets are always transmitted before low-priority packets. If a certain high-priority application sends out enough packets, no low-priority packets may be sent.

To prevent this problem, the driver uses a ratio value to periodically send out a low-priority packet (if one is waiting to be sent).

For example, if a value of 1000 is entered, one low-priority packet would be sent for every 1000 high-priority packets. The default value of 25 is the recommended setting for most applications.

Natural Packet Interval This ﬁeld is not applicable. Any value entered in this ﬁeld is ignored.

Disable Switch Packet Prioritization This option is not currently enabled. Any setting is ignored.

Disable Receive Packet Buffering This option is not currently enabled. Any setting is ignored.

IBM ENVIRONMENTS

This chapter describes how to install a 3C359 NIC network device driver for various IBM operating system environments.

This chapter also describes conﬁguring 3C359 NIC connectivity to an IBM host computer (mainframe or AS/400) for various Windows environments.

Installing a Driver for Various IBM Environments

This section describes how to install a 3C359 NIC network device driver for various IBM operating system environments.

Installing the IBM LAN Support Program (DXMAID) and the DOS NDIS 2.01 Driver

Follow these steps to install the IBM LAN Support Program (DXMAID) and the DOS NDIS 2.01 driver for IBM host connectivity applications. The DOS NDIS 2.01 driver can also handle DOS LAN requests to IBM LAN Server.

1 At the DOS prompt on a DOS machine, run the

DXMAID installer from the IBM LAN Support Program

diskette. 2 Press Enter at the ﬁrst three Information windows. 3 In the Setup window, press Enter to accept all the

default values. 4 If you are using the 3.5-inch TokenDisk diskettes, insert

TokenDisk diskette #2 in the drive. If you are using the

TokenDisk CD, insert it in the CD-ROM drive.

5 In the Process Driver Diskette window, enter the path

for the NDIS driver. For example, if you are using the

3.5-inch TokenDisk diskettes, enter:

a:\ndis2\dos

If you are using the TokenDisk CD, substitute the

appropriate drive in the path.

5-2 CHAPTER 5: IBM ENVIRONMENTS

6 Insert the IBM LAN Support Program diskette in the

drive when prompted.

The Primary Adapter Driver shown is 3Com TokenLink Velocity XL PCI.

7 Press F4 to install the driver. 8 If you are using the 3.5-inch TokenDisk diskettes,

insert TokenDisk diskette #1 in the drive when prompted.

This completes the installation of DXMAID and the DOS NDIS 2.01 driver. Restart your computer and install your host connectivity application.

Installing a Driver for IBM DOS LAN Services

Follow these steps to install the NDIS 2.01 driver for IBM DOS LAN Services for IBM LAN Server 4.0 or IBM Warp Server:

1 Create a temporary directory on your DOS PC. For

example, enter:

mkdir c:\temp

2 If you are using the 3.5-inch diskettes, insert

TokenDisk diskette #2 in the drive. If you are using the TokenDisk CD, insert it in the CD-ROM drive.

3 Copy the following ﬁles from the TokenDisk diskette

to the temporary directory. For example, enter:

copy a:\ndis2\dos\oemsetup.inf c:\temp copy a:\ndis2\dos\tlnkpn2.dos c:\temp

If you are using the TokenDisk CD, substitute the appropriate drive in the path.

4 Insert IBM DOS LAN Services diskette #1 in the drive. 5 From the DOS prompt, enter:

a:\install

6 Press Enter when the welcome screen is displayed. 7 Press Enter to accept the default directory C:\NET as

the location to install IBM DOS LAN Services.

8 From the list of network cards presented, select

Network Card Not Shown In List Below.

Installing a Driver for Various IBM Environments 5-3

9 Enter the path of the temporary directory for the

OEMSETUP.INF ﬁle:

c:\temp

10 The 3Com TokenLink Velocity XL PCI NIC is selected.

Press Enter.

11 Enter the machine ID, user name, and domain name. 12 Press Enter to accept the list of options chosen. 13 Finish installing ﬁles from the IBM DOS LAN Services

diskettes.

14 If you are using the 3.5-inch TokenDisk diskettes,

insert TokenDisk diskette #1 in the drive.

15 Copy the microcode ﬁle TLNKP.MAC from the

TokenDisk to your hard drive. For example, if you

are using the 3.5-inch TokenDisk diskettes, enter:

copy a:\tlnkp.mac c:\net

If you are using the TokenDisk CD, substitute the

appropriate drive in the microcode ﬁle’s path.

This completes the driver installation for IBM DOS LAN

Services. Restart your computer and install your host

connectivity application.

Using IBM MPTS to Install a Driver for OS/2

If your OS/2 network operating system has not yet been

installed on your computer, install it now and follow its

instructions for installing device drivers. If an OS/2 network

operating system has previously been installed, follow the

instructions here for using IBM Multiprotocol Transport

Services (MPTS) to install device drivers.

1 Start IBM MPTS by performing either of the

following actions:

■ From the OS/2 desktop, double-click the MPTS icon.

■ From an OS/2 window, go into the IBMCOM

subdirectory and at the OS/2 prompt, enter:

mpts

2 Select OK on the MPTS logo panel.

5-4 CHAPTER 5: IBM ENVIRONMENTS

3 Select Install.

You are prompted for the source of the NIF ﬁle.

4 If you are using diskettes, insert TokenDisk

diskette #2 in a drive (for example, drive A) and enter:

a:\ndis2\os2

If you are using the TokenDisk CD, insert it in the CD-ROM drive (for example, drive D) and enter:

d:\ndis2\os2

5 When the Installation Complete message appears,

select OK.

You are returned to the main menu.

6 Select Conﬁgure in the MPTS dialog box. 7 In the Conﬁgure panel, verify that LAN Adapters and

protocols is preselected, and then select Conﬁgure at the bottom of the panel.

8 In the Conﬁgure panel in the Network Adapters

group box, select 3Com TokenLink Velocity XL PCI and click ADD.

You can edit parameter settings for the 3C359 NIC. Select the 3C359 NIC in the Current Conﬁguration list box and click Edit. When you are ﬁnished with the parameter settings, click OK.

9 In the Protocols list box, select the protocols used by

your network application. Select each protocol and click ADD.

If you are not sure which protocols to use, select IBM IEEE 802.2 and IBM OS/2 NetBIOS protocol drivers or ask your network administrator.

The protocol drivers you have selected will appear under the NIC driver name in the Current Conﬁguration list box.

You can edit parameter settings for the protocols. Select a protocol and then click Edit.

10 When you have ﬁnished selecting and editing

protocols in the Conﬁguration panel, click OK.

11 Click Close in the Conﬁguration panel.

Conﬁguring IBM Host Connectivity 5-5

12 Click Exit in the MPTS dialog box. 13 Click Exit in the Update CONFIG.SYS panel to update

the CONFIG.SYS ﬁle.

14 When you get the message that the CONFIG.SYS ﬁle

has been successfully updated, click OK.

15 Click Exit in the Exiting MPTS panel. 16 If you are using the 3.5-inch TokenDisk diskettes,

insert TokenDisk diskette #1 in the drive.

17 Copy the microcode ﬁle TLNKP.MAC from the

TokenDisk to your hard drive. For example, enter:

copy a:\tlnkp.mac c:\ibm\macs

If you are using the TokenDisk CD, substitute the

appropriate drive in the microcode ﬁle’s path.

18 Shut down OS/2 and restart your computer to let the

changes take effect.

19 At system startup, check for the following conditions

to determine whether the NIC is working correctly and

whether installation has been completed successfully:

■ The device driver ﬁles loaded successfully. There are

no error messages.

■ You are able to log on and communicate with

the network.

If you experience problems, see Chapter 6,

“Troubleshooting.”

Installation of the driver for OS/2 is now complete.

Conﬁguring IBM Host Connectivity

This section describes the initial phase of conﬁguring

3C359 NIC connectivity to an IBM host computer

(mainframe or AS/400) for various Windows environments.

This phase involves adding the appropriate network

protocol to enable host connectivity.

After adding the network protocol, install the host

connectivity applications (such as client access and

emulator applications) that are appropriate for your

environment.

5-6 CHAPTER 5: IBM ENVIRONMENTS

Adding the MS-DLC Network Protocol for Windows for Workgroups

Follow the steps in this section to add the Microsoft MS-DLC network protocol to the Windows for Workgroups Add Network Protocol list for the 3C359 NIC. The MS-DLC protocol is required for connectivity between your PC and an IBM host computer.

Before proceeding, make sure that you have the Microsoft MS-DLC network protocol available. If the MS-DLC protocol is not currently available, download it from the Microsoft Web site to a temporary storage location on your PC’s hard disk or on a diskette.

1 In the Windows for Workgroups Program Manager

window, double-click the Network icon.

2 In the Network window, double-click the Network

Setup icon. 3 In the Network Setup window, click Network Drivers. 4 In the Network Drivers window, make sure that 3Com

TokenLink Velocity XL PCI Adapter is displayed. Click

Add Protocol. 5 In the Add Network Protocol window, select Unlisted

or Updated Protocol. Click OK.

6 In the Install Driver window, enter the path for the

MS-DLC protocol. If the protocol is stored on diskette,

insert the diskette in the drive. Click OK. 7 In the Unlisted or Updated Protocol window, select

MS-DLC. Click OK.

The Network Driver window is displayed.

8 Verify that the MS-DLC protocol is displayed under

3Com TokenLink Velocity XL PCI Adapter. Click Close.

The Network Setup window is displayed.

9 Click OK.

The MS-DLC ﬁles are copied, and the Network

Setup window displays a message indicating that the

AUTOEXEC.BAT, SYSTEM.INI, and PROTOCOL.INI ﬁles

have been modiﬁed.

Conﬁguring IBM Host Connectivity 5-7

10 In the Network Setup message window, click OK.

The Windows Setup window displays the following message:

You need to quit Windows and restart your computer so that changes you made will take effect. Do not press CTRL+ALT+DEL to restart your computer--this may cause you to lose work. Restart the computer now?

11 In the Windows Setup message window, click

Restart Computer.

This completes the procedure for adding the Microsoft MS-DLC network protocol to the Windows for Workgroups Add Network Protocol list for the 3C359 NIC.

After adding the network protocol, install the host connectivity applications (such as client access and emulator applications) that are appropriate for your environment.

Adding the 32-Bit DLC Network Protocol for Windows 95

Follow the steps in this section to add the Microsoft 32-bit DLC network protocol to the Windows 95 Network Protocols list for the 3C359 NIC. The 32-bit DLC protocol is required for connectivity between your PC and an IBM host computer.

Before proceeding, make sure that you have the Microsoft 32-bit DLC network protocol available. If you are using Windows 95 version 950 or 950a (the “retail” version), you must download the 32-bit DLC protocol from the Microsoft Web site to a temporary storage location on your PC’s hard disk or on a diskette. Windows 95 version 950b, OSR2, includes the 32-bit DLC protocol.

1 On the Windows 95 desktop, double-click the

My Computer icon. 2 Double-click the Control Panel icon. 3 Double-click the Network icon. 4 In the Network window, select 3Com TokenLink

Velocity XL PCI Adapter in the Conﬁguration tab.

Click Add.

5-8 CHAPTER 5: IBM ENVIRONMENTS

5 In the Select Network Component Type window,

select Protocol. Click Add.

Windows builds the driver information database and displays the Select Protocol window.

6 Select Microsoft in the Manufacturers list. 7 Do one of the following:

■ If you are using Windows 95 version 950b, OSR2, select

Microsoft 32-bit DLC in the Network Protocols list. The Conﬁguration tab of the Network window appears.

Proceed to step 9.

■ If you are using Windows 95 version 950 or 950a

(“retail” version), click Have Disk. The Install From Disk window is displayed. Continue at

step 8.

8 If you are using Windows 95 version 950 or 950a

(“retail” version), do one of the following:

■ If you have copied the Microsoft 32-bit DLC protocol to

diskette, insert the diskette in the drive.

■ If you have copied the DLC protocol to the hard drive,

enter the appropriate path for the downloaded Microsoft 32-bit DLC protocol in the Install From Disk window. Click OK.

9 Verify that Microsoft 32-bit DLC is displayed for

the 3Com TokenLink Velocity XL PCI Adapter in the Conﬁguration tab of the Network window. Click OK.

Windows copies the protocol ﬁles.The System Settings Change window displays the following message:

You must restart your computer before the new settings will take effect. Do you want to restart your computer now?

10 Click Yes.

This completes the procedure for adding the Microsoft 32-bit DLC network protocol to the Windows 95 Network Protocols list for the 3C359 NIC.

After adding the network protocol, install the host connectivity applications (such as client access and emulator applications) that are appropriate for your environment.

Conﬁguring IBM Host Connectivity 5-9

Adding the 32-Bit DLC Network Protocol for Windows NT

Follow the steps in this section to add the Microsoft

32-bit DLC network protocol to the Windows NT Network

Protocols list for the 3C359 NIC. The 32-bit DLC protocol is

required for connectivity between your PC and an IBM

host computer.

1 On the Windows NT desktop, double-click the

My Computer icon. 2 Double-click the Control Panel icon. 3 Double-click the Network icon. 4 In the Network window, select the Protocols tab.

Click Add. 5 In the Select Network Protocol window, select DLC

Protocol. Click OK. 6 Insert the Windows NT CD in the CD-ROM drive. In

the Windows NT Setup window, enter the path for

the Windows NT CD. For example:

d:\

The Protocols tab of the Network window is displayed.

7 Verify that DLC Protocol is displayed. Click Close.

Bindings messages are displayed. The Network Settings

window displays the following message:

You must shut down and restart your computer

before the new settings will take effect. Do

you want to restart your computer now?

8 Click Yes.

This completes the procedure for adding the Microsoft

32-bit DLC network protocol to the Windows NT Network

Protocols list for the 3C359 NIC.

After adding the network protocol, install the host

connectivity applications (such as client access and

emulator applications) that are appropriate for your

environment.

This chapter describes how to isolate and solve 3C359 NIC

hardware and network cabling problems.

3C359 NIC LEDs

Light-emitting diodes (LEDs) on the backplate of the

3C359 NIC, shown in Figure 6-1, indicate the conﬁgured

ring speed and whether or not the 3C359 NIC is inserted

into the ring. The LEDs also light when drivers are loading

and when the diagnostics program is running.

TROUBLESHOOTING

4 Mbps

16 Mbps

Figure 6-1 NIC LEDs

When the green LED (labeled “4”) is lit, it indicates that the

3C359 NIC is set to 4 Mbps speed and is correctly inserted

into the token ring network.

When the yellow LED (labeled “16”) is lit, it indicates that

the 3C359 NIC is set to 16 Mbps and is correctly inserted

into the token ring network.

Data

6-2 CHAPTER 6: TROUBLESHOOTING

Using the Diagnostic Program

You can troubleshoot the 3C359 NIC conﬁguration and test for physical board problems by running the DOS Conﬁguration and Diagnostic Program.

Conﬁguration instructions are described in Appendix B.

The diagnostic part of the program tests the 3C359 NIC, not the network. However, a lobe cable must be connected from the 3C359 NIC to a retiming concentrator or MAU for all tests. A lobe cable is the section of cable that attaches a ring station or network device to a MAU or wiring hub.

The diagnostic program does not function properly if the 3C359 NIC drivers are already installed and running in memory. You must bypass the drivers by performing a clean DOS boot before you run the diagnostic program. Use a DOS diskette if you are running a version of DOS earlier than DOS 6.x.

DOS Diagnostic Tests

The diagnostics test physical components, connectors, and circuitry of the 3C359 NIC, as follows.

Register Write/Read Test

This test veriﬁes accurate writing and reading of the 3C359 NIC’s control registers.

Local RAM Write/Read Test

This test veriﬁes that the PC can correctly access the total 64 KB of available local RAM.

Timer Test

This test veriﬁes the 3C359 NIC’s timer operations by comparing the 3C359 NIC’s timers to the PC’s timer.

Open NIC for Ring Operation Test

This test prepares the 3C359 NIC for a NIC ring operation

test and veriﬁes the 3C359 NIC’s ability to transmit and

receive data over the network. This test requires you to

connect to an STP or a UTP cable with a DAU, MAU, CAU,

or token ring switch at the other end.

Ring Operations Test

This test assesses communication on the ring. The

3C359 NIC must be attached to the ring to run this

test successfully. The 3C359 NIC also must be set to

the correct ring speed.

Close NIC Test

This test veriﬁes the 3C359 NIC’s ability to close the 3C359

NIC and terminate the Ring Operations Test. The 3C359

NIC must have been previously opened.

Running the DOS Diagnostic Tests

If you are using Windows 95 or Windows for Workgroups,

exit Windows and restart the PC in MS-DOS mode, or boot

from a DOS diskette. If you are running Windows NT, boot

from the DOS partition or boot from a DOS diskette to run

the diagnostic program.

1 If you are using the 3.5-inch diskettes, insert

TokenDisk diskette #1 in the drive (for example,

the A drive) and enter:

a:\3pcid

Using the Diagnostic Program 6-3

If you are using the TokenDisk CD, insert it in the

CD-ROM drive (for example, the D drive) and enter:

d:\3pcid

The DOS Conﬁguration and Diagnostic Program window

is displayed with the Test menu selected, as shown in

Figure 6-2.

6-4 CHAPTER 6: TROUBLESHOOTING

Figure 6-2 Test Menu

2 From the Test pull-down menu shown in Figure 6-2,

select Run Tests.

The Run Tests dialog box appears, similar to the one shown in Figure 6-3.

Figure 6-3 DOS Diagnostic Program Run Tests Dialog Box

3 Press Enter to start the tests.

Each test runs once unless you specify otherwise. The test results are displayed with “Passed” or “Failed” in the Results column.

To run the tests continuously, select the Continuous option

in the Test Setup dialog box, as described in the next

section, “Changing the DOS Test Setup.”

Changing the DOS Test Setup

To change the test parameters, follow these steps:

1 Select Test Setup in the Run Tests dialog box and

press Enter.

The Test Setup dialog box appears, as shown in Figure 6-4.

Using the Diagnostic Program 6-5

Figure 6-4 DOS Diagnostic Program Test Setup Dialog Box

2 Press Tab to move from ﬁeld to ﬁeld and select any

ﬁeld within the Test Setup dialog box.

Within the Group Select area, use the arrow keys to select

Group 1. (Future software enhancements will provide

additional test groups.) Use the Enable Group or Disable

Group options to enable or disable a group of tests.

For test descriptions, see “DOS Diagnostic Tests” earlier

in this chapter.

3 Select OK and press Enter. 4 To run the tests, select Run Tests from the Test menu

and select Start.

SPECIFICATIONS

This appendix lists 3C359 NIC speciﬁcations, connector pin

assignments, and cable requirements.

3C359 NIC Speciﬁcations

The 3C359 NIC provides a high-performance 32-bit PCI

local bus interface with bus mastering that runs at a clock

speed of 33 MHz.

Network Interface

IEEE 802.5 token ring network with 16 Mbps or 4 Mbps

transmission rate.

Physical Dimensions

Length: 14.605 cm (5.75 in)

Height: 10.668 cm (4.20 in)

Environmental Operating Range

Operating temperature: 0˚ to 55 ˚C (32˚ to 131 ˚F)

Storage –40˚ to 80 ˚C (–40˚ to 176 ˚F)

Relative humidity (noncondensing)

Operating: 10% to 90%

Storage: 5% to 95%

Power Requirements at 16 Mbps

0 mA @ +3.3 V, maximum

400 mA @ +5 V, maximum

0 mA @ +12 V, maximum

A-2 APPENDIX A: SPECIFICATIONS

Compatibility

PCI Local Bus Speciﬁcation, Revision 2.1

PCI Bus Power Management Interface Speciﬁcation, Revision 1.0 (Draft)

Advanced Conﬁguration and Power Interface Speciﬁcation, Revision 1.0

Bus Data Interface

32-bit bus mastering

Interrupts (IRQs)

Automatically allocated by system

Node ID

Globally administered node ID allocated by IEEE Locally administered node ID optional

Cables and Connectors

Category 3, 4, 5 for UTP (RJ-45) Type 1, 1A, 2, 6 for STP (DB-9)

Emissions Classiﬁcations

FCC Class B, digital device EN55022 Class B Canadian Class B digital apparatus VCCI Class 2 category

European Community Classiﬁcation

EE-Compliant

Safety Classiﬁcations

UL 1950 (ITE) TUV EN60950:1992

Electromagnetic Susceptibility

EN50082-1

Connector Pin Assignments

4 16

Data

6 7 8 9

1 2 3 4 5

4 Mbps

16 Mbps

You can connect the 3C359 NIC to a network through the

NIC’s DB-9 connector or RJ-45 connector. Pin assignments

for both connector types are shown in the following

sections.

DB-9 Connector Pin Assignments

You can use the 3C359 NIC’s DB-9 connector to connect to

shielded twisted-pair (STP) cabling (Type 1 or 6). The DB-9

connector pin assignments are shown in Figure A-1.

(

Connector Pin Assignments A-3

Figure A-1 DB-9 Connector Pin Assignments

RJ-45 Connector Pin Assignments

You can use the 3C359 NIC’s RJ-45 connector to connect to

unshielded twisted-pair (UTP) cabling (Category 3, 4, or 5).

The RJ-45 connector pin assignments are shown in

Figure A-2.

A-4 APPENDIX A: SPECIFICATIONS

4 Mbps

16 Mbps

Figure A-2 RJ-45 Connector Pin Assignments

Cable Requirements

The 3C359 NIC supports industry-standard token ring cabling that meets IEEE 802.5 speciﬁcations.

Connect shielded twisted-pair (STP) cables (type 1 or 6) to the 3C359 NIC’s DB-9 connector (Figure A-1).

Connect unshielded twisted-pair (UTP) cables (category 3, 4, or 5) to the 3C359 NIC’s RJ-45 connector (Figure A-2).

Data

4 16

8 7 6 TX 5 RX 4 RX 3 TX 2 1

12345678

3COM TokenLink VelocityTM XL PCI User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

ABOUT THIS GUIDE

Conventions

INTRODUCTION

High-Performance Features of the 3C359 NIC

Parallel Tasking II Performance

DynamicAccess Class of Service

Support for Full-Duplex/Dedicated Token Ring

Wake-up On LAN Capability

Other Features of the 3C359 NIC

Installation Overview

Installation Requirements

Safety Precautions

Unpacking and Inspecting the 3C359 NIC

Inserting the 3C359 NIC

Installing a DOS 16-Bit Client Driver

Installing a DOS 16-Bit Client Automatically

AutoLink Software Functions

Modifying AutoLink Default Settings

Running the AutoLink Program

AutoLink Troubleshooting

Installing a DOS 16-Bit Client Manually

Installing DOS Client32

Installing an OS/2 Client Driver for NetWare

Selecting the Appropriate NIC Address

Displaying the Universal Address

Installing the Novell OS/2 Requester

Installing a NetWare Server Driver

Driver Support

Installation Instructions

Drivers Available for Windows

Before Installing a Windows Driver

Selecting Ring Speed

Enabling Class of Service

Adding Class of Service Ranges and Protocols

Using Class of Service Advanced Options

Class of Service Advanced Options Settings

IBM ENVIRONMENTS

Installing a Driver for Various IBM Environments

Installing a Driver for IBM DOS LAN Services

Using IBM MPTS to Install a Driver for OS/2

3C359 NIC LEDs

TROUBLESHOOTING

DOS Diagnostic Tests

Register Write/Read Test

Local RAM Write/Read Test

Timer Test

Open NIC for Ring Operation Test

Ring Operations Test

Close NIC Test

Running the DOS Diagnostic Tests

Changing the DOS Test Setup

SPECIFICATIONS

Connector Pin Assignments

DB-9 Connector Pin Assignments

RJ-45 Connector Pin Assignments

Cable Requirements