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

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

SKFPOO.TXT



Readme-File for the SK-NET FDDI PCI Adapter /
Subject: SKFPOO.SYS, OS/2 ODI LAN Driver


Version/ Date/ Author of this file: 1.12 / 97/11/03 / MAl
Version/ Date/ Author of referred subject: v3.00 Rev. A / 26-Nov-1997 / MAl



CONTENTS
========

1	Overview
2	Driver Installation
3	Driver Configuration
4	Driver Parameters
4.1	 General Driver Parameters
4.2	 Advanced Management Parameters
5	Sample Driver Startup Screen Output
5.1	 Startup Error Messages
6	Sample NET.CFG and CONFIG.SYS Files
7	Known Limitations
8	History


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


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

SKFPOO.SYS is an OS/2 ODI LAN device driver which is intended to
operate with SK-NET FDDI PCI adapters on OS/2 Warp 3 and Warp 4. It
may also work on OS/2 v2.0, v2.1, and v2.11. 
You can install up to four adapters in an OS/2 station as long
as their settings do not conflict.

NOTE: The operating system OS/2 1.3x is not supported by this
      device driver.

The driver is built with Novell MSM Support v2.1 and Novell FDDI TSM
Support v1.00 according to Novell's Open Data-Link Interface Developer's
Guide for NetWare OS/2 Workstation Drivers v2.1.

This documentation gives useful hints on the installation and
configuration of this driver to get ODI Driver Interface (MLID)
support on OS/2 workstations.

The driver name for NET.CFG is SKFPOO.
Please make sure your NET.CFG files include the following lines:

		LINK SUPPORT
			BUFFERS 13 4495
***


(2) DRIVER INSTALLATION
=======================

The first step is the installation of the SK-NET FDDI PCI adapter
hardware in your workstation. For more information about this
installation and configuration, refer to the adapter's manual.

When the hardware installation is completed, boot your system and start
the installation of the driver software by copying  SKFPOO.SYS to
the NetWare Requester directory and loading the driver in the CONFIG.SYS
file. You can install the SKFPOO.SYS driver along with the NetWare
Requester for OS/2; or, if you have the NetWare Requester already
installed at your workstation, you can easily switch to the
SKFPOO.SYS driver from any driver used before.

To install SKFPOO.SYS from a diskette drive, a diskette that
contains the driver file in its root directory is required. Therefore
copy the driver file SKFPOO.SYS to the root directory of an empty
diskette.


Follow these steps:

Step 1A) First, install the NetWare Requester.
	 If you have the NetWare Requester already installed,
	 skip to step 1B.

	 Start the <<NetWare Requester for OS/2 Installation Utility>>
	 and follow the installation instructions. The CONFIG.SYS file
	 will have to be changed, and all the NetWare Requester files
	 and the SKFPOO.SYS driver will have to be copied to your
	 hard disk.

	 When the message "Choose the ODI LAN Driver" is displayed, type
	 in the name of the OS/2 ODI LAN driver (SKFPOO.SYS)
	 and continue.

	 If you proceed installation from a diskette drive, insert the
	 diskette (containing the SKFPOO.SYS file in its root)
	 into the drive.

	 Otherwise, the Installation Utility will fail to copy the
	 SKFPOO.SYS driver to the NetWare Requester
	 directory. (Do not try to type "A:\SKFPOO.SYS" or
	 "NOVELL\SKFPOO.SYS"; installation will not work in
	 this way.)

	 Anyway, continue installation. The Installation Utility will
	 copy the NetWare Requester files to the NetWare Requester
	 directory and prepare CONFIG.SYS to load the SKFPOO.SYS
	 driver and NetWare Requester drivers properly.

	 Skip to step 2.


