PCI/II 16/4 Adapter
Guide to Operations
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 ii
IBM, OS/2, Operating System/2, IBM PC LAN Program, IBM LAN Support Program, IBM Cabling System and NetBIOS are trademarks of International Business Machines Corporation. Novell, NetWare and NetWare Requester are trademarks of Novell Inc. Microsoft, MS-DOS, MS-OS/2, Windows 95, Windows NT and LAN Manager are trademarks of Microsoft Corporation. Olicom is a trademark of Olicom A/S
Olicom A/S reserves the right to modify the information given in this publication without prior notice. The warranty terms and conditions applicable for your purchase of this equipment are given at the time of purchase. Consult your place of purchase for details.
Publication: OC-6916 v. 2.2, P/N 710001434
© Copyright Olicom A/S, Denmark, October 1997 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or other- wise, without the prior written permission of the publisher.
FCC Compliance This equipment has been tested and found to comply with the limits for a Class B digital device, pursu- ant to Part 15 of the FCC Rules. 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 re- ception, 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: • Reorient or relocate the receiving antenna. • Increase the separation between the equipment and the receiver. • Connect the equipment into an outlet on a circuit different from the receiver’s. • Consult the dealer or an experienced radio/television technician for help. This device complies with part 15 of the FCC Rules. Operation is subject to the following two condi- tions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Modifications If the device is changed or modified without the express approval of Olicom A/S the user may void his or her authority to operate the equipment.
Declaration of Conformity We Olicom A/S Nybrovej 114 DK-2800 Lyngby Denmark declare under our sole responsibility that the product OC-3137, PCI/II 16/4 Adapter to which this declaration relates is in conformity with the following standards or other normative documents EN50082-1/1992 EN55022/1987 EN60950 EN60825-1 following the provisions of 89/336/EEC and 73/23/EEC Directives.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 iii
Table of Contents
1. Introduction 1 Diskette or CD-ROM Version ...... 1 Diskette Backup ...... 2 PackageContents...... 2 On-line Documentation ...... 2 Troubleshooting and getting Help ...... 3 Late-breaking News to the Printed Manual ...... 3 NotationalConventions...... 3
2. Installation Overview 5 How to install the Olicom PCI/II 16/4 Adapter ...... 5 Express Installation ...... 5 System Requirements ...... 7 Configuration using the Setup Program ...... 7 DOSOperation...... 7 WindowsOperation...... 7
3. Hardware Installation 9 Overview...... 9 Installation Requirements ...... 9 Adapter Installation ...... 9 Connecting the Adapter Cable ...... 10
4. Diagnostics 11 Running the Diagnostics Program ...... 11
5. Software Installation 13 Why Adapter Drivers? ...... 13 Supported Environments and Drivers ...... 13 5.1 Microsoft Windows 95 ...... 14 5.1.1 NDIS 3.0 Error Messages ...... 14 5.2 Microsoft Windows for Workgroups 3.11 ...... 15 5.2.1 Install NDIS Driver ...... 15 5.2.2 NDIS 3.0 Error Messages ...... 16 5.3 Microsoft Windows NT ...... 17 5.3.1 Miniport Installation during Windows NT 3.5x Installation . . . . . 17 5.3.2 Adding Adapter - Windows NT 3.5x ...... 18 5.3.3 Miniport Installation during Windows NT 4.0 Installation ...... 18 5.3.4 Adding Adapter - Windows NT 4.0 ...... 19
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 iv
5.3.5 Adapter Parameters/Properties ...... 19 5.3.6 Error messages ...... 19 5.4 Novell NetWare Workstations ...... 20 5.4.1 NetWare DOS ODI Workstation ...... 20 5.4.2 NetWare Client 32 for Windows 95 ...... 22 5.4.3 NetWare Client 32 for Windows 3.1x ...... 24 5.4.4 NetWare Client 32 for DOS ...... 24 5.5 Novell NetWare Servers ...... 25 5.5.1 NetWare 3.12 Server ...... 25 5.5.2 NetWare 4.x Servers ...... 25 5.6 Novell NetWare Source-Routing ...... 26 5.7 IBM DOS Environment ...... 27 5.7.1 IBM LAN Support Program (DOS) - NDIS 2.0 Driver ...... 27 5.7.2 IBM LAN Support Program (DOS) - DOS DLC Driver ...... 28 5.7.3 Configuring the DOS DLC Driver ...... 28 5.8 IBM OS/2 Environment ...... 31 5.8.1 IBM NTS/2 and IBM Extended Services ...... 31 5.8.2 IBM LAN Server 3.0 - LAPS ...... 31 5.8.3 IBM LAN SERVER 4.0 and MPTS ...... 33 5.9 Configuring the NDIS 2.0 MAC Driver ...... 34 5.10 NDIS 2.0 MAC Driver Messages ...... 34
6. Utilities 35 Adapter Information for Windows ...... 35 System Requirements ...... 35 Installation ...... 36 Activation ...... 36 De-installation ...... 36
7. Troubleshooting 37 Problems and Solutions ...... 37 PCI Specification Problems ...... 38
8. Getting in Touch with Technical Support 39 Before you contact Olicom Technical Support ...... 39 Hotline Support ...... 39 FAX Support...... 39 Bulletin Board Service ...... 39 CompuServe® ...... 40 Internet E-Mail ...... 40 Anonymous Internet FTP Server ...... 40 Internet World Wide Web Server (WWW) ...... 40 Problem Report Form ...... 41
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 v
Appendix A. Abbreviations 43
Appendix B. Driver Messages 45 B.1NovellNetWare...... 46 B.2 DOS DLC Driver Program ...... 48 B.3 DOS ODI Driver ...... 49 B.4 Microsoft/IBM NDIS 2.0 MAC Driver ...... 51 B.5 Microsoft NDIS 3.0 Drivers ...... 53 B.6 Diagnostics Error Messages ...... 58
Appendix C. Technical Information 59
Illustrations Figure 1. PCI 16/4 Adapter ...... 1 Figure 2. The Express Installation Prompt ...... 6 Figure 3. Startup Screen - Setup ...... 8 Figure 4. Hardware Configuration - Setup ...... 8 Figure 5. Top View of PC ...... 9 Figure 6. PC Back Panel ...... 10 Figure 7. Connector Configurations ...... 59 Figure 8. LEDs ...... 60
Tables Table 1. Factory Default Settings ...... 5
Index
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 vi
About this manual
Thank you for selecting Olicom’s PCI/II 16/4 Adapter.
This Guide to Operations is directed towards users without prior knowledge of network adapter installation, and it provides all the information required to per- form a standard installation of the PCI/II 16/4 Adapter.
This guide contains eight chapters and three appendices. Reading the sections that deal with the environment in which the adapter will be used will ease installation of the hardware and software described in this guide.
Chapter 1 is a general introduction to this manual.
Chapter 2 provides an installation overview
Chapter 3 describes the physical installation (hardware).
Chapter 4 describes the diagnostics.
Chapter 5 provides guidelines for installation of the adapter driver software in different network environments.
Chapter 6 describes the utility programs.
Chapter 7 provides troubleshooting hints to solve problems during installation and problems caused by compatibility issues for the new PCI indus- try specifications.
Chapter 8 describes how to contact Olicom Technical Support
Appendix A contains a list of abbreviations.
Appendix B contains error messages, return codes and suggested actions to re- cover from an error condition.
Appendix C lists the technical specifications and certifications
Expert users and end-users who need detailed technical information can obtain this from Olicom’s on-line documentation. The on-line documentation can be ac- cessed from DOS and Windows platforms. ❏
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 1
1. Introduction
The PCI/II 16/4 Adapter plugs into any free PCI expansion slot and provides true Plug and Play configuration in accordance with the PCI Local Bus specification. For standard operating modes, no configuration input is required from the user.
Figure 1. PCI/II 16/4 Adapter
Most of the Olicom adapter drivers support Full Duplex Token-Ring, also referred to as Dedicated Token-Ring (DTR). The drivers automatically detect if a Token-Ring switch is present and then set up for Full Duplex operation. If no switch is present, the drivers set up for classic Token-Ring operation. Full Duplex and classic Token-Ring drivers can be used simultaneously on a Token-Ring switch.
Diskette or CD-ROM Version
The OC-3137 PCI/II 16/4 Token-Ring Adapter is available in a diskette version with printed manual or in a CD-ROM version. When using the diskette version of the package, the Setup program is accessed by running SETUP.EXE (Windows) or INSTALL.EXE (DOS) on the Setup Disk. When using the CD-ROM version, running SETUP.EXE (for all environments) will start the Olicom Adapter CD-ROM Menu. Click the “Install and Configure” button to access the Adapter Setup Menu.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Introduction 2
Diskette Backup
If you are using the diskette version of the product, make a working copy of all diskettes and store the originals in a safe place. Use for example the diskcopy command, DISKCOPY A: A:.
Package Contents
The diskette version of the package contains the following items: • One OC-3137 PCI/II 16/4 Token-Ring Adapter (see Figure 1) • Four diskettes: Setup Disk, Disk 1 containing installation, utilities and documentation NetWare Client Disk, Disk 2 containing Novell NetWare Client for DOS and MS Windows Driver Disk, Disk 3 containing network drivers Diagnostics Disk, Disk 4 containing adapter diagnostics • One PCI/II 16/4 Adapter Guide to Operations, OC-6916 • One warranty card
The CD-ROM version of the package contains the following items: • One OC-3137 PCI/II 16/4 Token-Ring Adapter (see Figure 1) • One CD-ROM disk containing all the necessary software, documentation and utilities to install and configure the adapter • One booklet • One warranty card
On-line Documentation
This Guide to Operations contains all the information required for a standard adapter installation with default settings. However, if the installation is more complex or more information is needed, Olicom’s on-line documentation provides access to extensive information that complements what is given in this manual. The on-line documentation is available under both DOS and Windows.
To access the on-line documentation, insert the Setup Disk in drive A and execute the following command: A:SETUP. If you are using the CD-ROM version of the product, choose “Install and Configure” from the Olicom Adapter CD-ROM Menu to access the on-line documentation.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Introduction 3
Troubleshooting and getting Help
If the Olicom PCI/II 16/4 Adapter should perform unexpectedly, see chapter 8, Getting in Touch with Technical Support for technical assistance.
Late-breaking News to the Printed Manual
Additional information not available at the time of print is contained in the on-line documentation: Late-breaking News.
Notational Conventions
“CAPITAL LETTERS” (Helvetica typeface) indicates user input. You may use upper or lower case letters when entering names and commands. “ESC” (Helvetica Narrow typeface) indicates key entries, e.g. CTRL and F1.
“ h ” following a number indicates hexadecimal notation, e.g. 02AFh.
“ [ ] ” (square brackets) indicate an optional entry.
“ < > ” (angle brackets) indicate text to be substituted.
“ Courier typeface ” indicates screen display.
“ ❏ ” indicates the end of a chapter. ❏
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Introduction 4
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Introduction 5
2. Installation Overview
How to install the Olicom PCI/II 16/4 Adapter
❶ Install the adapter in the computer. Chapter 3, Hardware Installation explains this in detail. ❷ The system BIOS automatically assigns an interrupt level and an I/O range to the PCI/II 16/4 Adapter.
Function Default Setting Data Rate 16 Mbps Interrupt Level Assigned by system I/O Address Assigned by system Full Duplex (DTR) Auto-enabled
Table 1. Factory Default Settings
The setting for data rate is stored in non-volatile memory on the adapter. This setting can be changed using the Olicom Setup program or a separate utility program named OCT2PCFG. See section “Configuration using the Setup Program” in this chapter or chapter 6, Utilities, if you need to change the data rate to 4 Mbps. ❸ Install the adapter driver(s). If using Novell NetWare, use the Express Installation described below. If not, most network operating systems provide installation support for Olicom adapters. However, if no procedures are available - or manual driver installation is required - use Chapter 5, Software Installation as a guideline and/or the Olicom on-line documentation.
Express Installation
Express Installation is for people who want to configure their PC as a Novell NetWare DOS/Windows Client workstation. It installs the necessary drivers and programs to attach your computer to a Novell NetWare network.
1. Insert the adapter in the computer as described in chapter 3. 2. Insert the Setup Disk in drive A and enter:
A:SETUP
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Installation Overview 6
If you are installing from the CD-ROM, choose “Install and Configure” from the Olicom Adapter CD-ROM Menu to access the setup program. 3. You are asked if you want to proceed with an Express Installation as shown in figure 2. Select the “Yes” button to proceed with the Express Installation (use the mouse or press Enter).
Figure 2. The Express Installation Prompt 4. The Novell software licence is now displayed. The software needed to connect to a Novell NetWare server has been licensed from Novell by Olicom. Before installing, read the license. If the terms are acceptable to you, click the “Yes” button to accept the license terms. If the terms are unacceptable, return the product for a full refund. 5. You are now prompted for a directory for the Novell files. If you are using MS-Windows, install the Windows support files by clicking the Windows Support check box. Make sure that your MS-Windows directory is correctly specified. 6. The files will now be copied from the distribution media to your system’s hard disk. The installation program may prompt you for installation diskettes. Insert the appropriate diskette to continue installation. 7. When all files have been copied to the hard disk, some changes are made to your CONFIG.SYS and AUTOEXEC.BAT, as well as to your SYSTEM.INI and WIN.INI files if you are installing the Windows support. You are also asked whether or not you want to automatically log in to the NetWare server each time you re-boot the computer. Answering “Yes” will add the necessary commands to perform a log-in on each re-boot, whereas answering “No” will only load the necessary drivers to access the NetWare server. 8. A Utility Installation dialog box is now displayed. You can install the Installation Program and/or AIW, the Olicom Adapter Information for Windows utility.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Installation Overview 7
9. Re-boot your computer to complete the installation.
The Olicom PCI/II 16/4 Adapter is now installed and operational.
System Requirements
The system requirements for PCI/II 16/4 Adapter installation are: • A free PCI-bus expansion slot. • MS-DOS v. 3.3 or higher - Novell NetWare DOS workstation, IBM PC LAN Program NetWare 3.1x or higher - Novell NetWare 3.x and 4.x Servers Microsoft Windows, Microsoft Windows for Workgroups, Windows 95, Microsoft Windows NT - Microsoft environments IBM-OS/2 v. 2.0 or higher - IBM LAN Server/Extended Services • A free I/O address range and interrupt level. • Free memory capacity to load the PCI/II 16/4 Adapter driver, the network operating system and the required applications.
Configuration using the Setup Program
The Setup program can be used to perform hardware configuration of the adapter and provide on-line documentation about how to install the software drivers required in various operating environments. The Setup program can be run both under DOS and under Windows.
DOS Operation Insert the Setup Disk and type A:INSTALL. Press Enter to start the Setup program. If you are using the CD-ROM version, choose “Install and Configure” from the Olicom Adapter CD-ROM Menu to access the Setup program. Figure 3 shows the Startup screen.
Windows Operation Insert the Setup Disk, activate Program Manager, select “Run” from the File menu and type A:SETUP. Press Enter to start the Setup program. If you are using the CD-ROM version, choose “Install and Configure” from the Olicom Adapter CD-ROM Menu to access the Setup program. Figure 3 shows the Startup screen.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Installation Overview 8
Figure 3. Startup Screen - Setup
Select “Hardware Configuration” to invoke the configuration menu with ring speed setting (see figure 4).
Figure 4. Hardware Configuration - Setup
You may also select “Help” and “Installation Overview” to access Olicom’s on-line documentation.
Select “Utility Installation” to install additional utilities. Select “Express Install, NetWare Client” to run Express Install. See also page 5. ❏
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Installation Overview 9
3. Hardware Installation
Overview
This section describes how to install the Token-Ring adapter in one of the expansion slots in your computer. Refer to the documentation that came with your computer if you need additional information on how to install expansion cards. ➽ Important: Static electricity can be destructive to sensitive components on the adapter. Discharge yourself by touching a metal part of a grounded unit (for example a printer) before removing the adapter from the anti-static packing bag.
Installation Requirements
• The Operations Guide for your computer • A Token-Ring adapter cable supporting the media type of your network installation. For STP Media use a Type 1 or Type 6 cable (for example, Olicom 36507374). For UTP Media, use a Category 5 cable
Adapter Installation
1. Switch all computer components OFF and disconnect all power supply cables. 2. Place the peripheral units: keyboard, monitor, etc. away from the PC, and position the PC to allow easy access to the back panel. 3. Remove the PC top cover to expose the inside of the PC. See figure 5. 4. Choose a free PCI expansion slots. 5. Remove the screw from the top of the panel which holds the metal bracket on the back panel corresponding to the chosen slot. 6. Tilt the adapter to let the interface connector slip through the opening in the back panel, and then press the edge connector firmly into the chosen expansion slot. 7. Secure the card with the screw from the previously removed metal bracket and re-install the PC top cover.
Figure 5. Top View of PC
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Hardware Installation 10
Connecting the Adapter Cable
1. STP Media Cabling (type 1 and 6) Connect the PC adapter cable to the STP media connector and tighten the screws. See figure 6. UTP Media Cabling (Category 5) Insert the modular jack in the UTP media connector. See figure 6. ➽ Note: Make absolutely sure that you connect the cable to the adapter you have just installed. Connecting the cable to ANY OTHER expansion card than the Token-Ring adapter could result in serious damage to the expansion card and/or the Token-Ring Network. Do not connect cables to both the UTP and the STP connectors at the same time.
Figure 6. PC Back Panel
2. Connect the other end of the cable to a wall outlet or for example a Multistation Access Unit (MAU). 3. Make sure that the PC is turned OFF and then re-connect all power supply cables. 4. Switch power ON. ❏
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Hardware Installation 11
4. Diagnostics
The PCI/II 16/4 Adapter is supplied with a diagnostics program. The diagnostics program can be used to:
• Test the adapter(s) and the adapter cable(s) • View the current adapter(s) configuration
The adapter diagnostics comprise a series of tests that are executed in sequence.
The network diagnostics first attempts to transmit packets onto the network. If a network responder is detected, packets will be transmitted on the physical net between the machine running the test and the responder (a network responder is a station on the LAN which echoes packets transmitted from another station running network diagnostics).
If no network responder is detected, you can either do an External or Internal loopback test. An External loopback test transmits frames to itself through the network. An Internal loopback test performs a loopback in the cable without transmitting frames to the network.
Use the Diagnostics Program to check the PCI/II 16/4 Adapter(s) and cables if you suspect a problem. The PCI/II 16/4 Adapter has undergone stringent quality control tests before being released but damage may have occured during transportation.
See also chapter 8, Getting in Touch with Technical Support if the PCI/II 16/4 Adapter reports an error.
Running the Diagnostics Program
Diagnostics must be run from the Diagnostics Disk (Disk 4). If you are using the CD-ROM version of the product, you must first create a diagnostics diskette. Choose “Make Install Disks” from the Olicom Adapter CD-ROM Menu to create a diagnostics diskette.
1. Make sure that the adapter is connected to the network If using STP, a lobe cable will suffice. 2. Insert the diagnostics diskette into the diskette drive. 3. Boot the system from the diskette. Press simultaneously or turn power off and on.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Diagnostics 12
➽ Important: Do not run the Diagnostics Program with memory managers (HIMEM.SYS, EMM386.EXE, etc.) or network drivers loaded. Failure to do so may result in unreliable test results. Use the Diagnostics Program’s own on-line help for further information about the program. ❏
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Diagnostics 13
5. Software Installation
Why Adapter Drivers?
The adapter driver software is an upward interface to Local Area Network programs required to run applications on a Token-Ring Network. Most major NOS environments provide facilities for the installation of adapter driver software and, in many cases, Olicom drivers are pre-defined in the relevant configuration utilities. If the facility to install Olicom drivers from the NOS is available, use this approach. However, if no such procedures are available, or manual installation is preferred, use the following sections as guidelines for the adapter driver installation. Extensive installation procedures are available in the Olicom on-line documentation. Environments marked with an asterisk (*) in the list below are only described in the on-line documentation.
Supported Environments and Drivers
Environment Driver Full Section Duplex MS Windows 95 OCTK16.SYS yes 5.1 MS Windows for Workgroups 3.11 OCTK16.386 no 5.2 MS Windows NT OCTK16.SYS yes 5.3 MS Windows for Workgroups 3.1 OLITOK16.DOS yes *) MS LAN Manager OLITOK16.DOS/.OS2 yes *) NetWare DOS ODI Workstation OCTOK16.COM yes 5.4.1 NetWare Client 32 for Windows 95 OCTOK162.LAN yes 5.4.2 NetWare Client 32 for Windows 3.1x OCTOK162.LAN yes 5.4.3 NetWare Client 32 for DOS OCTOK162.LAN yes 5.4.4 NetWare 3.11 Server OCTOK161.LAN no *) NetWare 3.12 Server OCTOK162.LAN yes 5.5.1 NetWare 4.x Server OCTOK162.LAN yes 5.5.2 NetWare Source Routing ROUTE.COM/SYS - 5.6 NetWare OS/2 Requester OCTOK16.SYS no *) IBM LAN Support Program OLITOK16.DOS yes 5.7.1 IBM DOS LAN Services (DLS) OLITOK16.DOS yes *) IBM PC LAN Program (DOS DLC) OC02DLC.SYS no 5.7.2 IBM NTS/2 and IBM E.S. OLITOK16.OS2 yes 5.8.1 IBM LAN Server 3.0 (LAPS) OLITOK16.OS2 yes 5.8.2 IBM LAN Server 4.0 and MPTS OLITOK16.OS2 yes 5.8.3 IBM LAN Server 2.0 OLITOK16.OS2 yes *)
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 14
5.1 Microsoft Windows 95 This section describes the procedure for installation in Windows 95.
1. Install your Olicom PCI/II 16/4 Adapter in a free PCI slot. When starting Windows 95 the next time, a popup window will appear notifying that Windows 95 has found new hardware.
If you are prompted for a driver disk, insert the Olicom Driver Disk or CD-ROM and select “Driver from disk provided by hardware manufacturer”.
If you are not prompted for a driver disk and you want to use the latest enhancements of the Olicom driver, you can update your network driver with the driver supplied with the adapter. This can be done by using the Olicom Setup Program or by using the Windows 95 install procedure.
Update Driver using Olicom Setup Program 2. Run the Olicom Setup Program. 3. Click the “Windows 95 driver upgrade” button. Insert the Driver Disk when requested (diskette version only). 4. Restart Windows 95 for the changes to take effect.
Update Driver using Windows 95 2. From the “Start” menu select “Settings”, “Control Panel” and “Add/Remove Programs”. 3. Select the “Windows Setup” tab and click the “Have Disk” button. 4. If you are using the diskette version, insert the Driver Disk into drive A and click “OK”. If you are using the CD-ROM version, insert the CD-ROM and specify the path to your CD-ROM drive. Click “OK” to continue. 5. In the “Components” window select “Update Olicom Network Adapter Driver” and press the “Install” button. 6. Click “OK”. 7. Restart Windows 95 for the changes to take effect.
➽ Note: NetWare Client 32 for Windows 95 is described on page 22.
5.1.1 NDIS 3.0 Error Messages NDIS 3.0 error messages and actions are in appendix B.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 15
5.2 Microsoft Windows for Workgroups 3.11 This section describes the procedure for installation in Windows for Workgroups Version 3.11.
The following configurations may be used: • NDIS 3.0 driver only • NDIS 3.0 or NDIS 2.0 driver depending on protocols • NDIS 2.0 driver only • ODI driver If access to a Novell server is required, see “Installing NetWare Support” in Olicom’s on-line documentation.
5.2.1 Install NDIS Driver When installing an NDIS driver, both NDIS 2.0 and NDIS 3.0 drivers can be selected. 1. Open the “Network” window by double-clicking the Network icon and then select the “Network Setup” icon. 2. Click “Networks...” in the “Network Setup” panel and select “Install Microsoft Windows Network”. 3. Make sure “No additional network” is selected, click “OK” (or press Enter) and select “Drivers...”. 4. Click “Add Adapter...” in the “Network Drivers” panel, highlight the “Unlisted or Updated Network Adapter” choice and click “OK”. 5. When the setup program prompts for a vendor-provided driver disk, insert the Driver Disk or the CD-ROM. Make sure that the path to the disk is correct and click “OK”. 6. In the “Unlisted or Updated Network Adapter” panel, select the “Olicom Token-Ring Network 16/4 Adapter” and select “OK”. 7. Click “Setup...” in the “Network Drivers” panel to inspect the options. 8. The NDIS drivers automatically search for an adapter. If changing any of the parameters for the NDIS drivers is required, click the “Advanced...” button and proceed with step 9. Otherwise, proceed to step 11. 9. In the “Olicom Token-Ring Network 16/4 Adapter” panel the settings for the adapter can be edited . Highlight the required parameter. 10. Enter/select the value in the box below the parameters and select “Set”. When all parameters have been set correctly, click “OK”. 11. To select between NDIS 2.0 and NDIS 3.0 drivers, depending on when the workstation is started and which protocols are used, choose the “Real mode and Enhanced Mode NDIS Driver” in the “Driver Type” box. If using NDIS
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 16
2.0 drivers alone, choose “Real Mode NDIS Driver”. If using NDIS 3.0 drivers alone, choose “Enhanced Mode NDIS Driver”. Select “OK”. ➽ Note: When using NDIS 3.0 drivers alone, not all protocols can be used, as some protocols require an NDIS 2.0 driver. 12. Additional network drivers and/or protocols in the “Network Drivers” panel may be added . Select “Close” when done. 13. If sharing files and/or printers are needed, change the settings in the “Sharing” panel by clicking “Sharing...”. Select “OK” to exit the “Sharing” panel. Click “OK” to complete network setup. 14. If the network is installed for the first time, enter a user name, workgroup name and a computer name. Make sure the computer name is unique throughout the network. Click “OK” when done. 15. Setup may require additional files from the Windows for Workgroups 3.11 distribution disks. Insert these files when prompted. 16. Windows for Workgroups 3.11 automatically changes the CONFIG.SYS, AUTOEXEC.BAT, SYSTEM.INI and PROTOCOL.INI if necessary. Click “OK” to confirm these changes. 17. Select “Restart Computer” to make the changes take effect. Save any unsaved information before restarting the system.
5.2.2 NDIS 3.0 Error Messages NDIS 3.0 error messages and actions are in appendix B.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 17
5.3 Microsoft Windows NT The installation procedures for the Microsoft Windows NT workstation operating system and the Microsoft Windows NT server operating system are identical. Both operating systems will hereafter be referred to as “Windows NT”.
During installation of the NDIS 3.0 Miniport driver, you may find it convenient to have the Windows NT System Guide at hand. Review the “Configuring the Network” section in chapter 5 and chapter 19, “Installing Windows NT” prior to installation.
The NDIS 3.0 Miniport installation procedure described below will copy all necessary set-up files to your Windows NT “System32" directory and the driver to your ”System32\Drivers" directory. In addition, several changes will be made to your registry. Do not try to manually change entries in the registry. All Miniport driver parameters can be set from the Network control panel.
The installation procedure for the NDIS 3.0 Miniport driver allows installation either during the initial Windows NT installation or after Windows NT has been installed on your computer.
If you have already installed Windows NT on your computer, see “Adding Adapter - Windows 3.5x” or “Adding Adapter - Windows NT 4.0”.
Depending on your Windows NT version, proceed to: Miniport Installation during Windows NT 3.5x Installation or Miniport Installation during Windows NT 4.0 Installation.
5.3.1 Miniport Installation during Windows NT 3.5x Installation 1. Follow the instructions in the Windows NT System Guide to begin Windows NT installation. 2. If you have chosen custom set-up, you should choose “Do Not Detect” when the “Network Adapter Card Detection” window displays, as there is no netcard detection module included with the Olicom Miniport drivers. 3. When the message “Set-up did not detect a network card” displays, select “Continue” to go to the adapter card set-up phase. 4. Continue with step 2 in the following “Adding Adapter” section.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 18
5.3.2 Adding Adapter - Windows NT 3.5x If you are installing a network adapter after Windows NT has been successfully installed on your system, you must be logged on with administrative rights. This is necessary in order to be able to add, configure and remove network adapters in Windows NT.
1. Select the Control Panel in the Main window, select the Network icon and choose the “Add adapter” button in the Network Settings panel. 2. In the list of Network Adapter Cards, select “
5.3.3 Miniport Installation during Windows NT 4.0 Installation 1. Follow the instructions in the Windows NT System Guide to begin the Windows NT 4.0 installation. 2. If you have chosen custom setup, do not start the adapter-search in the “Network Setup Wizard” dialog box. Choose instead “Select from list”. 3. Click the “Have Disk...” button, and enter the full path to the Olicom setup files. If you are installing from the Setup disk, enter “A:\”. 4. Confirm choice by selecting proper adapter type and press the “OK” button. 5. Click the “Next” button when all adapters have been added. 6. Follow the Network Setup Wizard choosing appropriate Protocols and Services to continue the installation. You will be prompted twice for the path to your NT installation files. First enter the path to the NT installation files (for example the Windows NT CD-ROM) and second enter the path to the Olicom setup files (Same path as entered under step 2). 7. Follow the Network Setup Wizard to finish the installation.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 19
5.3.4 Adding Adapter - Windows NT 4.0 If you are installing a network adapter after Windows NT has been successfully installed on your system, you must be logged on with administrative rights. This is necessary in order to be able to add, configure and remove network adapters in Windows NT.
1. Select the Control Panel under Settings, select the Network icon and choose the “Adapters” tab and click the “Add...” button. 2. Click the “Have Disk...” button, and enter the full path to the Olicom setup files. If you are installing from the Setup disk, enter “A:\”. 3. Confirm choice by selecting proper adapter type and press the “OK” button. 4. Click the “Close” button in the Network dialog box when all adapters have been added. 5. The settings will not take effect, until the system is restarted. System restart can be initiated by selecting the “Yes” option in the dialog box shown when you exit the Network Setup Panel.
5.3.5 Adapter Parameters/Properties See the on-line documentation for details about the adapter parameters.
5.3.6 Error messages NDIS 3.0 error messages and actions are in appendix B.
See also the OCTK16.HLP file for a complete list of possible errors and recommended actions.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 20
5.4 Novell NetWare Workstations If the Novell NetWare version provides installation support for Olicom adapters and drivers, use the native NOS installation utility. Otherwise, proceed with the relevant section in this chapter.
With Novell server operating systems up to version 3.11, Novell shipped the NETX client software. With versions 3.12 and 4.x, Novell ships the VLM client software. While both may be used, the VLM client is required if you want to take advantage of the new functionality in version 3.12 and 4.x servers..
5.4.1 NetWare DOS ODI Workstation NetWare Client for DOS/MS Windows installation - VLM For installation of the NetWare DOS/Windows VLM client, run the Express Install option in the Olicom Setup Program (see chapter 2, Installation Overview) or run NOVELL’s install program.
The VLM (Virtual Loadable Module) client is loaded using the following sequence of commands: LSL.COM (Link support module, Novell supplied) OCTOK16 (Token-Ring ODI Driver) IPXODI.COM (IPX/SPX Protocol module, Novell supplied) VLM.EXE (NetWare Requester, Novell supplied) If using Novell’s install program, insert the Driver Disk or CD-ROM when prompted and select the OCTOK16 driver. The NET.CFG file is automatically generated. If you let the install program modify your CONFIG.SYS and AUTOEXEC.BAT files, the commands above are automatically executed during boot.
NETX installation This installation procedure requires the following software and documentation: • Novell NetWare DOS ODI support programs • The Olicom Driver Disk or CD-ROM
1. Copy the Novell NetWare DOS ODI support programs to a disk as explained in the Novell documentation. 2. Copy the OCTOK16.COM driver from the Driver Disk or CD-ROM to the same disk as the ODI Shell: COPY A:\DOS\OCTOK16.COM C:\
3. Insert the following line in the file AUTOEXEC.BAT:
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 21
OCTOK16
OCTOK16 must be loaded after LSL, but before any protocol stacks (for example, IPXODI). Sample AUTOEXEC.BAT: LSL (Link support module, Novell supplied) OCTOK16 (Token-Ring ODI driver) IPXODI (IPX/SPX Protocol module, Novell supplied) NETx (NetWare Requester, Novell supplied)
Other protocol stacks and requesters are possible. See Novell NetWare documentation. 4. Edit the NET.CFG file to configure the workstation. See the Novell documentation provided with the ODI Shell for general information about the NET.CFG file. Sample NET.CFG: # Start of NET.CFG #One adapter, with both SNAP and 802.2 support Link Driver OCTOK16 Frame TOKEN-RING Frame TOKEN-RING_SNAP # End of NET.CFG
The line “Link Driver .....” must begin in the first column and the parameters that follow must be indented.
The keywords recognized by OCTOK16 are: Max Frame Size The maximum frame size for the adapter. Default is 4216, maximum is 17960, minimum is 632. This parameter affects the resident driver size. Values smaller than default may affect performance. Node Address Enter this parameter only if you wish to manually administer node addresses in your installation. If not entered, the Burned in address will be used. If an address is entered, it must consist of 12 hexadecimal digits, the first being 4, 5, 6 or 7. Frame The link level frame type. Supported values are TOKEN-RING (default) and TOKEN-RING_SNAP. Port The I/O port address for the adapter is only needed if there is more than one adapter in the PC. Since the I/O port address assigned to PCI devices are not known on beforehand, the following artificial port addresses are used: FFF0h to select the first Olicom PCI/II 16/4 Adapter found by the system, FFF1h to select the second, FFF2h to select the third, etc. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 22
5.4.2 NetWare Client 32 for Windows 95 This installation requires: • Novell NetWare Client 32 for Windows 95 installation disks • Microsoft Windows 95 CD-ROM (or disks) • Olicom Driver Disk or CD-ROM
This installation consists of three steps:
1. Installing the NDIS 3.0 Miniport driver 2. Installing the Netware Client 32 software 3. Converting the NDIS 3.0 Miniport driver to a Novell ODI LAN driver (if desired)
Installing the NDIS 3.0 Miniport Driver If your NDIS 3.0 Miniport is already installed and running, proceed to Installing the NetWare Client 32 Software. Otherwise install the NDIS 3.0 Miniport driver as described under Microsoft Windows 95. See page 14.
Installing the NetWare Client 32 Software Run the setup program on the NetWare Client 32 installation disks to install the Novell NetWare Client 32 for Windows 95. See the Novell NetWare installation guide for details. When you have installed Novell NetWare Client 32, choose “Reboot” to restart the system.
The installation is now completed. If you want to use the Novell ODI LAN driver rather than the NDIS 3.0 Miniport driver, proceed to Converting the NDIS 3.0 Miniport Driver to a Novell ODI LAN Driver.
Converting the NDIS 3.0 Miniport Driver to a Novell ODI LAN Driver 1. Insert the Olicom Driver Disk, start Microsoft Explorer and locate your Windows 95 directory (C:\WINDOWS). 2. Change to the INF directory (hidden), locate the files NETOLI.INF and move it to a disk for later use (or rename the file). If renaming, the renamed file must have an extension different from INF. 3. Copy all the INF files from the A:\NETWARE\NW4X directory to the C:\WINDOWS\INF directory.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 23
4. Open the Network configuration screen (Start/Settings/Control Panel/Network) and look for any reference to “Olicom Token-Ring PCI/II 16/4 (OC-3137)”. Highlight all instances with the mouse and click “Remove”. When all instances of the “ Olicom Token-Ring PCI/II 16/4 (OC-3137)” has disappeared, click “OK” and restart the PC. 5. Windows 95 then displays “Windows has found new hardware and is installing software for it”. 6. When the system then prompts for the NetWare Client 32 setup disk, insert the disk and click “OK”. If you did not install NetWare Client 32 from disk, enter the correct path to the Client 32 files and click “OK”. 7. Windows 95 builds a new driver database and prompts for the disk where the Olicom INF and LAN Driver files are located. Insert the Olicom Driver Disk, correct the path to A:\NETWARE\NW4X and click “OK”. 8. The system may prompt for the source of the Windows 95 installation files. If Windows 95 was installed from disk, insert the requested disk. If Windows was installed from CD-ROM, make sure the original CD-ROM is inserted and enter the path to the installation files. If Windows was pre-installed on the hard disk, the path usually is C:\WINDOWS\OPTIONS\CABS. You may also be prompted for the location of the network driver. If so, insert the Olicom Driver Disk, type A:\NETWARE\NW4X and click “OK”. 9. If the system prompts for the remaining NetWare Client 32 disks, insert the disks one by one and click “OK”. If you did not install NetWare Client 32 from disk, enter the correct path to the Client 32 files and click “OK”. 10. When the installation is completed, the system requests to restart. Click “YES” to restart the PC. ➽ Note: If you want to re-use the NDIS 3.0 Miniport driver, remove the OCTOK162.INF file from the C:\WINDOWS\INF directory and copy back the old INF files (from step 2). Open the Network configuration screen (Start/Settings/Control Panel/Network) and look for any reference to “Olicom Token-Ring PCI Adapter 32 Bit ODI”. Highlight all instances with the mouse and click “Remove”. When all instances of “ Olicom Token-Ring PCI Adapter 32 Bit ODI ” have disappeared, click “OK” to restart the PC.
➽ Note: If your server is located on a network with bridges you must enable source routing for the driver to function correctly. From the Start Menu, select Settings/Control Panel/Network.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 24
Double-click “IPX/SPX-compatible Protocol”, choose the “Advanced” tab, select “Source Routing” from the “Property” list and set a value in the “Value” drop-down list.
5.4.3 NetWare Client 32 for Windows 3.1x This installation requires: • Novell NetWare Client 32 for DOS/Windows 3.1x installation disks • Olicom Driver Disk or CD-ROM
1. Run the INSTALL program on the NetWare Client 32 for DOS/Windows 3.1x installation disks and follow the installation guidelines given by Novell. See the Novell installation guide for details. 2. When prompted for Network Board drivers, select “USER SUPPLIED DRIVER”. 3. Insert the Olicom Driver Disk (or CD-ROM) and specify the path and filename for the Olicom NetWare Client 32 LAN driver: A:\NETWARE\NW4X\OCTOK162.LAN
Select “Olicom Token-Ring 16/4 Adapters”, press Next and follow the instructions to complete the installation.
5.4.4 NetWare Client 32 for DOS This installation requires: • Novell NetWare Client 32 for DOS/Windows 3.1x installation disks • Olicom Driver Disk or CD-ROM
1. Run the INSTALL program on the NetWare Client 32 for DOS/Windows 3.1x installation disks and follow the installation guidelines given by Novell. See the Novell installation guide for details. 2. When prompted for Network Board drivers, select “USER SPECIFIED 32 BIT DRIVER” or “OTHER DRIVERS”. 3. Insert the Olicom Driver Disk (or CD-ROM) and specify the path to the Olicom NetWare Client 32 drivers: A:\NETWARE\NW4X
Select “Olicom Token-Ring 16/4 Adapters” and follow the instructions to complete the installation.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 25
5.5 Novell NetWare Servers
5.5.1 NetWare 3.12 Server 1. Insert the Olicom Driver Disk or CD-ROM into the disk drive. Load the following NLMs with the following commands: LOAD
➽ Note: The driver requires that NBI31X.NLM is version 1.30 or later, MSM31X.NLM is version 3.03 or later, and that TOKENTSM.NLM is version 3.01 or later. Use the MODULE command to check if the modules are already loaded and the module version.
➽ Note: Disregard the warning message that appears. The driver will load. 2. Load the adapter driver with the following command: LOAD
3. With the server now accessible, copy the OCTOK162.LAN server driver and the NLMs from the Driver Disk or CD-ROM in a NetWare workstation to the SYSTEM directory of the connected server. 4. Ensure automatic loading of the 386 server driver at re-boot by inserting the following commands in the server’s AUTOEXEC.NCF file: LOAD NBI31X.NLM LOAD MSM31X.NLM LOAD TOKENTSM.NLM LOAD OCTOK162 SLOT=XXX BIND IPX OCTOK162
5.5.2 NetWare 4.x Servers 1. Install the NetWare 386 operating system on the server. Refer to the “NOVELL NetWare 386 Installation” manual. 2. Load the INSTALL.NLM module on the server with the following command: LOAD INSTALL
Select from the menu “LAN Driver Options” and insert the Driver Disk or CD-ROM when prompted. The PCI/II 16/4 Adapter requires a SLOT parameter. If a SLOT parameter is not supplied to the INSTALL utility, you must switch to the console screen where the driver presents a list of available slots and waits for user input.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 26
3. Tune to best performance by including the following line in the server’s STARTUP.NCF file: Set Maximum Physical Receive Packet Size=4202 5.6 Novell NetWare Source-Routing Source-routing is the method used in IBM Token-Ring networks to determine the route a frame must travel through a multi-ring Local Area Network to reach its destination.
To ensure flawless source-routing operation all workstations and servers on the network must have the source-routing feature enabled or disabled. Error messages for Novell NetWare are listed in appendix B begining on page 46.
See Olicom’s on-line documentation for source-routing details and procedures for Novell NetWare DOS ODI workstations, OS/2 workstations, DOS workstations, 3.1x and 4.x Servers.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 27
5.7 IBM DOS Environment IBM is migrating to the NDIS interface in their products. To be able to use NDIS in products like Lan Network Manager, IBM has made a superset of NDIS 2.01 called NDIS 2.02. Throughout the documentation, no distinction will be made between the two, and they will be referred to as NDIS 2.0. The NDIS 2.0 drivers (for DOS and OS/2) are also referred to as MAC drivers.
Two different drivers may be used with the IBM LAN Support Program: NDIS 2.0 for DOS and the DOS DLC driver.
5.7.1 IBM LAN Support Program (DOS) - NDIS 2.0 Driver This section describes the procedure for installing the Olicom NDIS 2.0 MAC Driver in the IBM LAN Support Program with the IBM Installation Aid.
1. Follow the guidelines described by IBM in “Installing the LAN Support Program” with the “Installation Aid” program. 2. Run the Installation Aid program: DXMAID
3. When prompted for changes in “Environment Information”, select “YES” (in the field that asks, if an adapter option diskette is available) and continue the installation. 4. When prompted for an “Adapter option diskette drive and directory for DOS NDIS files” in the “Process Adapter Option Diskette” window, insert the Driver Disk or CD-ROM and type:
5. Select in the “Selections for Adapter” window “Olicom Token-Ring Network 16/4 Adapters”. 6. Press F5 to change or view the NDIS driver parameters. If the parameters are changed, do not let the MaxFrameSize exceed approximately 4500 bytes, as this gives problems when using the IBM NetBIOS driver. Refer to the help text on “RecBufCount” for the formula for calculation of the ReceiveArea. For more information about parameters which may be used for configuring the network adapter, see section 5.9, Configuring the MAC Driver for detailed information. 7. Follow the IBM guidelines to complete the installation. The MAC driver for the adapter is now installed in the LSP configuration. To install the IBM DOS LAN Requester, follow the guidelines given by IBM.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 28
5.7.2 IBM LAN Support Program (DOS) - DOS DLC Driver This installation procedure requires the following software and documentation: • The Olicom Driver Disk or CD-ROM • IBM LAN Support Program diskette (if NetBIOS support is required) • MS-DOS 3.3 or higher
1. Insert the Olicom Driver Disk or CD-ROM in the disk drive. 2. Start the installation by entering the following command (substitute the drive letter of your diskette drive or CD-ROM drive):
This creates a subdirectory named NETWORK on your hard disk and copies all necessary files to the directory. 3. If NetBIOS support is required, insert the IBM LAN Support Program diskette in drive A when instructed to do so and press any key. The installation program copies the necessary device drivers to the NETWORK directory and inserts their names in the CONFIG.SYS file, if desired. 4. Remove any diskettes from your diskette drive and reboot the PC to load the drivers. 5. If installing IBM PC LAN Program, follow the installation procedure given in the documentation for IBM PC LAN Program and set up the network configuration in the AUTOEXEC.BAT file. The initial installation of the adapter driver on hard disk is now completed. All subsequent reboots will automatically load the DLC driver from the hard disk.
5.7.3 Configuring the DOS DLC Driver Node Address The adapter has a built-in node address which ensures a unique node address for each card. Two identical node addresses on the same Token-Ring Network will cause unpredictable behaviour of the conflicting nodes.
A customized node address can be defined for the installation. To do so, include a twelve digit, hexadecimal node address in the CONFIG.SYS file: device=\network\OC02DLC.SYS -n
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 29
[node_address] is a 12-digit hexadecimal number in the range 400000000000 through 7FFFFFFFFFFF. It is recommended that the first four digits are 4000.
Example: device=\network\OC02DLC.SYS -n0400000000010
Entering a zero forces the burned in address to be used even if an application at a later time tries to open the adapter with another address.
Early Token Release The Early Token Release function can be enabled or disabled manually by changing the device specification for the DLC driver in the CONFIG.SYS file. By default the function is enabled.
Modify the device specification (on one line) as follows: device=c:\network\OC02DLC.SYS -e
where
This parameter is ignored if the data rate is 4 Mbps.
Alternate Adapter The -A switch causes the driver to treat the first adapter found as ALTERNATE and ignore any other adapters. Without this switch, the first adapter found automatically becomes PRIMARY (adapter 0) and a second adapter becomes ALTERNATE (adapter 1).
Example: An alien driver/adapter needs to be configured as PRIMARY (adapter 0). Therefore a adapter handled by OC02DLC.SYS needs to be configured as ALTERNATE (adapter 1). Assume also that the latter uses node address 400011112222: device =
Interrupt Arbitrator Configuration A country code can be specified when loading the interrupt 5C arbitrator OC01IA.SYS. Subsequently loaded drivers will use this country code to display messages in the selected language: device =
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 30
The country code can be: 01 US English 33 French 34 Spanish 39 Italian 45 Danish 46 Swedish 49 German of which 01, 45 and 49 are currently supported. ➽ Note: IBM has changed the way that the interrupt arbitrator communicates the country code to the DLC and NetBIOS drivers. The change was made from LAN Support Program version 1.3 and means that the OC01IA.SYS and OC02DLC.SYS drivers conform to the new interface by default. If using NetBIOS driver DXMT0MOD.SYS prior to version 1.3 of the LAN Support program, the following new command line option “-ON” (old NetBIOS) must be given to both drivers: device=OC01IA.SYS -ON device=OC02DLC.SYS -ON device=DXMT0MOD.SYS
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 31
5.8 IBM OS/2 Environment IBM is migrating to the NDIS interface in their products. To use NDIS in products like LAN Network Manager, IBM has made a superset of NDIS 2.01 called NDIS 2.02. Throughout the documentation, no distinction will be made between the two, and they will be referred to as NDIS 2.0. The NDIS 2.0 drivers for DOS and OS/2 are also referred to as MAC drivers.
“Configuring the NDIS 2.0 MAC Driver” in the on-line documentation contains detailed information on configuration options. ➽ Note: When you install files from the Olicom CD-ROM disk using LAPS or MPTS, the installed files are read-only. If LAPS or MPTS fails to install certain files, it can be because they already exist and are read-only. Recover from this situation by removing the read-only attributes from the files on the hard disk with a file manager or by entering from a command line: attrib -r
5.8.1 IBM NTS/2 and IBM Extended Services This section describes how to install the MAC driver for the adapter with IBM NTS/2 and IBM Extended Services.
1. Start the Communication Manager and select “Advanced”, “Configuration”, “LAN Adapter and Protocol Support” and “Copy additional network adapter drivers”. 2. When requested to do so, insert the Driver Disk or CD-ROM and enter the path to the driver:
3. When the network driver has been copied, select “Configure workstation” and configure the workstation (refer the IBM documentation). See also “Configuring the NDIS 2.0 MAC Driver” in the Olicom’s on-line help file.
5.8.2 IBM LAN Server 3.0 - LAPS This section describes how to install the MAC driver for the Olicom adapter with LAN Server 3.0: – during LAN Adapter and Protocol Support (LAPS) – after LAN Adapter and Protocol Support (LAPS)
Install the MAC Driver During LAPS 1. Insert the “IBM Network Transport Services/2, LAN Adapter and Protocol Support” diskette in drive A and run the LAPS-program (i.e. A:\LAPS).
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 32
2. Select “Install” in the LAN Adapter and Protocol Support programs main menu. The program installs LAPS on the hard disk. 3. At a certain stage during installation, the LAPS programs main menu reappears, but this time with the “Install”, “Configure”, “Remove”, “Exit” and “Help” options selectable. Proceed with the installation as described in “Install the MAC Driver after LAPS”, step 2.
Install the MAC Driver After LAPS 1. Make \IBMCOM the current directory and run the LAPS program by typing: CD \IBMCOM LAPS
2. Select the “Install” option in the LAPS main menu. 3. When prompted for the source path of “Additional Network Drivers”, insert the Olicom Driver Disk or CD-ROM and enter the path:
Select “OK” to continue. 4. When the message “Installation Complete” appears on screen, select “OK”. Configuration of the Token-Ring adapter can now take place. 5. Select “Configure” in the LAPS main menu. 6. Select “Configure LAN Transport” in the “Configuration” dialog box and select “Continue”. 7. Select “Olicom Token-Ring Network 16/4 Adapters” as your network adapter by adding it to the “Current Configuration”. You may now edit the parameters of the Olicom adapter. 8. Select “Olicom Token-Ring Network 16/4 Adapters” in the current configuration list and then “Edit”. 9. Add and configure protocols to suit the requirements. See the Optimizations section in the Olicom on-line documentation and, if appropriate, make the suggested optimizations in the MAC-driver and protocol (i.e. “Olicom Token-Ring Network 16/4 Adapters” and “NETBEUI”). 10. Select “OK” when the configuration of the LAN Transports is complete. 11. Select “Exit” in the LAPS main menu and let LAPS update the CONFIG.SYS on the boot drive by selecting “Continue”. 12. Follow instructions given by LAPS to complete the installation.
PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 33
5.8.3 IBM LAN SERVER 4.0 and MPTS The MAC driver for the PCI/II 16/4 Adapter can be installed during MPTS (Multi-Protocol Transport Services) installation or after MPTS installation.
MAC Driver Installation during MPTS Installation 1. Install MPTS as described by IBM. 2. During installation the MPTS main menu reappears but this time with the “Exit”, “Configure”, “Install”, “Remove” and “Help” options selectable. 3. Proceed with the installation as described below in “How to install the MAC driver after LAN Adapter Protocol Support“ in step 2.
MAC Driver Installation after MPTS Installation 1. Run the MPTS program by making \IBMCOM your current directory (CD \IBMCOM) and typing: MPTS
2. Select the “Configure” option in the MPTS main menu. 3. Select “LAN Adapters and Protocols” and “Configure”.
You are now in “LAPS Configuration” and have two options:
a) Use the already installed “Olicom Token-Ring 16/4 Adapters”. b) Make an update with the drivers from the Olicom Driver Disk or CD-ROM. Option b) is recommended. The Olicom driver supplied with MPTS may not support this adapter type. Proceed with step 4.
4. Activate the “Other Adapters...” button and enter the path “ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 34 9. Select “OK” when the configuration of the LAPS configuration is completed and select “Close” to end the configuration. 10. Select “Exit” in the MPTS main menu and let MPTS update CONFIG.SYS on the boot drive by selecting “Continue”. 11. Follow instructions given by MPTS to complete the installation. The PCI/II 16/4 Adapter is activated when the system is re-booted. 5.9 Configuring the NDIS 2.0 MAC Driver Configuration of the NDIS 2.0 MAC driver is described in detail in Olicom’s on-line help file, Configuring the NDIS 2.0 MAC Driver. 5.10 NDIS 2.0 MAC Driver Messages When booting the adapter(s) with MAC driver(s) installed, a number of messages may be displayed during system initialization. Some messages are for information and some indicate warning conditions or errors. The messages have the format shown in the following example: PCI 16/4 300I: MAC Driver Installed where: 300I is a message number followed by a one-letter message indicator: I = Information, W = Warning and E = Error. “ “MAC Driver Installed”, the text following the colon, is descriptive. After the adapter has been installed, a message can be seen similar to one of the following during system initialization: OS/2 NDIS 2.02: MAC Driver for the Token-Ring Network, v. 8.xx (yy mm dd) (C) Copyright Olicom A/S, 1997 Int 15 Port FCC0 Max Frame 17954 Line Speed 16 Mbps PCI 16/4 300I: MAC Driver Installed or DOS NDIS 2.02: MAC Driver for the Token-Ring Network, v. 8.xx (yy mm dd) (C) Copyright Olicom A/S, 1997 Int 15 Port FCC0 Max Frame 17954 Line Speed 16 Mbps PCI 16/4 300I: MAC Driver Installed If a message other than “PCI 16/4 300I: MAC Driver Installed” is displayed during initialization, look up the message in appendix B and take the suggested action accompanying the message. If an error message is displayed repeatedly, write down the exact wording of the message and contact the place of purchase. ❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Software Installation 35 6. Utilities Four utilities are supplied with the PCI/II 16/4 Adapter. Described in this Guide to Operations (and in the on-line documentation) is: • Adapter Information for Windows (AIW) The following utilities are described in Olicom’s on-line documentation: • NDIS 2.0 Statistics Program for DOS and OS/2 • DOS Command Line Adapter Configurator • Adapter Detection Programs Adapter Information for Windows This section describes the Adapter Information for Windows program (AIW). AIW displays information about the adapter itself and the driver from the Windows platform. The following information is available: • Adapter type, version, serial number and configuration data • Driver type, version and configuration data • Driver statistics in numeric form • System files • Network traffic in graphic form • How to contact Olicom Support and Sales Division • Other Olicom products The information is displayed on the screen and the configuration data can be saved in a file or printed out. System Requirements • Microsoft Windows v. 3.1 or higher, Windows 95 or Windows NT. • An Olicom DMI enabled driver: OCTOK16.COM (DOS ODI driver) or OLITOK16.DOS (NDIS 2.0 DOS driver) or OCTK16.386 (NDIS 3.0 DOS driver) or OCTK16.SYS (NDIS 3.0 Miniport driver) PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Utilities 36 Installation 1. Insert the Setup Disk and run: A:\SETUP If you are installing from the CD-ROM, choose “Install and Configure” from the Olicom Adapter CD-ROM Menu to access the setup program. 2. Select “Utility Installation” and “Olicom Adapter Information for Windows”. 3. Follow the instructions to complete the installation. The installation process will create a new program group in which the AIW icon is located. Activation 1. Double-click on the AIW icon to activate the AIW program. 2. For more details about the AIW options, select the “Help” menu or press F1. De-installation If required, delete the AIW application from the hard disk by manually deleting the files originally installed in the installation directory (C:\OLICOM). These are AIW.EXE, AIW.HLP, AIW.INI, AIW.ATM, IMLIB221.DLL, OLIAIW.DLL, OLIAIW.VXD, OLIAIW32.DLL and the files in the HTML directory. ❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Utilities 37 7. Troubleshooting Problems and Solutions Problem Solutions The screen is blanked or displays an Ensure that only one cable is error message. connected to the adapter. Diagnostics are OK, but the network Make sure that the cable is securely connection fails. connected. Check that the cable media is correct and that the cable is connected to an attachment unit. The adapter stopped working when Make sure that the cable is connected another adapter was installed in the to the PCI/II 16/4 Adapter and not PC. another device. Ensure that the adapter is firmly seated. The adapter stopped working for no Run the adapter diagnostics. apparent reason. Try a different PCI slot. Reinstall the adapter software drivers. You are informed: “No adapter Use the driver supplied with the found”. adapter. If you have two drivers with the same name, use the time stamp to see the revision and use the latest driver. Running IBM DOS LSP in Windows Insert the following line under 3.x and WfW 3.x. [386.Enh] in the SYSTEM.INI file: TimerCriticalSection=10000 PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Troubleshooting 38 PCI Specification Problems Compatibility problems with the relatively new PCI industry specification call for troubleshooting techniques to isolate and resolve specific problems that may be encountered with the PCI Adapter. BIOS Settings The PCI/II 16/4 Adapter is self-configuring, so for most PCI-bus computers you need only install your adapter in a PCI-bus slot and power-up your computer. The computer’s BIOS automatically configures the adapter. In some PCI computers, however, the PCI interrupt INTA must be assigned to any available ISA interrupt. This is normally done with a jumper on the motherboard and/or the computer’s PCI BIOS SETUP. The computer manual describes how to set the motherboard jumpers and modify the BIOS settings. ➽ Note: Make sure that jumper and BIOS settings match when setting a jumper on the motherboard and modifying the computer’s BIOS. If a PCI computer contains ISA adapters without the Plug and Play feature, these adapters must be reported to the computer’s PCI BIOS. This is typically done via your computer’s PCI BIOS SETUP. If neglected, resource conflicts may arise when other PCI adapters are installed in the computer. The PCI BIOS assigns the next available ISA interrupt - or available I/O base address - to the new PCI adapter. If the Olicom PCI Adapter starts, but the adapter driver fails with an initialization error, information about the ISA interrupt request line (IRQ) is shown. Look through the computer’s device configuration to detect if any ISA device uses the same IRQ. Use the computers’s PCI BIOS SETUP program to move the interrupt level of the Olicom PCI Adapter or the interrupt level of the ISA device. EMM386 Memory Manager On some systems, drivers may halt the system while being loaded, if the DOS memory manager EMM386.EXE is installed. This problem does not occur for EMM386.EXE v. 4.49 supplied with MS-DOS v. 6.22 (or later) and IBM-DOS v. 7.00. In some cases it is possible to load the driver before EMM386.EXE to circumvent the problem. ❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Troubleshooting 39 8. Getting in Touch with Technical Support If support is not provided by your organization or the local vendor, contact Olicom Technical Support using one of the listed services. In addition, BBS, E-mail, FTP or WWW provide up-to-date software updates, application notes, quick fixes, FAQs, various utilities, etc. which just might solve your problem. Before you contact Olicom Technical Support • Run the adapter diagnostics and write down the message(s) ...... • Simplify the environment by removing memory managers, etc...... • Change the configuration if you suspect a resource conflict ...... (in particular a conflict with an interrupt occupied by a legacy ISA device) • Remove other devices one by one to detect a possible conflict . . . . . • Fill in the Problem Report Form included in this chapter ...... Hotline Support Call the following numbers for help with any problem you may encounter when installing Olicom software and hardware products: Europe: This service is open Monday to Friday from 8 am to 6 pm CET. Telephone: (+45) 45 27 01 02 USA: This service is open 24 hours a day, 7 days a week. Telephone: (+1) 800-OLICOM-1 or (972) 516-4638 FAX Support For assistance with any problem you may encounter when installing Olicom software and hardware products, Olicom’s Support department will reply either by FAX or by telephone within 24 hours, Monday to Friday. Europe: FAX: (+45) 45 27 02 40 USA: FAX: (+1) (972) 516-0640 Bulletin Board Service All Olicom’s support services are available via our BBS: software updates, application notes, quick fixes, FAQs, various utilities, etc. To contact our Bulletin Board Service (BBS) the following is required: Modem speed: 2400/4800/7200/9600/12K/14.4k bps PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Getting in Touch with Technical Support 40 Modem standard: CCITT V21/V22/V22bis/V32/V42bis/HST/MNP5 Parity: N (none) Databits: 8 Stop bits: 1 Files can be downloaded using one of the following transfer protocols: Zmodem, Xmodem, Ymodem and Kermit. Europe: Telephone: (+45) 45 27 01 00 (and create your own account). USA: Telephone: (972) 422-9835 CompuServe® Available via CompuServe are: software updates and FAQs (frequently asked questions). Type “GO OLICOM” after login. Dial the following numbers for information about CompuServe®: Europe: Telephone: (+44) 117 925 5111 USA: Telephone: (614) 457-0802 Internet E-Mail Olicom customer support is available on E-Mail through Internet. Use one of the following addresses: Europe: [email protected] USA: [email protected] Anonymous Internet FTP Server All Olicom’s support services can be obtained from our anonymous FTP server: software updates, application notes, quick fixes, etc. To connect, open an FTP session to: Europe: ftp.olicom.dk USA: ftp.olicom.com Internet World Wide Web Server (WWW) The Olicom WWW server contains up-to-date information about Olicom Products, newsletters and press releases. It also contains addresses of all Olicom offices and support centers worldwide. Our software library contains the latest adapter driver revisions. The WWW server can be accessed using these URL Addresses: Europe http://www.olicom.dk USA http://www.olicom.com PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Getting in Touch with Technical Support 41 Problem Report Form Fill in both sides of this Problem Report Form, print out the relevant system configuration files and FAX/mail to Olicom Technical Support: +45 45 27 02 40 Problem Description Network Information PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Getting in Touch with Technical Support 42 Adapter Information Adapter type ECO level and serial number (see labels on the adapter) I/O address Interrupt Driver Information Driver disk Operating system Network OS Driver name Version (usually the same as file time stamp) PC Information PC type PC vendor/model Bus type/processor Memory Additional boards BIOS version Motherboard rev. Print out and attach these configuration files: CONFIG.SYS for workstation and OS/2 servers. Check here: AUTOEXEC.BAT for all workstations. Check here: PROTOCOL.INI for NDIS workstations and servers. Check here: LANMAN.INI for NDIS workstations and servers. Check here: IBMLAN.INI for NDIS workstations and servers. Check here: DOSLAN.INI for NDIS workstations and servers. Check here: NET.CFG for NetWare workstations. Check here: AUTOEXEC.NCF for NetWare servers. Check here: STARTUP. NCF for NetWare servers. Check here: MSD.EXE for all Windows configurations. Check here: Name: ______Company: ______ Address: ______Country: ______ Telephone/FAX: ______❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Getting in Touch with Technical Support 43 Appendix A. Abbreviations ASIC Application Specific Integrated Circuit BIA Burned-in Address BIOS Basic Input Output System CPU Central Processing Unit DLC Data Link Control DMA Direct Memory Access DMI Desktop Management Interface DTR Dedicated Token-Ring (= Full Duplex) DOS Disk Operating System LAN Local Area Network LAPS LAN Adapter and Protocol Support LED Light Emitting Diode LLC Logical Link Control MAC Media Access Control NDIS Network Driver Interface Specification NetBIOS Network Basic Input Output System. NIC Network Interface Card (= Adapter) NT New Technology ODI Open Data-Link Interface OS/2 Operating System /2 PCI Peripheral Component Interconnect PnP Plug and Play PROM Programable Read Only Memory PS/2 Personal System /2 RAM Random Access Memory RPL Remote Program Load VLM Virtual Loadable Module ❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Abbreviations 44 PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Abbreviations 45 Appendix B. Driver Messages This appendix consists of six sections. Each section describes driver messages and return codes that may appear during installation and operation with OC-3137 PCI/II 16/4 Adapters and the network operating system or support program. The sections cover the following topics: Section B.1 Novell NetWare, lists commonly seen error return codes between 0211h and F400h. See page 46. Section B.2 DOS DLC Driver, lists error messages 161E to 167E incl. See page 48. Section B.3 DOS ODI Driver, describes the DOS ODI error messages. See page 49. Section B.4 Microsoft/IBM NDIS 2.0 MAC Driver, describes error messages 330E to 361E incl. See page 51. Section B.5 Microsoft NDIS 3.0 Drivers, describes error messages 1 to 5019 incl. See page 53 Section B.6 Diagnostics Error Messages, See page 58 PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 46 B.1 Novell NetWare Message format: Error opening Token-Ring Adapter. RC 0211 Message # # Message 02yz An error was detected while in serting into the ring. “y” indicates the command phase, and “z” specifies the type of error. 021- Lobe media test 022- Physical insertion 023- Address verification 024- Participation in ring poll 025- Request initialization 028- Unknown phase error 029- Request registration 02B- Address verification 02-1 Function failure 02-2 Signal loss 02-5 Time-out (at Full Duplex: Protocol error) 02-6 Ring failure 02-7 Ring beaconing 02-8 Duplicate node address (at Full Duplex: Insert denied) 02-9 Request initialization 02-A Remove received 02-B C-port changed 0400 Transmit buffer count error 0800 Adapter RAM error 1000 Buffer size error 2000 List size error 4000 Invalid node address passed with Open command F000 Time-out F030 Initial test error F031 Adapter ROM checksum error F032 Adapter RAM error F033 Instruction test error F034 Context/interrupt test error F035 Protocol handler hardware error F036 System interface register error F0xx Unexpected I/O register behaviour PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 47 F101 Invalid init block passed to adapter F102 Invalid initialization options F103 Invalid receive burst count F104 Invalid transmit burst count F105 Invalid DMA abort threshold F106 Invalid SCB address F107 Invalid SSB address F108 Direct I/O parity error F109 DMA time-out F10A DMA parity error F10B DMA bus error F10C DMA data compare error F10D Unrecoverable error during initialization F1FE Adapter DMA to wrong addresses in PC memory F1FF Time-out waiting initialize to complete F200 Time-out error waiting for a Read Adapter Buffer command to complete F300 Unexpected response to Open command F400 Adapter check during Open command. Possibly caused by RAM er- ror on the adapter. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 48 B.2 DOS DLC Driver Program Message format: OC-3841 0 161E: No adapters found Message (see list below) Message # (see list below) 0 = first adapter 1 = second adapter DOS DLC driver program identifier # Message and action 161E No adapters found Action: Check that you have installed the adapter correctly, and that it is firmly fixed in its expansion slot. - Driver not installed. Press PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 49 B.3 DOS ODI Driver This driver requires LSL version 2.11 or higher. The Olicom DOS ODI driver requires version 2.11 or higher of the Novell LSL module (LSL.COM). Problems may occur if using older versions of the Novell Install DOS / Windows Client. Action: Use the Olicom Express Install option to install the correct version of LSL.COM. Adapter card not found. Action: Check that the Olicom Enabler is installed correctly and that the card configuration does not conflict with other installed devices. Error resetting adapter Action: Run the diagnostics program. Contact your place of purchase if the error condition persists. Initialization error. Action: Run the diagnostics program. Contact your place of purchase if the error condition persists. Error reading from adapter. Action: Check for interrupt conflicts and run the diagnostics program. Contact your place of purchase if the error condition persists. Max Frame Size is too large in NET.CFG. Max = XXXX Action: Insert a valid number in the NET.CFG file. Max Frame Size is too small in NET.CFG. Min = XXX Action: Insert a valid number in the NET.CFG file. Unexpected adapter register behaviour or adapter not sup- ported. Action: Check that the Olicom Enabler is installed correctly and that the card configuration does not conflict with other installed devices. I/O register data error Action: Contact your place of purchase. Illegal I/O address specified in file: NET.CFG. Action: Correct your NET.CFG file. Illegal burned-in address in the adapter. Action: Contact your place of purchase. Error in the adapters checksum for the burned-in address. Action: Contact your place of purchase. No adapter found at port address specified in file: NET.CFG. Action: Check that the adapter configuration does not conflict with other installed devices. Node address must have 12 hex digits, the first being 4, 5, 6 or 7. Action: Correct the node address. Error opening adapter. Error code 02YZ Action: “Y” in the error code indicates the Open Phase and “Z” indicates the error type. See also the hints that follow the error codes. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 50 The “Y” error codes are: 021z Lobe media test 022z Physical insertion 023z Address verification 024z Participation in ring poll 025z Request initialization 028z Unknown phase error 029z Request registration 02Bz Address verification The “Z” error codes are: 02y1 Function failure 02y2 Signal loss 02y5 Timeout (at Full Duplex: Protocol error) 02y6 Ring failure 02y7 Ring beaconing 02y8 Duplicate node address (at Full Duplex: Insert denied) 02y9 Request initialization 02yA Remove received 02yB C-port changed Hints: 021z Check the cable from the card connector to the MAU or wall outlet (the lobe media). 02y7 Check that the card speed (4 or 16 Mbps) corresponds with the ring speed of the Token-Ring. 02y8 Another card on the Token-Ring network has a node address identical to yours. If you are using Local Administered Node Address, change it for one of the cards. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 51 B.4 Microsoft/IBM NDIS 2.0 MAC Driver Message format: PCI 16/4 333E: MAC Driver not installed Message (see list below) Message # (see list below) Adapter identifier # Message and action 330E MAC Driver not Installed -Adapter not found or invalid, CC= Action: Check that you have installed the adapter correctly. 333E MAC Driver not Installed - Interrupt conflict detected, CC= Action: Check that the interrupt level chosen for the adapter does not conflict with other expansion cards installed on your PC. 334E MAC Driver not Installed - Memory allocation error 1, CC= Action: This message is only received on OS/2 based systems. The MAC driver was not able to allocate the memory it needs neither in high (above 1M bytes) nor in low memory. Check configuration parameters in PROTOCOL.INI. 335E MAC Driver not Installed - Memory allocation error 2, CC= Action: This message is only recieved on OS/2 based systems. The MAC driver was not able to allocate the required number (two) of GDT (Global Descriptor Table) selectors. Check the configuration parameters for other installed devices, to see if you are able to decrease their GDT selector claim. 336E MAC Driver not Installed - Memory allocation error 3, CC= Action: This message is only received on OS/2 based systems. Check that your disk has not been damaged (CHKDSK). 337E MAC Driver not Installed - Memory allocation error 4, CC= Action: This message is only received on OS/2 based systems. Check that your disk has not been damaged (CHKDSK). 340E MAC Driver not Installed - PROTMAN open error, CC= Action: Check that your CONFIG.SYS has not been garbled. The device= ... \PROTMAN.SYS statement shall preceed the device= ...\OLITOK16.xxx statement. 341E MAC Driver not Installed - PROTMAN interface error, CC= Action: Check that your PROTMAN.SYS device installs properly (no error messages are displayed during system initialization). Check that your CONFIG.SYS has not been garbled. The /i parameter of the line device=...\PROTMAN.SYS must identify the path to the directory in which PROTOCOL.INI is located, e.g. C:\LANMAN. If you are using IBM LAN Server or LAN Requester, the PROTOCOL.INI file is normally located in the \IBMCOM directory. 342E MAC Driver not Installed - PROTMAN register error, CC= Action: Check that your PROTMAN.SYS device installs properly (no error messages are displayed during system initialization). Check that your CONFIG.SYS has not been garbled. The /i parameter of the line device= ...\PROTMAN.SYS must identify the path to the directory in which PROTOCOL.INI is located, e.g. C:\LANMAN\DRIVERS\TOKENRNG\OLITOK16. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 52 344W MAC Configuration Error - Unknown keyword, Keyw: Action: The OLITOK16 section of PROTOCOL.INI contains an unknown keyword. The keyword in question is the number indicated by Keyw counted from the start of the OLITOK16 section. Check the keyword for spelling errors. 345W MAC Configuration Error - Parameter out of Range, Keyw: Action: A keyword in the OLITOK16 section of PROTOCOL.INI has been assigned an illegal value. The keyword in question is the number indicated by Keyw counted from the start of the OLITOK16 section. If the keyword is ‘NODEADDRESS’, a universally administered address has been assigned. Correct the assigned value. 346W MAC Configuration Error - Too Few Parameters, Keyw: Action: A keyword in the OLITOK16 section of PROTOCOL.INI has been assigned too few values. The keyword in question is the number indicated by Keyw counted from the start of the OLITOK16 section. Assign the missing values. 347W MAC Configuration Error - Too Many Parameters, Keyw: Action: A keyword in the OLITOK16 section of PROTOCOL.INI has been assigned too many values. The keyword in question is the number indicated by Keyw counted from the start of the OLITOK16 section. Correct the keyword assignment. 348W MAC Configuration Error - Illegal Parameter Type, Keyw: Action: A keyword in the OLITOK16 section of PROTOCOL.INI has been assigned an illegal value, for example the assigned value is a text and it should be a decimal value. The keyword in question is the number indicated by Keyw counted from the start of the OLITOK16 section. Correct the keyword assignment. 349E MAC Driver not Installed - PROTMAN configuration error, CC= Action: Check your PROTOCOL.INI file for the correct specification of the protocols constituting the protocol stack. Check that the entry for the adapter contains the line: “Drivername=OLITOK$”. See “Configuring the NDIS 2.0 MAC Driver” and “multiple adapters” in the on-line documentation for further information. 350E MAC Driver not Installed - Dynamic data overflow, CC= Action: This message is only received on DOS based installations. The receive buffer pool size is too large. Decrease the values for either RecBufSize or RecBufCount in PROTOCOL.INI. 351E MAC Driver State Uncertain - Internal SW Error Action: Contact your place of purchase. 352E MAC Driver not Installed - Adapter I/O port conflict, CC= Action: Two adapters are installed, but there are no “IOBase =” statements in PROTOCOL.INI or they specify the same I/O port. 355W MAC Driver receive area too large - Receive area set to de- fault 0xNNNN Action: The receive buffer pool is too large. Decrease the values for RecBufSize or RecBufCount in PROTOCOL.INI. Default values will be used. 356W Failed to allocate interrupt 2F ID. SNMP will not be avail- able. Action: A large number of TSR programs using this interrupt is active. Reduce the number of active TSR programs. 361E MAC Driver not Installed - Adapter initialization error,CC= Action: Check that all switches are in the correct position. See MAC Driver Error Codes - NDIS 2.0 Environments in the on-line documentation for a description of the error codes. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 53 B.5 Microsoft NDIS 3.0 Drivers The NDIS 3.0 error messages reported under Microsoft Windows for Workgroups 3.11, Windows 95 and Microsoft Windows NT are identical. However, the way the errors are reported to the user differs. Windows for Workgroups 3.11 In Windows for Workgroups 3.11 error codes reported by NDIS 3.0 MAC drivers are written to the NDISLOG.TXT file located in your Windows directory. Error messages are divided into two groups: Olicom defined error messages and general error messages. An example of an Olicom defined error message reported by the MAC driver could be: OCTK16, Unknown Error Code, 0X8100000A, 0XC0000023, 0X0000D860 The error code (0X8100000A) describes the error and refers to a specific error. Ignore the leading “0X8100” (resulting in errorcode A for the example above - lobe wire fault). General error messages familiar to the system are displayed as: OCTK16A, Adapter Not Found, 0XAA000004, 0XC0000001, 0X0000FFFF If you experience any problems, make a backup copy of the NDISLOG.TXT file before restarting Windows For Workgroups 3.11. Windows 95 In Windows 95 error codes reported by NDIS 3.0 Miniport drivers are written to the NDISLOG.TXT file located in your Windows directory. An example of an error message reported by the MAC driver could be: Olicom Token-Ring PCI Adapter (0002). Error Code=0XA100000A, 0X00000008, 0XC0000023, 0X00005820 The text “0XA100000A” describes the error and refers to a specific error code, listed below. Ignore the leading “0XA100” (resulting in errorcode A for the example above - Lobe wire fault ...). If you experience any problems, you should make a backup copy of the NDISLOG.TXT file before restarting Windows 95. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 54 Windows NT When running Windows NT, errors are reported using the event log. This log can be examined using the Event Viewer located in the Administrative Tools group. If you experience any problems with the network, check if any error messages or warnings are posted by the Miniport driver. All error messages and/or warnings posted by the Olicom Miniport driver have the Source field set to “OCTK16”. System error messages, related to the Olicom Miniport driver, may occur with different source names, i.e. “Service Control Manager”. The messages are described below in Event field number order. You can display the message description by highlighting the message and pressing ENTER. Error messages below 5000 are Olicom defined error messages. Error messages 5000 and above are system specific general NDIS 3.0 error messages. If you experience any problems, write down the “Event ID”, “Source”, “Description” and “Data” fields in the “Event Detail” window. NDIS 3.0 Error Messages For each of the following error messages the first line contains the error code used by Windows 95 and Windows for Workgroups 3.11. The second line contains the “Event ID” and “Data” fields used by Windows NT. # Olicom Defined Error Message and Action 1 Unknown error code 1 Bring-up diagnostics failed for OcTk16 Action: The adapter failed during the bring-up diagnostics. Shut down your system and re-try the operation. If the error persists, write down the Data field in the Event Detail window and contact your place of purchase. 2 Unknown error code 2 Adapter initialize failed for OcTk16 Action: The adapter failed the initialization phase. Shut down your system and re-try the operation. If the error persists, write down the Data field in the Event Detail window and contact your place of purchase. 3 Unknown error code 3 Adapter Check on OcTk16. Action: A serious error occurred on the adapter, causing an adapter check code to be posted. Restart your system. If the error persists, write down the Data field in the Event Detail window and contact your place of purchase. 4 Unknown error code 4 Could not open adapter OcTk16. Ring beaconing. Check network speed settings. Action: The network speed settings is wrong. Change it and restart your system. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 55 5 Unknown error code 5 Could not open adapter OcTk16. Duplicate node address. Action: A duplicate address has been discovered on the ring. Change your locally administered address as described in the “Adapter parameter” section and restart your system. 6 Unknown error code 6 Could not open adapter OcTk16. Request initialisation failed. Action: An error occurred during adapter initialization. Restart your system. If the error persists, write down the Data field in the Event Detail window and contact your place of purchase. 7 Unknown error code 7 Could not open adapter OcTk16. Remove station received. Action: The adapter has been removed by a LAN Manager station. Contact your network administrator. 8 Unknown error code 8 Could not open adapter OcTk16. Action: The adapter failed to open. Check cables and connections and re-try the operation. 9 Unknown error code 9 Could not download code on adapter OcTk16. Action: The download operation failed. Write down the Data field in the Event Detail window and contact your place of purchase. A Unknown error code 10 Lobe wire fault detected by OcTk16. Please check cable connections. Action: Check all cables and connections and use another lobe media cable. re-try the operation. B Unknown error code 11 OcTk16 has failed the lobe wrap test resulting from the beacon auto-removal process and has deinserted from the ring. Action: The adapter has de-inserted from the ring, because the ring was beaconing. Check the network speed settings and cable connections and re-try the operation. If the error persists, contact your network administrator. C Unknown error code 12 OcTk16 has received a remove ring station Mac frame request and has deinserted from the ring. Action: The adapter has been removed by a LAN Manager station. Contact your network administrator. D Unknown error code 13 The detected adapter for OcTk16 is not supported by this driver. Action: You have installed a wrong MAC driver for the adapter used. E Unknown error code 14 The configuration read for OcTk16 is invalid. Action: A configuration entry is invalid. Use the network control panel to setup proper adapter settings. F Unknown error code 15 OcTk16 has received a Trace Tool Remove frame from a Network Management station and has disabled the promiscuous packet filter. Action: The adapter driver has cleared the PROMISCUOUS packet filter bit, as instructed by a LAN Manager station. Contact your network administrator. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 56 # General Error Message and Action 1388 Resource Conflict 5000 OcTk16: Has encountered a conflict in resources and could not load. Action: Check the resources used by the network adapter(s) to ensure that no conflicts exists. 1389 Out of resources 5001 OcTk16: Could not allocate resources necessary for operation. Action: The driver failed to load, because it tried to allocate too many resources. Decrease the number of receive and/or transmit buffers and re-try the operation. 138A Hardware Failure 5002 OcTk16: Has determined that the adapter is not functioning properly. Action: The adapter could not be found or is not working properly. Check I/O base settings and re-try the operation. 138B Adapter not found 5003 OcTk16: Could not find an adapter. Action: The adapter could not be found by the MAC driver. Check I/O base settings and re-try the operation. 138C Interrupt Connect 5004 OcTk16: Could not connect to the interrupt number supplied. Action: The interrupt is already used by another device. Change the adapter interrupt number and re-try the operation. 138D Driver Failure 5005 OcTk16: Has encountered an internal error and has failed. Action: An internal error has been discovered. Write down the Data field in the Event Detail window and contact your place of purchase. 138E Bad Version 5006 OcTk16: The version number is incorrect for this driver. Action: The driver version is incorrect. Write down the Data field in the Event Detail window and contact your place of purchase. 138F Time out 5007 OcTk16: Timed out during an operation. Action: A time-out error occurred. Write down the Data field in the Event Detail window and contact your place of purchase. 1390 Network Address 5008 OcTk16: Has encountered an invalid network address. Action: An invalid network address was specified. Change the locally administered network address and restart your system. The driver uses the burned-in address when loading. 1391 Unsupported Configuration 5009 OcTk16: Does not support the configuration supplied. Action: An invalid configuration entry was discovered. Use the network control panel to set proper adapter parameters. 1392 Invalid Value from Adapter 5010 OcTk16: The adapter has returned an invalid value to the driver. Action: An internal error has occurred. Write down the Data field in the Event Detail window and contact your place of purchase. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 57 1393 Missing Configuration Parameter 5011 OcTk16: A required parameter is missing from the registry. Action: A parameter necessary for operation has been omitted in the registry. Use the network control panel to set proper parameters. 1394 Bad IO Base Address 5012 OcTk16: The IO Base Address supplied does not match the jumpers on the adapter. Action: The adapter could not be found by the MAC driver. Check I/O base settings and re-try the operation. 1396 Adapter disabled 5014 OcTk16: The adapter is disabled. The driver cannot open the adapter. Action: Make sure the startup parameter for the Olicom Token Ring adapter driver is set to “Manual”. Use the “Devices” icon in the control panel to change the settings. 1397 I/O Port Conflict 5015 OcTk16: There is an I/O port conflict. Action: The ports used by the MAC driver is already in use by another device. Change the I/O Base address for the adapter. 1398 Port or DMA Conflict 5016 OcTk16: There is an I/O port or DMA channel conflict. Action: Check the I/O port and DMA usage by the adapter to ensure that there is no resource conflicts. 1399 Memory Conflict 5017 OcTk16: There is a memory conflict at address xx. Action: The MAC driver and another device could not share the memory. 139A Interrupt Conflict 5018 OcTk16: There is a interrupt conflict at interrupt number xx. Action: Change the interrupt selection on the adapter and re-try the operation. 139B DMA Resource Conflict 5019 OcTk16: There is a resource conflict at DMA channel xx. Action: Change the DMA channel selection on the adapter and re-try the operation. PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 58 B.6 Diagnostics Error Messages If errors are detected, make sure that: • The cabling matches the current test mode • The cabling is properly connected • The connectors are free of physical damage • The adapter ring speed matches the ring speed of the network • No resource conflicts present (I/O address range, interrupt level, DMA channel, etc.) ➽ Note: Running the test on a heavily-loaded network may cause the Transmit/Re- ceive test to report errors. Whenever an error is detected by the diagnostics program, an error message is displayed on the screen. These messages are self-explanatory, meaning that next to the error message you will find a more detailed description AND suggestions to solving the error condition. For this reason you will not find diagnostics error messages and suggested actions in this publication. ❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Driver Messages 59 Appendix C. Technical Information Processor: Texas Instruments TMS 380C30 Ring connectors: 8-pin RJ-45 for UTP with on-board media filter and 9-pin D sub-miniature for STP (DB-9) (see figure 8) 1 2 3456 78 5 4 3 2 1 9 8 7 6 Figure 7. Connector Configurations Power requirements: +5 VDC, 0.6A and +12 VDC, 0.03A Operating temperature: +10°C to +40°C (+50°F to +104°F) Humidity: 8% to 80% non-condensing Size: 136 x 78 mm (5.4" x 3.1") On-board memory: 128/512 Kbytes IEEE standards: 802.5 and 802.2 Certifications: FCC Part 15, subpart B Class B (shielded cable) CISPR 22 Class B (shielded cable) EN55022 Class B (shielded cable) FCC Part 15, subpart B Class A (unshielded cable) CISPR 22 Class A (unshielded cable) EN55022 Class A (unshielded cable) EN50082-1 EN60950 EN60825-1 I/O window: 128 bytes PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Technical Information 60 Data path width: 32 bit Data transfer: Bus-master DMA or programmed I/O Interrupt level: Any level assigned by the system LEDs: Figure 8. LEDs Green LED: ON when inserted into the network. OFF when not inserted into the network. Yellow LED: ON when running 4 Mbps. OFF when running 16 Mbps. ❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 Technical Information index-1 Index A I abbreviations 43 I/O address 5, 21 AIW Utility 6 IBM error messages 48 Extended Services 31 B LAN Server 3.0 31 backup 2 LAN Server 4.0 and MPTS 33 BIOS settings 38 LAN Support Program 28 bulletin board service 39 LAPS 31 NTS/2 31 PC LAN Program 28 C indicators 60 cable installation STP 10 adapter cable 10 UTP 10 adapter card 9 CompuServe 40 adapter driver 13 configuration preparing for 5 connector 59 Internet e-mail 40 MAC driver 34 interrupt level 5 connectors 59 K D keywords 21 dedicated Token-Ring 1, 13 diagnostic s 11 diskettes 2 L DLC LEDs 60 driver 28 light indicators 60 driver configuration 28 driver messages 45 M messages 19, 34, 45 E Microsoft e-Mail 40 error messages 51 early token release 29 Windows 95 14 error messages 19, 34, 45 Windows for Workgroups 3.11 15 expansion slots 7, 9 Windows NT 17 F N fax support 39 NDIS 2.0 FTP server 40 driver 27 full duplex 1, 13 driver messages 34 error messages 51 NDIS 3.0 H driver 15 hardware configuration 8 error messages 53 hardware installation 9 NETBEUI 33 help, on-line documentation 2 NetBIOS 28 hotline support 39 node address, changing 28 PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 index index-2 Novell NetWare client 32 for DOS 24 S client 32 for Windows 3.1x 24 software installation 13 client 32 for Windows 95 22 source routing 26 DOS ODI 20 speed setting 5, 8 error messages 46 STP (Shielded Twisted Pair) NetWare 3.12 25 cable connection 10 NetWare 4.x 25 supplied items 2 source routing 26 support, technical 39 system requirements 7 O OC01IA.SYS 30 T ODI driver 20 technical data 59 on-line documentation 2 technical support 39 P U PCI 1 utilities 35 problem report form 41 UTP (Unshielded Twisted Pair) protocol stacks 21 cable connection 10 R V ring speed 8 VLM 20 W Windows 95 14 Windows for Workgroups 3.11 15 Windows NT 17 ❏ PCI/II 16/4 Adapter GTO v. 2.2, P/N 710001434 index Olicom A/S Olicom, Inc. Olicom Enterprise Products, Nybrovej 114 900 East Park Boulevard Inc. 2800 Lyngby Suite 250 450 Donald Lynch Boulevard Denmark Plano, Texas 75074 Marlborough Tel: (+45) 45 27 00 00 Tel: (+1) 972 423 7560 MA 01752 Fax: (+45) 45 27 01 01 Fax: (+1) 972 423 7261 Tel: (+1) 508 481 4060 Olicom Africa Olicom France Fax: (+1) 508 229 5535 Johannesburg Office: Immeuble Plein Ouest Olicom Poland Sp. z o.o. 6th Floor, Nedbank House 177, Avenue G. Clemenceau ul. Uphagena 27 12 Fredman Drive 92000 Nanterre 80-237 Gdansk Sandown, Sandton Tel: (+33) 01 41 91 17 17 Tel: (+48) 58 471 451 P.O. Box 785136 Fax: (+33) 01 41 91 17 00 Fax: (+48) 58 461 238 2146 Sandton Olicom Germany Tel: (+27) 11 784 8990 Olicom Singapore Frankfurt Office: Fax: (+27) 11 784 9090 331 North Bridge Road Hessenring 13a #03-01 Odeon Towers Cape Town Office: 64546 Mörfelden Singapore 188720 4 Docav Road Tel: (+49) 06 105 2892-0 Tel: (+65) 339 7221 Constantia Fax: (+49) 06 105 2892-10 Fax: (+65) 339 1676 Cape Town Munich Office: P.O. Box 6196 Stefan-George-Ring 29 Olicom Sweden 8012 Roggebaai 81929 Munich Kanalvägen 10 C-12, 9 vån Tel: (+27) 21 758 525 Tel: (+49) 89 993 393-0 194 61 Uplands Väsby Fax: (+27) 21 758 527 Fax: (+49) 89 993 936-27 Tel: (+46) 8 590 041 94 Fax: (+46) 8 590 041 10 Olicom Australia Olicom Ibérica Olicom Enterprise Products Level 6 Edificio Valrealty, La Florida 73-79 Walker Street C/Basauri, 17 Edif. A 2a (UK) Ltd North Sydney, NSW 2060 28023 Madrid Swan House Tel: (+61) 2 9955 1755 Tel: (+34) 1 372 9814 Peregrine Business Park Fax: (+61) 2 9955 8488 Fax: (+34) 1 372 9645 Gomm Road High Wycombe Olicom Austria Olicom Italy Bucks HP13 7DL Mariahilfer Strasse 103/2/1/42a Via G. Rasori 13 Tel: (+44) 1494 556 600 1060 Vienna 20145 Milano Fax: (+44) 1494 556 616 Tel: (+43) 1 597 3131-0 Tel: (+39) 2 4800 3661 Fax: (+43) 1 597 3131-27 Fax: (+39) 2 4800 5888 Olicom Benelux Olicom Japan Bolduc Office Centre 21 Fl., KDD Otemachi Bldg. Utopialaan 35-N 1-8-1, Otemachi 5232 CD 's-Hertogenbosch Chiyoda-Ku Tel: (+31) 73 6 49 15 46 Tokyo 100 Fax: (+31) 73 6 49 15 45 Tel: (+81) 3 3243 9226 Fax: (+81) 3 3243 9227 World Wide Web URLs http://www.olicom.com http://www.olicom.dk OC-6916/2.2 *710001434* Printed in Denmark by