Copyright: Copyright (c) Olicom A/S 1993, 1994.


Parameters
Parameter descriptions

The following parameters are applicable for the NDIS 3 driver:

I/O Base Address

Receive Buffers

Transmit Buffers

Maximum Frame Size

Bus Number

Early Token Release

Full Transmit Status

Network address

All parameters have a default value suitable in most situations. However, if you need to install several adapters in your system, or use locally-administered addresses, you may need to change some of them.


IoBaseAddress
The I/O base address specifies where the network adapters I/O ports are located. If you select "Auto detect", the NDIS 3.0 driver will search for an adapter at all I/O addresses. If an I/O base address is specified, only that I/O range will be scanned for an adapter. If an invalid I/O address range is selected, you will be unable to connect to the network.

If no adapters can be found, the Cannot find adapter error message is posted.


ReceiveBuffers
This parameter specifies the number of receive buffers allocated by the NDIS 3 driver. Valid range is 5-32. Allocating a large number of receive buffers prevent the adapter from congesting when receiving large amounts of data.

However, system resources are limited and you may have problems loading the NDIS 3 driver if it allocates large amounts of data.

Allocating too many resources can result in a resource error.


TransmitBuffers
This parameter specifies the number of transmit buffers allocated by the NDIS 3 driver. Valid range is 2-32. Allocating a large number of transmit buffers will speed up data transmission.

However, system resources are limited and you may have problems loading the NDIS 3 driver if it allocates large amounts of data.

Allocating too many resources can result in a resource error.


MaxFrameSize
Specifies the maximum frame size the NDIS 3 driver can handle. This parameter is also used for allocating internal memory for handling frames in special situations.

However, system resources are limited and you may have problems loading the NDIS 3 driver if it allocates large amounts of data.

Allocating too many resources can result in a resource error.


Contents
Contents for Network Installation help

The Microsoft® Windows NT™ operating system uses NDIS 3 network drivers.

This help file explain the configuration parameters for the network driver you are installing or configuring. You must be logged on as a member of the Administrators group to install and configure network adapters.

Use this help file as a guide if you experience any problems with your network adapter. It contains a list of all NDIS 3 driver error messages and proposed actions.

The OCTKSTAT.EXE tool for obtaining driver statistics is also described.

Parameter descriptions

Error messages

Getting driver statistics

This help file is also accessible via the Winhelp.exe File|Open menu.


BusNumber
Use the Bus Number parameter only when the network adapter is installed in multi-bus PC's. If the PC only has a single bus, set this parameter to 0 (zero). This is the usual situation.


EarlyToken
Specifies whether Early Token release should be used or not.

This parameter is only applicable when running at 16 Mb/s.


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


NetAddress
Use the Network address field if you do not want to use the network adapter's burned in Token Ring address. The value entered must be a locally administered address, i.e. in the range from 400000000000 to 7FFFFFFFFFFF. The value can be entered as "XX-XX-XX-XX-XX-XX" for readability.

If the NDIS 3 driver encounteres an invalid network address, the invalid network address error message is posted.

The value entered is verified by the setup program when you click "Ok" in the setup dialog box.


DriverStat
Using OCTKSTAT.EXE to view statistics

Use the OCTKSTAT.EXE program to display adapter status and statistics. OCTKSTAT.EXE is copied to your Windows NT "System32" directory, when you install the NDIS 3.0 driver. In order to use the OCTKSTAT.EXE utility you must have the NDIS 3 driver installed and loaded.

The program is called using the following parameters:

      OCTKSTAT adapter name [options]

Examples:

      OCTKSTAT

shows the option list.

      OCTKSTAT octk1601 -s

will show the statistics for instance 01 of the octk16 driver.

      OCTKSTAT octk3203 -c

will show the adapter configuration for instance 03 of the octk32 driver.


AdapterName
The adapter name consists of a driver name and an instance number:

      <driver name><instance>

where <driver name> is the name of the driver, i.e. "Octk16" or "Octk32" and <instance> is the instance number of the network adapter installed, i.e. 01, 02 etc. This value is displayed to the left of the driver name in the Network Setting window.

Example: Octk1601 or Octk3203.

Notice: There must be no space between <driver name> and <instance>.


Options

Valid [options] are

           -c for adapter configuration

           -a for additional adapter configuration

           -s for general adapter statistics

           -m for media-specific statistics

