Copyright: Copyright © 1998 Olicom A/S


Adapter Detection Programs

In PC environments where network adapters from several different vendors are used in DOS workstations, it is possible to use three special utility programs, IF_OLI.COM, ELSE_OLI.COM, and END_OLI.COM, to create common CONFIG.SYS and/or AUTOEXEC.BAT files ensuring that the network drivers loaded are appropriate for the adapter in a given PC.  That is, the same CONFIG.SYS and AUTOEXEC.BAT files can be used on machines with different network adapter configurations.

The three COM files are located in the \IFOLI directory on the Setup Disk or CD-ROM.

The utility programs check for the presence of a RapidFire 314x Adapter in a machine.  The three programs work together to form conditional statements of the form "IF an Olicom adapter is found, do X, ELSE do Y."

Depending of whether you want this type of context-dependent configuration in your CONFIG.SYS or AUTOEXEC.BAT, you should read the corresponding section below.  Note that you can use both if this matches your needs.

Note:

In the examples below comments have been added and should not be entered as part of a CONFIG.SYS file. The comments are prefixed with "--" (quotes not included).

CONFIG.SYS

To add context-dependent configuration to your CONFIG.SYS file, use the "device=" statement to load the IF_OLI.COM, ELSE_OLI.COM, and END_OLI.COM files as device drivers.  These files do not take up any memory once the configuration process is complete.

The use of these files is illustrated through the following example, where either an Olicom RapidFire 314x or IBM driver is installed, depending on which adapter card is present in the machine:

device=\if_oli.com              -- Is there an Olicom adapter in the PC?

device=\oct3xnd2.dos            --   Yes, load the Olicom RapidFire 314x NDIS driver.

device=\else_oli.com            -- If not, do the following:

device=\ibmtok.dos              --   Load IBM's NDIS driver instead.

device=\end_oli.com             -- End of context-dependent section.

The use of the ELSE_OLI.COM program is optional.  The following example simply checks if a network card is present, and installs the network device drivers only if the adapter is there:

device=\if_oli.com              -- Is there an Olicom adapter in the PC?

device=\protman.dos /I:\        --   Yes, load the MS Protocol Manager

device=\oct3xnd2.dos            --   and the Olicom RapidFire 314x NDIS driver.

device=\end_oli.com             -- End of context-dependent section.

AUTOEXEC.BAT

To add context-dependent configuration to your AUTOEXEC.BAT file, use the IF_OLI.COM program in conjunction with the built-in DOS "IF ERRORLEVEL" command.  The IF_OLI.COM program sets the ERRORLEVEL variable to one if NO Olicom adapter is present and to greater than or equal to 10 if an Olicom adapter is found. The actual value of ERRORLEVEL set when an Olicom adapter is found depends on the adapter type. In the table below you will find a list of the actual values:

  Olicom adapter     Type            Value of ERRORLEVEL

 ========================================================

      BAD USAGE (accepts no arguments)       0

      NONE           -                       1

  16/4 Mbps adapters

     OC-3220         PCMCIA                  10

     OC-3115/14      ISA                     11

     OC-3129/28      MCA                     12

     OC-3133         EISA                    13

     OC-3121         PCA  (XT)               14

     OC-3117         ISA  2. generation      15

     OC-3118         ISA  3. generation      16

     OC-3136         PCI                     17

     OC-3221         PCMCIA 2.generation     18

     OC-3230         PCMCIA/Modem 144        19 *)

     OC-3137         PCI  2. generation      20

     OC-3232         PCMCIA/Modem 336        22

     OC-3139         PCI  3. generation      23

     OC-3140         PCI  3. generation      25

     OC-3141         PCI  3. generation      26

     OC-3250         Cardbus                 24

     OC-3135         EISA 2. generation      30

  4 Mbps adapters

     OC-3120         XT                      41

     OC-3112         AT                      42

     OC-3126         MCA                     42

*) If modem is disabled (LAN only) OC-3230 is reported

If you need to distinguish between different Olicom adapters use the different values of the ERRORLEVEL variable in conjunction with the built-in DOS "IF ERRORLEVEL" conditional. Please note that the order of the "IF ERRORLEVEL" statements is significant as the statement actually tests if ERRORLEVEL is greater than or equal to the specified value.

It is important to arrange the test for the various ERRORLEVEL values in descending order.

Please consult the following examples for guidance.

Load either IBM or Olicom Novell ODI driver

lsl.com                               -- Novell's Link Support program.

IF_OLI.COM                            -- Check for Olicom adapter presence

if ERRORLEVEL 10 goto is_oli

if ERRORLEVEL 1 goto is_other

echo Bad usage.                       -- a help message has been written

goto common

:is_oli                               -- Found an Olicom RapidFire 314x Adapter!

rem Found Olicom adapter as expected.

OCT3XODI.COM                           -- Load Olicom RapidFire 314x ODI driver

goto common

:is_other                             -- No Olicom adapter found!

rem NO Olicom adapter installed.

TOKEN.COM                             -- Load IBM ODI driver.

:common

rem only the MAC driver is hardware dependent

ipxodi.com                            -- Load the IPX protocol.

netx.exe                              -- Load the NetWare DOS shell.

Loading the optimal DOS ODI driver for an Olicom 16/4 adapter

lsl.com                               -- Novell's Link Support program.

IF_OLI.COM

if ERRORLEVEL 10 goto oli

if ERRORLEVEL 1 goto common

echo BAD USAGE.                       -- a help message has been written

goto common

:oli

if ERRORLEVEL 41 goto common          -- no ODI driver for 4Mbps adapters

if ERRORLEVEL 25 goto RF3140

\OLICOM\OCTOK16.COM                   -- Load default ODI driver

goto common

:RF3140                               -- Load high performance ODI driver

\OLICOM\OCT3XODI.COM

:common

ipxodi.com                            -- Load the IPX protocol.

netx.exe                              -- Load the NetWare DOS shell.

Distinguishing all Olicom adapters:

@echo off

if_oli.com

if ERRORLEVEL 43 goto oli_3126        -- remember to test for greatest

if ERRORLEVEL 42 goto oli_3112        -- value first as explained above.

if ERRORLEVEL 41 goto oli_3120

if ERRORLEVEL 30 goto oli_3135

if ERRORLEVEL 26 goto oli_3141

if ERRORLEVEL 25 goto oli_3140

if ERRORLEVEL 24 goto oli_3250

if ERRORLEVEL 23 goto oli_3139

if ERRORLEVEL 22 goto oli_3232

if ERRORLEVEL 20 goto oli_3137

if ERRORLEVEL 19 goto oli_3230

if ERRORLEVEL 18 goto oli_3221

if ERRORLEVEL 17 goto oli_3136

if ERRORLEVEL 16 goto oli_3118

if ERRORLEVEL 15 goto oli_3117

if ERRORLEVEL 14 goto oli_3121

if ERRORLEVEL 13 goto oli_3133

if ERRORLEVEL 12 goto oli_3129

if ERRORLEVEL 11 goto oli_3115

if ERRORLEVEL 10 goto oli_3220

if ERRORLEVEL 1 goto no_oli

echo Bad usage.                       -- a help message has been written

goto common

:no_oli

echo NO Olicom adapter installed.

goto common

:oli_3115

echo Found Olicom oc-3115 or oc-3114 ISA adapter.

goto common

:oli_3129

echo Found Olicom oc-3129 or oc-3128 MCA adapter.

goto common

:oli_3133

echo Found Olicom oc-3133 EISA adapter.

goto common

:oli_3121

echo Found Olicom oc-3121 PCA (XT) adapter as expected.

goto common

:oli_3117

echo Found Olicom oc-3117 ISA adapter.

goto common

:oli_3118

echo Found Olicom oc-3118 ISA adapter.

goto common

:oli_3136

echo Found Olicom oc-3136 PCI adapter.

goto common

:oli_3137

echo Found Olicom oc-3137 PCI adapter.

goto common

:oli_3232

echo Found Olicom oc-3232 GoCard TRN/Modem 336 adapter.

goto common

:oli_3139

echo Found Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter.

goto common

:oli_3140

echo Found Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter.

goto common

:oli_3141

echo Found Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter.

goto common

:oli_3250

echo Found Olicom GoCard 3250 Token-Ring 16/4 Cardbus PC Card.

goto common

:oli_3135

echo Found Olicom oc-3135 Server EISA adapter.

goto common

:oli_3220

echo Found Olicom oc-3220 PCMCIA adapter.

goto common

:oli_3221

echo Found Olicom oc-3221 PCI adapter.

goto common

:oli_3230

echo Found Olicom oc-3230 PCI adapter.

goto common

:oli_3120

echo Found Olicom oc-3120 4Mbps XT adapter.

goto common

:oli_3112

echo Found Olicom oc-3112 4Mbps AT adapter.

goto common

:oli_3126

echo Found Olicom oc-3126 4Mbps MCA adapter.

goto common

:common


Adapter Diagnostics
Adapter Diagnostics Program

The RapidFire 314x Adapter is supplied with a diagnostics program that can be used for:

  *	Testing the adapter and the adapter cable(s) if you suspect a problem.

  *	Viewing the current adapter configuration

Important:

The Diagnostics Program must be run from the Olicom Setup Disk.

Running the Diagnostics Program

1.	Insert the Olicom Setup Disk in the disk drive.

2.	Boot the system from the Olicom Setup Disk.

Adapter Test

To test that the adapter itself is working in the current configuration, run the internal tests by selecting "Run Diag" from the main window.

Note:

The network connection will not be tested (see below).

Network Connection Test

To test the network connection you must first set up a secondary workstation with an Olicom Token-Ring adapter.

1.	Start the Diagnostics Program on the secondary workstation and run the internal tests as described above (preferably from a copy of the Olicom Setup Disk).

2.	Select "Be Responder" to set up the secondary workstation as a responder (a responder is a station on the LAN which echoes packets transmitted from other workstations running the network diagnostics).

3.	When the responder is started on the secondary workstation, select "Network Test" on the primary workstation.

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.

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.

Additional Information

See also the Diagnostics Program online help for further information about the program.


Adapter Information for Windows (AIW)
Adapter Information for Windows - AIW

The Adapter Information for Windows (AIW) program displays information about the adapter and the adapter driver. The program can be used in Windows 3.x. If running Windows 95/98 or Windows NT, you must use LANscout. Different information about adapter, driver and network traffic can be shown, but only for the system on which AIW is runnning.

If needed, configuration data can be saved to a file or printed.

System Requirements

  *	Microsoft Windows 3.1x or Windows for Workgroups 3.11

  *	An Olicom DMI 1 enabled driver:

OCT3XND2.DOS (NDIS 2.0 DOS driver)

Installing AIW

Note:

AIW can only be installed from the CD-ROM.

1.	Insert the CD-ROM.

If the AutoPlay feature is enabled for your CD-ROM drive, a menu will popup.

If not, run SETUP.EXE from the CD-ROM (D:\SETUP.EXE).

2.	Select "Launch the Setup program" from the menu.

3.	From the Setup program select "Utility Installation" and "Olicom Adapter Information for Windows".

4.	Follow the instructions to complete the installation.

The installation process creates a new program group in which the AIW icons are located.

Running AIW

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>.

Uninstalling AIW

If required, the AIW application can be uninstalled by manually deleting the program files from your hard disk. These files are by default placed in the C:\OLICOM directory and are: AIW.EXE, AIW.HLP, AIW.INI, AIW.ATM, ILIB31HT.DLL, OLIAIW.DLL, OLIAIW.VXD and OLIAIW32.DLL. Any files in the HTML subdirectory may also be deleted.


Adapter Utility Programs

Three programs are available from the "Utility Installation" button in the Olicom Setup Program when run from DOS or Windows 3.x. The utilities are:

  *	Adapter Information for Windows - AIW

  *	Desktop Management Interface - DMI

  *	Olicom Adapter Help

Three additional utilities are contained on the Olicom CD-ROM and the Olicom Setup Disk:

  *	Runtime Statistics and Status Program

  *	DOS Command Line Adapter Configurator

  *	Detecting Olicom Adapters

When used in Windows 95/98 and Windows NT, the Setup Program provides installation and access to:

  *	LANscout

  *	Desktop Management Interface - DMI

  *	Documentation in PDF format and HTML format

DOS Command Line Adapter Configurator

The OCT3PCFG utility program is used to change the configuration of RapidFire 314x Adapters from the DOS command line. The new configuration data is stored in the adapter non-volatile memory, and remains active until it is changed again. See OCT3PCFG Utility Program.

Runtime Statistics and Status Program

The runtime statistics assist the network administrator in monitoring the actual network load including protocol stack overhead, as well as the frequency of a number of transient network errors.

The runtime configuration status display shows a number of configuration parameters as well as the status (open/closed) of the adapter card. See Runtime Statistics and Status Program.

Detecting Olicom Adapters

In environments having standard start-up files (CONFIG.SYS, AUTOEXEC.BAT) but network adapters from different vendors, it is very useful to be able to detect the Olicom adapters. For this purpose, Olicom supplies a set of adapter detection utilities.

Olicom Adapter Help

If you do not have a CD-ROM drive, you can install the online documentation on the hard disk to get faster access.


CFG3139 Utility Program
OCT3PCFG Utility Program

The OCT3PCFG utility program is used to change the configuration of RapidFire 314x Token-Ring 16/4 PCI Adapters from the DOS command line.

Note:

Before changing any parameters, make sure that all traffic to the adapter has been stopped.

New configuration data is stored in the adapter non-volatile memory and remains active until it is changed again.

The program is located in the \ADPCFG directory on the Olicom CD-ROM and the Olicom Setup Disk.

The configuration parameter(s) you want to change must be specified in the command line as parameters to the OCT3PCFG program. If no parameters are specified, the current configuration of the adapter is displayed.

The following command line parameters are valid:

/HELP

Activates the help:

OCT3PCFG setup program for the

Olicom RapidFire 3139/4x Token-Ring 16/4 PCI Adapters v.x.xx (yymmdd)

(C) Copyright 1998, Olicom A/S

Usage: OCT3PCFG [/KEYWORD=VALUE]

