(C)Copyright 1993-1999 SysKonnect. All rights reserved

skfpwin.htm created 27-Aug-1999

Readme File for SKFPWIN.SYS v5.08
SK-NET FDDI PCI NDIS4 32-bit Miniport  driver
used on Windows NT 4.0.



This file contains



NOTE:  Our Technical Support address dates are given in the 
       Support.htm/support.inf files
       


(1) Overview

SKFPWIN.SYS is the NDIS4 32-bit Miniport driver for the
SK-NET FDDI PCI adapter family.

This README file explains how to install the Miniport driver on a machine
running Windows NT 4.0.

**************************************************************************
  IMPORTANT NOTE

  The SKFPWIN NDIS4 Miniport driver cannot be used with
  Windows NT 3.51 or below. You must use Windows NT 4.0 if you want to use
  this driver.
**************************************************************************

(2) Required Files

To install the driver, you need the following files:

	SKFPWIN.SYS	SK-NET FDDI PCI NDIS4 Miniport driver
	OEMSETUP.INF	installation setup script
	OEMNADSK.HLP	installation help file
	OEMNADSK.DLL	installation dialogs

(3) Installation Instructions

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

Step 1:	Start Windows NT 4.0.

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

Step 3: Insert your driver CD into a disk drive (e.g. A:)
	and enter the path to the required files, e.g.

		D:\WINDOWS\NT400

	Then click OK.

Step 4:	Select the SK-NET FDDI PCI adapter and press OK.

Step 5:	Select the appropriate configuration (see section "Driver Options"
	in this readme file for details). Then choose OK and restart your
	system.
	
Step 6: Now update your system again with the currently used Service Pack.

(4) Updating the Driver

**************************************************************************
  IMPORTANT NOTE

  In most cases, you can use the CONTROL PANEL / NETWORK / ADAPTERS /
  UPDATE button to update an already installed driver for your
  SK-NET FDDI PCI adapter.
**************************************************************************

In some cases, however, you may get an error message during the driver
update procedure. This error message will appear when you try to upgrade
from the old "Full MAC" version of the driver (SKFPNT.SYS) to the new
"Miniport" version of the driver (SKFPWIN.SYS). The driver that ships
with this readme file is the new "Miniport" version.

In order to upgrade to the new Miniport driver, you must first remove the
old Full MAC driver. Follow these steps:

Step 1:	
Start Windows NT 4.0.

Step 2:	
Start NETWORK from the CONTROL PANEL, click ADAPTERS and select
the SK-NET FDDI PCI adapter.

Step 3:	
Click REMOVE and press YES when prompted "Do you still wish to
continue?".

Step 4: 
Click CLOSE and press YES when prompted "Do you want to restart
your computer now?".

Step 5:	
Install the new driver by following the steps in section
"Installation instructions" in this readme file.

(5) Unattended Setup of Windows NT 4.0

This chapter describes the required procedure for the automatic
installation of the SK-NET FDDI PCI Adapter during an unattended setup
of Windows NT 4.0. Before continuing, please also read the instructions
for unattended setup in the Windows NT documentation.

Step 1:	
After copying the I386 directory and its subdirectories from the
installation CD to the installation server, create the subdirectory

	$OEM$\NET\SKFPWIN

in the I386 directory and copy the files listed in the chapter
"Required Files" to the newly created SKFPWIN directory.

Do not forget to share the I386 directory on the installation
server (e.g. as INSTALL).

Step 2:	
Now create a network installation boot disk for the unattended
setup of Windows NT 4.0. If the installation is to be run from a
Windows NT Server you can create the start diskette using the
"Network Client Administrator", which is located in the folder
"Administrative Tools" on the Windows NT 4.0 Server.

Since this program does not support the SK-NET FDDI PCI Adapter
directly, you will need to add the DOS NDIS driver manually.
Select "Make Network Installation Startup Disk" from the first
screen of the network client administrator. Then select "Share
Files" and enter the path to the directory CLIENTS on the Windows
NT 4.0 Server CD (e.g. D:\CLIENTS) in the Path field. Choose a name
for the share (e.g. CLIENTS).

On the next screen select the media type, "Network Client v3.0 for
MS-DOS and Windows", and a network adapter e.g. "3Com EtherLink".

On the last screen you must enter a name for the client
workstation, user name, domain name and protocol. After inserting
a formatted system diskette containing an MS-DOS or compatible
operating system, the Network Client for MS-DOS is copied to the
installation start diskette.

Step 3:	
The start diskette created in Step 2 must now be modified
for the special needs of the SK-NET FDDI PCI Adapter:

Copy the files UPPSFP.EXE and UPPSND.DOS from the directory
\WINDOWS\WFW311\ located on the installation diskettes provided
with the SK-NET FDDI PCI Adapter and the file PROTOCOL.INI
provided with this readme file to the directory	\NET on the
installation start diskette.

Step 4:	
In the AUTOEXEC.BAT file insert the line:

		A:\NET\UPPSFP

before

		A:\NET\NET INITIALIZE

Change the line:

		NET USE Z: \\INSTALLSERVER\CLIENTS