Options may be combined, i.e. -c -a.


Errors
Error descriptions

If you have any problems with the network, you should check if any error messages or warnings are posted by the NDIS 3 driver by using the Event Viewer in the Administrative Tools group.

Ensure that the adapter is located at the correct I/O base address, and the cable is properly connected to the adapter.

All error messages and/or warnings posted by the NDIS 3 driver have the Source field set to "Octk16" or "Octk32" depending on the driver installed.

System error messages, related to the NDIS 3 driver, can occur with different source names, i.e. "Service Control Manager".

The messages are enumerated by the b Event field and are described below in Event number order. In the event viewer display the message description by highlighting the message and pressing the enter key. Error messages from 5000 are predefined error codes specific to the Windows NT™  operating system. You can retrieve additional information on these messages in your documentation.

0001 : Bring-up diagnostics failed for driver

0002 : Adapter initialize failed for driver

0003 : Adapter Check on driver

0004 : Could not open adapter driver. Ring beaconing. Check network speed settings

0005 : Could not open adapter driver. Duplicate node address

0006 : Could not open adapter driver. Request initialisation failed

0007 : Could not open adapter driver. Remove station received

0008 : Could not open adapter driver

0009 : Could not download code on adapter driver

0010 : Lobe wire fault detected by driver. Please check cable connections

0011 : driver has failed the lobe wrap test resulting from the beacon auto-removal process and has deinserted from the ring

0012 : driver has received a remove ring station Mac frame request and has deinserted from the ring

0013 : The detected adapter for driver is not supported by this driver

0014 : The configuration read for driver is invalid

0015 : driver has received a Trace Tool Remove frame from a Network Management station and has disabled the promiscuous packet filter

5000 : driver : Has encountered a conflict in resources and could not load

5001 : driver : Could not allocate resources necessary for the operation

5002 : driver : Has determined that the adapter is not functioning properly

5003 : driver : Could not find an adapter

5004 : driver : Could not connect to the interrupt number supplied

5005 : driver : Has encountered an internal error and has failed

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

5007 : driver : Timed out during an operation

5008 : driver : Has encountered an invalid network address

5009 : driver : Does not support the configuration supplied

5010 : driver : The adapter has returned an invalid value to the driver

5011 : driver : A required parameter is missing from the registry

5012 : driver : The IO Base Address supplied does not match the jumpers on the adapter

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

5015 : driver : There is an I/O port conflict

5016 : driver : There is an I/O port or DMA channel conflict

5018 : driver : There is a interrupt conflict at interrupt number xx

5019 : driver : There is a resource conflict at DMA channel xx

If you have any problems, write down the Event ID, Source, Description and Data fields in the Event Detail window. This information helps the support team to locate the error.


Bring-up diagnostic error
1 Bring-up diagnostics failed for driver.

The adapter failed during the bring-up diagnostics.

Action: Shut down your system and re-try the operation. If the error persists, contact your place of purchase for support.


Initialization error
2 Adapter initialize failed for driver.

The adapter failed the initialization phase.

Action: Shut down your system and re-try the operation. If the error persists, contact your place of purchase for support.


Adapter check
3 Adapter Check on driver.

A serious error occurred on the adapter, causing an adapter check code to be posted.

Action: Re-start your system. If the error persists, contact your place of purchase for support.


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

The network speed settings on your network adapter propably do not match the ring-speed  used on your token-ring network.

Action: Change your network speed settings and restart your system.


Duplicate node address
5 Could not open adapter driver. Duplicate node address.

A duplicate address has been discovered on the ring.

Action: Change your locally-administered address as discussed in the Adapter parameters section and restart your system.


Request initialization error
6 Could not open adapter driver. Request initialization failed.

An error occurred during adapter initialisation.

Action: Re-start your system. If the error persists, contact your place of purchase for support.


Remove station received
7 Could not open adapter driver. Remove station received.

The adapter has been removed by a LAN Manager station.

Action: Contact your network administrator.


Open error
8 Could not open adapter driver.

The adapter failed to open.

Action: Check cables and connections and re-try. If the error persists, try a different lobe media cable.


Download failed
9 Could not download code on adapter driver.

The download operation failed.

Action: Re-start your system. If the error persists, contact your place of purchase for support.