Keyword   Legal values     Description

      A  *0 1 2 3 4 5 6 7  Selects between more Adapters

    MEM  *ANY LOW          Sets the Adapter memory window ANYwhere/beLOW 1 Mb

  SPEED  *AUTO 16 4        Sets Ring Speed to AUTO detection, 16 or 4 Mbps

     PM  *ON OFF           Sets the Power Management option to ON or OFF

    RPL  *AUTO OFF         Sets the Remote Program Load option to AUTO or OFF

Factory default settings are marked with an asterix (*).

No parameters displays the actual setting

/A=<0,1,2,3,4,5,6,7>

Selects one of more RapidFire 314x Adapters by number. The default is 0.

/MEM=<LOW, ANY>

Selects where to place the adapter 16 kbyte memory window. The LOW option forces the memory window to be placed within the first megabyte of physical memory.

/SPEED=<AUTO | 16 | 4>

Sets the adapter ring speed to either Auto detection, 16 or 4 Mbps. The factory default setting is AUTO.

/PM=<ON | OFF>

Disables or enables Power Management and Wake-on-LAN of the adapter. The factory default setting is ON.

/RPL=<AUTO | OFF>

Disables or enables the Olicom Remote Program Load PROM (if installed). The factory default setting is AUTO.

Warning:

For changes other than speed setting to be effective, the main power must be turned off and on.

Example: Change the adapter network ring speed from AUTO to 4 Mbps. Enter:

OCT3PCFG /SPEED=4

Example: Actual parameter setting:

OCT3PCFG setup program for the

Olicom RapidFire 3139/4x Token-Ring 16/4 PCI Adapters v.x.xx (yymmdd)

© Copyright 1998, Olicom A/S

Node Address: 00008363bc3d (Serial Number = 63bc3d)

Date: 1998-03-04

Adapter Type: Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter

A=0

MEMORY=ANY

SPEED=AUTO

PM=ON

RPL=AUTO


Configuring the NDIS 2.0 MAC Driver

This section describes how to configure the NDIS 2.0 MAC driver via the PROTOCOL.INI file.

The adapter MAC driver, OCT3XND2, is delivered with installation files for IBM and Microsoft network operating systems. For an overall introduction to configuring Microsoft LAN Manager drivers, refer to "Microsoft LAN Manager, Network Device Driver Guide".

For an overall introduction to configuring IBM LAN Server drivers, refer to the IBM publications "LAN Adapter and Protocol Support Configuration Guide" and "IBM LAN Support Program User's Guide".

If you need specific information about parameters in the PROTOCOL.INI file - or if your network operating system does not provide utilities for configuring the MAC driver - the following pages provide the necessary information.

If you have installed your adapter with default configuration and have not changed any parameters for NetBIOS or DLC, there is no need for you to change the installed PROTOCOL.INI file. The PROTOCOL.INI file delivered with your adapter contains parameter settings which are tuned to the default settings of NetBIOS and DLC.

The PROTOCOL.INI section for OCT3XND2 has one required entry:

Drivername = OCT3XN$

The adapter implements the loopback function, so the [DLC] section of PROTOCOL.INI does not need a "loopback =" entry.

The NDIS 2.0 drivers support full duplex when connected to a Full Duplex Token-Ring switch. If the driver is running in Full Duplex mode, the EarlyRelease parameter will have no effect.

The entries in the OCT3XND2 section may be divided into two groups: Entries related to the configuration of the adapter itself and entries related to the driver software. The entries for the two groups as well as the syntax are:

Adapter Configuration Entries:

NodeAddress = hex value, hex value, hex value

NetAddress = value

EarlyRelease = value

A hex value has the format 0xdddd, where "d" may be any hexadecimal digit, for example 0x4ABC.

NetAddress and NodeAddress are two alternative formats for a node address.

OCT3XND2 Configuration Entries:

AdapterId = value (add quotes for WfW 3.11: AdapterId = "value")

MaxFrameSize = value

MaxRequests = value

MaxTransmits = value

RecBufSize = value

RecBufCount = value

ReOpen = value

RingSpeed = value

SupportGDT = value

NDIS201

WakeOnLan = value

The following table summarizes the valid entries and values in the OCT3XND2 section.

Entry          Min. Value      Max Value       Default

AdapterId=     -               -               -

MaxFrameSize=  512             17954           17954 (See RecBufSize)

NodeAddress=   4000 0000 0000  4FFF FFFF FFFF  On-Board

NetAddress=    4000 0000 0000  4FFF FFFF FFFF  On-Board

MaxRequests=   1               10              6

MaxTransmits=  2               100 (OS/2)      6

                               12  (DOS)       6

RecBufSize=    256             5080            512  (DOS)

                                               4500 (OS/2)

RecBufCount=   6               30              10

EarlyRelease=  NO              YES             YES

ReOpen=        NO              YES             YES

RingSpeed=     -               -               0

SupportGDT=    NO              YES             NO

NDIS201        -               -               -

WakeOnLan=     NO              YES             NO

The parameters have the following meaning:

AdapterId =

Purpose: This parameter identifies a specific adapter in the PC. The value of this parameter is a hexadecimal 12-digit number (for example 000083638CA3) and is located on the adapter bracket.

Example: AdapterId = 000083638CA3.

Note: Quotation marks must be used for Windows for Workgroups 3.11. They make the protocol manager accept the value as a string and not as a large number.

Windows for Workgroups 3.11 example: AdapterId = "000083638CA3".

Use only this parameter if more than one adapter is installed in the PC, and you want to override the automatic order in which the adapters are found.

MaxFrameSize =

Purpose: This parameter limits the maximum frame lengths that the driver supports. Some protocols, for example the IBM NetBIOS driver for DOS, require that the maximum frame size is below a certain value. The actual maximum frame length is the lowest value of MaxFrameSize, the ReceiveArea determined by RecBufSize and RecBufCount and TxBufferSize.

NodeAddress =

Purpose: If this entry is specified, the specified value will be used in place of the universal burned-in node address on the adapter.

Note that the entered address must be administered locally.

Example:  NodeAddress= 0x4000  0x1234  0x5678

NetAddress=

Purpose: Same as NodeAddress, but available for compatibility with IBM Extended Services 1.0 and LAN Server 2.0/3.0.

Example:  NetAddress = "400012345678"

Note the quotation marks enclosing the values. They are important as they make the protocol manager accept the value as a string and not as a large number.

The letter "t" can be inserted in front of the NetAddress value.  This is recommended when configuring the MAC driver in Windows for Workgroups.

Example:  NetAddress = "t400012345678"

MaxRequests =

Purpose: Sets the maximum number of outstanding GeneralRequests and configures the size of GeneralRequest Queue.

MaxTransmits =

Purpose: Sets the maximum number of outstanding TransmitChain commands. This configures the size of the TransmitChain Request Queue.

RecBufSize =

Purpose: Configures the size of each receive buffer (in bytes) in the PC. The number of receive buffers is defined by the RecBufCount entry. RecBufSize multiplied by RecBufCount is the total Receive Area allocated in the PC.

The maximum size of frames which may be received and transmitted by the adapter is limited by the lowest value of these factors:

- Ring speed, 17954 at 16 Mbps and 4472 at 4 Mbps.

- ReceiveArea minus 256 (RecBufSize x RecBufCount - 256)

- MaxFrameSize parameter (if defined in PROTOCOL.INI)

- TxBufferSize parameter (if defined in PROTOCOL.INI)

RecBufCount =

Purpose: Configures the number of Receive buffers in the PC.  The size of a receive buffer is defined by the RecBufSize entry. RecBufSize multiplied by RecBufCount is the total ReceiveArea allocated in the PC. See also the RecBufSize entry.

EarlyRelease =

Purpose: If set to "NO", the "early token release" function on a 16 Mbps Token-Ring is disabled. The keyword is ignored on a 4 Mbps Token-Ring.

This parameter has no effect when the adapter is in Full Duplex mode. The driver will always run as if the parameter was set to "Yes".

ReOpen =

Purpose:  This parameter specifies re-opening of the adapter by the network driver if it closes due to a lobe error.

RingSpeed =

Purpose: This parameter sets the ring speed of the Token-Ring network. "0" means auto-detection of the speed, "4" means 4 Mbps, "16" means 16 Mbps and "256" means adapter default..

Default is auto-detection of speed 0).

SupportGDT =

Purpose: To make the driver accept virtual addresses (GDT) in OS/2. This parameter specifies whether a protocol can transmit frames using virtual addresses, or if it must use physical addresses.

If your protocols can only use virtual addresses, set this parameter to "YES".

The default for SupportGDT is "NO" (it provides higher performance compared to "YES").

The parameter is only valid in OS/2.

NDIS201

Purpose: This parameter specifies that the network driver may only support NDIS201, and not the IBM extension to the NDIS 2.01 standard denoted NDIS 2.02 and disable support for promiscuous (receive any packet on LAN) receive mode.

The default is that this parameter is omitted, thus supporting LAN Station Manager, LAN Network Manager and IBM NDIS protocols that require NDIS 2.02.

The "NDIS201" parameter must be used if you want to perform NDIS 2.01 conformance tests.

WakeOnLan

Purpose: This parameter specifies if the the Wake-on-LAN facility should be enabled (YES) or disabled (NO).

Default is "NO".

Multiple Adapter Configuration

You may install up to four Token-Ring adapters in your computer (up to two in DOS systems). Observe the following guidelines if installing more than one adapter. Observe the following guidelines if installing more than one adapter.

If your network operating system is IBM LAN Server, IBM DOS LAN Services or Microsoft Windows for Workgroups, the network installation utilities provided with the systems execute configuration with multiple adapters.

The new PROTOCOL.INI will have two or more driver sections. The first section will be identified by "drivername=OCT3XN$". The following sections will be identified by "drivername=OCT3XN2$", OCT3XN3$ and OCT3XN4$ respectively.

In each of these sections, use the "AdapterId=nnnnnnnnnnnn" parameter to identify the address of the specific adapter. The address cab be found on the adapter metal bracket.


Contents of Help File

Help file for RapidFire 314x Adapters, version 1.00.02

RapidFire 3140 Token-Ring 16/4 PCI Adapter

RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter

This help file contains extensive information about the Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter and the Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter, and provides help for using the Olicom Setup Program.

Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter and Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter will in this online documentation also be referred to as "RapidFire 314x Adapter".

Select the topic about which you want more information:

Installation Overview 	Adapter Utility Programs

Olicom Setup Program	Contacting Olicom

Driver Installation 	Troubleshooting

Late-Breaking News	Error Messages

LANscout	Olicom CD-ROM

About the RapidFire 314x Adapters

The RapidFire 314x Adapters, Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter for UTP and STP media cabling and Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter for fiber media cabling, provide industry-leading performance for servers and workstations. Using Olicom's Token-Ring MAC technology and Dedicated Token-Ring PowerMACH drivers, the RapidFire 314x Adapters offer unsurpassed levels of throughput. With advanced power management utilities and automatic performance optimization, the adapters provide a state-of-the-art solution for Token-Ring networks.

The RapidFire 314x Adapter has extensive power management facilities and wake-up event support. The support includes AMD's Magic Packet, Microsoft's OnNow implementation of the Advanced Configuration and Power Interface (ACPI), and IBM's legacy Wake-on-LAN. The RapidFire 314x Adapter supports both Intel and IBM legacy wake-up cabling. In addition the RapidFire 314x Adapter is prepared to support coming wake-up events such as Virtually Connected and Cable connect/disconnect.

Intuitive management of the RapidFire 314x Adapter is achieved with the Olicom LANscout desktop management system together with implementation of industry standard Desktop Management Interface (DMI 1 and 2). The Olicom LANscout application provides local and remote access to all adapter information through a browser interface. LANscout allows comparing the installed drivers with the latest drivers available from Olicom's web site, and retrieve upgrades with a click of a button. With support of the open management initiative DMI, full support for third party management applications is achieved.

The RapidFire 314x Adapter automatically adjusts itself to the varying load on the PCI bus, making it an ideal choice for both server and workstation environments. The adapter’s powerful DMA engine with adaptive parameter optimization together with superior interrupt pacing provides extremely low CPU utilization in all environments.

Ease of use is ensured with extensive support for automatic configuration at installation. The adapter automatically detects ring speed, media type and full-duplex capabilities of the network. Combining the extensive support for automatic network configuration with PCI hot plug, Plug and Play compliance and Olicom's installation wizard, the installation will succeed with a minimum of effort.


Desktop Management Interface - DMI

The RapidFire 314x Adapter package includes DMI instrumentation modules for DMI 2 and DMI 1. DMI 2 is used with Windows 95/98 and Windows NT and DMI 1 is used with DOS and Windows 3.x.

The Olicom Adapter Setup Program will install the correct modules depending on your environment.

DMI 2

On the Olicom CD-ROM is a MIF and Component Instrumentation Code (CIC) complying with the DMI standard, rel. 2.

Support requires that:

*	a DMI Service Provider is running on the PC.

*	the Olicom MIF and corresponding instrumentation code has been installed.

Installation of the Olicom MIF and instrumentation code can be performed with the Olicom Adapter Setup program.

The CIC is for use with the DMI 2 Service Provider for Win32 by Intel, which runs on Windows 95/98, Windows NT 3.51 and Windows NT 4.0. This Service Provider will automatically be installed by the Setup program if there is no DMI Service Provider present on your system.

The MIF database will automatically be updated with information about all Olicom adapters installed on the system. If more adapters are added later, these will also automatically be added to the MIF database. However, adapters are not automatically removed from the MIF database.

Compliance

The DMI support has been certified to comply with the Desktop Management Interface specification, rel. 2.0.

The MIF complies with the DMTF standard LAN Adapter MIF, rel. 1.0, and has been certified by the DMTF as being DMI compliant.

Olicom drivers

Use of the Instrumentation code requires the presence of an Olicom adapter and a DMI-ready Olicom driver for Windows 95/98 or Windows NT.

DMI 1

The DOS- and Windows 3.x drivers shipped with this Olicom adapter support the Desktop Management Interface (DMI) specification, rel. 1.0.

Support requires that:

*	a DMI Service Layer is running on the PC

*	the Olicom MIF and corresponding instrumentation code has been installed

