             +++++++++++++++++++++++++++++++++              ++++
           ++++++++++++++++++++++++++++++++++++           +++++++
          +++++++++++++++++++++++++++++++++++++         ++++++++
          ++++++++++++++++++++++++++++++++++++        ++++++++
                                                   ++++++++
                                                  ++++++++
          +++++++++++++++++++++++++++           ++++++++
          +++++++++++++++++++++++++++++       ++++++++
           +++++++++++++++++++++++++++++     ++++++++
             +++++++++++++++++++++++++++     ++++++++
                                              ++++++++
                                               ++++++++
    ++++++++++++++++++++++++++++++++++++        ++++++++
   +++++++++++++++++++++++++++++++++++++         ++++++++
   ++++++++++++++++++++++++++++++++++++           ++++++++
    +++++++++++++++++++++++++++++++++               +++++

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

Readme-File for 32 bit ODI HSM Driver for SK-NET FDDI MCA adapters
	 on NetWare 4.1x servers. /
Subject: SKFMNW.LAN 32 bit ODI HSM Driver corresponding to the
	 Driver Specification Version 3.3 as specified in
	 document version 3.00 from September 26, 1995 with Addendum 2
	 from February 2, 1996.
	

Version / Date / Author of this file: v2.13 / 26-Jun-1996 / RA
Version / Date / Author of the referred subject: v4.11 / 17-May-1996 /
RA


This file contains
(1) Overview
(2) Required files
(3) Installation instructions
(4) Driver parameters
(5) History
(6) Support for frame type FDDI_RAW

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


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

This README explains how to install the SKFMNW.LAN driver at a
NetWare 4.1x server.
You can install up to four adapters as long as their settings do
not conflict.
Starting with version 4.00 the driver supports Synchronous FDDI.
In this mode each station can reserve part of the total bandwidth.
This is especially useful for video and multimedia applications.
***


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

- NBI.NLM (version 1.44 or higher)

- MSM.NLM (version 3.15 or higher)

- FDDITSM.NLM (version 3.09 or higher)

- SKFMNW.LAN
***


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

Step 1:	Installing the driver SKFMNW.LAN for NetWare v4.x may be done
	using INSTALL.NLM.  The installation support file SKFMNW.LDI will
	be used to install the driver.  If you are unsure about how to use
	this NLM, please look into its (printed) documentation or use the
	online help.

NOTE:	If you want NBI.NLM, MSM.NLM and FDDITSM.NLM to be copied to the
	system directory, provide INSTALL with the full path to the LAN
	driver (after you hit <INSERT>).  If you do not want (some of)
	these files to be replaced, press <ESC> when you are asked if the
	existing file should be saved.

Step 2:	Choose "Edit STARTUP.NCF" option.

Step 2a:
	Ensure that
		MAXIMUM PHYSICAL RECEIVE PACKET SIZE
	is set to 4491 or higher.
	If this is not already done, add the following line to STARTUP.NCF:
		SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 4491

Step 2b:
	If you changed STARTUP.NCF, save it and restart the server.
***


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

STANDARD PARAMETERS
-------------------

- SLOT = [Slot Number]
	Description:    "Defines the slot in which the network adapter is
			 installed."
	Help       :    "This parameter is required for SK-NET FDDI MCA
			 adapters.  If you do not enter a slot number, the
			 driver scans automatically for SK-NET FDDI MCA
			 network adapters and prompts the slot number in
			 which the network card is found at the server
			 console."
	Example    :
			 LOAD SKFMNW SLOT=5
			 BIND IPX to SKFMNW NET=0815

- FRAME = [FDDI_802.2|FDDI_SNAP]
	Description:    "Set the frame type on the network."
	Help       :    "The default frame type for NetWare IPX is
			 FDDI_802.2.  If you want to use TCP/IP or
			 AppleTalk, load the FDDI_SNAP frame additionally.
			 The NetWare Server and the Workstations must use
			 the same media frame and frame type.  Otherwise
			 they cannot communicate with each other.
			 FDDI_802.2 uses type code E0.
			 FDDI_SNAP uses type code 8137."
	Example    :
			 LOAD SKFMNW FRAME=FDDI_SNAP
			 BIND IPX to SKFMNW NET=0815

