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

UPPSND.TXT

Readme-File for SK-UPPS NDIS2 device driver /
Subject: UPPSND.DOS for adapting NDIS2 protocol stacks on SK-UPPS drivers.
	


Version / Date / Author of this file: v2.08 / 05-May-1998 / RA
Version / Date / Author of the referred subject: v2.13 / 19-Jan-1998 /
RA

This file contains
(1) Overview
(2) Driver installation using LSP
(3) Driver installation for IBM LAN Server 4.0
(4) Driver specific parameters

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


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

This README explains how to install the SK-UPPS NDIS2 device driver
UPPSND.DOS for the DOS client of the IBM LAN Server.
***


(2) DRIVER INSTALLATION USING LSP
=================================

To install the NDIS2 DOS Device Driver using LSP (LanServer 3.0 DOS
client software) you need the following items:

- LAN Support Program (LSP), LSP 1.3 is the first version supporting FDDI

- LSP documentation.

- The Installation Medium (disk, CD-ROM, or network drive).


Step 1:	Install LSP (insert the LSP diskette into drive A:, type at the
	C:\ prompt
		A:\DXMAID <enter>
	and follow the instructions given in the LSP documentation).

Step 2:	When requested by LSP enter the path where the Network
	driver files reside (e.g. drive:\[path]\LANSRVR\DOS).
	LSP copies the files to hard disk.

Step 3:	To configure the adapter, go to the "View/Change parameters"
	option of the LSP.  On the panel "configure workstation" you can
	override default parameters of the adapter.

Step 4:	When the installation is complete, the Installation Aid returns
	to DOS.  A new AUTOEXEC.BAT and a new CONFIG.SYS have been created.
	If you already had an AUTOEXEC.BAT and a CONFIG.SYS, they have been
	saved with the same file name and a unique numeric extension.

Step 5:	Copy the SK-UPPS DLI UPPSFP to your hard disk.

Step 6:	Modify the new AUTOEXEC.BAT as follows:

	- add at the first line:
		<Path to DLI>\UPPSFP

	  NOTE:	Each time you use the installation program, the
		AUTOEXEC.BAT is modified so you need to check if the
		UPPSFP is still at the first line.

	  NOTE:	If you want to change the SMT parameters, you have to load
		the SMTPARA.EXE program directly after loading the
		UPPSFP driver.  You have to write the path to the file
		OPTIONS.SMT file as parameter in the parameter line of
		SMTPARA.EXE.  All SMT parameters are described in the
		OPTIONS.SMT file.

	- If during the hardware installation you have changed the default
	  parameters you need to specify them to the device driver by using
	  the following UPPSFP options:
		Driver Options:

Step 7:	Reboot your workstation to load and start the adapter.

	WARNING: If you have installed your adapter at interrupt level 9
		 check that no other adapter in the host uses interrupt
		 level 2.  If these two interrupts are used simultaneously
		 you can get software problems.
***


(3) DRIVER INSTALLATION FOR IBM LAN SERVER 4.0
==============================================

To install the NDIS2 DOS Device Driver for usage with IBM LAN Server 4.0
DOS client software you need the following items:

- LAN Server 4.0 DOS LAN Services Diskettes 1-4 or LAN Server 4.0 CD

- The Installation Medium (disk, CD-ROM, or network drive).


The LANSRVR\DOS subdirectory of the installation medium contains all files
that are required for IBM DOS LAN Services support (LAN Server 4.0
DOS Clients).

To install the driver for IBM LAN Server 4.0 DOS LAN Services, use the
IBM INSTALL.EXE program on the IBM LAN Server 4.0 DOS LAN Services disk 1.
The following procedure is recommended by IBM:


Step 1:	Create a directory in the root of your fixed disk for temporary use
	for the SK-NET FDDI PCI NDIS2 driver files, e.g., C:\LS:
		MD C:\LS <enter>

Step 2:	Copy the LAN Server driver files from the SK-NET FDDI PCI
	Installation medium to the directory created in step 1
	above (e.g. COPY drive:\[path]\LANSRVR\DOS\*.* C:\LS <enter>).

Step 3:	Insert the IBM LAN Server 4.0 "DOS LAN Services Installation Disk 1"
	into the disk drive, e.g., drive A.

Step 4:	Start INSTALL.EXE:
		INSTALL.EXE <enter>
	INSTALL will ask you to input the directory where to install
	DOS LAN Services (do NOT use the directory you created in step 1
	above!), checks your current configuration, and then gives you a
	list of network adapters for installation.

Step 5:	Choose, from the list,
		"Network card not shown in list below ..."
	and you will be prompted for the location of the OEMSETUP.INF
	file for the SK-NET FDDI PCI driver UPPSND.DOS.

Step 6:	Enter the fully-qualified path (including drive letter) to the
	fixed disk directory created in step 1 above (e.g. C:\LS <enter>).
	and you will be given a list of available SK-NET FDDI PCI
	drivers.  Choose, from the list, the driver you want to install.

Step 7:	Complete the LAN Server 4.0 DOS LAN Services installation.
	The menus will allow you to select a proper driver configuration.
	There is online help available to every driver parameter.
	LAN Services INSTALL.EXE will modify CONFIG.SYS and PROTOCOL.INI
	automatically according to the driver configuration you selected.

Step 8:	Delete the directory created in step 1 above, e.g.,
		DEL C:\LS <enter>
		RD C:\LS <enter>


	NOTE:	If you want multiple UPPSND.DOS drivers to run multiple
		SK-NET FDDI PCI adapters, you have to modify
		PROTOCOL.INI manually.
		Remember to set the DRIVERNAME for the second..nineth
		driver instance to UPPSND2$..UPPSND9$.