Step 1B) If you have already installed the NetWare Requester for OS/2
	 on your workstation, start the <<NetWare Requester for OS/2
	 Installation Utility>>. Select the diskette drive as source
	 drive to load the driver file.

	 Now, instead of performing the full installation process,
	 you just have to update your CONFIG.SYS file to load
	 SKFPOO.SYS. Make the respective choices.
	 When the message "Choose the ODI LAN Driver" is displayed,
	 type in the name of the OS/2 ODI LAN driver (SKFPOO.SYS).

	 The Installation Utility will update your CONFIG.SYS file.

	 Continue with step 2.


Step 2) If the Installation Utility has copied the SKFPOO.SYS driver
	to the NetWare Requester directory during step 1A, or if you
	did this manually, skip to step 3.

	Otherwise, you have to restart the Installation Utility.
	Again, start "Requester on Workstation" in the "Installation"
	menu. Select the diskette drive as source drive to load the
	driver file.

	Now you just have to copy the SKFPOO.SYS driver file
	to the NetWare Requester directory. Make the respective choices
	and insert the diskette (containing the SKFPOO.SYS file
	in its root) into the drive.

	The Installation Utility will copy SKFPOO.SYS to the NetWare
	Requester directory.


Step 3) Now, configure the SKFPOO.SYS driver. From the "Configuration"
	menu of the NetWare Requester for OS/2 Installation Utility,
	select "This Workstation".
	Information on driver configuration using the NET.CFG
	configuration file is given in chapter 3 of this documentation
	file.

Step 4) Exit the Installation Utility, check if the FDDI cable is
	connected and reboot the workstation to establish the changes.
***


(3) DRIVER CONFIGURATION
========================

You can override OS/2 ODI LAN driver and OS/2 NetWare Requester
default parameters via a NET.CFG file. The NET.CFG file is a text
type file that can be created/edited by any text editor or by the
NetWare Installation Utility.

This chapter gives you all instructions to specify the
important parameters for the OS/2 ODI LAN driver.
A detailed description of all driver parameters is given in
chapter 4 "DRIVER PARAMETERS".

Please refer also to the <<NetWare Client for OS/2 User Guide>>,
"Configuring NetWare Client for OS/2" for creating, editing
and formatting requirements of the NET.CFG file.


Step 1) Configure the number of the communication buffers used by the
	NetWare Client.

Syntax: LINK SUPPORT
		BUFFERS 13 4495

NOTE:	The total memory range occupied by buffers cannot exceed 64 KB.
	The header information takes 5 KB. Hence, the number of buffers
	multiplied by the buffer size must be less than or equal
	to 60,415 Bytes. The SK-NET FDDI PCI adapter need buffers
	of the whole FDDI frame size plus 4 Bytes, that's 4495 Bytes
	per buffer.
	The statement "BUFFERS 13 4495" tells the requester to allocate
	13 buffers, each having 4495 Bytes. Therefore, this statement will
	allocate 58435 bytes of memory for communication buffers. To get
	a high performace, it is necessary to use a large buffer size.


Step 2) If your network uses other frame types than FDDI_802.2 or more
	than one frame type, the parameter FRAME <frame type> must be
	specified. Otherwise, skip to step 3.

Syntax: LINK DRIVER SKFPOO
		FRAME FDDI_SNAP
		FRAME FDDI_802.2

	The default frame type is FDDI_802.2. The driver supports the
	frame types FDDI_802.2 and FDDI_SNAP.


NOTE:	The frame type transmitted by the workstation should match the
	type of packets being transmitted by the server. For
	server attachment, the OS/2 workstation uses the first frame
	type specified in the LINK DRIVER section per default (can be
	overwritten with the parameter PROTOCOL).


Step 3) If you have installed more than one SK-NET FDDI PCI adapter
	in your workstation, you have to specify the parameter SLOT.
	If you have only one adapter installed, you can finish the
	configuration and reboot your workstation to establish the
	changes.

Syntax: LINK DRIVER SKFPOO
		SLOT 2

	LINK DRIVER SKFPOO
		SLOT 3

	parameter	default value	accepted values
	-----------------------------------------------
	 SLOT		    none	 1 to 4
