3Com TokenLink 3C339 Operation & User’s Manual

Network Interface Card User Guide A member of the 3Com TokenLink family of NICs Part No. 09-0807-001 Published May 1997

Copyright © 3Com Corporation, 1997. 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 permission from 3Com C0orporation. 3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change. 3Com Corporation provides this documentation without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time. UNITED STATES GOVERNMENT LEGENDS: If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following restricted rights: For units of the Department of Defense: Restricted Rights Legend: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) for Restricted Rights in Technical Data and Computer Software Clause at 48 C.F.R. 52.227-7013. 3Com Corporation, 5400 Bayfront Plaza, Santa Clara, California 95052-8145. For civilian agencies: Restricted Rights Legend: Use, reproduction, or disclosure is subject to restrictions set forth in subparagraph (a) through (d) of the Commercial Computer Software – Restricted Rights Clause at 48 C.F.R. 52.227-19 and the limitations set forth in 3Com Corporation’s standard commercial agreement for the software. Unpublished rights reserved under the copyright laws of the United States. If there is any software on removable media described in this documentation, it is furnished under a license agreement included with the product as a separate document, in the hard copy documentation, or on the removable media in a directory file named LICENSE.TXT. If you are unable to locate a copy, please contact 3Com and a copy will be provided to you. Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries. 3Com, the 3Com logo, NetAge, TokenDisk, and TokenLink are registered trademarks of 3Com Corporation. AutoLink and Velocity are trademarks of 3Com Corporation. Ask3Com is a service mark of 3Com Corporation. Artisoft and LANtastic are trademarks of Artisoft. Banyan and VINES are trademarks of Banyan Systems, Inc. CompuServe is a trademark of CompuServe, Inc. DEC and PATHWORKS are trademarks of Digital Equipment Corporation. Pentium is a trademark of Intel Corporation. IBM, OS/2, and Warp are trademarks of International Business Machines Corporation. Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation. Novell and NetWare are trademarks of Novell, Inc. Other brand and product names may be registered trademarks or trademarks of their respective holders. Manual written by John Jeter; revised by Norman Lundell and Pauline Garzelli. Edited by Nancy Kurahashi and Chris Dresden. Technical illustrations by Tim Buckreus; revised by Mary Inden. Production by Georgi Felix.

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.

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. I Asia 3Com Asia Ltd., Marketing Department Room 2506-07, 25/F. Citibank Tower Citibank Plaza, Central Hong Kong I Australia, New Zealand 3Com Australia, Marketing Department 99 Walker Street Level 7 North Sydney New South Wales 2060 Australia I Belgium, Netherlands, Luxembourg 3Com Benelux B.V., Marketing Department Nevelgaarde 8-9 3436 ZZ Nieuwegein Netherlands I France, Israel 3Com France, Marketing Department Immeuble McKinley BP 965 1, Avenue de l’Atlantique 91976 Les Ulis Courtaboeuf Cedex France I Germany, Austria, Switzerland 3Com GmbH, Marketing Department Gustav-Heinemann-Ring 123 D-81739 Muenchen Munich West Germany I Italy, Greece, Spain, Portugal, Malta 3Com Mediterraneo Srl, Marketing Department Via Michelangelo Buonarroti, 1 20093 Cologno Monzese MI Italy I Japan 3Com Japan, Marketing Department Shinjuku Sumitomo Building 23F 2-6-1 Nishi Shinjuku, Shinjuku-ku Tokyo 163-02 Japan I Sweden, Finland, Norway, Denmark 3Com Nordic, Marketing Department Torshamsgatan 39 Box 1110 164 22 KISTA Sweden I United Kingdom, Eire 3Com UK Ltd., Marketing Department Pacific House Third Avenue Globe Park Marlow-on-Thames Buckinghamshire, SL7 1YL England

How to Use This Guide 1 Conventions 2 1 INTRODUCTION Features 1-1 PCI Technology 1-2 Installation Requirements 1-2 Network Driver Options 1-3 Installation Summary 1-4 2 HARDWARE INSTALLATION Safety Precautions 2-1 Inspecting the NIC 2-1 Installing the NIC 2-2 Connecting to the Network 2-3 Connecting to UTP Cable 2-4 Connecting to STP Cable 2-5 Powering Up the PC 2-6 3 NETWORK DRIVER INSTALLATION Locating Driver Installation Procedures 3-1 Supplementary Procedures 3-3 Starting DOS 3-3 Finding the NIC’s Port Address 3-4

One NIC in a Client (DOS ODI) 3-5 About the AutoLink Program 3-5 AutoLink Program Requirements 3-5 Running the AutoLink Program 3-6 AutoLink Troubleshooting 3-7 About Installing on a NetWare Server 3-7 One NIC in a Server 3-7 Installation with NetWare 3.11 3-8 Installation with NetWare 3.12 and 4.x 3-8 Multiple NICs in a Server 3-9 Installation with NetWare 3.11 3-10 Installation with NetWare 3.12 and 4.x 3-11 Installing the Microsoft Windows Driver 3-12 Windows NT 3.51 3-12 Windows NT 4.0 3-13 Windows 95 3-15 About OSR Versions 3-15 OSR1 Installation 3-15 OSR2 Installation 3-16 Installing the OS/2 Driver 3-17 LAPS Installation 3-17 MPTS Installation 3-19 4 TROUBLESHOOTING About the Diagnostic Tests 4-1 Running the Diagnostic Tests 4-2 What to Do If a Test Fails 4-5 Status LEDs 4-7 A CONFIGURATION Changing Configuration Parameter Values A-3 B SPECIFICATIONS NIC Specifications B-1 RJ-45 Connector Pin Assignments B-3 DB-9 Connector Pin Assignments B-3 Cable Requirements B-4

Online Technical Services C-1 World Wide Web Site C-1 3Com Bulletin Board Service C-2 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-4 Support from 3Com C-4 Returning Products for Repair C-6 3COM CORPORATION LIMITED WARRANTY FCC CLASS B CERTIFICATION STATEMENT VCCI CLASS 2 STATEMENT 3COM END USER SOFTWARE LICENSE AGREEMENT

2-2 Connecting the RJ-45 Connector 2-4 2-3 Connecting the DB-9 Connector 2-5 4-1 3TLVDIAG Program Main Menu 4-2 4-2 Diagnostic Setup Screen 4-3 4-3 Diagnostic Test Screen 4-4 A-1 3TLVDIAG Program Main Menu A-4 A-2 Adapter Configuration Screen A-5 B-1 RJ-45 Connector Pin Assignments B-3 B-2 DB-9 Connector Pin Assignments B-3

2 Text Conventions 2 1-1 Driver Support 1-3 2-1 Connectors for 3C339 PCI NICs 2-4 3-1 Driver Installation Procedure Locations 3-1 3-2 Starting DOS from Other Operating Systems 3-3 4-1 LED Indicators 4-7 A-1 3C339 NIC Configuration Parameters (Modifiable with 3TLVDIAG) A-1 A-2 3C339 NIC Configuration Parameters (Not Modifiable with 3TLVDIAG) A-2

This guide contains installation procedures and other information about the 3Com TokenLink Velocity PCI network interface card (3C339 NIC). This guide is intended for those who install the NIC in PCs in a token ring network. It is assumed that the reader knows basic precautions and procedures for working with electrical equipment and with token ring networks, and knows how to use the PC operating system. If the information in the release notes shipped with the product differs from the information in this guide, follow the release notes. How to Use This Guide This table shows where to find specific information in this guide. If you are looking for... Turn to... A summary of installation procedures Chapter 1 Information about the 3C339 NIC and an introduction to PCI technology Chapter 1 Instructions for installing the NIC and connecting it to the network Chapter 2 Instructions for installing network drivers Chapter 3 Details on running diagnostic tests Chapter 4 Instructions for changing NIC configuration parameters Appendix A Information on NIC specifications, pin assignments, and cabling requirements Appendix B Information on 3Com’s technical support services Appendix C

Conventions Table 1 and Table 2 list conventions that are used throughout this guide. Table 1 Notice Icons Icon Notice Type Alerts you to... Information note Important features or instructions Caution Risk of personal safety, system damage, or loss of data Warning Risk of severe personal injury Table 2 Text Conventions Convention Description Screen displays This typeface represents information as it appears on the screen. The words “enter” and “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.” [Key] names Key names appear in text in one of two ways: I Referred to by their labels, such as “the Return key” or “the Escape key” I Written with brackets, such as [Return] or [Esc] If you must press two or more keys simultaneously, the key names are linked with a plus sign (+). Example: Press [Ctrl]+[Alt]+[Del]. Menu commands and buttons Menu commands or button names appear in italics. Example: From the Help menu, select Contents. Words in italicized type Italics emphasize a point or denote new terms at the place where they are defined in the text. Words in bold-face type Bold text denotes key features.

card (3C339 NIC) is a 32-bit bus-mastering NIC for use in token ring networks running at either 16 megabits per second (Mbps) or 4 Mbps. Features The 3C339 NIC complies with the following standards and specifications: I IEEE 802.2 Logical Link Control (LLC) I IEEE 802.5 Media Access Control (MAC) I PCI Local Bus Specification Revision 2.0 The 3C339 NIC supports the following features: I AutoLink installation software installs and configures 16-bit Novell NetWare DOS ODI client software. I On-board RJ-45 and DB-9 ports provide connection for unshielded twisted-pair (UTP) or shielded twisted-pair (STP) cabling without using an external media filter. I Auto Select Media Type capability enables drivers to automatically detect the type of media connector that connects the NIC to the network. I High-performance 32-bit PCI local bus interface with bus mastering runs at a clock speed of 33 MHz, increasing throughput dramatically while decreasing CPU utilization. I Status LEDs indicate insertion into the ring and transmission of data by the NIC. I Highly integrated design provides high reliability with minimal power consumption.

