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

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

UPPSND.TXT

Readme-File for SK-UPPS NDIS Device Driver /
Subject: UPPSND.DOS for adapting NDIS protocol stacks on SK-UPPS drivers.
	


Version / Date / Author of this file: v2.02 / 17-Oct-1995 / RA
Version / Date / Author of the referred subject: v2.10 Rev. A / 17-Oct-1995 /
RA

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

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


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

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


(2) PREREQUISITES
=================

To install NDIS DOS Lan driver you need the following items:

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

- LSP documentation.

- The Option Diskette delivered with the adapter.
***


(3) DRIVER INSTALLATION USING LSP
=================================

Step 1:	Copy the adapter driver files from the adapter
	driver installation diskette to system hard disk:

	- Insert LSP diskette into drive A: and follow LSP instructions.

	- Type at the C:\ prompt A:\DXMAID and press ENTER, then follow the
          instructions given in the LSP documentation.

	- Insert the adapter driver installation diskette into the diskette
	  drive when requested by LSP.

	- LSP asks you to give the path where Network driver files reside
	  on the driver installation diskette, enter the current path.

	- Validate the path: LSP copies the files to hard disk

Step 2:	Configure the adapter:

	- Go to "View/Change parameters" options of the LSP.

	- On panel "configure workstation":
	  you can override default parameters of adapter

Step 3:	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.
***


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

The LANSRVR\DOS subdirectory of the installation diskette 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 MCA LAN Server driver files, e.g., C:\LS:
		MD C:\ <enter>

Step 2:	Insert the SK-NET FDDI MCA Installation Diskette
	into a disk drive, e.g., drive A.

Step 3:	Copy the LAN Server driver files from the SK-NET FDDI MCA
	Installation Diskette to the directory created in step 1
	above, e.g.,
		COPY A:\LANSRVR\DOS\*.* C:\LS <enter>

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

Step 5:	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 6:	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 MCA driver UPPSND.DOS.

Step 7:	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 MCA
	drivers.  Choose, from the list, the driver you want to install.

Step 8:	Complete the LAN Server 4.0 DOS LAN Services installation.
	The menues 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 9:	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 MCA adapters, do not forget to specify
			DEVICE = 2..9
		for the second..nineth driver instance.  LAN Services will
		automatically provide device names UPPSND2$..UPPSND9$ for
		these additional driver instances.

Step 11:Copy the SK-UPPS DLI UPPSFM to your hard disk.

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

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

	  NOTE:	Each time you use the install program the AUTOEXEC.BAT is
		modified so you need to check if the UPPSFM 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
		UPPSFM 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 UPPSFM options:
		DLI Options:
		-u  unload resident DLI
		-o  remote boot support
		-p  max protocols (1..30), default 8
		-c  max multicasts (1..20), default 8
		-a  node address (hex), default ROM
		-k  DECnet node address (e.g. -k8.133), no default
		-x  service interrupt (hex), default 7Ch

		Driver Options:
		-s  current Slot (1..8)
		-r  number of receive buffers (1..7), default 2
		-t  number of transmit buffers (1..7), default 2

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

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


(5) DRIVER SPECIFIC PARAMETERS
==============================

Follows a list of parameters (including their values) you can modify
via LSP.

Example section for the NDIS/DOS driver in PROTOCOL.INI:

    [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:

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"

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 NDIS 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).


*** End of information file ***