Installation of the Olicom MIF and instrumentation code can be performed with the "Utility Installation" function of the Olicom Setup program.

This copies the MIF file to the Service Layer's MIFS directory (default: C:\DMI\DOS\MIFS), and the Instrumentation code to the Service Layer BIN directory (default: C:\DMI\DOS\BIN).

When the Service Layer is restarted (typically when the machine is booted), the MIF file is automatically added to the Service layer database of installed MIF-files.

Compliance

The DMI support has been certified to comply with the Desktop Management Interface specification, rel. 1.0.

DMI Service Layers

The Instrumentation code is intended for use with the DOS Service layer. It will also work with the DOS/Windows service layer that requires loading the DOS Service Layer before starting Windows, and with the Windows-only Service Layer.

These are not shipped with the adapter, but can be downloaded free of charge from the Desktop Management Task Force (DMTF) FTP server at ftp.dmtf.org.

If you are using the DOS or DOS+Windows Service Layer, make sure that the command used to load the DOS Service Layer include the option "o=12" (or any number greater than 12). Failure to do so will cause the CIC to fail.

Olicom drivers

Use of the Instrumentation code requires the presence of an Olicom adapter and a DMI-ready Olicom driver, for example the DOS ODI or DOS NDIS 2.0 drivers.


Driver Installation

Before the adapter can be used, one or more driver programs must be loaded. The driver required depends on the network environment in which you are going to operate.

The Olicom network drivers are available on both CD-ROM and on 3.5 inch high-density disks. It is assumed throughout the installation procedures that the Olicom CD-ROM is the source media, and that the CD-ROM drive is "D". If the CD-ROM drive is different from "D", or you want to install from the Olicom Driver Disk, change the drive letter as required.

Each Network Operating system normally has an installation program that supports installation of third party adapters. We recommend that you use this program. Consult the documentation that came with your Network Operating System for details.

You can, however, still get some help from this program. Select a network operating environment from the list below:

Microsoft	Windows 95, Windows 98, Windows NT

and Windows for Workgroups 3.11

Novell	NetWare workstations and servers

IBM 	Workstations and servers

All the Olicom adapter drivers support Full Duplex Token-Ring, also referred to as Dedicated Token-Ring (DTR).

The Full Duplex 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.


Error Messages

Select one of the drivers below for further information on driver and error messages:

Novell NetWare Server ODI and Client 32 Driver

NDIS 2.0 Driver

NDIS 3 Miniport Driver


Getting in Touch with Olicom

Olicom Offices Worldwide

Africa

Australia

Austria

Benelux

Denmark

France

Germany

Italy

Japan

Poland

Singapore

Spain

Sweden

UK

USA

Olicom Technical Support Centers

Denmark

USA


Hardware Configuration

Clicking on the "Hardware Configuration" button in the main window displays the hardware configuration dialog box. If your have more than one adapter in your computer, you must first select the appropriate adapter.

In this dialog box you can select the hardware settings to use with the Olicom adapter.

The settings you select on this screen will be written to the adapter when you press the OK button. You will then see a warning message at which stage you must confirm that you want to change the settings.

WARNING:

If you already have a network driver running and are connected to a server, your machine may hang or behave in an unexpected manner after you have changed the hardware configuration.

In the Hardware Configuration dialog box you can set the following configuration parameter for your adapter:

Ring Speed

Here you specify the transmission speed used on the network. It can be either 4, 16 Megabits per second or auto-detect.

Three buttons are available:

OK

Press this button to write the configuration to the adapter. You will be asked to confirm the action.

Cancel

Press this button to close the dialog box without saving the configuration.

Help

Press this button to display this help message.

Command-line configuration program

If you are going to configure a large number of PCs with identical adapters and identical configurable settings, you may want to use the command-line configuration program instead. The command-line configuration program OCT3PCFG can change the configuration of an adapter. You can also use it to monitor the configuration of installed adapter(s).


IBM DOS LAN Services (DLS) Details

The driver can be installed either during DOS LAN Services installation or after DOS LAN Services has been successfully installed.

Driver Installation during DOS LAN Services Installation

1.	Start the installation as described by IBM with the following command:

A:\INSTALL

2.	When prompted for the type of network card used, select 'Network card not shown in list below' and press <Enter> to continue.

3.	Insert the Olicom CD-ROM and specify the location of the OEMSETUP.INF file to be

D:\IBM\NDIS.DOS

4.	Select "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter" and change - if required - the default settings for the adapter by selecting 'Edit settings for network card driver'.

5.	Select 'Driver configuration is correct' and press <Enter> to continue.

6.	Follow the guidelines given by IBM to proceed with the installation.

7.	When the 'Installation Complete' screen appears, press <F3> for Exit without rebooting.

8.	Copy the driver from the Olicom CD-ROM to your default DOS LAN Services directory (for example C:\NET) by inserting the Olicom CD-ROM and entering the following command:

COPY D:\IBM\NDIS.DOS\OCT3XND2.DOS C:\NET

Press <Enter> to continue.

9.	Reboot your PC to start DOS LAN Services.

Driver Installation after DOS LAN Services Installation

1.	Start the installation as described by IBM - type:

C:\NET\INSTALL

2.	Select "The listed options are correct" and press <Enter> to continue.

3.	Select "Network Card" and press <Enter> to continue.

4.	Select "Change driver for network card" and press <Enter> to continue.

5.	Select "Network Card not shown in list below" and press <Enter> to continue.

6.	Insert the Olicom CD-ROM and specify the location of the OEMSETUP.INF file to be:

D:\IBM\NDIS.DOS

7.	Press <Enter> to continue.

8.	Select "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter" and change - if required - the default settings for the adapter driver by selecting "Edit settings for network card driver".

9.	Select "Driver configuration is correct" and press <Enter> to continue.

10.	Follow the guidelines given by IBM to complete the installation.

11.	When the "Installation Complete" screen appears, press <F3> for Exit without rebooting.

12.	Copy the driver from the Olicom CD-ROM to your default DOS Lan Services directory (for example C:\NET) by inserting the Olicom CD-ROM and entering the following command:

COPY D:\IBM\NDIS.DOS\OCT3XND2.DOS C:\NET

Press <Enter> to continue.

The configuration will become active when the system is re-booted.


IBM DOS LAN Services (DLS) Overview

Suggested Installation Method

Use the IBM install program.

Prerequisites

*	IBM DOS LAN Services disks

*	Olicom CD-ROM or Driver Disk

Driver Installation

See IBM DOS LAN Services (DLS) Details for information on how to install the driver.

Configurable Parameters

Configurable parameters are found in the PROTOCOL.INI file.

See Optimizations for information about recommended performance optimizations in server/workstation environments.

See Runtime Statistics and Status Program for information about the OMACSTAT program. A program that shows MAC driver status and statistics.

Technical Information

Driver type:	NDIS 2.0

Driver name:	OCT3XND2.DOS

Error Messages

See NDIS 2.0 Driver Error Messages.


IBM LAPS - LAN Server/Requester 3.0 Details

This section describes how to install the MAC driver for the RapidFire 314x Adapter.

You can install the adapter driver either while you are installing LAN Adapter and Protocol Support or after you have installed it.

For updated information about RIPL-installation in LAN Server 3.0, contact Olicom Support.

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 <filename> and pressing <Enter>, and then retry the installation.

Installing the Driver while installing LAPS

Install LAN Adapter and Protocol Support (LAPS) by doing the following:

1.	Insert the "IBM Network Transport Services/2, LAN Adapter and Protocol Support" diskette in drive A, and run the LAPS-program (A:\LAPS).

2.	Select "Install" in the LAPS program main menu. The program will now install LAPS on your hard disk.

3.	During the installation, the LAPS program main menu will appear again, but with the "Install", "Configure", "Remove", "Exit" and "Help" options selectable.

4.	Proceed with the installation as described in step 2 of "Installing the Driver after installing LAPS" below.

Installing the Driver after installing 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 CD-ROM and enter:

D:\IBM\NDIS.OS2

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 RapidFire 314x Token-Ring 16/4 PCI Adapter" as your network adapter by adding it to the "Current Configuration". You may now edit the parameters of the Olicom adapter.

8.	Select "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter" in the current configuration list and then "Edit".

9.	Select "OK" when the parameters for the adapter are correct.

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.

The RapidFire 314x Adapter is activated when the system is rebooted.


IBM LAPS - LAN Server/Requester 3.0 Overview

Suggested Installation Method

IBM LAN Server native installation procedure.

Prerequisites

  *	Olicom CD-ROM or Driver Disk

  *	IBM LAN Adapter and Protocol Support program

(LAPS) must be installed

Driver Installation

See IBM LAPS - LAN Server/Requester 3.0 Details for details on how to install the driver.

Configurable Parameters

Configurable parameters are found in the PROTOCOL.INI file.

Technical Information

Driver type:	NDIS 2.0

Driver name:	OCT3XND2.OS2

Error Messages

See NDIS 2.0 Driver Error Messages.


IBM MPTS - LAN Server/Requester 4.0/5.0 Details
IBM MPTS - LAN Server/Requester 4.0/5.0 and OS/2 WARP Details

The MAC driver for the RapidFire 314x Adapter can be installed during or after MPTS (Multi-Protocol Transport Services) installation.

For updated information about RIPL-installation in LAN Server 4.0/5.0, contact Olicom Support.

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 <filename> and pressing <Enter>, and then retry the installation.

Installing the Driver during MPTS Installation

1.	Install MPTS as described by IBM.

2.	During the installation the MPTS main menu is displayed again, but with the "Exit", "Configure", "Install", "Remove", and "Help" options selectable.

3.	Proceed with the installation as described in step 2 below.

Installing the Adapter Driver after MPTS Installation

1.	Start MPTS by double-clicking the MPTS icon in the IBM LAN Services folder or by making \IBMCOM your current directory (by typing "CD \IBMCOM") and type:

MPTS

2.	Select the "Configure" option in the MPTS main menu.

3.	Select "LAN adapters and Protocols" and then "Configure".

4.	Activate the "Other Adapters..." button

5.	Insert the Olicom CD-ROM and enter the path:

D:\IBM\NDIS.OS2

and select "OK".

6.	Select "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter" as your network adapter by adding it to the "Current Configuration".

7.	Edit the parameters of the RapidFire 314x Adapter by first selecting "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter " in the current configuration list and then selecting "Edit".

8.	Select "OK" when the adapter parameters are correct.

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 the instructions given by MPTS to complete the installation.

The RapidFire 314x Adapter is activated when the system is rebooted.


IBM MPTS - LAN Server/Requester 4.0/5.0 Overview
IBM MPTS - LAN Server/Requester 4.0/5.0 and OS/2 WARP Overview

Suggested Installation Method

IBM LAN Server native installation procedure.

Prerequisites

  *	Olicom CD-ROM or Driver Disk

  *	IBM Multi-Protocol Transport Services (MPTS)

must be installed

Driver Installation

See IBM MPTS - LAN Server/Requester 4.0/5.0 and OS/2 WARP Details.

Configurable Parameters

Configurable parameters are found in the PROTOCOL.INI file.

Technical Information

Driver type:	NDIS 2.0

Driver name:	OCT3XND2.OS2

Error Messages

See NDIS 2.0 Driver Error Messages.


IBM-based Systems

Whenever possible, you should use the driver installation utility that came with your Network Operating System.

We recommend that you consult your Network Operating System documentation, but you can use the following sections as guides for your adapter driver installation.

For information about how to install network drivers in an IBM environment, please select one of the following:

IBM DOS LAN Services

IBM LAPS - LAN Server/Requester 3.0

IBM MPTS - LAN Server/Requester 4.0/5.0 and OS/2 WARP


Installation Overview

There are two steps to installing the Olicom adapter:

1.	Install the adapter and connect the cables in the PC.

2.	Install the required network drivers.

During the installation the following material may be useful:

  *	The CD-ROM or the disks came with the RapidFire 314x Adapter.

  *	The manual(s) that came with your computer

  *	The manual(s) that came with your Operating System

  *	The manual(s) that came with your Network Operating System (NetWare, Windows NT, etc.)

Using CD-ROM or Disks

Olicom supplies both a CD-ROM and two 3.5" high-density disks.

If you have a CD-ROM drive, you should always use the Olicom CD-ROM when installing network drivers and utilities, or when you want to view the documentation for the adapter.

If you want to use the Diagnostics program, you must always use the Olicom Setup and Diagnostics Disk. See also Adapter Diagnostics Program

Olicom CD-ROM

The Olicom CD-ROM disc contains:

  *	LANscout - Olicom desktop management system for Windows 95/98 and Windows NT

  *	AIW - Olicom Adapter Information for Windows utility for Windows 3.1x

  *	DMI 1/DMI 2 - Desktop Management Interface for third-party management applications

  *	Olicom Adapter Setup Program

  *	Guide to Operation in PDF format incl. a free version of Adobe Acrobat Reader

  *	Online documentation in HTML format (requires a web browser)

  *	Make-disk utility for the following disks:

Olicom NetWare Server and Client 32 Driver Disk

Olicom Windows 95/98 Driver Disk

Olicom Windows NT Driver Disk

Olicom OS/2 Driver Disk

Olicom DOS Driver Disk

Olicom Setup and Diagnostics Disk (Disk 1)

Olicom Driver Disk (Disk 2)

All network drivers are contained on the CD-ROM.

The Olicom Adapter Setup Program on the CD-ROM runs both under DOS, Windows 3.x, Windows 95 and Windows NT. See Olicom Adapter Setup Program on Setup Disk or Olicom Adapter Setup Program on CD-ROM for details.

Note:

The Olicom LANscout desktop management system can only be installed from the CD-ROM.

Olicom Disks

The Olicom disks are:

  *	Olicom Setup and Diagnostics Disk (Disk 1) containing Olicom Adapter Setup Program, Diagnostics Program, utilities and online documentation in Windows help format.

  *	Olicom Driver Disk (Disk 2) containing most commonly-used network drivers.

The Olicom Adapter Setup Program on the Setup and Diagnostics Disk gives you access to the online documentation and allows you to install some of the utilities that come with the adapter. If you want to install other utilities, such as LANscout and DMI, you must use the CD-ROM.

