




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


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

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



SKFDDIFM.TXT



Readme-File for SK-NET FDDI-FM Adapter /
Subject: SKFDDIFM.SYS, OS/2 ODI LAN Driver


Version/ Date/ Author of this file: 1.2 / 95/02/03 / M. Althoff
Version/ Date/ Author of referred subject: v2.00 / April 3, 1995 / M. Althoff


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

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


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


SKFDDIFM.SYS is an OS/2 ODI LAN device driver which is intended to
operate with SK-NET FDDI-FM adapters on OS/2 v2.0, v2.1 and Warp 3.
You can install up to four adapters in a OS/2 station as long
as their settings do not conflict.

NOTE: The operating system OS/2 1.3x is no longer 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 SKFDDIFM.


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

The first step is the installation of the SK-NET FDDI 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  SKFDDIFM.SYS to
the NetWare Requester directory and loading the driver in the CONFIG.SYS
file. You can install the SKFDDIFM.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
SKFDDIFM.SYS driver from any driver used before.

To install SKFDDIFM.SYS from a diskette drive, a diskette that
contains the driver file in its root directory is required. Therefore
copy the driver file SKFDDIFM.SYS to the root directory of an empty
diskette. Otherwise, copy the driver to the directory that contains
(or is designated for) the NetWare Requester, usually, C:\NETWARE.


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 SKFDDIFM.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 (SKFDDIFM.SYS)
         and continue.

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

         Otherwise, the Installation Utility will fail to copy the
         SKFDDIFM.SYS driver to the NetWare Requester
         directory. (Do not try to type "A:\SKFDDIFM.SYS" or
         "OS2\SKFDDIFM.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 SKFDDIFM.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 SKFDDIFM.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
         (SKFDDIFM.SYS).

         The Installation Utility will update your CONFIG.SYS file.

         Continue with step 2.


Step 2) If the Installation Utility has copied the SKFDDIFM.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 SKFDDIFM.SYS driver file to the
        NetWare Requester directory. Make the respective choices and insert
        the diskette (containing the SKFDDIFM.SYS file in its root) into
        the drive.

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

NOTE:   Of course, you can also copy SKFDDIFM.SYS from the SysKonnect
        driver disk to your NetWare Requester directory manually.


Step 3) Now, configure the SKFDDIFM.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 SK-NET 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 SK-NET 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 for OS/2.

Syntax: LINK SUPPORT
                BUFFERS 14 4184

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. FDDI can use a buffer size up to 4491 Bytes.
        However there are combinations of NetWare Servers and OS/2
        NetWare Requesters which reduce the maximum buffer size
        independent of the specified value for the parameter BUFFER.
        The statement "BUFFERS 14 4184" tells the requester to allocate
        14 buffers, each having 4184 Bytes. Therefore, this statement will
        allocate 58576 bytes of memory for communication buffers. To get a high
        performance, 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 SKFDDIFM
                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 network. For
        server attachment, the OS/2 workstation uses the first frame
        type specified in the LINK DRIVER section. Therefore, this
        frame type should also match the frame type of the server.


Step 3) If you have installed more than one SK-NET FDDI-FM 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 SKFDDIFM
                SLOT 2

        LINK DRIVER SKFDDIFM
                SLOT 5

        parameter       default value   accepted values
        -----------------------------------------------
         SLOT               none         1 to 15


(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 SKFDDIFM
                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 SKFDDIFM
                NODE ADDRESS 020005a401234


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-FM 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 15.
NOTE:   Specifying the parameter SLOT is mandatory if more than one
        SK-NET FDDI-FM adapter is installed in the same computer.

Syntax: LINK DRIVER SKFDDIFM
                SLOT 5


        (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 SKFDDIFM
        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 SKFDDIFM.SYS driver startup output that may result
from this NET.CFG settings:

LINK DRIVER SKFDDIFM
        FRAME FDDI_SNAP
        SLOT 2
_____________________________________________________________________________

SK-NET FDDI-FM MLID  v2.00 (950403)
Copyright (C) 1995 SysKonnect. All Rights Reserved.

Adapter 1, Slot 2
Int 11, Port 2200, DMA Not Used, Mem Not Used
Max Frame 4184 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-FM 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-FM MLID  v2.00 (950403)
Copyright (C) 1995 SysKonnect. All Rights Reserved.

Adapter 1, Slot 2
Int 0, Port Not Used, DMA Not Used, Mem Not Used
Max Frame 4184 Bytes, Line Speed 100 Mbps, Node Address FFFFFFFFFFFF
Board 1, Frame FDDI_SNAP
MLI0207: No SK-NET FDDI-FM adapter found.
SYS1201: The device driver "C:\NETWARE\SKFDDIFM.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
SKFDDIFM.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-FDDI-FM adapter found.

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


Message: More than one SK-FDDI-FM adapter found.

Reason: The driver found more than one SK-NET FDDI 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 SKFDDIFM section of your NET.CFG file.


Message: CFG_CARD_EN bit not set!

Reason: The SK-NET FDDI 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 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. The OS/2 ODI LAN driver cannot
        share an interrupt with some other drivers.
Help:   Run the system configuration program and select an other unused
        interrupt. Specify this interrupt in the NET.CFG file.


Message: Invalid OS/2 Version

Reason: The driver can not run under OS/2 1.3x or previous versions of OS/2.
Help:   The operating system OS/2 1.3x is no longer supported by this
        device driver. Please update your operating system.




Message: Memory above 16 MByte, please use 32 Bit Slot.

Reason: The driver has been loaded into a memory area beyond
        16 MBytes, while the adapter has been inserted in a 16-Bit
        Slot and thus cannot be addressed. Consequently, the
        adapter can not operate.
Help:   Install the adapter in a 32-Bit slot.


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 0300005a401234
                                    driver uses   0200005a401234
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 0000005a401234
        driver uses   0200005a401234
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.




(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 SKFDDIFM
        FRAME FDDI_802.2
        FRAME FDDI_SNAP
        SLOT 2

LINK DRIVER SKFDDIFM
        FRAME FDDI_802.2
        FRAME FDDI_SNAP
        SLOT 4

LINK SUPPORT
        BUFFERS 14 4184
----- 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\SKFDDIFM.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
=====================

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

*** End of Readme File ***