to match your configuration. Replace INSTALLSERVER with the name
of your installation server and CLIENTS with the name of the
share containing the I386 directory copied from the Windows NT
installation CD.

Remove the last line of the AUTOEXEC.BAT file:

		Z:\MSCLIENT\NETSETUP\SETUP.EXE /$

It is also highly recommended to use SMARTDRV on the boot diskette
to speed up the installation process.

Step 5:	
Edit the file \NET\SYSTEM.INI on the boot diskette. Go to the
section [network drivers] and change the line

		netcard=
to
		netcard=uppsnd.dos

Step 6:	
Now that the installation start diskette has been created, the
next step is to create an answer file for the unattended setup of
Windows NT 4.0. The following parameters are network specific.
Please refer to the NT 4.0 documentation for details on general
parameters.

Start the tool SETUPMGR.EXE located in the directory
\SUPPORT\DEPTOOLS\I386 on the NT 4.0 Server CD. Under "Networking
Setup", "General" select "Unattended Network Installation" and
"Specify adapter(s) to be installed". In the folder "Adapters"
press "Add..." and choose "Other (OEM adapter installation)", then
press the "Parameters..." button. In the next window enter the
following name in the field "Inf Option Name":

		SKFPWIN

In the field "Location of OEM Files" enter:

		..\$OEM$\NET\SKFPWIN


Using the option "Save As...", save the installation setup file in
the shared installation directory as CLIENT1.TXT.

Step 7:	
Using the installation start diskette, boot a computer which is
connected to the installation server via the network. Login to
the server and run the unattended installation as follows:

	Z:\WINNT /s:Z:\ /t:C: /u:Z:\CLIENT1.TXT /b

where

	/s:Z:\			specifies the shared installation
				directory I386 accessed via drive Z:\
	/t:C:			copies temporary installation files to
				drive C:
	/u:Z:\CLIENT1.TXT	specifies the name and loction of the
				file used to automatically install Windows
				NT 4.0

When the setup is running, remove the boot diskette from the drive.

(6) Driver Options

The SKFPWIN.SYS driver allows you to modify several options in order
to optimize the operation of your SK-NET FDDI PCI adapter. The driver
options can be set as follows:

Step 1:	
Start NETWORK from the CONTROL PANEL, choose ADAPTERS, select
the SK-NET FDDI PCI Adapter and click PROPERTIES.

Step 2:	
In the SK-NET FDDI PCI Adapter Card Setup window, select the
option that you want to change and enter the desired value.

Step 3:	
Press OK when finished.

Step 4:	
Reboot the machine.

**************************************************************************
  IMPORTANT NOTE

  The machine must be rebooted before any changed options can take effect.
**************************************************************************

The SKFPWIN.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 disk.

All other parameters supported by the driver are described below.

The Windows NT Installation Support provides an online help utility, which
describes all available parameter options in detail.

MAXFRAMESIZE

Default value:	4491 (decimal)
Valid range:	13..4491 (decimal)

This parameter specifies the maximum frame size in bytes that the driver
will support. The performance of your FDDI network usually increases when
a large packet size is used.

BUS/SLOT

Default value:	next available adapter found when driver installed
Valid range:	depends on system configuration

This parameter specifies the adapter instance to which the driver shall be
bound. You can choose from a list of bus/slot combinations for which the
system has found SK-NET FDDI PCI adapters. When you add, remove, or
move any SK-NET FDDI PCI adapters to, from, or between PCI slots, this
list will change.

PCI FIX VALUE

Default value:	0
Valid range:	0..FFFFFFFF (hexadecimal)

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 not yet in
use.

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

NETWORK ADDRESS

