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


Readme-File for SK-NET NDIS and ODI Device Drivers /
Subjects: 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 /

This file contains
(1) Overview
(2) Installation instructions for the NDIS2 driver
(3) Installation instructions for NetWare support
(4) List of the NDIS2 driver specific parameters



This README explains how to install the SK-UPPS drivers UPPSND.DOS and
UPPSMLID.EXE under Microsoft Windows for Workgroups (WfW) 3.11.


To install the driver, you need the following items:

- the WfW Setup
- the installation medium (disk, CD-ROM, or network drive)

Follow these steps:

Step 1:	Start the WfW Setup program.

Step 2:	During the installation SETUP asks you for a network adapter

Step 3:	Select "Unlisted or Updated Network Adapter" in the list of network
	adapters (first line of the list).

Step 4:	Choose the correct path to the driver on your installation medium
	(e.g. drive:\[path]\WINDOWS\WFW311) and press ENTER.

Step 5:	Select the driver name shown by using ENTER.

Step 6:	SETUP installs the selected driver on your computer.

Step 7:
	You may run the SK-UPPS installation program AFTER the installation
	of WfW to configure the DLI.

	  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.



Step 1:	Install the ODI driver under DOS using support for MS Windows
	(see instructions in the ODI directory).


Due to the multi-protocol abilities of the UPPS architecture it is possible
to connect to a NetWare server under DOS and to additionally connect to
other Windows stations under WfW, although the Windows protocol drivers
do not support FDDI directly.

Step 1:	Install the ODI driver under DOS using support for MS Windows
	(see instructions in the ODI directory).

Step 2:	In the Network Setup, choose "Network".

Step 3:	Select "Install Microsoft Windows Network" and, as "Other" Network,
	"Novell NetWare ...".

Step 4:	Install the NDIS2 driver under WfW 3.11 (see above).  The driver
	should bind to IPX/SPX Compatible Transport with NETBIOS and to
	Microsoft NETBEUI.

Step 5:	Under Configure choose "Real Mode NDIS Driver".
	Under Configure\Advanced... verify, that "Topology" is set to
	Ignore the following 2 warnings (choose OK).

Step 6:	Ensure that UPPSFP is still loaded before any network ist started
	(e.g. it could be the first command in the AUTOEXEC.BAT).

Step 7:	Execute Step 7 of section (2).

At the next restart, NetWare support will be loaded automatically together
with WfW 3.11.


The following driver specific parameters are defined for UPPSND.DOS:

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

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

                           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

			   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 ***