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

Readme File for SKFPNT.SYS
	SK-NET FDDI PCI PowerPC NDIS3 driver for Windows NT v3.02 Rev. A (961025)

October 25, 1996



This file contains
(1) OVERVIEW
(2) REQUIRED FILES
(3) INSTALLATION INSTRUCTIONS
(4) DRIVER OPTIONS
(5) TROUBLESHOOTING
(6) HISTORY

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


(1) OVERVIEW
============

SKFPNT.SYS is a Windows NT 32-bit driver for
	SK-NET FDDI PCI Adapters.
It runs on PowerPC machines and corresponds to the NDIS 3.1
specification as delivered with Windows NT.

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


(2) REQUIRED FILES
==================

To install the driver, you need the following files:

	WINDOWS\NT\PPC directory of Installation Diskette:
		SkFpNt.SYS	FDDI NDIS 3 driver
		OEMSETUP.INF	Installation setup script
		OEMNADSK.HLP	Installation help file
		OEMNADSK.DLL	Installation dialogs
***


(3) INSTALLATION INSTRUCTIONS
=============================

First of all you should carefully read the installation instructions
contained in the adapter manual.  Follow these instructions to put the
adapter into the computer.

Step 1:	Start Windows NT.

Step 2:	Start NETWORK from the CONTROL PANEL, click ADD ADAPTER.
	Select <OTHER>.

Step 3: Insert Installation Diskette into a floppy disk drive
	(assumed A: here) and input, as path to the required files,
		A:\WINDOWS\NT\PPC
	Select the driver matching your adapter type.

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


(4) DRIVER OPTIONS
==================

The SKFPNT.SYS driver provides full SMT (FDDI station management)
support by a complete range of SMT parameter options. Using these options
it is possible to use such enhanced SMT features as Synchronous Bandwidth
Allocation (SBA) and End Station Support (ESS). For more details on these
parameters, check the SMTDOCU.TXT documentation file on the installation
diskettes.

The other parameter options the driver supports are described here.
The Windows NT installation support contains online help that describes,
in detail, all available parameter options.


BUS/SLOT
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 this bus
and slot number.

PCIFIX
	range	0..FFFFFFFF
	default	0
This parameter is reserved for fixing configuration problems
between the PCI BIOS and the adapter. For this release there
are no known configuration problems, therefor this parameter
is unused yet.
Contact the SysKonnect support for more information (check the
SUPPORT.INF file on the Installation Diskettes).

NETWORK ADDRESS
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 allowed 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 another 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.
***


(5) TROUBLESHOOTING
===================

If you encounter problems with SK-NET FDDI PCI adapters
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:	5001 -	Could not allocate the resources necessary
			for operation.
Reason(s):	Not enough RAM or pagefile too small.
---------------
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:	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
		  interrupts.
---------------
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 the SysKonnect support for more information (check the
SUPPORT.INF file on the Installation Diskettes).
***


(6) HISTORY
===========

v3.02 Rev. A
  - Added workaround for EBUF_ERR in SN3.
v3.02
  - 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.
v3.01
  - 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).
v3.00
    New features:
	None (First Release).
    Problems fixed:
	None.
    Known limitations:
	- The parameter MaxPacketSize is not supported correctly yet.

*** End of information file ***