- NODE
	Description:    "Overwrites the network card address."
	Help       :    "With this parameter you can overwrite the default
			 node address.  In a network, every network card
			 must have its own unique node address.  A node
			 address is a value of 6 hex words.  The first hex
			 word must be even (else it would be a multicast
			 address)."
	Example    :
			 LOAD SKFMNW ... NODE=00005A123456
			 BIND IPX to SKFMNW NET=0815

- NAME
	Description:     "Specify a logical name for the driver."
	Help       :     "With this parameter you can assign a logical name
			  to the network driver."
	Example    :
			 LOAD SKFMNW ... NAME=NWCardOne
			 BIND IPX to NWCardOne NET=0815

- NO_MULTICAST
	Description:    "Converts multicast addresses to the broadcast
			 address."
	Help       :    "If the keyword NO_MULTICAST is used, all multicast
			 addresses will be converted to the broadcast
			 To set this parameter in the install programm, set
			 YES in the NO_MULTICAST field."
	Example    :
			 LOAD SKFMNW ... NO_MULTICAST
			 BIND IPX to SKFMNW NET=0815


SMT PARAMETERS
--------------

- PMFPASSWD
	Description:    "Password for PMF Requests."
	Help       :    "This keyword defines the password that all remote
			 PMF (Parameter Management Frame) requests must
			 provide to change FDDI attributes within the
			 adapter.  The value for PMFPASSWD is 8 ASCII
			 characters long and not case sensitive since lower
			 case letters will be converted to upper case.
			 Password protection can be disabled by setting
			 this keyword to all zeros (default), or by not
			 specifying a PMFPASSWD."
	Example    :
			 LOAD SKFMNW ... PMFPASSWD=12345678
			 BIND IPX to SKFMNW NET=0815

- USERDATA
	Description:    "SMT User Data."
	Help       :    "This keyword provides local write access to the
			 User Data attribute, registered as fddiSMT 17 in
			 the SMT Standard.
			 The User Data must be an ASCII string for
			 compliance with the FDDI SMT standard."

- LERCUTOFFA
	Description:    "SMT LER Cutoff attribute Port A."
	Help       :    "This keyword provides local write access to the
			 LER Cutoff attribute, registered as fddiPORT 58 in
			 the SMT standard.  This attribute identifies the
			 excessive Link Error Rate that removes Port A/B
			 (or Port S).
			 This keyword is specified as an absolute value of
			 the base 10 logarithm of the LER Cufoff value.
			 The valid range reaches from 1E-4 to 1E-15.  If a
			 value is specified which lies outside the limits,
			 the upper/lower limit will be taken.  If no value
			 is specified, the default value for
			 LERCUTOFFA/LERCUTOFFB (1E-7) will be used."

- LERCUTOFFB
	Description:    "SMT LER Cutoff attribute Port B."
	Help       :    "This keyword provides local write access to the
			 LER Cutoff attributes, registered as fddiPORT 58
			 in the SMT standard.
			 This attributes identifies the excessive Link
			 Error Rate that removes Port A/B (or Port S).
			 This keyword is specified as absolute value of the
			 base 10 logarithm of the LER Cufoff value.
			 The valid range reaches from 1E-4 to 1E-15.  If a
			 value is specified which lies outside the limits,
			 the upper/lower limit will be taken.  If no value
			 is specified, the default value for
			 LERCUTOFFA/LERCUTOFFB (1E-7) will be used."

- LERALARMA
	Description:    "SMT LER Alarm attribute Port A."
	Help       :    "This keyword provides local write access to the
			 LER Alarm attribute, registered as fddiPORT 59 in
			 the SMT Standard.
			 This attribute identifies the excessive Link Error
			 Rate that shows an alarm at Port A/B (or Port S).
			 This keyword is specified as an absolute value of
			 the base 10 logarithm of the LER Alarm value.
			 The valid range reaches from 1E-4 to 1E-15.
			 If a value is specified which lies outside
			 the limits, the upper/lower limit will be taken.
			 If no value is specified, the default value for
			 LERALARMA/LERALARMB (1E-8) will be used."