The Olicom Driver Disk contains the most commonly-used network drivers, whereas all the network drivers can be found on the Olicom CD-ROM.


Installing the Network Adapter

Installation of the network adapter and cables varies from computer to computer. If in doubt, consult the documentation that came with your computer.

Important:

Static electricity can be destructive to sensitive components on the adapter. Discharge yourself by touching a metal part of a grounded unit before removing the adapter from the plastic container.

Adapter Installation

1.	Switch all computer components off and disconnect all power supply cables.

2.	Move the peripheral units (keyboard, monitor, etc.) away from the computer, and position the computer for easy access to the back panel.

3.	Remove the top cover of the computer and select one of the free PCI slots.

4.	Remove the screw from the top of the panel which holds the metal bracket on the back panel corresponding to the selected slot.

5.	Tilt the adapter to let the interface connector slip through the opening in the back panel then press the edge connector firmly into the selected expansion slot.

6.	Secure the adapter with the screw from the previously removed metal bracket.

7.	If the computer supports Wake-on-LAN (which makes it possible to remotely wake up a PC for management purposes), connect the special Wake-on-LAN cable between the PC motherboard and the the RapidFire 314x Adapter.

See the computer user guide for further details.

8.	Replace the computer top cover.

Connecting the Network Cable

1.	UTP Media Cabling (category 5)

Insert the modular jack in the RJ-45 connector. The jack is secured and correctly inserted when you hear a click.

STP Media Cabling (type 1 and 6)

Connect the adapter cable to the STP media connector and tighten the screws.

Fiber Media Cabling (type ST)

Remove the protection caps, connect the adapter RX connector to the switch TX port, and connect the adapter TX connector to the switch RX port.

Note:

Make absolutely sure that you connect the adapter cable to the adapter you have just installed. Connecting the cable to any other expansion card than the RapidFire 314x Adapter could result in serious damage to the expansion card and/or the Token-Ring network.

2.	Connect the other end of the UTP, STP or fiber cable to the Token-Ring network.

3.	Make sure that the PC is turned off, then re-connect the power supply cable and switch power on.

Connecting a Wake-on-LAN Cable (optional)

The RapidFire 314x Adapter supports Wake-on-LAN by using Auxilliary Power Supply and External Wake Signal.

If you want to use this feature, and the PC supports Wake-on-LAN (see the PC user documentation), you must connect a Wake-on-LAN cable between the RapidFire 314x Adapter and the PC motherboard.

IMPORTANT:

Ensure that the PC is unplugged from the electrical outlet before installing or removing the Wake-on-LAN cable. Most PCs with Wake-on-LAN support supply power through this cable even when the system appears to be in powered OFF state.

1.	Locate the Wake-on-LAN connectors.

The Wake-on-LAN connector on the 314x is the white 3-pin connector located just below the expansion PROM socket.

The Wake-on-LAN connector in the PC is identical to the connector on the RapidFire 314x Adapter (and maybe marked "Wake-on-LAN" or something similar). The connector is usually located on the PC motherboard, but on some systems you will find it on a riser card (a riser card is a board plugged into the motherboard to provide the necessary expansion slots).

2.	Connect the Wake-on-LAN cable.

The Wake-on-LAN cable connectors are identical, and they are coded to ensure that they are not inserted upside down.

Note:

On early IBM PCs with Wake-on-LAN support, the Auxilliary Power Supply and External Wake Signal use two different cables. In that case you need a special cable to connect the RapidFire 314x Adapter. Such a cable is not included in the RapidFire 314x Adapter package.
The special cable has a 3-pin connector that connects to the adapter and two 2-pin connectors that matches the IBM connector. On your IBM PC, locate the power supply and look for a power cable labelled P9 or P12. This cable fits one of the 2-pin connectors of the special RapidFire 314x Adapter cable. The second 2-pin connector of the cable must be connected to the 2-pin Wake-on-LAN connector on the PC motherboard.


LANscout

The Olicom LANscout desktop management system provides from a single workstation essential information about all Olicom adapters in the network.

LANscout has two components: LANscout Agent and LANscout Manager.

LANscout Agent must be installed on all managed workstations. It collects  extensive information about the adapter and drivers, and formats them into a HTML page which can be viewed from a web browser anywhere on the network. LANscout Agents also reports back to LANscout Manager.

LANscout Manager can be installed anywhere on the network. It collects and displays statistics from each LANscout Agent.

Furthermore LANscout can compare installed driver versions (using a web browser) against the latest drivers downloadable from Olicom’s web site. If newer drivers exist, you have the option to download them immediately.

LANscout Manager includes extensive context-sensitive help which is displayed by pressing <F1>.

If  reporting problems to Olicom Technical Support, always include an LANscout report which can be generated by pressing <F3>.

System Requirements

  *	Microsoft Windows 95/98 or Windows NT

  *	WinSock 1 (TCP/IP) installed

  *	Display resolution: 800x600 or higher is recommended

  *	Display colors: 65536 (16 bit) or higher is recommended

  *	An Olicom Windows 95/98 or Windows NT driver:

OCT3XND3.SYS (NDIS 3 Miniport driver)

Installing LANscout

Note:

LANscout can only be installed from the CD-ROM.

1.	Insert the CD-ROM.

If the AutoPlay feature is enabled for your CD-ROM drive, a menu will popup.

If not, run SETUP.EXE from the CD-ROM (D:\SETUP.EXE)

2.	Select "Launch the Setup program" from the menu and follow the instructions to install LANscout.

The installation process creates a new program group in which the LANscout icons are located.

Running LANscout

By default LANscout Agent is placed in the startup folder. That will start LANscout Agent each time you start Windows. Furthermore, LANscout Agent is started after the installation is completed.

When LANscout is running, an icon appears in the system tray (the right side of the task bar).

Right-clicking on the LANscout icon will bring up a pop-up menu from which LANscout Manager and LANscout Web can be started. Configuration of the LANscout Agent can also be started from the menu.

If LANscout Agent is not started, choose "Olicom Applications" from the "Start/ Program Files" menu to start the LANscout applications.


Late-Breaking News

None


MAC Driver Error Codes - NDIS 2.0 Environments

This text describes the possible error codes from the OCT3XND2 NDIS drivers during driver initialization or opening of the Token-Ring adapter.

The error codes may appear in two places:

1)	As error code in the message 361:

    PCI 16/4   361E MAC Driver not Installed -

    Adapter initialization error, CC=

2)	As Diagnostics Result in the Configuration Status Display from the OMACSTAT utility.

Network Interface Card Reset Errors

Indicate a network card self-test error during card reset.

F100    Initial test error

F101    Adapter ROM CRC error

F102    Adapter RAM error

F103    Instruction test error

F104    Context/interrupt test error

F105    Protocol handler hardware error

F106    System interface register error

F107    Driver failed to attach to PCMCIA Card Services

F108    Driver failed to register as a client to PCMCIA Card Services

Network Interface Card Initialization Errors

Indicate a network card self-test error during card initialization.

F200    Timeout waiting for initialization to finish

F201    Invalid initialization block

F202    Invalid options

F203    Invalid receive burst count

F204    Invalid transmit burst count

F205    Invalid DMA abort threshold

F206    Invalid SCB

F207    Invalid SSB

F208    DIO parity error

F209    DMA timeout

F20A    DMA parity error

F20B    DMA bus error

F20C    DMA data compare error

F20D    Unrecoverable hardware error

F2FF    DMA test pattern error

Network Interface Card Open Errors

Indicate a problem with the opening of the network card. If the error code has the form F3xy, x indicates the open phase, and y specifies the error type. These errors will not occur during driver initialization. They may, however, be displayed as Diagnostics Result by the OMACSTAT utility. They will typically result in problems during Netbind or start of LAN Manager Workstation.

F31?    Lobe media test

F32?    Physical insertion

F33?    Address verification

F34?    Participation in ring poll

F35?    Request initialization

F3?1    Function failure

F3?2    Signal loss

F3?5    Time out

F3?6    Ring failure

F3?7    Ring beaconing

F3?8    Duplicate node address

F3?9    Request parameters

F3?A    Remove received

Error F311 will typically indicate problems with the cable between PC and MAU, while F327 typically indicates that the network card has the wrong speed for the ring.

F408    Adapter RAM configuration error

F440    Error in burned-in or configured node address

Network Interface Card Download Errors

Indicate problems during the initial adapter download.

F700    Adapter download failed

F7B1    Adapter ROM CRC error

F7B2    Adapter RAM error

F7B3    Instruction test error

F7B4    Context/interrupt test error

F7B5    Protocol handler hardware error

F7B6    System interface register error

Fatal Ring Status

Indicates that a fatal ring status has been detected.

F801    Remove command received from Network Management.

F804    Adapter detected internal error and removed itself.

F808    Lobe wire fault


Microsoft Windows 95 Details

The RapidFire 314x Adapter may be installed after Windows 95 has been installed or while Windows 95 is being installed.

Proceed to Driver Installation - During Windows 95 Installation or Driver Installation - After Windows 95 Installation as required.

Driver Installation - During Windows 95 Installation

1.	Install your RapidFire 314x Adapter in a free PCI expansion slot as described in Installing the Network Adapter.

Note:

Do not add the adapter driver manually during installation of Windows 95. The adapter(s) will be detected automatically.

2.	Install Windows 95.

3.	When Windows 95 has been installed, go to the Control panel by selecting "Start", "Settings" and "Control Panel".

4.	Start the System Manager by clicking the "System" icon.

5.	Select the "Device Manager" tab, locate "Other Devices" and look for "PCI Token Ring Controller".

6.	Select the "PCI Token Ring Controller", click the "Remove" button, and click the "Yes" to confirm device removal.

7.	If prompted, restart the PC so Windows 95 can locate the RapidFire 314x Adapter.

If you are not prompted, restart the PC by selecting "Start" and "Shut Down" and clicking "Yes".

8.	Proceed to step 2 in the "Driver Installation - After Windows 95 Installation" section and follow the steps to complete the installation.

Driver Installation - After Windows 95 Installation

1.	Install your RapidFire 314x Adapter in a free PCI expansion slot as described in Installing the Network Adapter.

2.	When starting Windows 95 the next time, a popup window will appear notifying that Windows 95 has found new hardware.

3.	Insert the Olicom CD-ROM and change the path from "A:\" into "D:\".

4.	Press <Enter> at each dialog box displayed by Windows 95 to complete the installation.

5.	Restart Windows 95 for the changes to take effect.

Note:

If you want to change or configure the default protocol and client (TCP/IP and Client for Microsoft Networks), open the Network Control Panel and make these changes before restarting Windows.

Note:

NetWare Client 32 for Windows 95 is described in NetWare Client 32 for Windows 95.

Wake-on-LAN Activation

If the computer has support for Wake-on-LAN (see also Installing the Network Adapter), the RapidFire 314x Adapter driver must be configured for this purpose.

1.	Open "Network" in the "Control Panel", select "Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter", click the "Properties" button and the "Advanced" tab.

2.	Select the "Wake-on-LAN" parameter, change the setting to "Enabled" and restart the computer.

Note:

Once Wake-on-LAN has been enabled, the RapidFire 314x Adapter will remain inserted on the network after Windows has been closed down and the computer appears to be off.

Adapter Parameters

To configure the network adapter, open Network in the Control Panel, select the "Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter" and click the Properties button. Click the Advanced tab to set the adapter parameters.

The following parameters can be modified:

Wake-on-LAN

When enabled, the adapter remains on the ring even when Windows 95 is closed.

Early Token Release

Selects the early token release feature. This parameter has only effect, when running 16 Mbps.

This parameter has no effect, when the adapter is in Full Duplex mode. In Full Duplex mode the driver always runs as if the parameter was set to "Yes".

Frame Status

When set to "Yes", normal transmit verification is performed, and the upper layer drivers will be notified about the status of the transmitted frame, that is whether the destination address has been recognized and the frame has been copied by the receiving station. When this value is "No", all transmitted frames are assumed both recognized and copied by another station on the ring. If you have a bridge/router in your network, or discover abnormal network behaviour, this value should be set to "Yes".

Network Address

If this entry is specified, the specified value will be used in place of the universal burned-in node address on the adapter card. Note that the entered address must be administered locally. It can be entered as "XX-XX-XX-XX-XX-XX" or "XXXXXXXXXXXX". For example as "40-00-12-34-56-78" or "400012345678".

Ring Speed

If appropriate, use this parameter to override the value stored on the adapter. The ring speed can be forced to 4, 16 Mbps or adapter setting.

Default is Auto (auto sense).

Maximum Frame Size

Specifies the largest frame the adapter is capable of transmitting or receiving. Values from 512 to 18,000 bytes are accepted.

Default is 4540.

Transmit Buffers

Determines the number of allocated transmit buffers in the system memory. Values from 8 to 64 are accepted.

Default is Auto (auto adjusting).

Receive Buffers

Determines the number of allocated receive buffers in the system memory. Values from 8 to 128 are accepted.

Default is Auto (auto adjusting).


Microsoft Windows 95 Overview

Suggested Installation Method

Windows 95 will automatically install the driver for the Olicom adapter.

Prerequisites

    *	Olicom CD-ROM or Driver Disk

    *	Microsoft Windows 95 installation CD-ROM

Driver Installation

See Microsoft Windows 95 Details.

Configurable Parameters

Configurable parameters for the NDIS 2.0 driver are found in the PROTOCOL.INI file.

Configurable parameters for the NDIS 3 driver are in Adapter Parameters.

Technical Information

Driver type:	NDIS 2.0 or NDIS 3 Miniport

Driver name:	OCT3XND2.DOS	(NDIS 2.0)

      	OCT3XND3.SYS	(NDIS 3 Miniport)

Error Messages

Error information is available for:

NDIS 2.0 Drivers

NDIS 3 Drivers


Microsoft Windows 98 Details

The RapidFire 314x Adapter may be installed after Windows 98 has been installed or while Windows 98 is being installed.

Proceed to Driver Installation - During Windows 98 Installation or Driver Installation - After Windows 98 Installation as required.

Driver Installation - During Windows 98 Installation