PCI Technology The PCI local bus provides a processor-independent data path between the CPU in a PC and high-speed peripherals. This high-performance bus accommodates multiple high-performance peripheral devices for networking and disk subsystems, graphics, full-motion video, and multimedia. There are two types of PCI devices: a master that transfers information directly to system memory without interrupting the system processor; and a target, which accepts commands and responds to requests from a master. The 3C339 PCI NIC is a master device. A shared expansion backplate slot on the PCI device provides access to one of two types of NICs: a PCI NIC and an ISA NIC, for example, or a PCI NIC and an EISA NIC. Only one NIC at a time can be installed in a shared slot. Manufacturers are currently producing computers that support the PCI bus in conjunction with conventional ISA or EISA buses in the same chassis. The PCI 32-bit bus supports multiple peripheral components and add-in cards at a peak bandwidth of 132 Mbps, which is up to an order of magnitude greater than that of ISA, EISA, and MCA PC buses. Automatic configuration sets the basic configuration during installation. For detailed information about the PCI local bus, consult the PCI specification. Installation Requirements The following items are required to install the 3C339 NIC: I PC with at least 640 KB of RAM and an 80486 or Pentium processor I Sufficient memory to load the 3C339 NIC driver from the network operating system I PCI bus slot that supports bus mastering

1-3 I High-density 3.5-inch floppy diskette drive I One of the following token ring cable types: I UTP category 3, 4, or 5 I STP type 1 or 6 I 3Com TokenDisk diskettes #1 and #2, which contain the following items: I Drivers I AutoLink installation program for NetWare DOS ODI clients I 3TLVDIAG configuration and diagnostic program The AutoLink and 3TLVDIAG programs are DOS applications. They must be run in DOS, not in a DOS window. I One of the following PC or network operating systems: I Novell NetWare version 3.1x or 4.x I Microsoft Windows NT version 3.51 or later I Microsoft Windows 95 I Microsoft Windows for Workgroups version 3.11 I DOS version 6.x or later I IBM OS/2 version 2.0 or later Network Driver Options Table 1-1 summarizes 3C339 NIC network drivers and the environments they support. Table 1-1 Driver Support Driver Name Environment 3C3X9.COM Novell NetWare DOS Open Data-Link Interface (ODI) client 3C3X9.LAN Novell NetWare 3.1x and 4.x server, or NetWare Client 32 TLVMP339.SYS Microsoft Windows NT 3.51 and 4.0 Microsoft Windows 95 TL3C3X9.386 Microsoft Windows for Workgroups 3.11 (continued)

Installation Summary These brief installation instructions are for experienced token ring network users. Less experienced users should use the detailed hardware and driver installation instructions beginning in Chapter 2. 1 Install the 3C339 NIC in a PCI slot that supports bus mastering. 2 Connect a token ring cable between the NIC and a hub, a multistation access unit (MAU), a controlled access unit (CAU), or a token ring switch. 3 Power on the PC. At power up, the PC system BIOS automatically configures the NIC’s base I/O address (port address) and interrupt request (IRQ) line. You cannot change these settings, but you can set other parameters or run diagnostics with the 3TLVDIAG configuration and diagnostic program, located on TokenDisk diskette #1. 4 Install the network driver from the TokenDisk diskettes. The default ring speed is 16 Mbps. TL3C3X9.DOS IBM LAN Server 3.0 or later Microsoft Windows for Workgroups Microsoft LAN Manager Banyan VINES Artisoft LANtastic/AI DEC PATHWORKS TL3C3X9.OS2 IBM LAN Server 3.0 or later IBM OS/2 Warp Server Microsoft LAN Manager Banyan VINES 3C3X9LLC.EXE IBM host emulation applications (Client Access/400) Table 1-1 Driver Support (continued) Driver Name Environment

