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

(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.00 / 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
(4) Driver specific parameters

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


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

This README explains how to install the SK-UPPS driver UPPSND.DOS
for the DOS client of DEC Pathworks.
***


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

Use the NDIS driver UPPSND.DOS, if you are using DEC Pathworks with
SK-NET Boards.
***


(3) DRIVER INSTALLATION
=======================

Step 1:	Insert the first diskette of DEC Pathworks into the floppy
	drive A: (or B:) and start NETSETUP.

Step 2:	Follow the instructions of NETSETUP.

Step 3:	When NETSETUP asks for a network adapter, select NDIS.
	Type in the correct path to the NDIS driver on the driver diskette
	(A:\PCSA\) and the correct path and name of the PROTOCOL.INI STUB
	file (A:\PCSA\PROTOCOL.INI).

Step 4:	Answer the following questions of NETSETUP.  Finally Pathworks for
	DOS should be installed successfully.


NOTE:	THE DLI driver (UPPSFM) has to be loaded BEFORE starting
	DEC Pathworks for DOS.  All hardware dependent parameters are set
	in the parameter line of the DLI driver.  The DLI driver has to be
	loaded BEFORE any other network driver in the AUTOEXEC.BAT file.


If you want to change the SMT parameters, you have to load the SMTPARA.EXE
program directly after loading the UPPSFE driver.  SMTPARA.EXE can be found
in the \DLI directory on the installation disk.

You have to write the path to the file OPTIONS.SMT file as parameter in
the parameter line of SMTPARA.EXE.  OPTIONS.SMT can be found in the \DLI
directory on the installation disk.  All SMT parameters are described in
the OPTIONS.SMT file.


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

	[UPPSND_NIF]
	DriverName	= "UPPSND$"
	Topology	= "FDDI"
	Emulate		= "TokenRing"
	ForceFeedback	= "YES"

[UPPSND_NIF] 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_NIF"
***


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

Follows a list of parameters (including their values) you can modify
in the PROTOCOL.INI.

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