1.	Install your RapidFire 314x Adapter in a free PCI expansion slot as described in Installing the Network Adapter.

Note:

Do not add the adapter driver manually during installation of Windows 98. The adapter(s) will be detected automatically.

2.	Install Windows 98.

3.	When Windows 98 has been installed, go to the Control panel by selecting "Start", "Settings" and "Control Panel".

4.	Start the System Manager by clicking the "System" icon.

5.	Select the "Device Manager" tab, locate "Other Devices" and look for "PCI Token Ring Controller".

6.	Select the "PCI Token Ring Controller", click the "Remove" button, and click the "Yes" to confirm device removal.

7.	If prompted, restart the PC so Windows 98 can locate the RapidFire 314x Adapter.

If you are not prompted, restart the PC by selecting "Start" and "Shotdown" and clicking "Yes".

8.	Proceed to step 2 in the "Driver Installation - After Windows 98 Installation" section and follow the steps to complete the installation.

Driver Installation - After Windows 98 Installation

1.	Install the RapidFire 314x Adapter in a free PCI expansion slot as described in Installing the Network Adapter.

2.	When starting the next time, the "Add New Hardware Wizard" pops up saying that it is searching for new drivers for a PCI Token-Ring controller.

3.	Click "Next" and the Wizard asks what you want Windows to do.

4.	Click "Next" once again to accept a search for the best driver for your device. Apart from the Windows driver library, the Wizard now allows searching alternative locations for a driver.

5.	Insert the Olicom CD-ROM, ensure that the CD-ROM drive is checked, and then click "Next".

Windows then searches the specified locations and eventually states that it has found an updated driver for this device.

6.	Follow the instructions given by Windows and the driver will be installed and started.

Note:

If you want to change or configure the default protocol and client (TCP/IP and Client for Microsoft Networks), open the Network Control Panel and make these changes before restarting Windows.

Wake-on-LAN Activation

If the computer has support for Wake-on-LAN (see also Installing the Network Adapter), the RapidFire 314x Adapter driver must be configured for this purpose.

1.	Open "Network" in the "Control Panel", select "Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter", click the "Properties" button and the "Advanced" tab.

2.	Select the "Wake-on-LAN" parameter, change the setting to "Enabled" and restart the computer.

Note:

Once Wake-on-LAN has been enabled, the RapidFire 314x Adapter will remain inserted on the network after Windows has been closed down and the computer appears to be off.

Adapter Parameters

To configure the network adapter, open Network in the Control Panel, select "Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter" and click the Properties button. Click the Advanced tab to set the adapter parameters.

The following parameters can be modified:

Wake-on-LAN

When enabled, the adapter remains on the ring even when Windows 98 is closed.

Early Token Release

Selects the early token release feature. This parameter has only effect, when running 16 Mbps.

This parameter has no effect, when the adapter is in Full Duplex mode. In Full Duplex mode the driver always runs as if the parameter was set to "Yes".

Frame Status

When set to "Yes", normal transmit verification is performed, and the upper layer drivers will be notified about the status of the transmitted frame, that is whether the destination address has been recognized and the frame has been copied by the receiving station. When this value is "No", all transmitted frames are assumed both recognized and copied by another station on the ring. If you have a bridge/router in your network, or discover abnormal network behaviour, this value should be set to "Yes".

Network Address

If this entry is specified, the specified value will be used in place of the universal burned-in node address on the adapter card. Note that the entered address must be administered locally. It can be entered as "XX-XX-XX-XX-XX-XX" or "XXXXXXXXXXXX". For example as "40-00-12-34-56-78" or "400012345678".

Ring Speed

If appropriate, use this parameter to override the value stored on the adapter. The ring speed can be forced to 4, 16 Mbps or adapter setting..

Default is Auto (auto sense).

Maximum Frame Size

Specifies the largest frame the adapter is capable of transmitting or receiving. Values from 512 to 18,000 bytes are accepted.

Default is 4540.

Transmit Buffers

Determines the number of allocated transmit buffers in the system memory. Values from 8 to 64 are accepted.

Default is Auto (auto adjusting).

Receive Buffers

Determines the number of allocated receive buffers in the system memory. Values from 8 to 128 are accepted.

Default is Auto (auto adjusting).


Microsoft Windows 98 Overview

Suggested Installation Method

Windows 98 will automatically install the driver for the Olicom adapter.

Prerequisites

    *	Olicom CD-ROM or Driver Disk

    *	Microsoft Windows 98 installation CD-ROM

Driver Installation

See Microsoft Windows 98 Details.

Configurable Parameters

Configurable parameters for the NDIS 2.0 driver are found in the PROTOCOL.INI file.

Configurable parameters for the NDIS 3 driver are in Adapter Parameters.

Technical Information

Driver type:	NDIS 2.0 or NDIS 3 Miniport

Driver name:	OCT3XND2.DOS	(NDIS 2.0)

      	OCT3XND3.SYS	(NDIS 3 Miniport)

Error Messages

Error information is available for:

NDIS 2.0 Drivers

NDIS 3 Drivers


Microsoft Windows NT Installation

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 Miniport driver, you may find it convenient to have the Windows NT System Guide at hand. See the "Configuring the Network" and "Installing Windows NT" sections prior to installation.

The installation procedure described below will copy all necessary setup 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. See also Adapter Parameters.

Installation Procedure

The installation procedure for the NDIS 3 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 NT 4.0" or "Adding Adapter - Windows 3.51".

Depending on your Windows NT version, proceed to:

Driver Installation during Windows NT 4.0 Installation

or

Driver Installation during Windows NT 3.51 Installation

Driver Installation during Windows NT 4.0 Installation

1.	Install the RapidFire 314x Adapter in a free expansion slot as described in Installing the Network Adapter.

2.	Follow the instructions in the Windows NT System Guide to begin the Windows NT 4.0 installation.

3.	If you have chosen custom setup, do not start the adapter search in the "Network Setup Wizard" dialog box. Choose instead "Select from list".

4.	Click the "Have Disk..." button, and enter the full path to the Olicom setup files. If you are installing from the Olicom CD-ROM, enter "D:\".

5.	Confirm choice by selecting proper adapter type and press the "OK" button.

6.	Click the "Next" button (even if you have more than one RapidFire 314x Adapter installed).

7.	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 secondly enter the path to the Olicom setup files (same path as entered under step 4).

8.	Follow the Network Setup Wizard to finish the installation.

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 required to add, configure and remove network adapters.

1.	Install the RapidFire 314x Adapter in a free expansion slot as described in Installing the Network Adapter.

2.	Select the Control Panel under Settings, select the Network icon and choose the "Adapters" tab and click the "Add..." button.

3.	Click the "Have Disk..." button, and enter the full path to the Olicom setup files. If you are installing from the Olicom CD-ROM, enter "D:\".

4.	Confirm choice by selecting proper adapter type and press the "OK" button.

5.	Click the "Close" button in the Network dialog box when all adapters have been added.

6.	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.

Note:

If the system is already using an adapter of the same type (and the driver on the Olicom CD-ROM is newer than the driver currently on the system), the driver has to be updated manually. See the next steps to accomplish this.

1.	Select "Network" from the Control Panel.

2.	Select the "Adapters" tab.

3.	Select the RapidFire 314x Adapter and press the "Update" button.

4.	Enter the full path to the Olicom setup files. When installing from the Olicom CD-ROM, enter "D:\".

5.	The settings will not be effective until the system is restarted. System restart can be initiated by selecting the "Yes" option in the dialog box shown when you close the Network setup panel.

Driver Installation during Windows NT 3.51 Installation

1.	Install the RapidFire 314x Adapter in a free expansion slot as described in Installing the Network Adapter.

2.	Follow the instructions in the Windows NT System Guide to begin Windows NT installation.

3.	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.

4.	When the message "Set-up did not detect a network card" displays, select "Continue" to go to the adapter card set-up phase.

5.	Continue with step 3 in the "Adding adapter" section below.

Adding Adapter - Windows NT 3.51

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.	Install the RapidFire 314x Adapter in a free expansion slot as described in Installing the Network Adapter.

2.	Select the Control Panel in the Main window, select the Network icon and choose the "Add adapter" button in the Network Settings panel.

3.	In the list of Network Adapter Cards, select "<Other> Requires disk from manufacturer" and press the "Continue" button.

4.	Enter the full path to the set-up files for the desired adapter type. If you are installing from the Olicom CD-ROM, enter "D:\".

5.	Confirm choice, by selecting proper adapter type and press the "OK" button.

The Setup program now copies installation files to your harddisk.

6.	You may wish to review the binding settings by selecting the "Bindings" button. Press "OK" to return from the Network Bindings windows.

7.	Select the "OK" button in the Network control panel, when all adapters have been added.

8.	The settings will not take effect, until the system is restarted. System restart can be initiated by selecting the "Restart Now" option in the dialog box shown when you exit the Network Control Panel.

Note:

If the system is already using an adapter of the same type (and the driver on the Olicom CD-ROM is newer than the driver currently on the system), the driver has to be updated manually. See the next steps to accomplish this.

1.	Select "Network" from the Control Panel.

2.	Select the RapidFire 314x Adapter and press the "Update" button.

3.	Enter the full path to the Olicom setup files. When installing from the Olicom CD-ROM, enter "D:\".

4.	The settings will not be effective until the system is restarted. System restart can be initiated by selecting the "Restart Now" option in the dialog box shown when you close the Network setup panel.

Wake-on-LAN Activation

If the computer has support for Wake-on-LAN (see also Installing the Network Adapter), the RapidFire 314x Adapter driver must be configured for this purpose.

1.	Open "Network" in the "Control Panel", select the "Adapters" tab, select "Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter" and click the "Properties" button.

2.	Select the "Wake-on-LAN" parameter, change the setting to "Enabled" and restart the computer.

Note:

Once Wake-on-LAN has been enabled, the RapidFire 314x Adapter will remain inserted on the network after Windows has been closed down and the computer appears to be off.

Adapter Parameters/Properties

When configuring an adapter, the following parameters can be modified:

Wake-on-LAN

When enabled, the adapter remains on the ring even when Windows NT is closed.

Early Token Release

Selects the early token release feature. This parameter has only effect, when running 16 Mbps.

This parameter has no effect, when the adapter is in Full Duplex mode where the driver always runs as if the parameter was set to "Yes".

Frame Status

When set to "Yes", normal transmit verification is performed, and the upper layer drivers will be notified about the status of the transmitted frame, that is whether the destination address has been recognized and the frame has been copied by the receiving station. When this value is "No", all transmitted frames are assumed both recognized and copied by another station on the ring. If you have a bridge/router in your network, or discover abnormal network behaviour, this value should be set to "Yes".

Network Address

If this entry is specified, the specified value will be used in place of the universal burned-in node address on the adapter card. Note that the entered address must be administered locally. It can be entered as "XX-XX-XX-XX-XX-XX" or "XXXXXXXXXXXX". For example as "40-00-12-34-56-78" or "400012345678".

Ring Speed

If appropriate, use this parameter to override the value stored on the adapter. The ring speed can be forced to 4, 16 Mbps or adapter setting.

Default is Auto (auto sense).

Maximum Frame Size

Specifies the largest frame the adapter is capable of transmitting or receiving. Values from 512 to 18,000 bytes are accepted.

Default is 4540.

Transmit Buffers

Determines the number of allocated transmit buffers in the system memory. Values from 8 to 64 are accepted.

Default is Auto (auto adjusting).

Receive Buffers

Determines the number of allocated receive buffers in the system memory. Values from 8 to 128 are accepted.

Default is Auto (auto adjusting).


Microsoft Windows NT Overview

Suggested Installation Method

Windows NT native installation procedure.

If you want to perform an unattended setup for Windows NT, proceed to Unattended Setup for Windows NT.

Prerequisites

    *	Olicom CD-ROM or Driver Disk

Driver Installation

Install the adapter driver either while installing Windows NT or after installing it. See Microsoft Windows NT Installation for details

Technical Information

Driver type:	NDIS 3 Miniport

Driver name:	OCT3XND3.SYS

Error Messages

See NDIS 3 Miniport Driver Error Messages.


Microsoft Windows for Workgroups 3.11 NDIS Installation

This topic describes the procedure for installation in Windows for Workgroups Version 3.11.

1.	Install the RapidFire 314x Adapter in a free expansion slot as described in Installing the Network Adapter.

2.	Open the "Network" window by double-clicking the Network icon and then select the "Network Setup" icon.

3.	Click "Networks..." in the "Network Setup" panel and select "Install Microsoft Windows Network".

4.	Make sure "No additional network" is selected, click "OK" (or press Enter) and select "Drivers...".

5.	Click "Add Adapter..." in the "Network Drivers" panel, highlight the "Unlisted or Updated Network Adapter" choice and click "OK".

6.	The setup program prompts for a vendor-provided network driver disk. Insert the Olicom CD-ROM and change the path to:

D:\WFW

and click "OK" to continue.

7.	In the "Unlisted or Updated Network Adapter" panel, select the "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter " and select "OK".

8.	Click "Setup..." in the "Network Drivers" panel to inspect or change the options.

9.	In the "Olicom RapidFire 314x Token-Ring 16/4 PCI 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.	Additional network drivers and/or protocols in the "Network Drivers" panel may be added. Select "Close" when done.

12.	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.

13.	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.

14.	Setup may require additional files from the Windows for Workgroups 3.11 distribution disks. Insert these when prompted.

15.	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.

16.	Select "Restart Computer" to make the changes take effect. Save any unsaved information before restarting the system.

NDIS Driver Configuration

To view or change the adapter parameter settings for the Olicom driver, do the following:

1.	Select the "Network Setup" icon from the Network Window.

2.	Select the "Drivers..." button.

3.	Highlight the adapter you wish to review.

4.	Press the "Setup..." button.

5.	Highlight the adapter parameter you wish to review.  The value is displayed in the box below the "Advanced Network Adapter Settings" box.

6.	If you need to change a setting, enter the new value in the "Value" field for the proper parameter.

7.	Press the "Set" button to accept the setting.

8.	When all parameters have been set correctly, press the "OK" button. Press the "OK" button in the "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter" panel to return to the "Network Drivers" panel.

