(C)Copyright 1993-1997 SysKonnect,
a business unit of Schneider & Koch & Co. Datensysteme GmbH.
All rights reserved

Readme File for SKFPNT.SYS
	SK-NET FDDI PCI NDIS3 driver for Windows NT v3.03 (970526)

May 26, 1997

This file contains



SKFPNT.SYS is a Windows NT 32-bit driver for SK-NET FDDI PCI adapters.
It runs on machines with Intel processors and conforms with the NDIS 3.1
specification as delivered with Windows NT.

This README file explains how to install the FDDI NDIS 3 driver
SKFPNT.SYS in a Windows NT station.


To install the driver, you need the following files:

	From WINDOWS\NT\I386 directory of Installation Diskette:

		OEMSETUP.INF	installation setup script
		OEMNADSK.HLP	installation help file
		OEMNADSK.DLL	installation dialogs


Read the installation instructions in the adapter manual carefully. Follow
these instructions to install the adapter in your computer.

Step 1:	Start Windows NT.

Step 2:	Start NETWORK from the CONTROL PANEL, click ADD ADAPTER.
	Select HAVE DISK.

Step 3: Insert Installation Diskette into a floppy disk drive (e.g. A:)
	and enter the path to the required files, e.g.


	Select the driver matching your adapter type.

Step 4:	Select the appropriate configuration. Then choose OK and restart
	your system.


The SKFPNT.SYS driver provides full SMT (FDDI Station Management) support
by a complete range of SMT parameter options. These parameters offer
enhanced SMT features such as Synchronous Bandwidth Allocation (SBA) and
End Station Support (ESS). For details on these parameters, refer to the
SMTDOCU.TXT documentation file on the installation diskette.

All other parameters the driver supports are described below.

The Windows NT installation support contains online help that describes all
available parameter options in detail.

This combination specifies the adapter to which the driver shall be bound.
During adapter installation, the system will scan the PCI buses for
SK-NET FDDI PCI adapters and present them to you, along with the bus
and slot number.

	range	0..FFFFFFFF
	default	0

This parameter is reserved for fixing configuration problems between the
PCI BIOS and the adapter. For the current release of the driver, there are
no known configuration problems. Therefore, this parameter is yet unused.

Contact SysKonnect support for further information (or refer to the
SUPPORT.INF file on the Installation Diskette).

To use a network address other than the one burned into the adapter card,
enter the network address in hexadecimal form, in the following format:

	XX-XX-XX-XX-XX-XX (for instance, 40-00-5A-12-34-56).

The valid range reaches from 40-00-00-00-00-00 to 7F-FF-FF-FF-FF-FF.
If you leave the network address blank (or specify a different number of
digits), the network address burned into the adapter card is used.
If you do not know the network address, ask your network administrator.


If you encounter problems with your SK-NET FDDI PCI adapter
under Windows NT, please re-read carefully the instructions above
and the documentation supplied with the Windows NT system.

Also refer to your system log file (using the Event Viewer) and check
it for entries from SKFPNT.

The last 5 DWORDs of the logging data are:

- Slot number,

- Interrupt number,

- Dma channel,

- Base I/O port and

- Vendor code (3 bytes) / adapter id (1 byte)

of the adapter that caused the error.

Following is a list of some events, possible reasons (may be incomplete)
and suggestions to fix your problem.

Event ID:	5000 -	Has encountered a conflict in resources
			and could not load.
Reason(s):	The driver failed closing.
Event ID:	5001 -	Could not allocate the resources necessary
			for operation.
Reason(s):	Not enough RAM or pagefile too small.
Event ID:	5002 -	Has determined that the adapter is not functioning
Reason(s):	Driver has reset the adapter because it detected a deadlock
Event ID:	5003 -	Could not find an adapter.
Reason(s):	Wrong slot.
		Adapter physically not installed.
		System configuration information invalid.
Help:		Check configuration.
		Look if adapter is physically present.
		Check system configuration.
Event ID:	5004 -	Could not connect to the interrupt number supplied.
Reason(s):	The selected interrupt is already in use.
Help:		Select free interrupt.
Event ID:	5005 -	Has encountered an internal error and has failed.
Reason(s):	This error may have miscellanous reasons.
Help:		Please call our support and tell them the logging data as
		 dwords, at least the last 5 dwords in the error log entry.
Event ID:	5007 -	Timed out during an operation.
Reason(s):	Wrong interrupt, DMA channel or base address.
		Cable not connected.
Help:		Start a driver under e.g. DOS (with the same resource usage)
		 and look if it works.
		Check cabling.
Event ID:	5009 -	Does not support the configuration supplied.
Reason(s):	Shared interrupt configured.
Help:		The driver does not support interrupt sharing.
		 Please re-configure the adapter to not using shared
Event ID:	5014 -	The adapter is disabled.
			The driver cannot open the adapter.
Reason(s):	The adapter was not enabled at system startup.
Help:		First, check the system configuration. If it looks ok,
		 run the diagnostic program supplied with the adapter.

If your special problem is not listed or the error persists, please
send us your system log file or at least the event id number and the
logging data (as dwords) of the entries made by SKFPNT.

Contact SysKonnect support for further information (or refer to the
SUPPORT.INF file on the Installation Diskette).


v3.02 Rev. C
  - Fixed interrupt problems during initialization.
  - Fixed reception of multicast frames problem after a reset.
  - Fixed Dual Homing feature for DAS adapters in a Cisco environment.
v3.02 Rev. B
  - Modified workaround for EBUF_ERR in SN3.
v3.02 Rev. A
  - Added workaround for EBUF_ERR in SN3.
  - Fixed a bug that caused the driver to stop sending due to the unability
    of handling packets with more than 40 fragments.
v3.01 Rev. A
  - Fixed Dual Homing feature for DAS adapters: The driver sometimes
    required up to 50 seconds before re-inserting the station into
    the FDDI ring.
  - Software or hardware failure detected by driver caused the driver to
    stop (endless software loop).
  - Sender could deadlock when network load was heavy.
  - Fixed lookahead length problems (OID_GEN_CURRENT_LOOKAHEAD) experienced
    with new NDIS Tester (NCT).
    New features:
	None (First Release).
    Problems fixed:
    Known limitations:
	- The parameter MaxPacketSize is not supported correctly yet.

*** End of information file ***