***


(4) DRIVER PARAMETERS
=====================

(4.1) GENERAL DRIVER PARAMETERS

FRAME

Description:	Frame type used by the driver.
Help:	The default frame type for NetWare IPX is FDDI_802.2.
	The NetWare Server and the OS/2 workstation must use the
	frame type, otherwise they cannot communicate with each
	other. For server attachment, the OS/2 workstation
	uses the first frame type specified in the LINK DRIVER
	section.

Syntax: LINK DRIVER SKFPOO
		FRAME FDDI_802.2
		FRAME FDDI_SNAP


NODE ADDRESS

Description:	 Overwrites the network adapter's node address
Help:	With this parameter, you can overwrite the default node address.
	In a network, every adapter must have its own and unique node
	address. A node address consists of 12 hexadecimal bytes.
	You have to specify the node address in canonical format.
	At the driver startup, the adapter's node address is
	displayed on the screen.

NOTE:	Do not specify multicast or broadcast addresses for the
	parameter NODE ADDRESS.
NOTE:	The Locally Administrated Bit of your specified node address
	should be set. This is bit 1 of the first byte of the node
	address.

Syntax: LINK DRIVER SKFPOO
		NODE ADDRESS 02005a401234


SLOT

Description: Defines the slot in which the adapter is installed.
Help:	If you do not specify a slot number, the driver scans
	automatically for an SK-NET FDDI PCI adapter and prompts
	the slot number in which the adapter is found with the driver
	output on workstation startup. The valid range for this
	parameter reaches from 1 to 4.
NOTE:	Specifying the parameter SLOT is mandatory if more than one
	SK-NET FDDI PCI adapter is installed in the same computer.

Syntax: LINK DRIVER SKFPOO
		SLOT 2
***


(4.2) ADVANCED DRIVER PARAMETERS

This section will give you a list of the advanced parameters established
in the OS/2 ODI LAN driver. These parameters will give access to the
FDDI Station Management (SMT).

The SMT parameters are divided into three groups:

      - General SMT parameters
      - Synchronous Bandwith Allocator (SBA) parameters
	for configuring the SBA
      - End Station Support (ESS) parameters
	for using synchronous bandwidth

The SBA is not established in the OS/2 ODI LAN driver. Therefore,
the SBA parameter are not supported by this driver.

Follows a list and a short description for each supported parameter.
Supported general SMT parameters by this driver:

parameter	short description
-----------------------------------------------------------------------------
PmfPassWd	Password for Parameter Management Frames (PMF) Set Requests
UserData	SMT User Data
LerCutOffA	Link Error Rate that removes port A (or port S)
LerCutOffB	Link Error Rate that removes port B (or port S)
LerAlarmA	Link Error Rate that signals an alarm at port A (or port S)
LerAlarmB	Link Error Rate that signals an alarm at port B (or port S)
TMin		minimum allowed value for the Token Rotation Timer (TRT)
TMax		maximum allowed value for the Token Rotation Timer
TReq		requested Target Token Rotation Time (TTRT)
TVX		control of the recovery time from transient ring errors
-----------------------------------------------------------------------------


ESS parameters supported by this driver:

parameter	short description
-----------------------------------------------------------------------------
SbaPayLoad	requested synchronous bandwidth for static allocation
SbaOverHead	requested overhead for static allocation
MaxTNeg 	maximum token rotation time delay
MinSegmentSize	minimum synchronous segmentation size
SbaCategory	session ID for the static allocation
SynchTxMode	synchronous transmission mode
-----------------------------------------------------------------------------

NOTE:	A detailed description of each parameter is given in the
	SMTDOCU.TXT file in the root of this diskette.

To specify an advanced driver parameter in the Link Driver Section, you
have to type the keyword SMT followed by the parameter name and the
parameter value. Parameter values which are strings and including white
spaces, should be set in quotation marks.