9.	Press "Close" to exit the drivers panel.

10.	Selecting "OK" in the "Network Setup" panel will create a new set of network files, i.e. PROTOCOL.INI, SYSTEM.INI etc. Press "OK". The changes will take effect when you restart your computer.

NDIS Parameters

The following parameters are used in the drivers.

Adapter ID

Disable NDIS 2.02 support

Early Token Release

Maximum FrameSize

Maximum General Requests

Maximum Transmits

Net Address

Receive Buffer Count

Receive Buffer Size

ReOpen adapter on lobe fault

Ring Speed

Click here for a description of the parameters.


Microsoft Windows for Workgroups 3.11 Overview

Suggested Installation Method

Use Windows for Workgroups' native installation procedure.

Prerequisites

    *	Olicom CD-ROM or Driver Disk

    *	Windows for Workgroups 3.11 must be installed

    *	Windows for Workgroups installation diskettes

Driver Installation

See Microsoft Windows for Workgroups 3.11 NDIS Installation.

Configurable Parameters

Configurable parameters for the NDIS driver are found in the PROTOCOL.INI file.

Technical Information

Driver type:	NDIS 2.0

Driver name:	OCT3XND2.DOS

Error Messages

See NDIS 2.0 Driver Error Messages.


Microsoft-based systems

Whenever possible, you should use the driver installation utility that came with your Network Operating System. We recommend that you consult your Network Operating System documentation, but you can use the following sections as guides for your adapter driver installation.

For information about how to install network drivers in a Microsoft environment, select one of the following:

Windows 95

Windows 98

Windows NT

Windows for Workgroups 3.11

Unattended Setup for Windows NT


NDIS 2.0 Driver Error Messages

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 received on OS/2 based systems. The MAC driver was not able to allocate the needed 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 precede the device= ...\OCT3XND2.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, for example 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, for example C:\LANMAN\DRIVERS\TOKENRNG\OCT3XND2.

344W	MAC Configuration Error - Unknown keyword, Keyw:

Action:  The OCT3XN section of PROTOCOL.INI contains an unknown keyword. The keyword in question is the number indicated by Keyw counted from the start of the OCT3XN section. Check the keyword for spelling errors.

345W	MAC Configuration Error - Parameter out of Range, Keyw:

Action:  A keyword in the OCT3XN 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 OCT3XN 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 OCT3XN 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 OCT3XN section. Assign the missing values.

347W	MAC Configuration Error - Too Many Parameters, Keyw:

Action:  A keyword in the OCT3XN 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 OCT3XN section. Correct the keyword assignment.

348W	MAC Configuration Error - Illegal Parameter Type, Keyw:

Action:  A keyword in the OCT3XN 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 OCT3XN 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=OCT3XN$".  See Configuring the NDIS 2.0 MAC Driver and Multiple Adapter Configuration  for further information.

350E	MAC Driver not Installed - Dynamic data overflow, CC=

Action:  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 Olicom Technical Support.

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 default 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 available.

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:  See MAC Driver Error Codes - NDIS 2.0 Environments for details.


NDIS 3 Driver Error Messages

The NDIS 3 error messages reported under Microsoft Windows 95/98 and Microsoft Windows NT are identical. However, the way the errors are reported to the user differs.

Windows 95/98

In Windows 95/98 error codes reported by NDIS 3 drivers are written to the NDISLOG.TXT file located in your Windows directory.

An example of an error message reported by the driver could be:

Olicom RapidFire 3140 Token-Ring 16/4 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/98.

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, you should check if any error messages or warnings are posted by the Miniport driver by using the Event Viewer found in the Administrative Tools window. All error messages and/or warnings posted by the Olicom Miniport driver have the Source field set to "OCT3XND3". System error messages, related to the Olicom Miniport driver, may occur with different source names, such as "Service Control Manager".

The messages are enumerated by the Event field and are described below in Event number order. You can display the message description, by highlighting the message and pressing enter.

If you experience any problems, you should write down the "Event ID", "Source", "Description" and "Data" fields in the "Event Detail" window.

NDIS 3 Driver Error Messages

For each of the following error messages the first line contains the error code used by Windows 95/98. The second line contains the "Event ID" and "Data" fields used by Windows NT.

Olicom-defined Error Messages and Actions

Code	Description

1	Unknown error code

1	Bring-up diagnostics failed.

Action: The adapter failed during the bring-up diagnostics. Shut down your system and retry the operation. If the error persist, contact Olicom Technical Support.

2	Unknown error code

2	Adapter initialize failed.

Action: The adapter failed the initialization phase. Shut down your system and retry the operation. If the error persist, contact Olicom Technical Support.

3	Unknown error code

3	The network adapter generated an Adapter Check error.

Action: A serious error occurred on the adapter, causing an Adapter check code to be posted. Restart your system. If the error persist, contact Olicom Technical Support.

4	Unknown error code

4	Could not open network adapter. Ring beaconing. Check network speed settings.

Action: The network speed settings is wrong. Change it and restart you system.

5	Unknown error code

5	Could not open network adapter. Duplicate node address.

Action: A duplicate address has been discovered on the ring. Change your locally administered address as discussed in the "Adapter parameter" section above and restart your system.

6	Unknown error code

6	Could not open network adapter. Request initialization failed.

Action: An error occurred during adapter initialization. Restart your system. If the error persist, contact Olicom Technical Support.

7	Unknown error code

7	Could not open network adapter. 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 network adapter.

Action: The adapter failed to open. Please check cables and connections and retry the operation.

9	Unknown error code

9	Could not download code on the network adapter.

Action: The download operation failed. Contact Olicom Technical Support.

A	Unknown error code

10	Lobe wire fault detected. Please check cable connections.

Action: Check all cables and connections and try another lobe media cable. Retry the operation.

B	Unknown error code

11	The network adapter has failed the lobe wrap test resulting from the beacon auto-removal process and has deinserted from the ring.

Action: The adapter has deinserted from the ring, because the ring was beaconing. Check the network speed settings and cable connections and retry the operation. If the error persist, contact your network administrator.

C	Unknown error code

12	The network adapter 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 network adapter is not supported by this driver.

Action: You have installed a wrong driver for the adapter used.

E	Unknown error code

14	The configuration read from the network adapter is invalid.

Action: A configuration entry is invalid. Use the network control panel to set up proper adapter settings.

F	Unknown error code

15	The network adapter 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.

10	Unknown error code

16	The memory window could not be accessed. Check that no other devices uses the 4K region reserved to access the PC Card CIS through the Memory Window parameter.

Action: Change the Memory Window parameter to a different value.

11	Unknown error code

17	The interrupt specified for the PC Card driver is not supported by the PC Card controller in the system.

Action: Change the interrupt level to a value supported by the PC Card controller.

12	Unknown error code

18	There where no PC Card windows available to retrieve the CIS

The DataBook PC Card controller had no free PC Card Memory Windows to access the CIS.

Action: Remove unneeded PC Card devices and reboot the system. If the error persists, contact your place of purchase.

13	Unknown error code

19	The node address found on the PC Card for driver is invalid.

The node address read from the PC Card is invalid, that is it has either wrong length or it is an invalid node address.

Action: Check that the 4K memory region starting at the address specified by the Memory Window parameter is not in use by other devices. Try using a different memory region by changing the Memory Window parameter. If the error persists, run diagnostics on the PC Card to verify that a correct node address is stored on the PC Card.

14	Unknown error code

20	An error occurred while testing the PC Card found

The driver has found a PC Card in the system, but was unable to access the card correctly.

Action: Check for I/O port conflicts with other adapters in the system. Try changing the Data Size parameter and adding Additional Waitstates for the adapter.

15	Unknown error code

21	The number of receive buffers allocated cannot handle the maximum frame size specified. Maximum frame size has been modified

The specified maximum frame size cannot be set due to limitations on the receive area allocated. Each receive buffer is 2048 bytes long, so the maximum frame size will be adjusted to 2048 * the number of receive buffers allocated.

Action: Increase the number of receive buffers for driver or decrease the maximum frame size for the driver.

17	Unknown error code

23	Could not open network adapter. Speed sense failed

Try restarting your system. If the error persists you should force the ring speed to a fixed value.

18	Unknown error code

24	Could not open network adapter. Insert denied

The network adapter was unable to attach to the network.

Contact your network administrator.

19	Unknown error code

25	Adapter disabled due to multiple severe warnings

The adapter was disabled because several non-fatal errors occurred. Look at the preceding warning messages in the Event Log to determine the source of the problem.

1D	Unknown error code

29	Adapter failed to open because it was the first station to insert to the ring.

If the adapter is the first station to insert to an empty token ring it will not be able to auto sense the ring speed. You can prevent this problem by selecting a fixed ring speed in the Network Control Panel.

Normally you would force the speed setting for stations acting as servers to let these stations determine ring speed for workstations that are usually shut down during non-working hours. In a switched network you should never see this error message.

General Error Messages

For each error message below the first line contains the error code used by Windows 95.

The second line contains the "Event ID" and "Data" fields used by Windows NT.

Code	Description

1388  Resource Conflict

5000  OCT3XND3 : 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  OCT3XND3 : 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 retry the operation.

138A  Hardware failure

5002  OCT3XND3 : 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 retry the operation.

138B  Adapter not found

5003  OCT3XND3 : Could not find an adapter.

Action: The adapter could not be found by the driver. Check I/O base settings and retry the operation.

138C  Interrupt Connect

5004  OCT3XND3 : Could not connect to the interrupt number supplied.

Action: The interrupt is already used by another device. Change the adapter interrupt number and retry the operation.

138D  Driver Failure

5005  OCT3XND3 : Has encountered an internal error and has failed.

Action: An internal error has been discovered. Contact Olicom Technical Support.

138E  Bad Version

5006  OCT3XND3 : The version number is incorrect for this driver.

Action: The driver version is incorrect. Contact Olicom Technical Support.

138F  Time out

5007  OCT3XND3 : Timed out during an operation.

Action: A time-out error occurred. Contact Olicom Technical Support.

1390  Network Address

5008  OCT3XND3 : 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  OCT3XND3 : 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  OCT3XND3 : The adapter has returned an invalid value to the driver.

Action: An internal error has occurred. Contact Olicom Technical Support.

1393  Missing Configuration Parameter

5011  OCT3XND3 : 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  OCT3XND3 : The IO Base Address supplied does not match the jumpers on the adapter.

Action: The adapter could not be found by the driver. Check I/O base settings and retry the operation.

1396  Adapter disabled

5014  OCT3XND3 : The adapter is disabled. The driver cannot open the adapter.

Action: Make sure the start-up 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  OCT3XND3 : There is an I/O port conflict.

Action: The ports used by the driver is already in use by another device. Change the I/O Base address for the adapter.

1398  Port or DMA Conflict

5016  OCT3XND3 : 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  OCT3XND3 : There is a memory conflict at address xx.

Action: The driver and another device could not share the memory.

139A  Interrupt Conflict

5018  OCT3XND3 : There is a interrupt conflict at interrupt number xx.

Action: Change the interrupt selection on the adapter and retry the operation.

139B  DMA Resource Conflict

5019  OCT3XND3 : There is a resource conflict at DMA channel xx.

Action: Change the DMA channel selection on the adapter and retry the operation.


NetWare Client 32 for DOS

This installation requires:

  *	Novell NetWare Client 32 for DOS/Windows 3.1x version 2.20 (or higher) installation disks

  *	Olicom CD-ROM or Driver Disk

Installing the NetWare Client 32 Software

1.	Run the install program on the NetWare Client 32 for DOS/Windows 3.1x installation disks and follow the installation guidelines given by the Novell install program.

See the Novell NetWare installation guide for details.

2.	When prompted for Network Board drivers, select "USER SPECIFIED 32 BIT DRIVER" or "OTHER DRIVERS".

3.	Insert the Olicom CD-ROM and specify the path to the Olicom NetWare Client 32 drivers:

D:\NETWARE\NW4X

4.	Select "Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter" and follow the instructions given by the Novell Setup program to complete the installation.


NetWare Client 32 for Windows 3.1x

This installation requires:

   *	Novell NetWare Client 32 for DOS/Windows 3.1x version 2.20 (or higher) installation disks

   *	Olicom CD-ROM or Driver Disk

Installing the NetWare Client 32 Software

1.	Run the install program on the NetWare Client 32 for DOS/Windows 3.1x installation disks and follow the installation guidelines given by the Novell install program.

See the Novell NetWare installation guide for details.

2.	When prompted for a LAN adapter, select "HAVE DISK".

3.	Insert the Olicom CD-ROM, and specify the path to the Olicom NetWare Client 32 drivers:

D:\NETWARE\NW4X\

and select "Add".

4.	Select the manufacturer "Olicom" and the model "32 bit - Olicom RapidFire 314x Token-Ring 16/4 PCI Adapter (Have Disk)", and follow the instructions given by the Novell Setup program to complete the installation.


NetWare Client 32 for Windows 95

This installation requires:

  -	Novell NetWare Client 32 for Windows 95 version 2.20 (or higher) installation disks

  -	Microsoft Windows 95 CD-ROM

  -	Olicom CD-ROM or Driver Disk

The installation consists of two steps:

1.	Installing the Windows 95 driver

2.	Installing the Netware Client 32 software

Installing the Windows 95 Driver

If your NDIS 3 driver is already installed and running, proceed to Installing the NetWare Client 32 Software. Otherwise install the Windows 95 driver as described under Microsoft Windows 95.

Installing the NetWare Client 32 Software

1.	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.

2.	When you have installed Novell NetWare Client 32, choose "Reboot" to restart the system.

3.	The installation is now completed.

Note:

If your server is located on a network with bridges, you must

enable source routing for the driver to function correctly.

A.	From the Start Menu, select Settings/Control

Panel/Network.

B.	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.


Novell NetWare 3.12 Server Installation

1.	Insert the Olicom CD-ROM and load the following NLMs with the following commands:

LOAD D:\NETWARE\NW312\NBI31X.NLM (see note)

LOAD D:\NETWARE\NW312\MSM31X.NLM

LOAD D:\NETWARE\NW312\TOKENTSM.NLM

Note:

