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

skfp.README

Readme File for Driver.o:
	SK-NET FDDI PCI Network driver for SCO OpenServer 5, Version 1.0.4.

December 9, 1997


Version / Date of the referred subject:
	skfp v1.04 / 9-Dec-1997

This file contains :
(1) Overview
(2) Supported Adapters
(3) Installation instructions
(4) Removing the driver
(5) Configuration of an adapter
(6) Deconfigure an adapter
(7) Advanced Device Configuration Parameters
(8) History

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


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

This README explains how to use the SCO Open Server driver 'skfp' with your
network adapter.

Chapter 2 contains a list of all network adapters that are supported by this
driver.

Chapter 3 describes the installation process.

Chapter 4 explains how to remove the driver from your system.

Chapter 5 explains how to configure the adapter.

Chapter 6 explains how to remove a network adapter.

Chapter 7 contains a detailed description of all advanced device
configuration parameters.
***


(2) SUPPORTED ADAPTERS
======================

The network driver 'skfp' supports the following network adapters:

	*) SK-NET FDDI PCI series
***


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

To install the driver from the SCO Desktop carry out the following steps:

Step 1: Start an Open Desktop session by logging in to your system.

Step 2: Double-click the "Software Manager" icon.

Step 3: From the software menue, select "Install new ...".

Step 4: Select the local host for software installation.

Step 5: Select the appropriate installation media.

Step 6: Select the "SK-NET FDDI PCI Network Driver" and click on "install".
        The software package will now be installed.

NOTE:
- You can also run the "custom" - utility from the console login to perform
  the above steps.
- Please also refer to your system documentation.
- The driver release has not been tested with the early release of
  SCO OpenServer 5.0.0. Therefore there is no guarantee for proper
  execution of the device driver on the OS release 5.0.0. It is highly
  recommended that you UPGRADE THE OS RELEASE before installing this
  driver.
***


(4) REMOVING THE DRIVER
=======================

Follow the steps below to remove the network driver from your system:

Step 1: Start an Open Desktop session by logging in to your system.

NOTE:
- You should first deconfigure all network adapters that are configured
  with this network driver.

Step 2: Double-click the "Software Manager" icon.

Step 3: Select the "SK-NET FDDI PCI Network Driver" from the list of
	software.

Step 4: From the software menu, select "Remove Software".

NOTE:
- You can also run the "custom" - utility from the console login to perform
  the above steps.
- Please also refer to your system documentation.
***


(5) CONFIGURATION OF AN ADAPTER
===============================

To configure the adapter for your system, follow these steps:

Step 1: Start an Open Desktop session by logging in to your system.

Step 2: Double-click the "System Administration" icon.

Step 3: Double-click the "Networks" icon.

Step 4: Double-click the "Network Configuration Manager" icon.

Step 5: From the Hardware menu, select "Add a new LAN adapter".

Step 6: Now a list of all boards that were detected and have not yet been
	configured is shown. Please, select the adapter you wish to
	configure from the list. Adapters that are not currently installed
	may also be configured. You will however require the exact bus
	parameters to do so.

NOTE:
- On OpenServer 5.0.2 and prior, only one adapter is auto-detected.
  Please use the "pcislot" command by typing "`llipathmap`/bin/pcislot" to
  determine all network adapters in the system. From the displayed list
  select the vendor and device number of the cards you wish to install.
  Note the bus number and the device number of the cards you wish to
  configure and configure the cards manually.

Step 7: Select the protocol stack to be configured for the adapter.

NOTE:
- If you are running on Open Server 5.0.0 or 5.0.2 and you install the
  TCP/IP protocol stack for the driver, select the "Advanced options" icon
  in the SCO TCP/IP Configuration box and select the Frame Format "802.n"
  for the FDDI network driver.

Step 8: Now you can change the advanced options of the network adapter.
        To do this select "Modify hardware configuration" from the Hardware
	menu.

NOTE:
- If you are running Open Server 5.0.0 or 5.0.2 and you configure TCP/IP
  on top of the network adapter, source routing will be enabled
  automatically. The driver does NOT support source routing. In order to
  work properly, you must disable source routing for each FDDI interface
  configured by editing the file "/etc/conf/pack.d/netX/space.h" and
  setting the SRMODE to 0!