Syntax: 	SMT <parameter name> <parameter value>

Some Examples:

LINK DRIVER SKFPOO
	SMT UserData "PC 1, Warp 3, etc."
	SMT TMin     5
	SMT TMax     100
	SMT Treq     10
***


(5) SAMPLE DRIVER STARTUP SCREEN OUTPUT
=======================================

The following section contains sample driver output as it may
appear during workstation startup.

Follows a sample SKFPOO.SYS driver startup output that may result
from these NET.CFG settings:

LINK DRIVER SKFPOO
	FRAME FDDI_SNAP
	SLOT 2
_____________________________________________________________________________

SK-NET FDDI PCI MLID  v3.00 Rev. A (971126)
(C) Copyright 1993-1997 SysKonnect. All Rights Reserved.

Adapter 1, Slot 2
Int 11, Port FF00, DMA Not Used, Mem Not Used
Max Frame 4195 Bytes, Line Speed 100 Mbps, Node Address 00005A40000A
Board 1, Frame FDDI_SNAP
_____________________________________________________________________________

Of course, this output may vary on different configuration settings.
If you have more than one SK-NET FDDI PCI adapter installed in one
workstation, each instance of the driver will return individual
information.


(5.1) STARTUP ERROR MESSAGES

If there are any initialization errors, an error code will be printed
past the above output, followed by a short error message. In case of
an error, some of the resource values given in the output may not yet be
set correctly. For example, if no adapter had been found, the output
would be similar to the following example:

_____________________________________________________________________________

SK-NET FDDI PCI MLID  v3.00 Rev. A (971126)
(C) Copyright 1993-1997 SysKonnect. All Rights Reserved.

Adapter 1, Slot 2
Int 11, Port FF00, DMA Not Used, Mem Not Used
Max Frame 4195 Bytes, Line Speed 100 Mbps, Node Address 00005A40000A
Board 1, Frame FDDI_SNAP
SKFPOO OS/2-No SK-NET FDDI PCI adapter found.
SYS1201: The device driver "C:\NETWARE\SKFPOO.SYS" specified in the DEVICE
command on line 73 of the CONFIG.SYS file was not installed. Line 73 is
ignored.

Press Enter to continue.
_____________________________________________________________________________

In this case, the INT, DMA and Node Address values given are invalid
since the driver does not set appropriate values for a non-existing
adapter. The driver will not be loaded, and in consequence, neither
the LSL, IFS.SYS, and NetWare Requester drivers will be loaded.

The following list holds example error messages that may occur on
SKFPOO.SYS driver startup. If one of these errors occurs,
take a look of this describtion for error detection and problem fixing:


Message: LSL support module not installed.

Reason: The driver cannot bind to the LSL module.
Help:	Verify that the statement to load the LSL module in the
	CONFIG.SYS file is placed before the driver statement.


Message: No SK-NET FDDI PCI adapter found.

Reason: The driver did not find an SK-NET FDDI PCI adapter which
	it was able to use. Perhaps you have specified a wrong
	value for the parameter SLOT?
Help:	Check the hardware configuration (system configuration).
	Refer section (3) and (4) for hints about using NET.CFG.


Message: More than one SK-NET FDDI PCI adapter found.

Reason: The driver found more than one SK-NET FDDI PCI adapter during
	EISA or Micro Channel slot search. Thus, it could not decide
	which one to use actually.
Help:	Select one of the adapters by setting a SLOT <slot number> entry
	into the LINK DRIVER SKFPOO section of your NET.CFG file.


Message: CFG_CARD_EN bit not set!

Reason: The SK-NET FDDI PCI adapter was not properly installed by the
	system configuration program. The present configuration of
	your adapter is void.
Help:	Restart the conifguration program and configure the adapter
	manually if necessary.


Message: Selected adapter is already in use.

Reason: You have tried to use the same SK-NET FDDI PCI Adapter
	more than once.