Disregard the warning message that appears. The driver will load.

If the modules are already loaded, make sure that NBI31X.NLM is version 1.50 or higher. This is required by the driver. Use the command "MODULES" to make sure that the modules are loaded and which version they have.

2.	Load the adapter driver with the following commands (substitute appropriate values for "xxx" and "yyy"):

LOAD D:\NETWARE\NW312\OCT3XODI SLOT=xxx

BIND IPX OCT3XODI NET=yyy

3.	With the server now accessible, copy the OCT3XODI.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 3.12 server driver at reboot by inserting the following commands in the server’s AUTOEXEC.NCF file (substitute appropriate values for "xxx" and "yyy"):

LOAD NBI31X.NLM

LOAD MSM31X.NLM

LOAD TOKENTSM.NLM

LOAD OCT3XODI.LAN SLOT=xxx

BIND IPX OCT3XODI.LAN NET=yyy

Hints

A.	In an IPX internal router configuration (a server with two adapters, each connected to a different network), the data transfer rate across the router can be low. This happens if client workstations have CPU speeds equal to or higher than the server. You may be able to increase the data transfer rate by adding the following to STARTUP.NCF:

SET MAXIMUM INTERRUPT EVENTS = 100000

The default setting is 10.

B.	The ring speed can be configured manually. Override the ring speed by adding a speed parameter to the load command in AUTOEXEC.NCF:

LOAD OCT3XODI SLOT=XXX SPEED=AUTO/4/16

By choosing "AUTO" (the default), the adapter auto-detects the speed.

Source-Routing for 3.12 Servers

Source-routing is the method used in Token-Ring networks to determine the route a frame must travel through a multi-ring Local Area Network to reach its destination.

Support for Novell NetWare source-routing gives you access to NetWare services across an IBM compatible source-routing bridge, and expands the NetWare horizon to all the rings in the network.

To ensure flawless source-routing operation all workstations and servers on the network must have the source-routing feature enabled. Failure to enable all units (or disable all units) will lead to inconsistencies in the NetWare router tables resulting in unexpected network behaviour.

1.	Activate the module by entering:

LOAD ROUTE  or

LOAD ROUTE BOARD = <board number>

where <board number> must be specified, if the adapter is not board 1.

2.	Invoke the SYSTEM OPTIONS menu under the INSTALL utility and insert the command from step 1 in the AUTOEXEC.NCF file.


Novell NetWare 3.12 Server Overview

Suggested Installation Method

Manual copying of drivers.

Prerequisites

   *	The NetWare 3.12 operating system must be installed on the server. (See the Novell NetWare Installation manual.)

   *	Olicom CD-ROM or Driver Disk

Driver Installation

See Novell NetWare 3.12 Server Installation for details on how to install the driver.

Technical Information

Driver type: 	ODI

Driver name:	OCT3XODI.LAN

Driver spec.:	3.31

Error Messages

See Novell NetWare Error Messages.


Novell NetWare 4.x Server Details

1.	If the NetWare 4.x server operating system has not been installed already, install it now. As part of the installation process, the INSTALL utility prompts for a LAN driver. Proceed to step 4.

2.	If the server is up, load the INSTALL.NLM utility at the server console.

3.	If you are using NetWare 4.0x, select "Maintenance/Selective Install" and then "LAN driver options".

If you are using NetWare 4.10 or 4.11, select "Driver Options" and then "Configure Network Drivers".

4.	Enter "Select additional driver" and press INS to install an unlisted driver.

5.	Insert the Olicom CD-ROM, press <F3> and set the path to:

D:\NETWARE\NW4X

6.	Press <Enter> and follow the instructions.

Note:

The RapidFire 314x Adapter driver 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 SLOT numbers and awaits user input.

Hints

A.	In an IPX internal router configuration (a server with two adapters, each connected to a different network), the data transfer rate across the router can be low. This happens if client workstations have CPU speeds greater than or equal to the server. You may be able to increase the data transfer rate by adding the following to STARTUP.NCF:

SET MAXIMUM INTERRUPT EVENTS = 100000

The default setting is 10.

B.	Tune to best performance by including the following line in the server’s STARTUP.NCF file:

Set Maximum Physical Receive Packet Size=4202 (or higher)

The ring speed can be configured manually. Override the line speed by adding a speed parameter to the load command in AUTOEXEC.NCF:

LOAD OCT3XODI SLOT=XXX SPEED=AUTO/4/16

By choosing "AUTO" (the default), the adapter auto-detects the speed.

Source-Routing for 4.x Servers

Source-routing is the method used in Token-Ring networks to determine the route a frame must travel through a multi-ring Local Area Network to reach its destination.

Support for Novell NetWare source-routing gives you access to NetWare services across an IBM compatible source-routing bridge, and expands the NetWare horizon to all the rings in the network.

To ensure flawless source-routing operation all workstations and servers on the network must have the source-routing feature enabled. Failure to enable all units (or disable all units) will lead to inconsistencies in the NetWare router tables resulting in unexpected network behaviour.

1.	Activate the module by entering:

LOAD ROUTE  or

LOAD ROUTE BOARD = <board number>

where <board number> must be specified, if the adapter is not board 1.

2.	Invoke the SYSTEM OPTIONS menu under the INSTALL utility and insert the command from step 1 in the AUTOEXEC.NCF file.


Novell NetWare 4.x Server Overview

Suggested Installation Method

Using the NetWare 4.x INSTALL utility

Prerequisites

   *	Olicom CD-ROM or Driver Disk

Driver Installation

See Novell NetWare 4.x Server Installation for information on how to install the driver

Technical Information

Driver Type:	ODI

Driver name:	OCT3XODI.LAN

Driver spec.:	3.31

Error Messages

See Novell NetWare Error Messages.


Novell NetWare Error Messages
Novell NetWare Server ODI and Client 32 Driver Error Messages

This section lists commonly-occuring error return codes between 0211h and F400h.

 #	Message

02yz	An error was detected while inserting 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	Duplicate address

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

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 error on the adapter


Novell NetWare Server

For information about how to install network drivers on a server running Novell NetWare, select one of the following:

NetWare 3.12 server

NetWare 4.x server


Novell NetWare Workstation

For information about how to install network drivers for Novell NetWare on a workstation, select one of the following:

NetWare Client 32 for Windows 95

NetWare Client 32 for Windows 3.1x

NetWare Client 32 for DOS


Novell-based systems

Whenever possible, you should use the driver installation utility that came with your Network Operating System.

We recommend that you consult your Network Operating System documentation, but you can use the following sections as guides for your adapter driver installation.

For information about how to install network drivers in a Novell environment, select one of the following:

Workstation installation

Server installation


Olicom Adapter Setup Program

The Olicom Adapter Setup Program is available both on the Olicom CD-ROM and on the Olicom Setup Disk.

See Olicom Adapter Setup Program on CD-ROM and Olicom Adapter Setup Program on Setup Disk for details.


Olicom Adapter Setup Program on CD-ROM

The Adapter Setup Program on the CD-ROM can be used to install the programs and utilities that come with the adapter. The functionality depends on the environment in which the program is run.

Windows 95/98 and Windows NT

Under Windows 95/98 and Windows NT the Adapter Setup Program can be used to install:

  *	LANscout

  *	Documentation

  *	DMI 2 Instrumentation Code

  *	Windows 95 driver upgrade

DOS and Windows 3.x

From the program you have access to:

Installation Overview

Hardware Configuration

Utility Installation


Olicom Adapter Setup Program on Setup Disk

The Olicom Adapter Setup Program on the Olicom Setup Disk gives you access to the online documentation, hardware configuration, and allows you to install some of the utilities that come with the RapidFire 314x Adapter.

If you want to install LANscout and other utilities like AIW, the Olicom CD-ROM must be used.

The Adapter Setup program can be run both under DOS, Windows 3.x, Windows 95/98 and Windows NT.

DOS

Insert the Olicom Setup Disk and enter:

A:\INSTALL

Windows 3.x, Windows 95/98 and Windows NT

Insert the Olicom Setup Disk and run:

A:\SETUP

From the program you have access to the following:

Installation Overview

Hardware Configuration (only DOS and Windows 3.x)

Utility Installation

Windows 95 Driver Upgrade (only Windows 95)


Olicom Africa

Olicom Africa

6th Floor, Nedbank House

12 Fredman Drive

Sandown

Gauteng 2196

South Africa

Tel: 	(+27) 11 784 8990

Fax:	(+27) 11 784 9090


Olicom Australia

Olicom Australia

Level 6

73-79 Walker Street

North Sydney, NSW 2060

Australia

Tel: 	(+61) 2 9955 1755

Fax:	(+61) 2 9955 8488


Olicom Austria

Olicom Austria

Regus Business Centre GmbH

Mariahilfer Strasse 103/2/1/42a

A-1060  Vienna

Austria

Tel: 	(+43) 1 597 3131-0

Fax:	(+43) 1 597 3131-31


Olicom Benelux

Olicom Benelux

Bolduc Office Centre

Utopialaan 35-N

5232 CD 's-Hertogenbosch

The Netherlands

Tel: 	(+31) 73 6 49 15 46

Fax:	(+31) 73 6 49 15 45


Olicom CD-ROM

Insert the CD-ROM to start the Olicom CD-ROM Menu. If the operating system does not have an AutoPlay function (or it is disabled), run D:\SETUP.EXE.

Note:

If your CD-ROM drive letter is not "D", substitute the correct drive letter.

The menu provides six options:

  *	Launch the Setup Program

  *	View Guide to Operations (PDF)

  *	View Online Documentation (HTML)

  *	Make Install Disks

  *	Install Adobe Acrobat Reader

  *	Exit

Launch the Setup program

This will start the Setup program. For a description on the Setup program see Olicom Adapter Setup Program on CD-ROM.

View Guide to Operations (PDF)

This will display the Guide to Operations. Adobe Acrobat Reader version 3.0 is required to view the PDF file. If you do not have it installed, do so by selecting "Install Adobe Acrobat Reader".

View Online Documentation (HTML)

This will display the online documentation. A web browser is required for viewing the online documentation, for example Netscape Navigator or Microsoft Internet Explorer.

Make Install Disks

Install disks for use on systems without a CD-ROM drive can be generated. This includes a copy of the supplied Setup Diagnostics Disk and Driver Disk, and environment specific install disks for Windows 95/98, Windows NT, Novell, DOS and OS/2.

Install Adobe Acrobat Reader

Installs version 3.0 which is required to view the Guide to Operations manual in PDF format.


Olicom Denmark

Olicom A/S

Nybrovej 114

DK-2800 Lyngby

Denmark

Tel: 	(+45) 45 27 00 00

Fax:	(+45) 45 27 01 01


Olicom France

Olicom France

Immeuble Plein Ouest

177, Avenue G.Clemenceau

F-92000 Nanterre

France

Tel: 	(+33) 01 41 91 17 17

Fax:	(+33) 01 41 91 17 00


Olicom Germany

Olicom Germany

Hessenring 13a

D-64546 Mörfelden

Germany

Tel: 	(+49) 06 105 2892-0

Fax:	(+49) 06 105 2892-10


Olicom Italy

Olicom Italia

Via G. Rasori 13

I-20145 Milano

Italy

Tel:	(+39) 2 4800 3661

Fax:	(+39) 2 4800 5888


Olicom Japan

Olicom Japan

4F, Shin-yokohama Daisan Tosho Bldg.

3-5-9, Shin-yokohama

Kohoku-ku

Yokohama 222-0033

Japan

Tel:	(+81) 45 477 3105

Fax:	(+81) 45 477 3106


Olicom Poland

Olicom Poland Sp. z o.o.

ul. Uphagena 27

80-237 Gdansk

Poland

Tel:	(+48) 58 347 1451

Fax:	(+48) 58 346 1288


Olicom Singapore

Olicom Singapore

152 Beach Road

#11-05 Gateway East

Singapore 189721

Tel: 	(+65) 324 5652

Fax:	(+65) 324 7019


Olicom Spain

Olicom Iberica

Edificio Valrealty, La Florida

C/Basauri, 17 Edif. A 2a

E-28023 Madrid

Spain

Tel: 	(+34) 1 372 9814

Fax:	(+34) 1 372 9645


Olicom Sweden

Olicom Sweden

Kanalvägen 10 C-12, 9 vån

194 61 Uplands Väsby

Sweden

Tel: 	(+46) 8 590 041 94

Fax:	(+46) 8 590 041 10


Olicom Technical Support - Denmark

Hotline Support: 	(+45) 45 27 01 02

Fax Support: 	  	(+45) 45 27 02 40

BBS Service: 	     	(+45) 45 27 01 00

BBS Service - ISDN      	(+45) 45 96 32 48

Internet E-Mail:   	support@olicom.dk

Internet Anonymous FTP:	ftp.olicom.dk

Internet WWW:   	http://www.olicom.dk

Olicom Support WEB	http://www.olicom.dk

     	  	     	     	Select "SERVICES & SUPPORT" from the

main menu to access the area that contains

technical support hints and problem report

form registration.

Select "SOFTWARE" from the main menu to

access the software library.


Olicom Technical Support - USA

Hotline Support: 	1-800-OLICOM-1

     	  	     	     	972 907 4200

Fax Support: 	  	972 671 7524

BBS Service:     	972 422 9644

Internet E-Mail:   	support@olicom.com

Internet Anonymous FTP:	ftp.olicom.com

Internet WWW:   	http://www.olicom.com

Olicom Support WEB	http://www.olicom.dk

  	     	     	Select "SERVICES & SUPPORT" from the

main menu to access the area that contains

technical support hints and problem report

form registration.

Select "SOFTWARE" from the main menu to

access the software library.


Olicom UK

Olicom UK Ltd.

Swan House

Peregrine Business Park

Gomm Road

High Wycombe

Bucks HP13 7DL

United Kingdom

Tel:	(+44) 1494 556 600

Fax:	(+44) 1494 556 616


Olicom USA

Olicom, Inc.

1680 North Prospect Drive

Richardson, Texas 75081

USA

Tel:	1-800-2-OLICOM

Tel:	(+1) 972 907 4600

Fax:	(+1) 972 671 7525

Olicom, Inc.