in a PC and how to connect the PC to the network. Before installing the NIC, verify that you have met the installation requirements listed in Chapter 1. Safety Precautions WARNING: Personal computers operate with voltages that may be lethal. Before removing the cover, follow these steps to protect yourself and the PC. 1 Turn off the computer and unplug it. 2 Remove jewelry from your hands and wrists. 3 Use insulated or nonconductive tools. CAUTION: The NIC is packed in a clear plastic antistatic container to protect it during shipment. To avoid damaging the NIC or the PC, reduce static electricity on your body by wearing an electrostatic discharge wrist strap attached to the chassis or by touching the chassis before handling the NIC. Inspecting the NIC 1 Remove the contents of the shipping container and return any packing materials to the shipping container. Verify that the following items were shipped: I TokenLink Velocity PCI NIC (3C339) I TokenLink Velocity PCI Network Interface Card User Guide I Two TokenDisk diskettes (#1 and #2)

If items are missing, contact your authorized network supplier. If it is necessary to return a NIC to 3Com, pack it in the original (or equivalent) packing material to maintain the warranty. 2 Set the antistatic container on a nonstatic surface. 3 Remove the NIC from the antistatic container. 4 Inspect the NIC for visible signs of damage. If you find a problem, contact your network supplier and the carrier that delivered the package. Complete the Product Registration Card and return it to 3Com. Or call 1-800-NET-3Com for immediate registration. Installing the NIC Observe the precautions listed in “Safety Precautions” earlier. Verify that the PC is unplugged. Unpack and inspect the NIC as described in “Inspecting the NIC” earlier. To install the NIC in the PC, follow these steps: 1 Remove the computer cover. Refer to the PC manufacturer’s documentation if necessary. 2 Select an available bus mastering PCI slot and remove its expansion cover plate. 3 Insert the NIC in a PCI-bus slot that supports bus mastering. CAUTION: Do not attempt to install the 3C339 NIC in an ISA or EISA slot. Doing so may damage the NIC and the computer. The 3C339 PCI NIC works only in a PCI-bus slot that supports bus mastering. Check the computer manufacturer’s documentation to determine which PCI slots support bus mastering and which are target slots (sometimes called slave slots).

2-3 In Figure 2-1, PCI-bus slots are the short, white slots; ISA and EISA slots are the longer, shaded slots. Make sure the NIC is completely seated in the slot by pushing down firmly on both ends of the NIC. If necessary, refer to the documentation provided by the computer’s manufacturer for details on installing expansion boards. Figure 2-1 PCI and ISA/EISA Bus Slots in a PCI Computer 4 Secure the slot screw. Connecting to the Network You must connect the NIC to the network before installing drivers or running diagnostics. This section describes how to connect the types of network cables listed in Table 2-1 to the 3C339 NIC. PCI slot ISA/EISA slot

Follow the appropriate procedure for connecting to either a UTP or an STP cable. Connecting to UTP Cable 1 Locate the NIC’s RJ-45 port on the backplate, as shown in Figure 2-2. . Figure 2-2 Connecting the RJ-45 Connector 2 Align the RJ-45 connector on the end of the UTP cable with the notch on the NIC’s RJ-45 port and insert the connector into the port. 3 Connect the other end of the cable to a dual access unit (DAU), a multistation access unit (MAU), a controlled access unit (CAU), or a token ring switch. Table 2-1 Connectors for 3C339 PCI NICs Cable Type Port Used on NIC UTP RJ-45 STP DB-9 RJ-45 port RJ-45 connector INS ACT

2-5 CAUTION: Connect the cable only to the 3C339 NIC you just installed. Connecting the cable to other NICs could seriously damage the NIC and the token ring network. Do not daisy-chain token ring NICs or connect them back to back. Connecting to STP Cable 1 Locate the NIC’s DB-9 port on the backplate, as shown in Figure 2-3. Figure 2-3 Connecting the DB-9 Connector 2 Connect the cable’s DB-9 connector to the NIC’s DB-9 port, and secure the connector by tightening the two screws. 3 Connect the other end of the cable to a dual access unit (DAU), a multistation access unit (MAU), a controlled access unit (CAU), or a token ring switch. CAUTION: Connect the cable only to the 3C339 NIC you just installed. Connecting the cable to other NICs could cause serious damage to the NIC and the token ring network. Do not daisy-chain token ring NICs or connect them back to back. DB-9 port DB-9 connector INS ACT

Powering Up the PC After completing the installation procedures, power up the PC. At power up, the PC system BIOS automatically configures the NIC’s base I/O address (port address) and interrupt request line (IRQ). You cannot change these settings, but you can set other parameters or run diagnostics with the 3TLVDIAG configuration and diagnostic program, located on TokenDisk diskette #1. Before installing drivers as described in Chapter 3, you may want to run diagnostics as described in Chapter 4. Wait until you are satisfied that the NIC hardware and drivers are installed correctly before replacing the computer cover.

NIC network drivers. The drivers are located on the TokenDisk diskettes shipped with the NIC. To obtain drivers not included on the diskettes, contact the manufacturer of that network operating system or application. To obtain software updates and patches for 3Com drivers, use one of the bulletin board services listed in Appendix C, “Technical Support.” The 3C339 PCI drivers are not backward-compatible with the 3Com TokenLink Velocity 3C319 ISA NIC or with TokenLink III 3C6x9 ISA, EISA, MCA, or PC Card NICs. Locating Driver Installation Procedures Table 3-1 shows where to find driver installation procedures, whether in this chapter or on the TokenDisk diskettes. Table 3-1 Driver Installation Procedure Locations Environment Driver Installation Procedure Location Novell NetWare One NIC in a client “One NIC in a Client (DOS ODI)” on page 3-5 One NIC in a server “Installation with NetWare 3.11” on page 3-8 “Installation with NetWare 3.12 and 4.x” on page 3-8 Multiple NICs in a server “Installation with NetWare 3.11” on page 3-10 “Installation with NetWare 3.12 and 4.x” on page 3-11 Microsoft Windows NT 3.51 “Windows NT 3.51” on page 3-12 Microsoft Windows NT 4.0 “Windows NT 4.0” on page 3-13 Microsoft Windows 95 “Windows 95” on page 3-15 IBM OS/2 (IBM LAN Server) “Installing the OS/2 Driver” on page 3-17 (continued)

You can use any text editor to read the text files on diskettes. Or, use this procedure to read the text files. 1 Use the appropriate procedure described in Table 3-2 to boot the computer with DOS version 6.x or later. 2 Verify that no network drivers are loaded into RAM. 3 Verify that the computer is physically connected to the network. (Refer to Chapter 2.) 4 Insert TokenDisk diskette #1 in a floppy drive (usually A: or B:) and make that the active drive. 5 At the prompt enter: install 6 Select Network Drivers in the main menu. 7 Select NDIS Driver Installation and Information. 8 Select the appropriate network operating system from the menu choices. An information screen appears with instructions on how to manually install and configure the driver. Refer also to your network operating system manuals for additional information. 9 Follow the instructions to install the drivers. Microsoft Windows for Workgroups 3.11 TokenDisk diskette #1, \NDIS\WFW.TXT IBM LAN Server TokenDisk diskette #1, \NDIS\LANSRV.TXT Microsoft LAN Manager TokenDisk diskette #1, \NDIS\LANMAN.TXT Banyan VINES DOS Client TokenDisk diskette #1, \NDIS\BANYAN.TXT Artisoft LANtastic/AI TokenDisk diskette #1, \NDIS\LANTASTK.TXT DEC PATHWORKS TokenDisk diskette #1, \NDIS\PATHWORK.TXT IBM Client Access/400 TokenDisk diskette #1, \NDIS\LANSUP.TXT Table 3-1 Driver Installation Procedure Locations (continued) Environment Driver Installation Procedure Location

accessing DOS and for finding the NIC’s port address. Use these procedures only when other procedures in this guide tell you to do so. Starting DOS The AutoLink installation program and the 3TLVDIAG configuration and diagnostic program are DOS applications that must be run with no drivers or memory managers installed. They require that you boot from DOS without running the AUTOEXEC.BAT or CONFIG.SYS files. The programs do not run in Windows NT or Windows 95 DOS windows. If you are using an operating system other than DOS, use the appropriate procedure in Table 3-2 to start DOS before running the AutoLink program or 3TLVDIAG. Table 3-2 Starting DOS from Other Operating Systems Operating System Procedure for Starting DOS OS/2 1 Boot the computer from a bootable DOS diskette. 2 Run the AutoLink program or 3TLVDIAG from the DOS command prompt. Windows 3.x 1 Boot the computer from a bootable DOS diskette. 2 Run the AutoLink program or 3TLVDIAG from the DOS command prompt. Windows 95 1 Select Shutdown. Then select Restart the computer in MS-DOS mode from the Restart menu. 2 Run the AutoLink program or 3TLVDIAG from the DOS command prompt. Windows NT 1 Boot the computer from a bootable DOS diskette. 2 Run the AutoLink program or 3TLVDIAG from the DOS command prompt.

Finding the NIC’s Port Address In a NetWare environment, you must know the NIC’s port address (base I/O address) to install the driver when there are multiple NICs in a server. To find the port address, follow these steps: 1 Make a note of the NIC’s node (MAC) address. The address (a number such as A02461179) is located on the NIC label. 2 Start DOS using the appropriate procedure in Table 3-2. 3 Insert TokenDisk diskette #1 in the floppy drive and make that the active drive. 4 At the DOS prompt, enter: 3tlvdiag 5 When the 3Com 3TLVDIAG main menu appears, select Adapter Configuration, and press [Enter]. The Adapters Found in System screen appears, listing all installed 3C339 PCI NICs and their node addresses. Locate the node address you noted earlier. This is the NIC whose port address you need. 6 Select the NIC whose port address you need and press [Enter]. The Adapter Configuration screen appears with the base I/O address shown as a four-digit hexadecimal number. This is the port address. Installing NetWare Drivers This section describes how to install NetWare drivers in these networking situations: I One NIC in a client (DOS ODI environment) I One NIC in a server I Multiple NICs in a server When you install drivers, you can set certain parameters. For details, see Table A-1.

3-5 One NIC in a Client (DOS ODI) This section describes a procedure for using the AutoLink program to install a NetWare DOS ODI client for a single NIC. DOS ODI client drivers for the 3Com 3C339 PCI NIC support shared interrupts (IRQs). However, in some dual-bus EISA/PCI systems, an EISA or an ISA NIC may be unable to resolve contentions for the IRQ shared with a PCI NIC. This may impair the operation of one or both of the NICs sharing the IRQ. In this case, assign the EISA or ISA NIC another IRQ using the system CMOS configuration program or another utility appropriate to your operating system. If you discover that another PCI NIC does not support shared interrupts, contact the manufacturer for a shared interrupt driver. About the AutoLink Program The AutoLink program installs NetWare DOS ODI client software, including drivers. It also modifies the CONFIG.SYS and AUTOEXEC.BAT files. The AutoLink program is a DOS application. The program will not run in a Windows NT or Windows 95 DOS window. The AutoLink program cannot be used to install an OS/2, Windows NT, or Windows 95 client. If your system administrator has configured a 3Install account on your server, the AutoLink program automatically logs on to the server and updates the client software. Otherwise, client software is installed from the TokenDisk diskettes. For instructions on configuring a 3Install account, see the QINSTALL\SERVER\README.TXT text file on TokenDisk diskette #1. AutoLink Program Requirements To use the AutoLink program, your computer must meet the following requirements: I Have only one 3C339 PCI NIC installed

I Be intended for use as a NetWare DOS ODI client connecting to a Novell NetWare 3.x or 4.x server I Have no network drivers loaded before you run the AutoLink program You can use the AUTOLINK.CFG file to modify the AutoLink process. The AUTOLINK.CFG file in the root directory of TokenDisk diskette #1 contains default settings and descriptions of other control parameters. Running the AutoLink Program Follow these steps to run the AutoLink program: 1 Verify that no network drivers are loaded into RAM. 2 Verify that the computer is physically connected to the network. (Refer to Chapter 2.) 3 Insert TokenDisk diskette #1 in the floppy drive and make that the active drive. 4 At the DOS prompt enter: autolink A screen appears, prompting you to enter the ring speed. 5 Enter the ring speed. Ring speed may be 4 or 16; 16 is the default. Be sure the number you enter matches the network’s ring speed. If the numbers do not match, an error removes the NIC from the network. Auto installation may take a few moments. Several messages appear while the AutoLink program is running. A final message indicating successful installation appears. 6 When the auto installation process is finished, remove the diskette and reboot the computer. A DOS ODI client starts and connects the client computer to a NetWare server. This concludes the procedure for installing the driver for one NIC in a NetWare DOS ODI client.

3-7 AutoLink Troubleshooting If you experience problems when using the AutoLink program, display or print the AUTOLINK.LOG file, which contains a log of the events that occurred during the AutoLink installation and configuration process. 1 To display the file, enter the following DOS command: type autolink.log | more 2 To print the file, connect to a local printer and enter: copy autolink.log prn About Installing on a NetWare Server NetWare Loadable Modules (NLMs) permit the 3C3X9.LAN NetWare 4.x server driver to be used with NetWare versions 3.11, 3.12, or 4.x. The driver and NLM files are in the following locations on TokenDisk diskette #1: I NetWare 3.11: \NETWARE\SERVER\3.11 I NetWare 3.12: \NETWARE\SERVER\3.12 I NetWare 4.x: \NETWARE\SERVER\4.X Use the most recent NLMs available. Compare the versions that accompanied your NetWare software with the appropriate files on TokenDisk diskette #1. For the latest NLMs, contact Novell. For more details on the driver and examples of server installation options, see the \NETWARE\SERVER\3C3X9SRV.TXT file on TokenDisk diskette #1. One NIC in a Server This section describes procedures for installing the driver when you are running NetWare and have installed a single NIC in a computer that is functioning as a server. Before installing the driver, see the previous section “About Installing on a NetWare Server” for important information about NetWare Loadable Modules.

Installation with NetWare 3.11 To install the NetWare server driver for NetWare 3.11, follow these steps: 1 Determine the NIC’s port address, as described in “Finding the NIC’s Port Address” earlier in this chapter. 2 Before starting the server, copy the contents of the \NETWARE\SERVER\3.11 directory on TokenDisk diskette #1 to the boot partition of the server’s hard disk. 3 Start the server and enter the following commands at the server prompt: load C:LSLENH.NLM load C:3C3X9.LAN PORT=XXXX where XXXX is the NIC’s port address. Be sure to load LSLENH.NLM before loading the 3C3X9.LAN driver, or system malfunction will occur. If your token ring network is running at 4 Mbps, add the SPEED parameter to the driver load command. For example: load C:3C3X9.LAN PORT=XXXX SPEED=4 4 Bind the transport protocol to the driver. Add the load and bind commands to the AUTOEXEC.NCF file for automatic execution when you start or restart the server. This concludes the procedure for installing the NetWare server driver for one NIC in a server with NetWare 3.11. Installation with NetWare 3.12 and 4.x To install the NetWare server driver under NetWare 3.12, you need the following files from Novell: I 312PTA.EXE (or later) I LANDR9.EXE

3-9 To install the NetWare server driver while running NetWare 3.12 or 4.x, follow these steps: 1 Determine the NIC’s port address, as described in “Finding the NIC’s Port Address” earlier in this chapter. 2 Before starting the server, copy the contents of the appropriate directory on TokenDisk diskette #1 to the boot partition of the server’s hard disk: I For NetWare 3.12, use the \NETWARE\SERVER\3.12 directory. I For NetWare 4.x, use the \NETWARE\SERVER\4.X directory. 3 Start the server and enter the following command at the server prompt: load C:3C3X9.LAN PORT=XXXX where XXXX is the NIC’s port address. 4 Bind the appropriate transport protocol to the NIC name. Add the load and bind commands to the AUTOEXEC.NCF file for automatic execution when you start or restart the server. This concludes the procedure for installing the NetWare server driver for one NIC in a server with NetWare 3.12 and 4.x. Multiple NICs in a Server If you are running NetWare and have installed multiple NICs in a computer that is functioning as a server, follow the instructions in this section to install the driver. Before installing the driver, see “About Installing on a NetWare Server” earlier in this chapter for important information about NetWare Loadable Modules.

Installation with NetWare 3.11 To install the NetWare server driver for NetWare 3.11, follow these steps: 1 Determine the NIC port addresses, as described in “Finding the NIC’s Port Address” earlier in this chapter. 2 Before starting the server, copy the contents of the \NETWARE\SERVER\3.11 directory on TokenDisk diskette #1 to the boot partition of the server’s hard disk: 3 Start the server and enter the following commands at the server prompt: load C:LSLENH.NLM load C:3C3X9.LAN PORT=XXXX NAME=X load C:3C3X9.LAN PORT=XXXX NAME=Y where XXXX is a NIC port address and X and Y are names that you assign to help distinguish the multiple NICs. Be sure to load LSLENH.NLM before loading the 3C3X9.LAN driver, or system malfunction will occur. The PORT=XXXX parameter must be completed for all NICs. 4 Bind the appropriate transport protocol to each NIC name. Add the load and bind commands to the AUTOEXEC.NCF file for automatic execution when you start or restart the server. This concludes the procedure for installing the NetWare server driver for multiple NICs in a server with NetWare 3.11.

3-11 Installation with NetWare 3.12 and 4.x To install the NetWare server driver for NetWare while running NetWare 3.12 or 4.x, follow these steps: 1 Determine the NIC port addresses, as described in “Finding the NIC’s Port Address” earlier in this chapter. 2 Before starting the server, copy the contents of the appropriate directory on TokenDisk diskette #1 to the boot partition of the server’s hard disk: I For NetWare 3.12, use the \NETWARE\SERVER\3.12 directory I For NetWare 4.x, use the \NETWARE\SERVER\4.X directory 3 Start the server and enter the following commands at the server prompt: load C:3C3X9.LAN PORT=XXXX NAME=X load C:3C3X9.LAN PORT=XXXX NAME=Y where XXXX is a NIC port address and X and Y are names that you assign to help distinguish the multiple NICs. The PORT=XXXX parameter must be completed for all NICs. 4 Bind the appropriate transport protocol to each NIC name. Add the load and bind commands to the AUTOEXEC.NCF file for automatic execution when you start or restart the server. This concludes the procedure for installing the NetWare server driver for multiple NICs in a server with NetWare 3.12 or 4.x.

Installing the Microsoft Windows Driver This section contains procedures for installing the driver for the following Microsoft Windows environments: I Windows NT 3.51 I Windows NT 4.0 I Windows 95 Windows NT 3.51 Follow this procedure to install the driver for Windows NT 3.51. It is assumed that you are already running Windows NT. 1 Go to the Add Network Adapter dialog box as follows: a From the Main group, double-click the Control Panel icon. b From the Control Panel group, double-click the Network icon. c From the Network Settings dialog box, click the Add Adapter button. 2 From the Add Network Adapter dialog box, scroll to the bottom of the Network Adapter Card selection list. Click Requires disk from manufacturer and click Continue. The Insert Disk dialog box appears. 3 Insert TokenDisk diskette #2 in the floppy drive. 4 Type the following path and click OK: a:\winnt There is a short delay while Windows NT reads the diskette. The Select OEM Option dialog box appears. 5 Select 3Com TokenLink Velocity PCI Adapter and click OK. Messages appear while files are being copied. The Bus Location dialog box appears.

3-13 6 Select bus type PCI and bus number 0, and click OK. The 3Com TokenLink Adapter Setup dialog box appears. 7 Select any of the following setup options and click OK: I PCI slot—Autodetect, Slot 1, Slot 2, or Slot 3. It is recommended that you use the default setting, Autodetect. I Network speed—4 or 16 Mbps. This selection must match the network speed, or an error will remove the NIC from the network. I Advanced—You can specify maximum packet size, network address, and product ID. It is recommended that you use the default settings. The Network Setup dialog box appears. 8 Verify that 3Com TL 3C339 Adapter is in the Installed Adapter Cards list and that 3Com TokenLink Driver is in the Installed Network Software list, and click OK. Configuration messages appear. The Network Settings Change dialog box appears. 9 Remove the TokenDisk diskette from the floppy drive and restart the computer. This concludes the procedure for installing the driver for Windows NT 3.51. Windows NT 4.0 Follow this procedure to install the driver for Windows NT 4.0. It is assumed that you are already running Windows NT. 1 From the My Computer group, double-click the Control Panel icon. 2 From 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 Insert TokenDisk diskette #2 in the floppy drive. 7 Type the following path and click OK: a:\winnt The Select OEM Option dialog box appears. 8 Select 3Com TokenLink Velocity PCI Adapter and click OK. The 3Com TokenLink Velocity PCI Adapter Bus dialog box appears. 9 Select bus type PCI and bus number 0 and click OK. The 3Com TokenLink Adapter Setup dialog box appears. 10 Make any of the following adapter setup selections and click OK: I PCI slot—Autodetect, Slot 1, Slot 2, or Slot 3. It is recommended that you use the default setting, Autodetect. I Network speed—4 or 16 Mbps. This selection must match the network speed, or an error will remove the NIC from the network. I Advanced—You can specify maximum packet size, network address, and product ID. It is recommended that you use the default settings. 11 Verify that 3Com TL 3C3X9 Adapter appears in the list in the Network Adapters tab and click Close. Bindings messages appear, followed by a prompt to restart the computer. 12 Remove the TokenDisk diskette from the floppy drive. 13 Click Yes to restart the computer. This concludes the procedure for installing the driver for Windows NT 4.0.

3-15 Windows 95 This section describes procedures for installing the Windows 95 driver under Microsoft OEM Service Release (OSR) versions 1 and 2. About OSR Versions Some computers are sold with a special Windows 95 OEM Service Release (OSR) already installed. The installation procedures under OSR version 2 (OSR2) differ from those of the previous OSR release (OSR1). To determine which OSR version you are using, open the Control Panel, select System, and look at System information under the General tab. If your release is version 4.00.950, you are using OSR1. If your release is version 4.00.950 B, you are using OSR2. OSR1 Installation Follow this procedure to install the driver for Windows 95 under OSR1. It is assumed that you are already running Windows 95. During installation, have the Windows 95 software accessible on diskettes, CD, or a hard drive in case the installation utility requests files from the Windows 95 software library. 1 Install the 3C339 NIC and start the computer. Windows 95 detects the new hardware. PCI Token Ring Controller appears in the New Hardware Found dialog box. 2 Click the Driver from disk provided by hardware manufacturer radio button and click OK. The Install from Disk dialog box appears. 3 Insert TokenDisk diskette #2 in the floppy drive. 4 Type the following path and click OK. a:\win95 Messages appear while files are being copied. The System Settings Change dialog box appears.

5 Remove the TokenDisk diskette from the floppy drive. 6 Click Yes to restart the computer. This concludes the procedure for installing the driver for Windows 95 under OSR1. OSR2 Installation Follow this procedure to install the driver for Microsoft Windows 95 under OSR2. It is assumed that you are already running Windows 95. During installation, have the Windows 95 software accessible on diskettes, CD, or a hard drive in case the installation utility requests files from the Windows 95 software library. 1 Install the 3C339 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 Locations dialog box appears. 4 Insert TokenDisk diskette #2 in the floppy drive. 5 Type the following path and click OK: a:\win95 6 Verify that the Update Device Driver Wizard dialog box lists 3Com TokenLink Velocity PCI Adapter, and click Finish. Messages appear while files are being copied. The System Settings Change dialog box appears. 7 Remove the TokenDisk diskette from the floppy drive.

3-17 8 Click Yes to restart the computer. This concludes the procedure for installing the driver for Windows 95 under OSR2. Installing the OS/2 Driver To install the OS/2 driver, you need one of the following IBM installation programs: I LAN Adapter and Protocol Support (LAPS) I Multi Protocol Transport Services (MPTS) LAPS Installation To install the OS/2 driver with LAPS, you must be running OS/2 version 2.11 or later, including any software fixes for PCI support. (For OS/2 fix packs, contact IBM.) You also need to know the names of the network protocols your network environment uses. 1 Insert TokenDisk diskette #2 in the floppy drive. 2 Open an OS/2 window. At the OS/2 prompt, enter: laps LAPS is usually located in the \IBMCOM directory on the boot drive. 3 In the LAPS window, select Install. At the prompt for the source of the .NIF file, type the following path and click OK: a:\ndis\os2 4 When the Installation Complete for PCI Token Ring Adapter message appears, click OK. The LAPS dialog box appears. 5 Select Configure. 6 Verify that the Configure LAN Transport radio button is selected, and click Continue. The Configuration Workstation panel appears.

7 From the Network Adapters list box, select 3C339 TokenLink Velocity Adapter and click Add. You can edit parameter settings by selecting 3Com TokenLink Velocity Adapter and clicking Edit. 8 In the Protocols list box, select each protocol used by your network application and click Add. The protocol drivers appear under the NIC driver name in the Current Configuration list box. You can edit protocol parameter settings by selecting a protocol and clicking Edit. 9 Click OK and then click Exit. 10 In the IBM logo panel, click Exit. Messages about updates to the CONFIG.SYS file appear. 11 Make sure the correct drive and directory for the CONFIG.SYS file are specified, and click Continue. 12 Exit the program. At the prompt for updating the CONFIG.SYS, STARTUP.CMD, and PROTOCOL.INI files, click OK. 13 In the Exiting LAPS window, click Exit. 14 If your token ring network is running at 4 Mbps, you must edit the PROTOCOL.INI file to set the ring speed. Include the SPEED parameter after the DriverName TL3C3X$ line. For example: [TL3C3X9_NIF] DriverName=TL3C3X$ SPEED=4 PACKETSIZE=4096 15 Remove the TokenDisk diskette and restart the computer. This concludes the LAPS procedure for installing the OS/2 driver.

3-19 MPTS Installation To install the OS/2 driver with MPTS, you need to know the names of the network protocols your network environment uses. 1 Use one of the following methods to start MPTS: I From the OS/2 desktop, double-click the MPTS icon. I From an OS/2 window, go to the \IBMCOM subdirectory and at the OS/2 prompt enter: mpts 2 In the MPTS logo panel, click OK. The MPTS window appears. 3 Insert TokenDisk diskette #2 in the floppy drive. 4 In the MPTS window, select Install. At the prompt for the source of the .NIF file, type the following path and click OK: a:\ndis\os2 5 When the Installation Complete for PCI Token Ring Adapter message appears, click OK. The MPTS dialog box appears. 6 Select Configure. The Configure panel appears. 7 Verify that the LAN adapters and protocols radio button is selected, and click Configure. 8 From the Network Adapters list box, select 3C339 TokenLink Velocity Adapter and click Add. You can edit parameter settings by selecting 3C339 TokenLink Velocity Adapter and clicking Edit. 9 In the Protocols list box, select each protocol used by your network application and click Add. The protocol drivers appear under the NIC driver name in the Current Configuration list box. You can edit protocol parameter settings by selecting a protocol and clicking Edit.

10 Click OK when you have finished selecting and editing protocols. 11 In the Configure panel, click Close. 12 In the MPTS dialog box, click Exit. 13 In the Update CONFIG.SYS panel, click Exit to update the CONFIG.SYS file. 14 When a message indicates that the CONFIG.SYS file has been successfully updated, click OK. 15 In the Exiting MPTS panel, click Exit. 16 If your token ring network is running at 4 Mbps, you must edit the PROTOCOL.INI file to set the ring speed. Include the SPEED parameter after the DriverName TL3C3X$ line. For example: [TL3C3X9_NIF] DriverName=TL3C3X$ SPEED=4 PACKETSIZE=4096 17 Remove the TokenDisk diskette and restart the computer. This concludes the MPTS procedure for installing the OS/2 driver.

3TLVDIAG diagnostic and configuration program and what to do if a test fails. 3C339 PCI NIC diagnostics are not backward-compatible with the 3Com TokenLink Velocity 3C319 ISA NIC or with TokenLink III 3C6X9 ISA, EISA, MCA, or PC Card NICs. About the Diagnostic Tests The diagnostic tests discover problems such as hardware conflicts or NIC faults, and they check the NIC’s overall operation. The NIC must be connected to the network to run the tests. The following tests check the NIC’s physical components and circuitry: I Adapter Register Test I EEPROM Checksum Test I Adapter Memory Test The following tests check the NIC’s ability to transmit and receive packets to and from the network: I Transmit in Wrap Mode Tests I Transmit in Insert Mode Tests The tests may be run separately, in combination with one another, or all together as a suite. If the NIC passes all tests successfully, NIC hardware failure is ruled out. If a problem still remains, look at cabling, software, and other issues that affect functionality on the network. For troubleshooting suggestions, see “What to Do If a Test Fails” later in this chapter.

Running the Diagnostic Tests The 3TLVDIAG diagnostic and configuration program is a DOS application that must be run with no drivers or memory managers installed. It requires that you boot from a bootable DOS diskette without running the AUTOEXEC.BAT or CONFIG.SYS files. 3TLVDIAG will not run in a Windows NT or a Windows 95 DOS window. To use 3TLVDIAG, follow these steps: 1 Make sure that the NIC is correctly installed. (For installation procedures, see Chapter 2.) 2 If you are using an operating system other than DOS, use the appropriate procedure in Table 3-2 to start DOS. 3 Insert TokenDisk diskette #1 in the floppy drive and make that the active drive. 4 At the DOS prompt, enter: 3tlvdiag The 3Com 3TLVDIAG program main menu appears, as shown in Figure 4-1. Figure 4-1 3TLVDIAG Program Main Menu 3Com 3TLVDIAG Main Menu Adapter Diagnostics F1 = Help F2 = Keyboard Conventions This choice allows you to configure your adapter. Exit Continue Adapter Configuration

4-3 5 In the main menu, select Adapter Diagnostics and then select Continue. To make selections in 3TLVDIAG: I Use the [Tab] key to select buttons, and press [Enter]. I Use the arrow keys to select other items, and press [Enter]. The Adapters Found in System screen appears, listing all installed 3C339 PCI NICs. 6 Select the NIC you want to test. The Diagnostic Setup screen for the selected NIC appears, as shown in Figure 4-2. Figure 4-2 Diagnostic Setup Screen 7 Select the ring speed and select Continue. The ring speed can be 4 or 16 Mbps (16 is the default). This selection must match the network speed, or an error will remove the NIC from the network. This selection remains in effect during the diagnostics session. When you exit the diagnostics, the ring speed reverts to that specified during installation. 3Com 3TLVDIAG – Diagnostics Diagnostic Setup 3C3X9 Node Address: 00E0FCFFFCFE Diagnostic Options Override Ring Speed: 16 Mbps Adapter Configuration F1 = Help F2 = Keyboard Conventions Press Continue or to see the list of tests to run. Base I/O: IRQ: FCE0 15 LAN Speed: 4 Mbps Exit Previous Screen Continue Main Menu

The Diagnostic Test screen appears, as shown in Figure 4-3. Figure 4-3 Diagnostic Test Screen 8 To run all the tests once (one iteration of the test suite), select Run Diagnostics. The number entered in the Full Test Suite field is the number of times the test suite will run. To run the tests individually or in various combinations, enter 0 in the Full Test Suite field. Then enter the number of times you want a test to run in the field next to its name. Then select Run Diagnostics. If the NIC fails a test, an information screen appears. For a description of each test, press [F1] to access help. The following message indicates that all tests have passed: Diagnostics have completed with the status of PASSED. 9 Select Exit to exit the diagnostic tests. 10 Remove the TokenDisk diskette and reboot the computer. 3Com 3TLVDIAG – Diagnostics Diagnostic Test 3C3X9 Node Address: 00E0FCFFFCFE Ring Speed: 16 Mbps Select the number of iterations to run the tests: Runs through all the tests listed below. F1 = Help F2 = Keyboard Conventions Exit Previous Screen Run Diagnostics Main Menu Full Test Suite: 1 Adapter Register Test: 0 EEPROM Checksum Test: 0 Adapter Memory Test: 0 Transmit In Wrap Tests: 0 Transmit In Insert Tests: 0

4-5 What to Do If a Test Fails If the diagnostic tests fail, the NIC may not be defective. The problem may be an incorrect setting of a NIC configuration parameter that conflicts with the settings of other NICs, or improper installation. Complete the following checks to test the NIC further. CAUTION: Turn the power off and unplug the computer before inserting or removing the NIC. I Make sure the NIC is seated correctly in the slot. Check the NIC installation by reviewing the installation instructions in Chapter 2. I Inspect all cables and connections. Check for specific hardware problems, such as broken traces or loose/broken solder connections. Swap with known working parts. I Make sure that the PCI slot containing the NIC is activated. PCI computers allow PCI slots to be activated or deactivated. This is done through the computer’s CMOS utility, or in some cases, with a special PCI utility. Refer to your computer documentation for information about activating PCI slots. I Make sure that the PCI slot with the NIC in it is a bus master slot. Bus mastering is not supported on all PCI slots in all computers. The 3C339 PCI NIC will work only in a bus master slot. Refer to your computer documentation to identify the bus mastering slots, or call the computer manufacturer. I If you have installed the NIC correctly and you still experience problems, check the software. Make sure that you have installed the correct drivers for the network operating system you are running (refer to Chapter 3, “Network Driver Installation”).

I Make sure you booted your computer with a bootable diskette of DOS version 6.x or later, and that no device drivers or memory managers are loaded. I Install the NIC in another PCI slot and run the diagnostic tests again. The original slot may be defective, or it may not support bus mastering. I Replace the failed NIC with a working NIC and run the diagnostic tests again. Use the same option settings as those used on the failed NIC. If the working NIC passes all tests, the original NIC is probably defective. For details on repair procedures, refer to Appendix C, “Technical Support.” I Install the NIC in another functioning computer and run the tests again. Your computer may be defective or there may be a resource conflict. If the NIC passes the tests in the second computer, contact the reseller or manufacturer of the original computer. Make sure you have the latest BIOS installed in the computer. I If you experience problems that occur only when using the AutoLink program, display or print the AUTOLINK.LOG file. The AUTOLINK.LOG file contains a log of all the events that occurred during the AutoLink installation and configuration process. To display the file, enter: type autolink.log | more To print the file, enter: print autolink.log If any problem persists, refer to Appendix C, “Technical Support.’’

(LEDs) that facilitate troubleshooting and maintenance. Table 4-1 describes the LEDs. Table 4-1 LED Indicators LED State Meaning INS (green) ON NIC is inserted into the ring. OFF NIC is not inserted into the ring. ACT (amber) ON Data is being transmitted by the NIC. OFF No data is being transmitted by the NIC.

configuration parameter values with the 3TLVDIAG diagnostic and configuration program. At power up, the system BIOS automatically configures the NIC with port address and IRQ parameters. You cannot change these parameters with the 3TLVDIAG program. Table A-1 lists the 3C339 PCI NIC configuration parameters you can change with the 3TLVDIAG program. Table A-2 lists other 3C339 PCI NIC configuration parameters. You cannot change these parameters with the 3TLVDIAG program. They can be changed within the operating system configuration files. The parameter syntax shown in Table A-1 and Table A-2 is for NetWare and may be included in the NetWare NET.CFG file. The parameter syntax may be different with different operating systems. Table A-1 3C339 NIC Configuration Parameters (Modifiable with 3TLVDIAG) Parameter Description Default Value Supported Values SPEED Sets the ring speed of the network to which the NIC is connecting. 16 Mbps 4,16 Mbps POST WRITE Allows the driver to post one command to the controller. DISABLED DISABLED ENABLED (continued)

SBCLK RATIO Determines the speed at which the NIC operates as a ratio of PCI bus speed. If the NIC fails to initialize or performs erratically, set at 1. If necessary try settings 2, 3, and 4 in order. 1 1, 2, 3, 4 LOCAL BUS SPEED Sets the speed of the NIC’s on-board communications processor. 6 MHz 4, 6 MHz Table A-1 3C339 NIC Configuration Parameters (Modifiable with 3TLVDIAG) (continued) Parameter Description Default Value Supported Values Table A-2 3C339 NIC Configuration Parameters (Not Modifiable with 3TLVDIAG) Parameter Description Default Value Supported Values FRAME Specifies the frame type. TOKEN-RING TOKEN-RING TOKEN-RING_SNAP NODE ADDRESS Sets the optional locally administered node address. IEEE globally administered node ID 400000000000 to 400023456789 DETR Disables early token release. Early token release enabled Not applicable MAX FRAME SIZE Sets the maximum frame size transmitted and received by the NIC. 4216 bytes 618 to 17960 bytes NON-VDS Used when the memory manager does not conform to virtual DMA services. Memory manager assumed to conform to virtual DMA services Not applicable REINSERT Makes the NIC driver automatically reinsert into the network after a remove frame is received. Driver does not reinsert after a remove frame is received Not applicable LATENCY TIMER Sets the maximum length of time during which the NIC can transfer data to the PCI bus. Set by PCI system 0–248 (units of 8)

A-3 Changing Configuration Parameter Values You can change only the following configuration parameter values with the 3TLVDIAG program: I Ring Speed This selection remains in effect during the 3TLVDIAG session. When you exit the program, the ring speed reverts to that specified during installation. I Post Write I SBCLK Ratio I Local Bus Speed All other parameters must be changed within the system configuration files appropriate to your operating system. Refer to the sample NET.CFG and PROTOCOL.INI files on the TokenDisk diskettes. The 3TLVDIAG program is a DOS application that must be run with no drivers or memory managers installed. It requires that you boot from DOS without running the AUTOEXEC.BAT or CONFIG.SYS files. The 3TLVDIAG program will not run in a Windows NT or a Windows 95 DOS window. To change NIC configuration parameter values with the 3TLVDIAG diagnostic and configuration program, follow these steps: 1 If you are using an operating system other than DOS, use the appropriate procedure in Table 3-2 to start DOS. 2 Insert TokenDisk diskette #1 in a floppy drive and make that the active drive. 3 At the DOS prompt enter: 3tlvdiag The 3Com 3TLVDIAG program main menu appears, as shown in Figure A-1.

Figure A-1 3TLVDIAG Program Main Menu 4 In the main menu, select Adapter Configuration. To make selections in 3TLVDIAG: I Use the [Tab] key to select buttons, and press [Enter]. I Use the arrow keys to select other items, and press [Enter]. The Adapters Found in System screen appears, listing all installed 3C339 PCI NICs. 5 In the Adapters Found in System screen, do one of the following: I If you have a single NIC installed, it is already selected. Press [Enter]. I If you have multiple NICs installed, use the arrow keys to select a NIC. Press [Enter]. The Adapter Configuration screen for the selected NIC appears, as shown in Figure A-2. 3Com 3TLVDIAG Main Menu Adapter Diagnostics F1 = Help F2 = Keyboard Conventions This choice allows you to configure your adapter. Exit Continue Adapter Configuration

A-5 Figure A-2 Adapter Configuration Screen The NIC configuration parameters that can be changed are shown in the Extended Options box. These Extended Options are Ring Speed, Post Write, SBCLK Ratio, and Local Bus Speed. 6 Select the arrow buttons for the Extended Options fields to display lists of values for the options. Select new values if desired. 7 Select Save Config to save any changes. 8 Select Exit to exit the program. 9 Remove the TokenDisk diskette and reboot the computer. 3Com 3TLVDIAG – Diagnostics Adapter Configuration 3C3X9 Node Address: 00E0FCFFFCFE Standard Options The above settings have been automatically configured via PCI BIOS Base I/O: IRQ: 15 FCE0 Extended Options F1 = Help F2 = Keyboard Conventions Select the speed of you network. SBCLK Ratio: Local Bus Speed: Exit Previous Screen Auto Config Save Config Main Menu 6 1 Mbps Disabled Ring Speed: Post Write: 16

assignments, and cable requirements for the 3C339 PCI NIC. NIC Specifications Network Interface IEEE 802.5 token ring network with 16 Mbps or 4 Mbps transmission rate. Physical Dimensions Environmental Operating Range Power Requirements 0 mA @ +3.3V, maximum 450 mA @ +5V, maximum 3 mA @ +12V, maximum Compatibility PCI Local Bus Specification, Rev. 2.0 Bus Data Interface 32-bit bus-mastering Length: 5.3 in (2.1 cm) Height: 2.7 in (1.1 cm) 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%

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 Classifications FCC Class B, digital device EN55022 Class B VCCI 2nd Class category European Community Classification EE-Compliant Safety Classifications UL 1950 (ITE) TUV EN60950:1992 Electromagnetic Susceptibility EN50082-1 IEC801-2 (ESD) IEC801-3 (Radiated Immunity) IEC801-4 (Fast Transient Burst)

B-3 RJ-45 Connector Pin Assignments The RJ-45 connector pin assignments are shown in Figure B-1. Figure B-1 RJ-45 Connector Pin Assignments DB-9 Connector Pin Assignments The DB-9 connector pin assignments are shown in Figure B-2. Figure B-2 DB-9 Connector Pin Assignments ACT Receive pair (4 and 5) Transmit pair (3 and 6) 8 7 6 5 4 3 2 1 1 2 3 4 5 6 7 8 A Receive pair Transmit pair Orange Green Black Red 9 8 7 6 5 4 3 2 1 9 8 7 6 5 4 3 2 1

Cable Requirements The DB-9 connector can be used to connect to shielded twisted-pair (STP) cabling (Type 1 or 6). The RJ-45 connector can be used to connect to unshielded twisted-pair (UTP) cabling (Category 3, 4, or 5). Media type selection is made automatically when you connect cabling to one of the connectors. The Auto Select Media Type capability enables drivers to automatically detect the type of media connector.

information through a variety of services. This appendix describes these services. Information contained in this appendix is correct at time of publication. For the very latest, we recommend that you access 3Com Corporation’s World Wide Web site as described below. Online Technical Services 3Com offers worldwide product support 24 hours a day, 7 days a week, through the following online systems: I World Wide Web site I 3Com Bulletin Board Service (3ComBBS) I 3ComFactsSM automated fax service I 3ComForum on CompuServe® online service World Wide Web Site Access the latest networking information on 3Com Corporation’s World Wide Web site by entering our URL into your Internet browser: http://www.3Com.com/ This service features the latest information about 3Com solutions and technologies, customer service and support, news about the company, NetAge® Magazine, and more.

3Com Bulletin Board Service 3ComBBS contains patches, software, and drivers for all 3Com products, as well as technical articles. This service is available through analog modem or digital modem (ISDN) 24 hours a day, 7 days a week. Access by Analog Modem To reach the service by modem, set your modem to 8 data bits, no parity, and 1 stop bit. Call the telephone number nearest you: Access by Digital Modem ISDN users can dial in to 3ComBBS using a digital modem for fast access up to 56 Kbps. To access 3ComBBS using ISDN, use the following number: 408 654 2703 3ComFacts Automated Fax Service 3Com Corporation’s interactive fax service, 3ComFacts, provides data sheets, technical articles, diagrams, and troubleshooting instructions on 3Com products 24 hours a day, 7 days a week. Country Data Rate Telephone Number Australia up to 14400 bps 61 2 9955 2073 Brazil up to 14400 bps 55 11 547 9666 France up to 14400 bps 33 1 6986 6954 Germany up to 28800 bps 4989 62732 188 Hong Kong up to 14400 bps 852 2537 5608 Italy (fee required) up to 14400 bps 39 2 27300680 Japan up to 14400 bps 81 3 3345 7266 Mexico up to 28800 bps 52 5 520 7853 P. R. of China up to 14400 bps 86 10 684 92351 Singapore up to 14400 bps 65 534 5693 Taiwan up to 14400 bps 886 2 377 5840 U.K. up to 28800 bps 44 1442 438278 U.S.A. up to 28800 bps 1 408 980 8204

C-3 Call 3ComFacts using your Touch-Tone telephone using one of these international access numbers: Local access numbers are available within the following countries: 3ComForum on CompuServe Online Service 3ComForum is a CompuServe-based service containing patches, software, drivers, and technical articles about all 3Com products, as well as a messaging section for peer support. To use 3ComForum, you need a CompuServe account. To use 3ComForum: 1 Log on to CompuServe. 2 Type go threecom 3 Press [Return] to see the 3ComForum main menu. Country Telephone Number Hong Kong 852 2537 5610 U.K. 44 1442 438279 U.S.A. 1 408 727 7021 Country Telephone Number Country Telephone Number Australia 1800 678 515 Netherlands 06 0228049 Belgium 0800 71279 New Zealand 0800 446 398 Denmark 800 17319 Norway 800 11062 Finland 98 001 4444 Portugal 0505 442 607 France 05 90 81 58 Russia (Moscow only) 956 0815 Germany 0130 81 80 63 Singapore 800 6161 463 Hong Kong 800 933 486 Spain 900 964 445 Italy 1678 99085 Sweden 020 792954 Malaysia 1800 801 777 U.K. 0800 626403

Support from Your Network Supplier If additional assistance is required, contact your network supplier. Many suppliers are authorized 3Com service partners who are qualified to provide a variety of services, including network planning, installation, hardware maintenance, application training, and support services. When you contact your network supplier for assistance, have the following information ready: I Diagnostic error messages I A list of system hardware and software, including revision levels I Details about recent configuration changes, if applicable If you are unable to contact your network supplier, see the following section on how to contact 3Com. Support from 3Com If you are unable to receive support from your network supplier, technical support contracts are available from 3Com. Contact your local 3Com sales office to find your authorized service provider using one of these numbers: Regional Sales Office Telephone Number 3Com Corporation P.O. Box 58145 5400 Bayfront Plaza Santa Clara, California 95052-8145 U.S.A. 800 NET 3Com or 1 408 764 5000 408 764 5001 (fax) (continued)

C-5 3Com Asia Limited Australia China Hong Kong India Indonesia Japan Korea Malaysia New Zealand Philippines Singapore Taiwan Thailand 61 2 9937 5000 (Sydney) 61 3 9866 8022 (Melbourne) 8610 68492568 (Beijing) 86 21 63740220 Ext 6115 (Shanghai) 852 2501 1111 91 11 644 3974 6221 572 2088 81 6 536 3303 (Osaka) 81 3 3345 7251 (Tokyo) 822 2 319 4711 60 3 732 7910 64 9 366 9138 632 892 4476 65 538 9368 886 2 377 5850 662 231 8151 4 3Com Benelux B.V. Belgium Netherlands 32 2 725 0202 31 30 6029700 3Com Canada Calgary Montreal Ottawa Toronto Vancouver 403 265 3266 514 683 3266 613 566 7055 416 498 3266 604 434 3266 3Com European HQ 49 89 627320 3Com France 33 1 69 86 68 00 3Com GmbH Austria Czech Republic/Slovak Republic Germany (Central European HQ) Hungary Poland Switzerland 43 1 513 4323 420 2 21845 800 49 30 34 98790 (Berlin) 49 89 627320 (Munich) 36 1 250 83 41 48 22 6451351 41 31 996 14 14 3Com Ireland 353 1 820 7077 3Com Latin America U.S. Headquarters Northern Latin America Argentina Brazil Chile Colombia Mexico Peru Venezuela 408 326 2093 305 261 3266 (Miami, Florida) 541 312 3266 55 11 546 0869 562 633 9242 571 629 4110 52 5 520 7841/7847 51 1 221 5399 58 2 953 8122 (continued) Regional Sales Office Telephone Number

Returning Products for Repair Before you send a product directly to 3Com for repair, you must first obtain a Return Materials Authorization (RMA) number. Products sent to 3Com without RMA numbers will be returned to the sender unopened, at the sender’s expense. To obtain an RMA number, call or fax: 3Com Mediterraneo Italy Spain 39 2 253011 (Milan) 39 6 5279941 (Rome) 34 1 383 17 00 3Com Middle East 971 4 349049 3Com Nordic AB Denmark Finland Norway Sweden 45 39 27 85 00 358 0 435 420 67 47 22 18 40 03 46 8 632 56 00 3Com Russia 007 095 258 09 40 3Com Southern Africa 27 11 807 4397 3Com UK Ltd. 44 131 220 8228 (Edinburgh) 44 161 873 7717 (Manchester) 44 162 889 7000 (Marlow) Regional Sales Office Telephone Number Country Telephone Number Fax Number U.S.A. and Canada 1 800 876 3266, option 2 408 764 7120 Latin America 1 408 326 2927 408 764 7120 Europe, South Africa, and Middle East 44 1442 438125 44 1442 435822 Outside Europe, U.S.A., and Canada 1 408 326 2926 1 408 764 7120

connecting to the network 2-3 defined 1-1 diagnostics compatibility 4-1 driver compatibility 3-1 drivers 1-3 installation 2-2 port address 3-4 specifications B-1 unpacking 2-2 3C3X9.COM driver 1-3 3C3X9.LAN driver 1-3 3C3X9.LAN NetWare server driver 3-7 3C3X9LLC LAN Support driver 1-4 3Com Bulletin Board Service (3ComBBS) C-2 3Com sales offices C-4 3Com URL C-1 3ComFacts C-2 3ComForum C-3 3Install account 3-5 3TLVDIAG program defined 4-1 requirements 3-3, 4-2, A-3 A accessing DOS 3-3 Artisoft LANtastic/AI 1-4, 3-2 Auto Select Media Type 1-1, B-4 AUTOEXEC.BAT file, AutoLink modifications 3-5 AUTOEXEC.NCF file 3-8, 3-9, 3-10, 3-11 AutoLink installation program defined 1-1, 3-5 file modifications AUTOEXEC.BAT 3-5 CONFIG.SYS 3-5 modifying defaults 3-6 operating system 3-3 requirements 3-5 use with 3Install account 3-5 AUTOLINK.CFG file 3-6 AUTOLINK.LOG file 3-7, 4-6 automatic configuration 1-4, 2-6 B Banyan VINES 1-4, 3-2 base I/O address configuration 1-4, 2-6, A-1 finding 3-4 binding transport protocol 3-8, 3-9, 3-10, 3-11 BIOS, automatic configuration 1-4, 2-6, A-1 bulletin board service C-2 C cable requirements B-4 CompuServe C-3 CONFIG.SYS file, AutoLink modifications 3-5 configuration at power up 1-4, 2-6, A-1 base I/O address 1-4, 2-6, A-1 IRQ 1-4, 2-6, A-1 parameters changing A-3 default values A-1, A-2 port address 1-4, 2-6, A-1 connecting the NIC to the network 2-3 connector types 2-4 conventions notice icons, About This Guide 2 text, About This Guide 2

cable types B-4 pin assignments B-3 DEC PATHWORKS 1-4, 3-2 diagnostic and configuration program 4-1 diagnostic tests 4-1 failures 4-5 help 4-4 operating system requirements 4-2, A-3 running 4-2 diagnostics compatibility 4-1 DOS accessing 3-3 driver 1-4 driver Artisoft LANtastic/AI 1-4, 3-2 Banyan VINES 1-4, 3-2 compatibility 3-1 DEC PATHWORKS 1-4, 3-2 DOS 1-4 IBM Client Access/400 1-4, 3-2 IBM LAN Server 1-4, 3-2 IBM Warp Server 1-4 installation LAPS 3-17 MPTS 3-19 NetWare 3-4 to 3-11 OS/2 3-17 procedure locations 3-1 Windows 3-12 to 3-17 Windows 95 OSR1 3-15 Windows 95 OSR2 3-16 Windows NT 3.51 3-12 Windows NT 4.0 3-13 LAN Manager 1-4 LAN Support 1-4 NetWare DOS ODI 1-3 NetWare server 1-3 options 1-3 OS/2 1-4, 3-1, 3-17 VINES 3-2 Windows 95 1-3, 3-1, 3-15, 3-16 Windows for Workgroups 1-3, 1-4, 3-2 Windows NT 1-3, 3-1, 3-12, 3-13 F fax service. See 3ComFacts I IBM Client Access/400 1-4, 3-2 IBM LAN Server 1-4, 3-2 IBM OS/2 1-4, 3-1, 3-17 IBM Warp Server 1-4 installation driver Artisoft LANtastic/AI 3-2 Banyan VINES 3-2 DEC PATHWORKS 3-2 DOS ODI 3-5 IBM Client Access/400 3-2 IBM LAN Server 3-2 LAN Manager 3-2 LAPS 3-17 MPTS 3-19 multiple NICs, NetWare 3-9 NetWare 3-4 to 3-11 NLM requirements 3-7 one NIC, NetWare 3-7 OS/2 3-17 procedure locations 3-1 Windows 3-12 to 3-17 Windows 95 OSR1 3-15 Windows 95 OSR2 3-16 Windows for Workgroups 3-2 Windows NT 3.51 3-12 Windows NT 4.0 3-13 hardware 2-2 requirements 1-2 summary 1-4 IRQ configuration 1-4, 2-6, A-1 contentions 3-5 L LAN Manager 1-4, 3-2 LAN Server 1-4, 3-2 LAN Support driver 1-4 LANtastic/AI 1-4, 3-2 LAPS 3-17 LEDs 4-7 LSLENH.NLM file 3-8

driver 1-3 installation multiple NICs in a server 3-9 one NIC in a client 3-5 one NIC in a server 3-7 Loadable Modules 3-7 server driver 1-3 3.11 installation 3-8 3.12 installation 3-9 4.x installation 3-9 network cables B-4 connection 2-3 STP cable 2-5 UTP cable 2-4 interface specifications B-1 speed. See ring speed network driver. See driver network supplier support C-4 NIC. See 3C339 NIC NLM files 3-7 O online technical services C-1 OS/2 driver 1-4, 3-1, 3-17 LAPS 3-17 MPTS 3-19 OSR1 3-15 OSR2 3-16 P PATHWORKS 1-4, 3-2 PCI slot setup 3-13, 3-14 technology, defined 1-2 physical dimensions B-1 pin assignments B-3 port A-1 port address configuration 1-4, 2-6, A-1 finding 3-4 power requirements B-1 power up 2-6 R requirements 3TLVDIAG program 3-3, 4-2, A-3 AutoLink installation program 3-3, 3-5 diagnostic tests 4-2, A-3 installation 1-2 returning products for repair C-6 ring speed 3-6, 3-13, 3-14 RJ-45 connector 2-4 cable categories B-4 pin assignments B-3 S shared interrupts, contentions 3-5 shielded twisted-pair connections 2-5, B-4 specifications, NIC B-1 status LEDs 4-7 T technical support 3Com URL C-1 bulletin board service C-2 fax service C-2 network suppliers C-4 product repair C-6 using CompuServe C-3 tests, diagnostic. See diagnostic tests TL3C3X9.386 driver 1-3 TL3C3X9.DOS driver 1-4 TL3C3X9.OS2 driver 1-4 TLVMP339.SYS driver 1-3 troubleshooting 4-5 to 4-6 AUTOLINK.LOG file 3-7, 4-6 diagnostic tests 4-1 U unshielded twisted-pair connections 2-4, B-4 URL C-1 V VINES 1-4, 3-2

Windows 95 driver 1-3 OSR1 installation 3-15 OSR2 installation 3-16 Windows for Workgroups driver 1-3, 1-4, 3-2 Windows NT driver 1-3 3.51 installation 3-12 4.0 installation 3-13 World Wide Web (WWW) C-1

HARDWARE 3Com warrants its hardware products to be free from defects in workmanship and materials, under normal use and service, for the following lengths of time from the date of purchase from 3Com or its Authorized Reseller: If a product does not operate as warranted above during the applicable warranty period, 3Com shall, at its option and expense, repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or refund to Customer the purchase price paid for the defective product. All products that are replaced will become the property of 3Com. Replacement products may be new or reconditioned. Any replaced or repaired product or part has a ninety (90) day warranty or the remainder of the initial warranty period, whichever is longer. 3Com shall not be responsible for any software, firmware, information, or memory data of Customer contained in, stored on, or integrated with any products returned to 3Com for repair, whether under warranty or not. SOFTWARE 3Com warrants that the software programs licensed from it will perform in substantial conformance to the program specifications therefor for a period of ninety (90) days from the date of purchase from 3Com or its Authorized Reseller. 3Com warrants the media containing software against failure during the warranty period. No updates are provided. 3Com’s sole obligation with respect to this express warranty shall be (at 3Com’s discretion) to refund the purchase price paid by Customer for any defective software products, or to replace any defective media with software which substantially conforms to 3Com’s applicable published specifications. Customer assumes responsibility for the selection of the appropriate applications program and associated reference materials. 3Com makes no warranty or representation that its software products will work in combination with any hardware or applications software products provided by third-parties, that the operation of the software products will be uninterrupted or error free, or that all defects in the software products will be corrected. For any third-party products listed in the 3Com software product documentation or specifications as being compatible, 3Com will make reasonable efforts to provide compatibility, except where the noncompatibility is caused by a “bug” or defect in the third-party’s product. STANDARD WARRANTY SERVICE Standard warranty service for hardware products may be obtained by delivering the defective product, accompanied by a copy of the dated proof of purchase, to 3Com’s Corporate Service Center or to an Authorized 3Com Service Center during the applicable warranty period. Standard warranty service for software products may be obtained by telephoning 3Com’s Corporate Service Center or an Authorized 3Com Service Center, within the warranty period. Products returned to 3Com’s Corporate Service Center must be pre-authorized by 3Com with a Return Material Authorization (RMA) number marked on the outside of the package, and sent prepaid, insured, and packaged appropriately for safe shipment. The repaired or replaced item will be shipped to Customer, at 3Com’s expense, not later than thirty (30) days after receipt of the defective product by 3Com. WARRANTIES EXCLUSIVE IF A 3COM PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, CUSTOMER’S SOLE REMEDY FOR BREACH OF THAT WARRANTY SHALL BE REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT 3COM’S OPTION. TO THE FULL EXTENT ALLOWED BY LAW, THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES, TERMS, OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING WARRANTIES, TERMS, OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND SATISFACTORY QUALITY. 3COM NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE, OR USE OF ITS PRODUCTS. Network adapters Lifetime Other hardware products (unless specified above) 1 year Spare parts and spares kits 90 days

DISCLOSE THAT THE ALLEGED DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY CUSTOMER’S OR ANY THIRD PERSON’S MISUSE, NEGLECT, IMPROPER INSTALLATION OR TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR OR MODIFY, OR ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING, OR OTHER HAZARD. LIMITATION OF LIABILITY TO THE FULL EXTENT ALLOWED BY LAW, 3COM ALSO EXCLUDES FOR ITSELF AND ITS SUPPLIERS ANY LIABILITY, WHETHER BASED IN CONTRACT OR TORT (INCLUDING NEGLIGENCE), FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL, OR PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE OR PROFITS, LOSS OF BUSINESS, LOSS OF INFORMATION OR DATA, OR OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE, USE, PERFORMANCE, FAILURE, OR INTERRUPTION OF ITS PRODUCTS, EVEN IF 3COM OR ITS AUTHORIZED RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND LIMITS ITS LIABILITY TO REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT 3COM’S OPTION. THIS DISCLAIMER OF LIABILITY FOR DAMAGES WILL NOT BE AFFECTED IF ANY REMEDY PROVIDED HEREIN SHALL FAIL OF ITS ESSENTIAL PURPOSE. Some countries, states, or provinces do not allow the exclusion or limitation of implied warranties or the limitation of incidental or consequential damages for certain products supplied to consumers or the limitation for personal injury, so the above limitations and exclusions may be limited in their application to you. This warranty gives you specific legal rights which may vary depending on local law. GOVERNING LAW This Limited Warranty shall be governed by the laws of the state of California. 3Com Corporation, 5400 Bayfront Plaza, Santa Clara, CA 95052-8145 (408) 764-5000 FCC CLASS B CERTIFICATION STATEMENT 3Com Corporation Model No: 3C339 FCC ID:DF63C339 Made in U.S.A. This device complies with Part 15 of the FCC Rules.Operation is subject to the following two conditions: 1 This device may not cause harmful interference, and 2 This device must accept any interference received, including interference that may cause undesired operation. WARNING: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules, and the Canadian Department of Communications Equipment Standards entitled, “Digital Apparatus,” ICES-003.These limits are designed to provide reasonable protection against harmful interference in a residential installation.This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.However, there is no guarantee that interference will not occur in a particular installation.If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: I Reorient or relocate the receiving antenna. I Increase the separation between the equipment and receiver. I Connect the equipment into an outlet on a circuit different from the one which the receiver is connected to. I Consult the dealer or an experienced radio/TV technician for help.

helpful: The Interference Handbook This booklet is available from the U.S. Government Printing Office, Washington, D.C. 20402.Stock No. 004-000-00345-4. NOTE: In order to maintain compliance with the limits of a Class B digital device, 3Com requires that you use quality interface cables when connecting to this device. Changes or modifications not expressly approved by 3Com could void the user’s authority to operate this equipment.Refer to the manual for specifications on cabling types. VCCI CLASS 2 STATEMENT This equipment is in the Class 2 category (Information Technology Equipment to be used in a residential area or an adjacent area thereto) and conforms to the standards set by the Voluntary Control Council For Interference by Information Technology Equipment aimed at preventing radio interference in such residential area. When used near a radio or TV receiver, it may become the cause of radio interference. Read the instructions for correct handling. 3COM END USER SOFTWARE LICENSE AGREEMENT IMPORTANT: Read Before Using This Product YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THIS PRODUCT. IT CONTAINS SOFTWARE, THE USE OF WHICH IS LICENSED BY 3COM CORPORATION ("3COM") TO ITS CUSTOMERS FOR THEIR USE ONLY AS SET FORTH BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT USE THE SOFTWARE. USING ANY PART OF THE SOFTWARE INDICATES THAT YOU ACCEPT THESE TERMS. LICENSE: 3Com grants you a nonexclusive license to use the accompanying software program(s) (the "Software") subject to the terms and restrictions set forth in this License Agreement. You are not permitted to lease, rent, distribute or sublicense the Software or to use the Software in a time-sharing arrangement or in any other unauthorized manner. Further, no license is granted to you in the human readable code of the Software (source code). Except as provided below, this License Agreement does not grant you any rights to patents, copyrights, trade secrets, trademarks, or any other rights in respect to the Software. The Software is licensed to be used on any workstation or any network server owned by or leased to you, provided that the Software is used only in connection with a 3Com adapter. You may reproduce and provide one (1) copy of the Software and supporting documentation for each such workstation or network server on which the Software is used as permitted hereunder. Otherwise, the Software and supporting documentation may be copied only as essential for backup or archive purposes in support of your use of the Software as permitted hereunder. You must reproduce and include all copyright notices and any other proprietary rights notices appearing on the Software and the supporting documentation on any copies that you make. NO ASSIGNMENT; NO REVERSE ENGINEERING: You may not transfer or assign the Software and/or this License Agreement to another party without the prior written consent of 3Com. If such consent is given and you transfer or assign the Software and/or this License Agreement, then you must at the same time either transfer any copies of the Software as well as the supporting documentation to the same party or destroy any such materials not transferred. Except as set forth above, you may not transfer or assign the Software or your rights under this License Agreement. Modification, reverse engineering, reverse compiling, or disassembly of the Software is expressly prohibited. However, if you are a European Community ("EC") resident, information necessary to achieve interoperability of the Software with other programs within the meaning of the EC Directive on the Legal Protection of Computer Programs is available to you from 3Com upon written request.

accompanying documentation (or any copies thereof) or any products utilizing the Software or such documentation in violation of any applicable laws or regulations of the United States or the country in which you obtained them. TRADE SECRETS; TITLE: You acknowledge and agree that the structure, sequence and organization of the Software are the valuable trade secrets of 3Com and its suppliers. You agree to hold such trade secrets in confidence. You further acknowledge and agree that ownership of, and title to, the Software and all subsequent copies thereof regardless of the form or media are held by 3Com and its suppliers. UNITED STATES GOVERNMENT LEGEND: The Software is commercial in nature and developed solely at private expense. The Software is delivered as “Commercial Computer Software” as defined in DFARS 252.227-7014 (June 1995) or as a commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in this License Agreement, which is 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. TERM AND TERMINATION: This license will expire fifty (50) years from the date that you first use the Software, if it is not earlier terminated. You may terminate it at any time by destroying the Software and documentation together with all copies and merged portions in any form. It will also terminate immediately if you fail to comply with any term or condition of this License Agreement. Upon such termination you agree to destroy the Software and documentation, together with all copies and merged portions in any form. GOVERNING LAW: This License Agreement shall be governed by the laws of the State of California as such laws are applied to agreements entered into and to be performed entirely within California between California residents and by the laws of the United States. You agree that the United Nations Convention on Contracts for the International Sale of Goods (1980) is hereby excluded in its entirety from application to this License Agreement. LIMITED WARRANTY; LIMITATION OF LIABILITY: All warranties and limitations of liability applicable to the Software are as stated on the Limited Warranty Card or in the product manual accompanying the Software. Such warranties and limitations of liability are incorporated herein in their entirety by this reference. SEVERABILITY: In the event any provision of this License Agreement is found to be invalid, illegal or unenforceable, the validity, legality and enforceability of any of the remaining provisions shall not in any way be affected or impaired and a valid, legal and enforceable provision of similar intent and economic impact shall be substituted therefor. ENTIRE AGREEMENT: This License Agreement sets forth the entire understanding and agreement between you and 3Com, supersedes all prior agreements, whether written or oral, with respect to the Software, and may be amended only in a writing signed by both parties. 3Com is a registered trademark of 3Com Corporation. 3Com Corporation, 5400 Bayfront Plaza, P.O. Box 58145, Santa Clara, CA 95052-8145, (408) 764-5000