- If you are running Open Server 5.0.4, do NOT change the adavanced
  options here. You need to change the space.h file manually instead!
  But if you install the patch rs5.0.4c the configuration will work
  properly. (See ftp://ftp.sco.com for more infos on available patches.)

Step 9: The last step is to activate the new driver configuration. After
	exiting the Network Configuration Manager the system will prompt
	you to relinking the kernel.
	After relinking the kernel and rebooting the system, the network
	will be availalble and active.

NOTE:
- If you are using the SBA or ESS feature, the driver will start SBA
  immediately at driver initialization. The driver will immedialetly
  request synchronous bandwidth after initialization. Both the SBA and
  ESS may be active on the same network adapter. But only one SBA may
  be active in the  same network. For a description of SBA / ESS
  configuration parameter please refer to section (7).
***


(6) DECONFIGURE AN ADAPTER
==========================

To remove an existing network configuration, perform the following steps:

Step 1: Start an Open Desktop session by logging in to your system.

Step 2: Double-click the "System Administration" icon.

Step 3: Double-click the "Networks" icon.

Step 4: Double-click the "Network Configuration Manager" icon.

Step 5: Select the line displaying the network adapter you wish to
	deconfigure.

Step 6: From the Hardware menu, select "Remove network device" and
	follow the instructions displayed on the screen.

NOTE:
- You can also run the "netconfig" utility from the console login to
  perform the above steps.
***


(7) ADVANCED DEVICE CONFIGURATION PARAMETERS
============================================

Configuration parameters indicated with a '*' are not currently provided
by the driver's configuration environment.

* "USER Data"
User data to be passed to the SMT.
	
* "PMF password"
Parameter Management Frame (PMF) password for the adapter. A nonzero PMF
password enables authorization checking of the adapter for remote change
requests. A PMF password of 0 disables the authorization checking of the
adapter. The PMF password consists of 16 hexadecimal digits. Default value
is 0.

"SMT T-Req"
This parameter provides local write access to the T-Req value that is
registered as fddiMAC 51 in the SMT Standard. The value for T-Req is
specified in milliseconds. The valid range is between 5 ms and 165 ms.
If any value is specified which is outside the limits, the upper/lower
limit will be used. If no value is specified, the default value for T-Req
(165 ms) will be used.

"SMT TVX lower bound"
This parameter 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 is between
2500 us and 10000 us. If a value is specified outside the limits, the
upper/lower limit is used. If no value is specified the default value for
TVX (2700 us) is used.

NOTE:
- Due to hardware limitations the upper value for the TVX attribute is
  restricted to 5200 us. It is recommended to specify a value below this
  limit.

"Alternate MAC/SMT Address"
This address describes the MAC address that is used as the adapter's
alternate network address. A valid address consists of 12 hexadecimal
digits. The default value is none, in which case the adapter's factory
address is used.

"SBA_Payload"
This parameter defines the requested synchronous bandwidth for manual
static allocations. The valid range is between 0 and 1562 bytes per
125 us. For example: if the required bandwidth is 1 MBits/s
(125,000 Bytes/s), the value of the payload is 125,000 * 125E-6 = 15.625
round up to 16. If a value outside the limits is specified, the upper/
lower limit will be used. The default value is zero which means no
synchronous bandwidth is used. The user is required to define the amount of
bandwidth to be able to send  synchronous frames. If this parameter is not
specified, the keyword "SBA_OverHead", "MaxTneg", "MinSegmentSize", and
"SBA_Category" have no effect. The end station supports either the static
allocation model, if the requested payload is specified by the parameter
"SBA_Payload", or the dynamic allocation model, where the required
synchronous bandwidth is allocated by a multimedia application. If a
multimedia application is used that can dynamically allocate the bandwidth,
the parameter SBA_PayLoad should not be specified.

"SBA_Overhead"
This parameter defines the requested overhead for static allocations.
The valid range reaches from 0 to 5000 bytes. If a value is specified
which is outside the limits, the upper/lower limit is taken. The default
value is 50 bytes. This parameter has no effect, unless the parameter
SBA_PayLoad is specified.

"MaxTneg"
This parameter defines the maximum token rotation delay that is acceptable
to the application(s) using synchronous bandwidth. The valid range is
between 5 ms and 165 ms. If a value is specified outside the limits, the
upper/lower limit is used. The default value is 25 ms. This parameter has
no effect, unless the parameter SBA_PayLoad is specified.

"MinSegmentSize"
This parameter defines the minimum synchronous segmentation size. The
value corresponds to the amount of bytes to be transmitted on a per token
opportunity. The valid range is between 1 and 4478 bytes. If a value is
specified which is outside the limits, the upper/lower limit is used. The
parameter has no effect unless the parameter SBA_PayLoad is specified.

* "SBA_Category"
This parameter defines the session ID of the SBA_Category for the static
allocation.The valid range is between 0 and 65535. If a value is specified
which is outside the limits, the upper/lower limit will be taken. This
parameter has no effect, unless the parameter SBA_PayLoad is specified.

"Sync_Tx_Mode"
This keyword defines the synchronous transmission mode. The default value
is "SPLIT" which means that only packets identified as synchronous packets
will be transmitted via the synchronous queue. The other value is "ALL"
which means that all LLC packets received from upper layers are transmitted
via the synchronous queue. This keyword has no effect, unless the end
station support was able to get the required synchronous bandwidth from the
SBA.

"SBA_Command"
This parameter specifies an SBA local action to start/stop the SBA of the
network device. Valid values are "START" and "STOP". The default value is
"STOP".

"SBA_Available"
This parameter specifies the maximum synchronous bandwidth in percent
available for the primary path. If the value is outside the valid range,
the upper/lower limit is used. The valid range is 0-100. The default value
is 50.
***


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

v1.0.4
    New features:
	None.
    Problems fixed:
	- Frames were not looped back correctly.
	- Frames were received with the address in MSB format rather than
	  in canonical format.
	- A full multicast address table was not returned correctly.
	- If you had configured and not configured boards in your machine
	  at the same time, the configured boards did not work correctly.
	- The implementation did not meet some SCO requirements.
    Known limitations:
	None.

v1.0.3
    New features:
	None.
    Problems fixed:
	None.
    Known limitations:
	None.
***