450 Donald Lynch Boulevard

Marlborough

MA 01752

USA

Tel:	(+1) 508 481 4060

Fax:	(+1) 508 229 5535


Optimizations - IBM NDIS 2.0

This help section describes how to improve performance in DOS workstations and OS/2 servers or workstations.

OS/2 Server or Workstation

The standard PROTOCOL.INI for OS/2 is appropriate for a high-performance file server. If, however, you are using the NETBEUI protocol driver, add the following entry to the [NETBEUI] section of PROTOCOL.INI:

MaxTransmits = 38

as the default value (MaxTransmits = 6) is not adequate for a file server or a workstation with heavy network activity.

In an IBM environment you can change the MaxTransmits parameter of NETBIOS with the Installation/Configuration program (or LAPS).

Pay special attention to the chapters in the IBM LAN Server manuals that describe performance optimizations. Following the guidelines they supply can yield greatly-improved server performance.

See Configuring the NDIS 2.0  MAC Driver for details about the effect of the keyword.

For an Entry Level server you do not need all the resources allocated in PROTOCOL.INI. Save memory by modifying the parameters in the OCT3XN section as follows:

MaxTransmits = 15

RecBufSize = 2032

RecBufCount = 8

In this case do not add the MaxTransmits entry to the NETBEUI section.

The parameters suggested above for an Entry Level server will also be suitable for an OS/2 workstation.

DOS Workstation

The standard PROTOCOL.INI for DOS has a MaxTransmits value of 4. This allows a protocol to transmit 4 frames in a row.

If the MaxTransmits value is changed to 6:

MaxTransmits = 6

about 300 bytes extra memory will be used.

The standard PROTOCOL.INI for DOS has 2 receive-buffers of 4064 bytes each, and a maximum frame size of 4060 bytes. This gives a good performance.

If the receive-buffer configuration is changed to 5 buffers of 508 bytes each, about 8000 bytes of memory will be saved. Enter:

RecBufSize = 508

RecBufCount = 5

The resulting maximum frame size will be 2284 bytes, and this reduction will result in a performance degradation in file transfers between workstation and server. However, for all but the most file-transfer-intensive applications the degradation will be negligible.

In a 386-based workstation, memory managers such as 386MAX or QEMM can be used to load the OCT3XND2 driver (and protocol drivers such as NETBEUI) into high memory.


Runtime Statistics and Status
Runtime Statistics and Status Program

This section describes the runtime statistics and configuration status display utility for OLICOM Token-Ring MAC Drivers. The utility is named OMACSTAT and is located in the \OMACSTAT directory on the Setup Disk or CD-ROM.

The runtime statistics assist the network administrator in monitoring the actual network load including protocol stack overhead, as well as the frequency of a number of transient network errors.

The runtime configuration status display shows a number of configuration parameters as well as the status (open/closed) of the adapter card.

Operation

The statistics support consists of two parts: statistics accumulation and statistics display.

Statistics accumulation is done by the Token-Ring MAC Driver during runtime. The counters may wrap around, if they are not read by the display utility.

The collection of statistics by a MAC driver is required in the "LAN Manager Network Driver Interface Specification 2.0.1". The LAN Manager has, however, no tools for display of MAC Driver statistics.

Statistics display is performed by the OMACSTAT program requesting the statistics counters from the driver via a normal IOCTL driver request. The accumulated adapter error log is also displayed. The adapter error log consists of a number of counters, counting the number of times which specific events have occurred. Upon a "read error log" request the adapter resets the counters. The driver maintains a set of counters accumulating the adapter error log counters. The adapter error log may be read upon request from either a protocol or OMACSTAT.

Statistics Display

The statistics display format is shown below. It is displayed on current output by the operator command:

OMACSTAT

The statistics may be reset by the operator command:

OMACSTAT -r

     OLICOM MAC Driver Runtime Status

     Adapter 0 Statistics:

     Bytes Transmitted:    1877910278

     Bytes Received:       1250246408

     Frames Transmitted:   16608343

     Frames Received:      16063182

     Transmit Interrupts:  15464717

     Receive Interrupts:   14159935

     Out Of Resource:             0

     Transmit ARI Errors:        30

     Transmit FCI Errors:        29

     Free XCB Count:             12

     Packet Filter:               3

     Error Log:

       Line Error:              0

       Burst Error:             0

       ARI_FCI Error:           0

       Transmit Abort Del:      0

       Lost Frame Error:        1

       Congestion Error:        0

       Copied Error:            0

       Token Error:             0

       Bus Error:               0

       Parity Error:            0

The fields "Bytes Transmitted" and "Bytes Received" include the LAN headers of the frames.

The fields "Frames Transmitted" and "Frames Received" include all frames, data frames as well as protocol overhead frames.

"Out of Resource" means that a "Transmit Chain" request is issued by the protocol at a time when the MAC Driver has no free transmit resources. A large figure usually means that the "MaxTransmits" parameter in the OCT3XN section of PROTOCOL.INI should be increased.

The "Transmit ARI Errors" and "Transmit FCI Errors" are related to frames which are not picked up by the destination station. The ARI (Address Recognized Indicator) counter is incremented each time a frame is sent to a destination that no longer exists on the network. This may happen, for example, when a workstation closes down, without removing its sessions. The server will then transmit "session alive" messages, which are not recognized by any stations. The FCI (Frame Copied Indicator) counter is incremented each time a frame is sent, and is not received by any station. This will happen in the same situations as described above for the ARI counter. If, however, the FCI counter is smaller, frames which were recognized by the destination have been sent, but not picked up. This may be caused by receive-buffer congestion in the destination station.

"Free XCB Count" is a low-water mark of the free transmit resources in the MAC Driver. It is related to the "Out of Resource" counter.

"Packet Filter" is the NDIS packet filter set by the protocols. For normal operation this will have the value 3. If a protocol is using the MAC driver in promiscuous mode (receiving all packets on the ring) bit 2 will be set, giving a the typical value of 4 or 7.

"Error Log" is an accumulation of the error logs read from the adapter. The "Congestion Error" counter accumulates the number of times on which the adapter cannot receive a frame because of receive buffer shortage. The sending station will, in this case, increment the ARI counter, but not the FCI counter.

Configuration Status Display

The status display format is shown below. It is displayed on current output by the operator command:

OMACSTAT -c

    OLICOM MAC Driver Runtime Status

    Adapter 0 Configuration Status:

    Hardware State:        Operational

    Adapter Type:          PCI 16/4

    Permanent Address:     00 00 83 20 15 70

    Current Address:       00 00 83 20 15 70

    Adapter State:         OPEN

    IO Address:            FCC0

    Interrupt Level:       9

    Diagnostics Result:    0000

    Link Speed:            16 Mbps

    Max Frame Size:        4096

    MaxTransmits:          4

    Receive Buffer Size:   512

    Receive Buffer Count:  9

    MaxDataBlocks:         8

    MACServiceFlags:       0x29A9D

    Functional Address:    0x00000080

    MACOpenOptions:        0x0020

    EarlyTokenRelease      YES

    FullDuplexSupport      YES

    Duplex                 FULL

The "Diagnostics Result" is the latest completion code from the adapter start-up diagnostics. The error codes are the same as the ones displayed by the driver during system initialization if an adapter error occurs.

The "Max Frame Size" is the largest frame size allowed by the driver and adapter buffer configuration. The actual maximum frame size is decided by the protocol modules, for example DLC and NETBIOS, and is typically smaller.

"MaxDataBlocks" indicates the number of buffers into which a message frame may be split when issued by protocol to MAC driver using a TransmitChain Request.

"MACServiceFlags" shows the significant part of the Service flags as set in the MAC Service-Specific Characteristics Table.

"Functional Address" shows the current functional address set on the adapter.

"MACOpenOptions" shows the current open options for the adapter. See IBM Token-Ring Network Technical Reference for further information.

Commands

The command format is:

OMACSTAT [func][adapter]

where

  func:	-c	Configuration Status

-s	Statistics (default)

-r	Reset Statistics

  adapter:	-a0	First adapter (default)

-a[n][s|p]   nth adapter.

Use the "s" parameter to access a Server MAC Driver in an environment with other Olicom MAC Drivers, and the "p" parameter to access a Pocket MAC Driver in an environment with other Olicom MAC drivers.


Troubleshooting

If you encounter a problem with your RapidFire 314x Adapter, run the Adapter Diagnostics Program to isolate and possibly resolve the problem.

See also if one the following techniques solves the problem.

Interrupt problems in NetWare servers

When a RapidFire 314x Adapter autoconfigures to IRQ7 or IRQ15, the primary/secondary controller detects lost hardware interrupts.

This is due to a bug in the server. Solve the problem by configuring another device in the PC to IRQ7 or IRQ15.

The adapter does not detect the ring speed

For the RapidFire 314x Adapter to detect the ring speed, another station (PC) must already have been attached and opened on the the ring. If the RapidFire 314x Adapter is the first station on the ring, the ring must be configured either via the Setup Program or via a driver parameter (SPEED or Ring Speed).

The RapidFire 314x Adapter always detects the duplex setting automatically.

IBM DOS LAN Support Program runs slowly

Using the default DXMT0MOD NetBIOS driver results in poor performance. Use instead the DXMJ0MOD NetBIOS driver.

EMM386

If using EMM386 make sure it is version 4.49 or later. This version is available with MS DOS version 6.22 or IBM DOS version 7.00.

IBM Value Point 6384-1V0

If using an IBM ValuePoint 6384-1V0 machine (Pentium/60), make sure you have an updated BIOS in order to run the OS/2 drivers. The Flash Prom version should be at least 1.00.06.AV0M.

BIOS Settings

PCI is self-configuring, so for most PCI computers, you need only install your adapter in a PCI bus slot and power-up your computer. The computer's BIOS will then automatically configure the adapter.

With some PCI computers, however, you may need to assign the PCI interrupt INTA to an available interrupt level. This is usually done via a jumper on the motherboard and/or your computer's PCI BIOS SETUP. Your computer manual should describe how to set the motherboard jumpers and modify BIOS settings.

If the driver recognizes the PCI adapter but an initialization error occurs, this may be caused by an interrupt conflict. An ISA adapter (undetected by the BIOS) could be occupying the interrupt assigned to the PCI adapter.


Unattended Setup for Windows NT
Unattended Setup for Windows NT 4.0

This topic explains how to perform an unattended installation of a Windows NT 4.0 system.

Make sure that you have the Windows NT 4.0 CD-ROM and Olicom Driver Disk ready.

1.	Create a copy of the NT CD-ROM installation files on the server hard-drive by copying all files from the \i386 directory.

Remember to copy all subdirectories as well.

2.	Copy the Olicom miniport driver and related setup files to a temporary directory on the local hard drive, for example C:\OLIINST.

The files are located in the root of the Driver Disk and are as follows:

*.SY?

*.DL?

*.HL?

OEMSETUP.INF

3.	Create an unattended answer file, for example C:\OLIINST\OLICOM.TXT which matches your settings.

If using the SETUPMGR located in the \SUPPORT\DEPTOOLS\I386 directory on the NT 4.0 CD-ROM, you will not be able to select the Olicom adapter directly, but Olicom adapters can be added using the OEM option.

4.	Select Networking Setup.

5.	Make sure the "Unattended Network Installation" and "Specify adapter(s) to be installed" boxes are selected in the General tab.

6.	Click the Adapters tab.

7.	The Setup Manager defaults to SelectedAdaptersSection for the Adapter section name (which is correct).

Click the "Add..." button to select which adapters to install.

8.	In the drop-down list, choose the "Other (OEM adapter installation)" and click <OK>.

9.	Click the "Parameters..." button to enter settings for the adapter to install.

10.	Enter the OPTION name (see step 16) that matches the adapter to install.

11.	For the "Location of OEM Files", enter for example C:\OLIINST.

12.	Additional parameters can be entered in the "Adapter Parameters" box by entering the Parameter name and value and clicking "Add".

When all parameters has been added, click the <OK> button.

13.	Protocols and services to install may be selected in the Network Options dialog box.

14.	Click <OK> when all network options has been configured, and configure the General and Advanced setup to match your settings.

15.	Save the unattended setup file as for example C:\OLIINST\OLICOM.TXT.

16.	Verify that the OLICOM.TXT file contains entries that looks like the following:

[Network]

   InstallAdapters = SelectedAdaptersSection

[SelectedAdaptersSection]

   OCTX3140 = OEMCardParameters,C:\OLIINST

[OEMCardParameters]

The ",C:\OLIINST" text in the line for the option to install specifies where to search for the installation files and drivers.

Example: An OLICOM.TXT file:

[Unattended]

   OemPreinstall = yes

   NoWaitAfterTextMode = 0

   NoWaitAfterGUIMode = 0

   FileSystem = LeaveAlone

   ExtendOEMPartition = 0

   ConfirmHardware = no

   NtUpgrade = no

   Win31Upgrade = no

   TargetPath = winnt

   OverwriteOemFilesOnUpgrade = no

[UserData]

   FullName = "User Name"

   OrgName = "Olicom A/S"

   ComputerName = OLICOM

[GuiUnattended]

   OemSkipWelcome = 1

   OEMBlankAdminPassword = 1

   TimeZone = "(GMT+01:00) Berlin, Stockholm, Rome, Bern, Brussels, Vienna"

[Display]

   ConfigureAtLogon = 0

   BitsPerPel = 8

   XResolution = 640

   YResolution = 480

   VRefresh = 60

   AutoConfirm = 1

[Network]

   InstallAdapters = SelectedAdaptersSection

   InstallProtocols = ProtocolsSection

   InstallServices = ServicesSection

   JoinWorkgroup = workgroup

[SelectedAdaptersSection]

   OCTX3140 = OEMCardParameters,c:\oliinst

[OEMCardParameters]

[ProtocolsSection]

   NBF = NBFParamSection

[NBFParamSection]

[ServicesSection]

17.	Login to your server, change to the directory containing the NT installation files mentioned in step 1 and start the NT installation by entering:

winnt /b /u:C:\OLIINST\OLICOM.TXT /s:e:\ /t:c

Change the source path "/s:<path>" and target drive "/t:<drive>" to match your settings.