Default value:	burned-in adapter address
Valid range:	0y-00-00-00-00-01 to 7y-FF-FF-FF-FF-FF (hexadecimal), 
		where at least the bit 2h (i.e. bit #1) in the 'y' nibble  
		must be set.

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

	XX-XX-XX-XX-XX-XX (e.g. 02-00-5A-12-34-56).

If you leave the NETWORK ADDRESS blank (or specify a different number of
digits), the network address burned into the adapter card will be used.

NOTE!		Incorrect use of this feature may disrupt your network.
		Please ensure that a unique address is assigned.              
		If you are unsure about a valid address please ask your 
		network administrator.

(7) Troubleshooting

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

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

Here is a list of events, possible reasons (may be incomplete), and
suggestions to fix the problem.

---------------
Event ID:	5001
Type:		Error
Description:	"Could not allocate the resources necessary for operation."
Reason:		Not enough RAM or pagefile too small.
Action:		Install more system RAM or increase size of pagefile.
---------------
Event ID:	5002
Type:		Error
Description:	"Has determined that the adapter is not functioning
		 properly."
Reason:		The driver has detected a possible adapter hardware failure
		 and has performed a hardware reset on the adapter.
Action:		Replace adapter if error persists. Note that this error can
		 also be the result of a system hardware failure or a
		 hardware resource conflict.
---------------
Event ID:	5003
Type:		Error
Description:	"Could not find an adapter."
Reason:		- Adapter not physically installed.
		- System configuration information invalid.
Action:		- Check slot setting.
		- Check system configuration.
---------------
Event ID:	5005
Type:		Error
Description:	"Has encountered an internal error and has failed."
Reason:		The driver has detected an internal software inconsistency.
Action:		If the error persists please send your system event log file
		 to our technical support.
---------------
Event ID:	5009
Type:		Error
Description:	"Does not support the configuration supplied."
Reason:		- Invalid configuration parameter setting.
Action:		- If you have manually added or changed any of the driver's
		 configuration parameters with the Registry Editor, remove
		 and re-install the driver in CONTROL PANEL / NETWORK /
		 ADAPTERS.
---------------
Event ID:	5021
Type:		Warning
Description:	"The specified Registry entry MaxReceives is out of range.
		 Using default value."
Reason:		The parameter specifying the number of software receive
		 buffers that the driver will use, 'MaxReceives', is out
		 of the valid range.
Action:		Change parameter setting in CONTROL PANEL / NETWORK /
		 ADAPTERS / PROPERTIES.
---------------
Event ID:	5022
Type:		Warning
Description:	"The specified Registry entry MaxTransmits is out of
		 range. Using default value."
Reason:		The parameter specifying the number of software transmit
		 buffers that the driver will use, 'MaxTransmits', is out
		 of the valid range.
Action:		Change parameter setting in CONTROL PANEL / NETWORK /
		 ADAPTERS / PROPERTIES.
---------------
Event ID:	5023
Type:		Warning
Description:	"The specified Registry entry MaxFrameSize is out of
		 range. Using default value."
Reason:		The parameter specifying the maximum frame size that the
		 driver will support, 'MaxFrameSize', is out of the valid
		 range.
Action:		Change parameter setting in CONTROL PANEL / NETWORK /
		 ADAPTERS / PROPERTIES.
---------------
Event ID:	5025
Type:		Warning
Description:	"The specified Registry entry MaxMulticast is out of
		 range. Using default value."
Reason:		The parameter specifying the maximum number of multicast
		 addresses that the driver will support, 'MaxMulticast',
		 is out of the valid range.
Action:		Change parameter setting in CONTROL PANEL / NETWORK /
		 ADAPTERS / PROPERTIES.
---------------
Event ID:	5030
Type:		Informational
Description:	"The adapter has successfully reinserted back into the
		 ring."
Reason:		- Network cable reconnected to this station or peer
		  station or concentrator.
		- Peer station or concentrator powered on.
---------------
Event ID:	5033
Type:		Warning
Description:	"The adapter has detected that the Token Ring cable is
		 disconnected from the adapter. Please reconnect the
		 Token Ring cable. The adapter will continue to try to
		 reset until the connection is repaired."
Note:		The term "Token Ring" is used here as a synonym for FDDI.
Reason:		- Network cable unplugged or broken.
		- Peer station or concentrator not connected, shut down,
		  or malfunctioning.
Action:		- Connect or replace network cable.
		- Try to plug in other end of cable at a different peer
		  station or concentrator port.
---------------

If your particular problem is not listed or the error persists, please
send your system event log file or at least the event id number and the
logging data (as WORDs) of the entries made by SKFPWIN to our technical
support.

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

(8) History

v5.08
    New features:
	None.
    Problems fixed:
	- Fixes Bug where SMT could not diconnect sometimes at
	  a Dup MAC Disconnect conditions. (#10419) 
	- Number of values returned for OID LCONNECTIONSTATE 
	  reduced to one. (#10416)
	- Fixes a bug where the driver causes the CPU utillisation to spike 
	  up to 80% every few seconds in special environments. (#10289) 

v5.04
    New features:
	- The behaviour of the adapters LEDs was changed.  
	  (Also see:	FUNCTION OF THE ADAPTER LEDs.)
    Problems fixed:
	- RMT enters the RM4 (Duplicate Mac Adress) state 
	  under wrong conditions. (Bug #10375)
	- A wrong multicast adress was used for directed 
	  beacons. (Bug #10373)
	- Fixes a bug which causes the driver to hang in environments 
	  with bad hardware. (Bug #10285)
	- Fixes a Bug with dual homing in multi adapters environments,
	- where the adapters influenced each other. (Bug #10287)
	- Fixes a bug where the driver stops sending of SMT frames 
	  after he had received Directed Beacons. (Bug #10276)

v4.00
  - First release of NDIS4 Miniport driver.

(9) Function of the Adapter LEDs

The functionality of the LED's on the FDDI network adapters was changed
in driver version v5.03. With this new version, the yellow LED works as
a ring operational indicator. An active yellow LED indicates that the 
ring is down.  The green LED on the adapter now works as a link indicator
where an active GREEN LED indicates that the respective port has a 
physical connection.

With earlier version of the driver a ring up was indicated if the 
yellow LED was off while the green LED(s) showed the connection status 
of the adapter. During a ring down the green LED was off and the 
yellow LED was on.

All implementations indicate that a driver is not loaded if all 
LEDs are off.

***End of Readme file***