- LERALARMB
	Description:    "SMT LER Alarm attribute Port B."
	Help       :    "This keyword provides local write access to the
			 LER Alarm attribute, registered as fddiPORT 59 in
			 the SMT standard.
			 This attribute identifies the excessive Link Error
			 Rate that signals an alarm at Port A/B
			 (or Port S).
			 This keyword is specified as absolute value of the
			 base 10 logarithm of the LER Alarm value.
			 The valid range reaches from 1E-4 to 1E-15.  If a
			 value is specified which lies outside the limits,
			 the upper/lower limit will be taken.  If no value
			 is specified, the default value for
			 LERALARMA/LERALARMB (1E-8) will be used."

- TMIN
	Description:    "SMT T-Min attribute."
	Help       :    "This keyword provides local write access to the
			 2's complement T-Min attribute, registered as
			 fddiMAC 55 in the SMT standard.
			 The value for TMIN is specified in milliseconds.
			 The valid range reaches from 5 ms to 165 ms.  If a
			 value is specified which lies outside the limits,
			 the upper/lower limit will be taken.  If no value
			 is specified, the default value for TMIN (5 ms)
			 will be used."

- TMAX
	Description:    "SMT T-Max attribute."
	Help       :    "This keyword provides local write access to the
			 2's complement T-Max attribute, registered as
			 fddiMAC 53 in the SMT standard.
			 The value for TMAX is specified in milliseconds.
			 The valid range reaches from 5 ms to 165 ms.  If a
			 value is specified which lies outside the limits,
			 the upper/lower limit will be taken.  If no value
			 is specified, the default value for TMAX (165 ms)
			 will be used."

- TREQ
	Description:    "SMT T-Req attribute."
	Help       :    "This keyword provides local write access to the
			 2's complement T-Req attribute, registered as
			 fddiMAC 51 in the SMT standard.
			 The value for TREQ is specified in milliseconds.
			 The valid range reaches from 5 ms to 165 ms.  If a
			 value is specified which lies outside the limits,
			 the upper/lower limit will be taken.  If no value
			 is specified, the default value for TREQ (165 ms)
			 will be used."

- TVX
	Description:    "SMT TVX attribute."
	Help       :    "This keyword provides local write access to the
			 TVX attribute, registered as fddiMAC 54 in the SMT
			 standard.
			 This attribute provides local control of the
			 recovery time from transient ring errors.
			 The value for TVX is specified in microseconds.
			 The valid range reaches from 2500 us
			 (microseconds) to 10000 us.  If a value is
			 specified which lies outside the limits, the
			 upper/lower limit will be taken.  If no value is
			 specified, the default value for TVX (2700 us)
			 will be used."


SBA PARAMETERS
--------------

- SbaCommand
	Description:	"STARTs or STOPs the SBA application."
	Help	   :	"This keyword is an SBA local action to start or
			 stop the SBA application.  The default value is
			 'STOP'.
			 NOTE:	There should be only one active SBA
				application per ring."

- SbaAvailable
	Description:	"Sets the bandwidth available for the
			 SBA application."
	Help	   :	"This keyword defines the maximum synchronous
			 bandwidth in percent available for the primary
			 path.  The valid range reaches from 0 - 100
			 percent.  The default value is 50 percent
			 (6.25 MBytes/s).  If a value is specified which
			 lies outside the limits, the upper/lower limit
			 will be taken.  This value remains zero until the
			 SBA application is enabled and active."


ESS PARAMETERS
--------------

- SbaPayLoad
	Description:	"Bandwidth requested for static allocations."
	Help	   :	"This keyword defines the requested synchronous
			 bandwidth for manual static allocations.
			 The valid range reaches from 0 to 1562 bytes
			 per 125 microseconds.  For example, if the
			 required bandwidth is 1 MBit/s (125,000 Bytes/s)
			 the value of the payload is 125,000 * 125E-6 =
			 15.625 round up to 16.  If a value is specified
			 which lies outside the limits, the upper/lower
			 limit will be taken.  The default value is zero -
			 no synchronous bandwidth is used.  The user is
			 required to define the amount of bandwidth to be
			 able to send synchronous frames.  If the keyword
			 SbaPayLoad is not specified, the keywords
			 SbaOverHead, MaxTNeg, MinSegmentSize, and
			 SbaCategory have no effect.  The end station
			 supports either the static allocation model, where
			 the requested payload is specified by the keyword
			 SbaPayload, or the dynamic allocation model, where
			 the required synchronous bandwidth is allocated
			 directly by the multimedia application.
			 Therefore, if a multimedia application is used
			 which can dynamically allocate the bandwidth, the
			 keyword SbaPayLoad should not be specified."