Cable connection
10 Lobe wire fault detected by driver. Please check cable connections.

The connection to the network has been removed.

Action: Check all cables and connections and try another lobe media cable. The adapter continues to try to re-insert on the ring.


Ring beaconing
11 driver has failed the lobe wrap test resulting from the beacon auto-removal process and has deinserted from the ring.

The adapter has deinserted from the ring, because the ring was beaconing.

Action: Check the network speed settings and cable connections and re-try. If the error persists, contact your network administrator.


Adapter removed from ring
12 driver has received a remove ring station Mac frame request and has deinserted from the ring.

The adapter has been removed by a LAN Manager station.

Action: Contact your network administrator.


Adapter not supported
13 The detected adapter for driver is not supported by this driver.

You have installed the wrong NDIS 3 driver for the adapter or your adapter is not supported.

Action: Get the newest NDIS 3 driver available for your network adapter.


Configuration
14 The configuration read for driver is invalid.

A configuration entry is invalid.

Action: Use the network control panel to set-up proper adapter settings.


Auto disabled
15 driver has received a Trace Tool Remove frame from a Network Management station and has disabled the promiscuous packet filter.

The NDIS 3 driver has cleared the PROMISCUOUS packet filter bit, as instructed by a LAN Manager station.

Action: Contact your network administrator.


5000
5000 driver : Has encountered a conflict in resources and could not load.

The resources needed for your network adapter conflicts with another adapter.

Action: Check the resources used by the network adapter(s) to ensure that no conflicts exists.


5001
5001 driver : Could not allocate resources necessary for operation.

The NDIS 3 driver failed to load, because it tried to allocate too many resources.

Action: Decrease the number of receive and/or transmit buffers and re-try.


5002
5002 driver : Has determined that the adapter is not functioning properly.

The adapter could not be found or is not working properly.

Action: Check I/O base settings and re-try.


5003
5003 driver : Could not find an adapter.

The adapter could not be found by the NDIS 3 driver.

Action: Check I/O base settings and re-try.


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

The interrupt is already used by another device.

Action: Change the adapter interrupt number and re-try.


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

An internal error has been discovered.

Action: Re-start your system. If the error persists, contact your place of purchase for support.


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

The NDIS 3 driver version is incorrect.

Action: Re-start your system. If the error persists, contact your place of purchase for support.


5007
5007 driver : Timed out during an operation.

A time-out error occurred.

Action: Re-start your system. If the error persists, contact your place of purchase for support.


5008
5008 driver : Has encountered an invalid network address.

An invalid network address was specified.

Action: Change the locally administered network address and re-start your system. If the error persists, try clearing the network address in the setup dialog. The NDIS 3 driver will then use the burned-in address when opening.


5009
5009 driver : Does not support the configuration supplied.

An invalid configuration entry was discovered.

Action: Use the network control panel to set proper adapter parameters. Do not try to manually change any parameters in the registry.


5010
5010 driver : The adapter has returned an invalid value to the driver.

An internal error has occurred.

Action: Re-start your system. If the error persists, contact your place of purchase for support.


5011
5011 driver : A required parameter is missing from the registry.

A parameter necessary for operation has been omitted in the registry.

Action: Use the network control panel to set proper parameters.


5012
5012  driver : The IO Base Address supplied does not match the jumpers on the adapter.

The adapter could not be found by the NDIS 3 driver.

Action: Check I/O base settings and re-try.


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

The adapter is disabled.

Action: Make sure the start-up parameter for the NDIS 3 driver is set to "Manual". Use the "Devices" applet in the control panel to change the settings.


5015
5015 driver : There is an I/O port conflict.

The ports used by the NDIS 3 driver are already in use by another device.

Action: Change the I/O Base address for the adapter.


5016
5016 driver : There is an I/O port or DMA channel conflict.

The ports or DMA channel used by the NDIS 3 driver are already in use by another device.

Action: Check the I/O port and DMA usage by the adapter to ensure that there is no resource conflicts.


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

The adapter tried to use an interrupt currently in use.

Action: Change the interrupt selection on the adapter and re-try.


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

The adapter tried to use a DMA channel currently in use.

Action: Change the DMA channel selection on the adapter and re-try.


Support
If you have any problems, write down the Event ID, Source, Description and Data fields in the Event Detail window. This information helps the support team to locate the error.