Step 9:	Copy the SK-UPPS DLI UPPSFP to your hard disk.

Step 10:Modify the new AUTOEXEC.BAT as follows:

	- add at the first line:
		<Path to DLI>\UPPSFP

	  NOTE:	Each time you use the installation program, the
		AUTOEXEC.BAT is modified so you need to check if the
		UPPSFP is still at the first line.

	  NOTE:	If you want to change the SMT parameters, you have to load
		the SMTPARA.EXE program directly after loading the
		UPPSFP driver.  You have to write the path to the file
		OPTIONS.SMT file as parameter in the parameter line of
		SMTPARA.EXE.  All SMT parameters are described in the
		OPTIONS.SMT file.

	- If during the hardware installation you have changed the default
	  parameters you need to specify them to the device driver by using
	  the following UPPSFP options:
		Driver Options:

Step 11:Reboot your workstation to load and start the adapter.

	WARNING: If you have installed your adapter at interrupt level 9
		 check that no other adapter in the host uses interrupt
		 level 2.  If these two interrupts are used simultaneously
		 you can get software problems.
***


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

Follows a list of parameters (including their values) you can modify
via the installation utility.

Example section for the NDIS2 DOS driver in PROTOCOL.INI (the section name
will differ in various versions of LAN Server):

    [UPPSND_MOD]
            DriverName    = "UPPSND$"
            NDISREVISION  = "2.0.2"
	    NETADDRESS    = "400000000B03"
	    TOPOLOGY      = "FDDI"
	    EMULATE       = "TokenRing"
            FORCEFEEDBACK = "YES"

[UPPSND_MOD] is the name of the driver section in the PROTOCOL.INI file.
Drivers that depend on this driver must refer to this name with the option:

        BINDINGS = "UPPSND_MOD"


The following driver specific parameters are defined (if a single parameter
is not shown in the installation program, you may enter it manually in the
PROTOCOL.INI file):

DriverName = "UPPSND$"   : Defines the logical name of the driver.
			   This parameter is mandatory.

Topology = "FDDI"	 : Defines the topology the board is running on.

			   Possible values : "FromDLI", "Ethernet",
					     "FDDI", "TokenRing"
			   Default value   : "FromDLI"

Emulate = "TokenRing"	 : Defines the emulation that is used by the
			   driver on FDDI.

			   Possible values : "TokenRing", "Ethernet"
			   Default value   : "TokenRing"

			   NOTE: TokenRing emulation can not be
				 used with the IPX protocol.
				 Use Ethernet instead.

MaxFrameSize = nnnn	 : Can be used to decrease the maximum packet
			   size (on FDDI only).  The Microsoft network
			   client 3.11 with IPX protocol sets the
			   packet size 30 bytes larger than the value
			   given by the driver.  Setting MaxFrameSize
			   to a value 30 bytes smaller than the maximum
			   size for the emulated medium solves this.

SrcRtg = "No"		 : Defines that source routing info is to be
			   deleted when a packet is sent.

			   Possible values : "No", <other>
			   Default value   : <parameter absent>

ForceFeedback = Yes	 : Forces the driver to return a packet to the
			   DLI driver, even if the packet was processed (or
			   an application mistakenly indicates it, like
			   BANYAN VINES or WOLLONGONG TCP do in some cases).
			   Other DLI clients can now use this packet
			   correctly.

NDISRevision = "2.0.2"	 : The UPPSND NDIS2 driver is loaded by default
			   as an NDIS 2.0.1 driver.  This can be changed
			   to NDIS 2.0.2 with the NDISREVISION parameter.

NetAddress = <addr>[L|M] : The logical net address can be changed with the
			   NETADDRESS parameter.

			   <addr> has to be a 12 character HEX string.

			   L and M are optional parameters:

			   L means the address is in LSB mode
			   (least significant bit, standard on Ethernet).

			   M means the address is in MSB mode
			   (most significant bit, standard on Token Ring).

			   The default setting on FDDI depends on the
			   selected emulation.

                           The driver must know the topology, therefore
			   this parameter must not be used together with
			   the setting TOPOLOGY = FROMDLI.

			   At least one bit of the address must be set.
			   The multicast bit must not be set.

			   NOTE: The net address can only be set in
				 this way, if the UPPSND.DOS driver is the
			   	 first client that is registered by the DLI
				 driver.

			   Default value : address given by DLI parameter
					   -a or ROM address of the board
					   if -a parameter is omitted.
	
NetStatusMask = "mmmmmmmmmmmmmmmm" :
			   With NETSTATUSMASK, you can switch off the
			   Network Status Events on Token Ring and FDDI bit
			   by bit.
			   "m" has to be "0" (off) or "1" (on).
			   Use this parameter only for testing
			   (e.g. MtTool).

FIX = n :		   A bitmask to change some internal behavior of
			   the driver. May be entered as a number (e.g. 3)
			   or as a bitstring (e.g. "011").
			   Bit 0 (least significant) avoids crashes
			   caused by a stack overflow problem (observed
			   only with MtTool 3.0).
			   Bit 1 will let the driver queue packets
			   internally.  MS network client 3.11 with IPX
			   stopped working if out of send buffers.
			   The other bits are not used and should be 0.
			   Try those switches only if you experience
			   crashes or system stops.

*** End of information file ***