- SbaOverHead
	Description:	"Overhead requested for static allocations."
	Help	   :	"This keyword defines the requested overhead for
			 static allocations.  The valid range reaches from
			 50 to 5000 bytes.  If a value is specified which
			 lies outside the limits, the upper/lower limit
			 will be taken.  The default value is 50 bytes.
			 This keyword has only an effect, if the keyword
			 SbaPayLoad is specified."

- MaxTNeg
	Description:	"Maximum token rotation delay."
	Help	   :	"This keyword defines the maximum token rotation
			 delay acceptable to the application(s) using
			 synchronous bandwidth.  The valid range reaches
			 from 5 ms to 165 ms.  If a value is specified
			 which lies outside the limits, the upper/lower
			 limit will be taken.  The default value is 25 ms.
			 This keyword has only an effect, if the keyword
			 SbaPayLoad is specified."

- MinSegmentSize
	Description:	"Minimum synchronous segmentation size."
	Help	   :	"This keyword defines the minimum synchronous
			 segmentation size.  This value corresponds to the
			 amount of bytes to be transmitted on a per token
			 opportunity.  The valid range reaches from
			 1 to 4478 bytes.  If a value is specified which
			 lies outside the limits, the upper/lower limit
			 will be taken.  This keyword has only an effect,
			 if the keyword SbaPayLoad is specified."

- SbaCategory
	Description:	"Session ID of SBA_Category."
	Help	   :	"This keyword defines the session ID of the
			 SBA_Category for the static allocation.  The valid
			 ranges reaches from 0 to 65535.  If a value is
			 specified which lies outside the limits, the
			 upper/lower limit will be taken.  This parameter
			 has only an effect, if the keyword SbaPayLoad is
			 specified."

- SynchTxMode
	Description:	"Synchronous transmission modes."
	Help	   :	"This keyword defines the synchronous transmission
			 mode.  The default value is 'SPLIT', where only
			 packets identified as synchronous packets shall be
			 transmitted by the synchronous queue.  The other
			 value is 'ALL', where all LLC packets received
			 from upper layers are transmitted via the
			 synchronous queue.  This keyword has only an
			 effect, if the end station support was able to
			 get the required synchronous bandwidth from the
			 SBA."
***


(5) HISTORY
===========

v4.11
    New features:
	- Written to HSM Assembler Spec 3.3 Addendum 2.
    Problems fixed:
        None.
    Known limitations:
	None.
v4.10 Rev. A
    New features:
	- Client 32 support.
    Problems fixed:
	- After a ring op change or a driver reset it may happen, that the
	  FORMAC and the ASIC becomes asynchronous.
	  Possible behaviours are:
      		o PCI bus violations, the machine may hang up.
		o The FORMAC may send frames which will never be stripped
		  by any station after a ring operational change.
	- Only supporting NetWare 3.12 and above (NBI31X does not load on
	  NetWare 3.11).
    Known limitations:
	None.
v4.10
    New features:
	- Written to HSM Assembler Specification 3.3.
    Problems fixed:
        None.
    Known limitations:
	- NBI up to v1.24 does not run under NetWare for OS/2 4.10.
***


(6) SUPPORT FOR FRAME TYPE FDDI_RAW
===================================

As there is a wide base of ETHERNET installations using frame type
ETHERNET_802.3 (ETHERNET_RAW), and this frame type is switched into the
FDDI ring as frame type FDDI_RAW, we also offer a driver version supporting
the FDDI_RAW frame type.  This driver will only run on NetWare servers.
It is not Novell certified.  It is available on our BBS.  Please contact
our hotline if you need this driver.

NOTE:	Using the frame type FDDI_RAW is not recommended, as it is an
	undefined frame type.  Therefore it might cause problems with other
	types of stations in the same ring, at least they will not support
	FDDI_RAW.  Also, Novell does not certify or support drivers using
	frame type FDDI_RAW.

*** End of information file ***