Help:	Check the LINK DRIVER sections for the parameter SLOT in your
	NET.CFG file. Each LINK DRIVER section should have different
	values for the parameter slot.


Message: Selected IRQ is in use and not sharable.

Reason: The configured hardware interrupt is already used by
	some other hardware and cannot be shared.
Help:	Run a system configuration utility and solve the interrupt
	conflict.


Message: Invalid Node Override, Group Address bit was set now reset.

Reason: A multicast or broadcast address was specified for
	the parameter NODE ADDRESS. The driver has reset the
	Group Address bit. Example: specified was 03005a401234
				    driver uses   02005a401234
Help:	Reset the Group Address bit for the parameter NODE ADDRESS
	in the NET.CFG file. This is an information message, not
	an error message.


Message: Invalid Node Override, Local Administrated bit was reset now set.

Reason: The Local Administrated bit of the parameter NODE ADDRESS
	was not set. The driver has set this bit. Example:
	specified was 00005a401234
	driver uses   02005a401234
Help:	Set the Local Administrated bit for the parameter NODE ADDRESS
	in the NET.CFG file. This is an information message, not
	an error message.

Message: Warning: Receive buffer size below 4495 Bytes,
		  long frames may not be received.
Help:	Please add the following lines to the net.cfg file.

		LINK SUPPORT
			BUFFERS 13 4495
***


(6) SAMPLE NET.CFG AND CONFIG.SYS FILES
=======================================

This section contains a sample NET.CFG and CONFIG.SYS file.

CAUTION: THE DESCRIBED FILE EXAMPLES ARE FOR INFORMATION ONLY AND SHOULD
	 NOT BE USED AS IS.

----- sample NET.CFG file for two adapters : -----

LINK DRIVER SKFPOO
	FRAME FDDI_802.2
	FRAME FDDI_SNAP
	SLOT 2

LINK DRIVER SKFPOO
	FRAME FDDI_802.2
	FRAME FDDI_SNAP
	SLOT 4

LINK SUPPORT
	BUFFERS 13 4495
----- end of NET.CFG -----------------


----- SAMPLE CONFIG.SYS Entries: -----
These CONFIG.SYS entries will automatically be set by the NetWare OS/2
Requester installation procedure.

REM --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
rem Now comes our OS/2 ODI LAN driver.
DEVICE=C:\NETWARE\SKFPOO.SYS
rem The following line is required only if you want NDIS support.
DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
rem DEVICE=C:\NETWARE\NMPIPE.SYS
rem DEVICE=C:\NETWARE\NPSERVER.SYS
rem RUN=C:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
rem DEVICE=C:\NETWARE\NETBIOS.SYS
rem RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\NETWARE\VIPX.SYS
DEVICE=C:\NETWARE\VSHELL.SYS
REM --- NetWare Requester statements END ---
***


(7) KNOWN LIMITATIONS
=====================

	o Installation and configuration of the ODINSUP protocol driver
	  combined with the OS/2 ODI LAN driver for SK-NET FDDI PCI
	  adapters is not possible, because the ODINSUP protocol driver
	  does not support FDDI frame types.

	o The OS/2 ODI LAN driver does not work with the Source Route
	  Handle ROUTE.SYS, because ROUTE.SYS don't support FDDI
	  frame source routing.

	o Some older versions of the OS/2 NetWare Requester does not
	  work proberly with packet burst. On large file transfers,
	  it may happen, that the transfer ofen makes no progress and
	  it takes a long time to complete the process.
	  If this occurs disable the Packet Burst of the NetWare Client
	  for OS/2 and update your NetWare Requester as soon as possible.
***


(8) HISTORY
=============

v3.00 Rev. A
    New features:
	None.	
    Problems fixed:
	- The driver crashes when receiveing a source routing frame with
	  a source routing field longer than 2 bytes.
    Known limitations:
	None.

v3.00
    New features:
	- The driver supports the SK-NET FDDI PCI Adapter.

*** End of Readme File ***