		Reflection Network Series Product Information
			    3000 Connection Version 2.2
			    Disk 1 - Installation Disk

		(C)opyright 1994 Walker Richer & Quinn Inc.


README         This file.
SETUP.EXE      Installation program.  (Type A:SETUP at the DOS
			prompt.)
OSETUP.EXE     File used for ODI setup.
NSETUP.EXE     File used for NDIS setup.
IPX30.COM      This file communicates to a NetWare network via
			RNDIS.EXE. Renamed to IPX.COM during SETUP (for
			Windows 3.0 users only).
IPX31.COM      This file communicates to a NetWare network via
			RNDIS.EXE. Renamed to IPX.COM during SETUP (if not
			using Windows 3.0).
IPXODI.COM     NetWare IPX support in an ODI environment.
LANTRACE.EXE   WRQ trace program.
LSL.COM        Link Support Layer file provided by Novell; used for
			ODI.
NETBIND.COM    Starts the binding process between all NDIS-compliant
			modules.
PROTMAN.DOS    DOS device driver used to register all NDIS-compliant
			modules.
PROTMAN.EXE    Works with PROTMAN.DOS to bind NDIS-compliant
			modules.
RDLL.EXE       The data link layer between RLAT.EXE and RNDIS.EXE.
RLAT.EXE       Reflection's LAT interface.
RNDIS.EXE      Interface converter between WRQ's packet driver
			interface and Microsoft/3Com's NDIS.
RODI.EXE       WRQ's interface converter between WRQ's packet
			driver interface and Novell's ODI.
RSN.EXE        Manages static/dynamic entries in the LAT service
			table.
SEETRACE.EXE   WRQ's network trace summary program.
SETUP.INI      Setup configuration file.
STAT.EXE       Provides statistical information about TCP/IP
			network activity.
PING.EXE       Program to test network connection over TCP/IP.
TCP2PDIS.EXE   WRQTCP to packet driver interface - ARP and PROBE
			protocols.
WRQHPSO.EXE    WRQ Windows and TCP Sockets interface.
WRQSLIP.EXE    WRQ SLIP driver.
WRQTCP.EXE     WRQ TCP/IP protocol.
WRQTICL.EXE    WRQ NetIPC interface to TCP.

README Table of Contents
========================

What's New in Version 2.2
WRQ's Anonymous FTP Server
/GROUP Switch for NB
Setup Error Message "Unable to add the RNS directory to your DOS PATH..."
Error Message "Cannot find RNNET.DLL"
Replacing HP Network Software With the Reflection Network Series
Additional Keywords Used by WRQSLIP
LAN Manager and 3COM 3C523
Using Reflection Network Series for Windows Applications
  Installing Reflection Network Series for Windows and Reflection Network
    Series for DOS on the Same Machine
Reflection Network Series and PATHWORKS 4.x
  Using WRQ's NetBIOS and TCP/IP as a Transport for PATHWORKS for
    DOS 4.x 
  Using WRQ's TCP/IP in the Same Environment as DECnet 4.x
FTP.EXE (Reflection for Windows Users)
  FTP Command Syntax
RLATCP for LAT

***************************************************************************

What's New in Version 2.2
=========================

*  Windows Sockets support--WRQ's Windows Sockets support lets you run
   Windows Sockets-compatible applications over the Reflection Network
   Series DOS TCP/IP stack.
*  New NetBIOS support--WRQ's new NetBIOS module NB.EXE offers performance
   improvements, and the ability to configure performance and name
   resolution options.
*  Direct support for a wider variety of network cards. 

***************************************************************************

WRQ's Anonymous FTP Server
==========================

WRQ's anonymous FTP server (ftp.wrq.com) can also be used to access the
files on WRQ's BBS.  Technical Notes are in the /bbsfiles/techdocs
subdirectory.  The /bbsfiles/techdocs/00index file gives an index of
Technical Notes.  The /README file provides general information about the
server.

***************************************************************************

/GROUP Switch for NB
====================

The following switch has been added to NB.EXE.

/GROUP
Enables NetBIOS broadcasts for Group names. /GROUP is not necessary for LAN
Manager or Windows for Workgroups; however other applications may require
it. This is a startup switch.

***************************************************************************

Setup Error Message "Unable to add the RNS directory to your DOS PATH..."
=========================================================================

When running Setup, the following error message may appear:

"Unable to add the RNS directory to your DOS PATH without losing current
DOS PATH information."

If you see this message, it means that your DOS PATH in your AUTOEXEC.BAT
file exceeds the 128 character limit. To fix this problem, do one of the
following:

*   Using a text editor, manually edit the DOS PATH in your AUTOEXEC.BAT
    file so that it does not exceed the 128 character limit when the
    Reflection Network Series directory is added.

*   Use the DOS command SUBST to associate your path with a virtual drive.
    See your MS-DOS documentation for more information on using the SUBST
    command.

***************************************************************************

Error Message "Cannot find RNNET.DLL"
=====================================

If the error message "Cannot find RNNET.DLL" appears while loading a
Windows Sockets-compatible application, it means that WRQHPSO has not been
loaded. Exit Windows, confirm that your AUTOEXEC.BAT file includes
STARTNET.BAT, then run STARTNET.BAT from the DOS prompt.

***************************************************************************

Replacing HP Network Software With the Reflection Network Series
================================================================

If you have replaced HP network software (ARPA Services or NS Services, for
example) with the Reflection Network Series, and you see the error message
"Please load WRQHPSO" when starting the Reflection Network Series, make sure
the line that loads TCPDRV.DOS in your CONFIG.SYS file is commented out.

***************************************************************************

Additional Keywords Used by WRQSLIP
===================================

In addition to the keywords listed in "Serial TCP/IP Support: WRQSLIP" in
the Technical Reference, the following keywords are also applicable to
SLIP:


Keyword:                    For more information see:

DNSServerAddr0              Reflection Network Series Technical Reference
DNSServerAddr1              Reflection Network Series Technical Reference
DNSServerAddr2              Reflection Network Series Technical Reference
DNSServerAddr3              Reflection Network Series Technical Reference
DNSServerAddr4              Reflection Network Series Technical Reference
DNSServerAddr5              Reflection Network Series Technical Reference
FileModeMask                NFS Option User Guide
Hook2A                      Reflection Network Series Technical Reference
NFSFileCacheSz              NFS Option User Guide
NFSHostFINameSz             NFS Option User Guide
NFSReadSize                 NFS Option User Guide
NFSWriteSize                NFS Option User Guide
NISDomainName               NFS Option User Guide
NISIPAddress                NFS Option User Guide
NumNBBuffers                Reflection Network Series Technical Reference
NumNBNames                  Reflection Network Series Technical Reference
NumNFSRedirects             NFS Option User Guide
PCNDSHostName               Reflection Network Series Technical Reference
TCPLocalMSS                 Reflection Network Series Technical Reference
TCPRemoteMSS                Reflection Network Series Technical Reference
TCPSessions                 Reflection Network Series Technical Reference
TimeZoneMinutes             NFS Option User Guide

***************************************************************************

LAN Manager and 3COM 3C523
==========================

If you are using the 3C523 card and LAN Manager, we recommend using the
ELNKMC.DOS driver distributed with the Reflection Network Series.  Copy the
ELNKMC.DOS driver located on the "Supported Drivers" disk over the version
installed by LAN Manager.  This should improve your performance running
server applications.

***************************************************************************

Using Reflection Network Series for Windows Applications
========================================================

Some Reflection Network Series for Windows applications can be configured
to use the Reflection Network Series for DOS NetBIOS transport and TCP/IP
stack.  This configuration--which requires modules from both Reflection
Network Series for Windows 4.0 and Reflection Network Series for DOS
2.2--lets you use Reflection Network Series for Windows applications such
as LPR, while providing simultaneous access to NetBIOS applications and the
NFS Option over the DOS TCP/IP stack.

After completing the following installation procedure, the Reflection
Network Series for Windows modules listed below are available when running
over the Reflection Network Series for DOS TCP/IP stack. For information on
configuring and using these applications, refer to the Reflection Network
Series for Windows Technical Reference.

LPD
LPD is a line printer server utility that allows you to configure your
locally attached printer as a network printer available to others on the
network.  

LPR
LPR is a line printer utility that enables you to print on a network
printer. 

FTP Server
FTP Server lets you make your PC files accessible to others on the network.
It includes a user database capability for security and control, activity
logging, and other management features.

FTP Client
FTP CLient lets you connect to an FTP server running on a UNIX, VAX, IBM,
HP, or other host, and use File Transfer Protocol (FTP) to transfer files
between your PC and the host server.

Event Viewer
The Event Viewer is a troubleshooting tool that lets you record and view
events reported by the Reflection Network Series DLL modules. It does not
record events for DOS (TSR) modules.

Finger
Finger is a standard TCP/IP protocol that provides an interface for
querying the current status of a remote host or or a user ID on a remote
host.

Online Help
You can get online Help for each Reflection Network Series application by
opening the application and choosing Help from the application's main menu.
Online Help is not available from the RNS Help icon in the Reflection
Network Series program group, or the Help command in the RNS icon menu.

The following Reflection Network Series for Windows utilities are not
functional when running over the Reflection Network Series for DOS TCP/IP
stack: 

*  PING
*  Network Statistics
*  Network Trace utilities

Installing Reflection Network Series for Windows and
====================================================
Reflection Network Series for DOS on the Same Machine
=====================================================

This configuration requires:

*   One of the following Reflection Network Series for Windows products:

    -   TCP Connection
    -   3000 Connection
    
*   One of the following Reflection Network Series for DOS products:

    -   NS Connection, version 2.2
    -   TCP Connection, version 2.2
    -   3000 Connection, version 2.2

IMPORTANT:
If the Reflection Network Series for DOS is currently installed on your PC,
re-install it AFTER installing the Reflection Network Series for Windows
using the procedure below. That way, the correct versions of the Windows
Sockets modules are used.

To install the Reflection Network Series for Windows and the Reflection
Network Series for DOS on the same PC:

1.  Run the Reflection Network Series for Windows 4.0 Setup program.

    See the Reflection Network Series for Windows Technical Reference for
    more information on running Setup.

2.  Reboot your PC and start Windows.

3.  Click the RNS icon in the Reflection Network Series for Windows program
    group and choose About. In the Information box you'll see a summary of
    your network configuration. The TCP/IP Stack listed here is "RNS for
    Windows".

4.  Exit Windows and run the Reflection Network Series for DOS 2.2 Setup
    program. Be sure to install the Reflection Network Series for DOS into
    the same subdirectory as Reflection Network Series for Windows (\WRQNET
    by default).

    *  When Setup prompts you for Windows Sockets, answer yes.

    *  If you want to use LAN Manager or Windows for Workgroups, see
	  the Reflection Network Series for DOS version 2.2 Technical
	  Reference.

5.  Reboot your PC, run STARTNET.BAT, and start Windows. 

6.  Click the RNS icon on in the Reflection Network Series for Windows
    program group and choose About. In the Information box you'll see a
    summary of your network configuration. The TCP/IP Stack listed here
    should now be "RNS for DOS".

7.  If desired, install the NFS Option. See the NFS Option User Guide for
    more information on running Setup.

NOTE:
When you install the Reflection Network Series for Windows and DOS as
described in the procedure above, the network settings from any current
copy of the Reflection Network Series for DOS on your PC will be used as
the default settings. For example, your IP address, default gateway, subnet
mask, and other settings will reflect the settings already on your PC.

In general, the settings for the Reflection Network Series for Windows are
written to different sections in PROTOCOL.INI or NET.CFG than the settings
for the Reflection Network Series for DOS.  The only exception is the
network card bindings; these are configured in the same way as the
Reflection Network Series for DOS.

When using the Reflection Network Series for DOS TCP/IP stack, your DOS
environment settings will be used. However, any updates you make to
protocol settings after installing the Reflection Network Series for
Windows will not be reflected in your Reflection Network Series for DOS
configuration.

***************************************************************************

The Reflection Network Series and PATHWORKS 4.x
===============================================

Below are two separate sets of guidelines for using PATHWORKS and the
Reflection Network Series:

I.  Using WRQ's NetBIOS and TCP/IP as a Transport for PATHWORKS for DOS

    In this case, you are replacing the TCP/IP support provided by
    PATHWORKS and using the Reflection Network Series TCP/IP and NetBIOS
    support.

II. Using WRQ's TCP/IP in the same environment as DECnet

    In this case, you are still using the File Services, DECnet, and LAT
    support provided with PATHWORKS, but you are using the Reflection
    Network Series TCP/IP support for Telnet terminal sessions and FTP.

These procedures apply to separate configurations; do not attempt to combine
them.


Using WRQ's NetBIOS and TCP/IP as a Transport for PATHWORKS for DOS 4.x
=======================================================================

You can use the WRQ TCP/IP stack with PATHWORKS instead of the TCP/IP
transport provided with PATHWORKS, but manual configuration is required.

Note: This procedure assumes you are already using a TCP/IP transport, with
	 the server already configured for TCP/IP.

1.  Edit your AUTOEXEC.BAT and CONFIG.SYS files.

    a) Remove or comment out the line in AUTOEXEC.BAT that calls STARTNET,
	  typically in your \TCPIP directory.

    b) Remove or comment out the lines in CONFIG.SYS that load devices from
	  the \TCPIP directory; these may include NEMM.DOS, an NDIS driver
	  such as MACWD.DOS, PROTMAN.SYS, and TCPDRV.DOS.

2.  Run the Reflection Network Series SETUP program.  Choose the NDIS
    option.

3.  When Setup asks if you want to use NetBIOS support, answer YES. Setup
    will prompt you for the Reflection Network Series disk labelled "NDIS
    Supplemental Drivers." Insert the disk, and Setup will copy NB.EXE to
    your Reflection Network Series directory and will include it in
    STARTNET.BAT.

4.  When you are asked if you are using File Services as part of Reflection
    Network Series SETUP, answer NO. This question applies only to those
    using the Microsoft LAN Manager Supplemental Drivers option.

5.  After you have successfully installed the Reflection Network Series
    software, edit PROTOCOL.INI.

    a) Add the following line under the section [WRQNDIS1]:

	  NBSessions = 5

    b) Increase the value of TCPSessions to 10.

    c) Add the keyword Hook2A to the section [WRQNDIS1]. Refer to the
	  Technical Reference for more information on Hook2A.

6.  Confirm that the Reflection Network Series SETUP allows you to
    successfully connect to your host.   (Run the STARTNET.BAT produced by
    the Reflection Network Series SETUP after rebooting, but do not run the
    PATHWORKS network startup file.)

7.  Locate the STARTNET.BAT file in your PATHWORKS TCP/IP directory. Edit
    this file so that those lines associated with the PATHWORKS TCP/IP are
    not run; however, those lines that are associated with the redirector
    must be maintained.

    A sample STARTNET.BAT from PATHWORKS with the appropriate lines
    commented out with REM is listed below.  (Disregard any lines where
    "rem" is in lowercase.)

 @echo off
 if no (%echo%) == () echo %echo%
 rem break on
 rem if "$1"=="RELOAD" goto reload_entry
 rem cls
 echo -----------------------------------------------------------
 echo PATHWORKS for DOS (TCP/IP) v2.0 Network Operating Environment
 echo       Created by NETSETUP.EXE <version>
 echo       TCPIPMO <version>
 echo       TCPWIK <version>
 echo    Copyright by Digital Equipment Corporation
 echo -----------------------------------------------------------
 REM if "%BOOT%"=="" goto nbc
 REM %BOOT%
 REM :nbc
 REM %BOOT%\tcpip\netenvi <netenv#>
 REM if errorlevel 1 goto error
 set PCSA=%BOOT%\tcpip
 REM if %S_RUN%"=="YES" goto already_run
 REM %BOOT%\tcpip\netbind
 REM if errorlevel 1 goto error
 REM set S_RUN=YES
 REM :already done
 REM %BOOT%\tcpip\tcplite
 REM if errorlevel 1 goto error
 REM %BOOT%\tcpip\tinyrfc
 REM if errorlevel 1 goto error
 REM %BOOT%\tcpip\emsbfr
 REM if exist %BOOT%\tcpip\nbhosts goto nbalready
 REM %BOOT%\tcpip\inetnename <nnnn.nnnn.nnnn.nnnn>/store %BOOT%\tcpip\nbhosts
 REM goto nbdone
 REM :nbalready
 REM %BOOT%\tcpip\inetname /load %BOOT%\tcpip\nbhosts
 REM :nbdone
 REM %BOOT%\tcpip/inetname /load %BOOT%\tcpip\nbhosts
 REM :nbdone
 REM %BOOT%\tcpip\save
 REM %BOOT\tcpip
 echo------------------------------------------------------------
 echo Using Basic Redirector
 if not %psc% == () %pcsa%\psc %psc%
 c:\tcpip\redir5 /l:10 /P1:512 /P3:128 /himem:no
 pause
 if errorlevel 1 goto rderror
 if NOT errorlevel 1 goto rrdone
 :rdrerror
 echo ** ERROR ** Unable to start the Redirector
 goto error
 :rdrdone
 echo Setting the workstation name
 %BOOT%c:\tcpip\setname <name>
 echo------------------------------------------------------------
 echo Now attempting connection to the system file service <servername>
 set _SYSD=?
 %BOOT%\tcpip\use ?: \\<servername> /ENV=SYSD >>NUL
 if not errorlevel 1 goto c_sysdone
 echo ** WARNING ** Unable to connect to <servername>
 echo                  retrying...
 echo %BOOT% \tcpip\use ?: <servername> /REUSE ENV=_SYSD >>NUL
 echo ** ERROR ** unable to connect to <servername>
 set _SYSD=
 goto error
 :c_sysdone
 set bisrsvr=<servername>
 echo------------------------------------------------------------
 echo Setting Path and Environment Variables
 set HELP=%_SYSD%\tcpip;%BOOT%\tcpip
 goto pathdone
 :nopath
 path %_SYSD%\pcapp;%_SYSD%\tcpip\%BOOT%\tcpip
 :pathdone
 path %path%;%-SYSSD%\<directory>
 :reload_entry
 REM echo--------------------------------------------------------
 REM echo Starting the Domain Name Resolver
 REM %SYSD%\tcpip\dnrtsr
 REM echo--------------------------------------------------------
 REM echo Starting the Telnet Driver
 REM %_SUSD%\tcpip\tn
 REM ;if you have a line that loads BAPI here, REM the line that loads it
 REM if "%1"=="RELOAD" goto exit
 echo------------------------------------------------------------
 echo Setting the date and time...
 %_SYSD%\pcapp\nettime <servername>
 if not errorlevel 1 goto timedone
 echo ** WARNING ** Unable to set date and time from network
 :no_+2bott
 echo Enter the date and time:
 date
 time
 :timedone
 if exist %pcsa%\startup.bat echo Making node specific connection...
 if exist %pcsa%\startup.bat call %pcsa%\startup
 rem echo--------------------------------------------------------

 echo               There were start-up errors
 echo------------------------------------------------------------

 path %-PATH%
 :exit
 set_PATH=


8. After you have edited this file, reboot, run the WRQ STARNET.BAT, then
   run the PATHWORKS batch file.  Confirm that you can reach your server
   successfully.

9. Set up your network startup procedure so that you always run the
   Reflection Network Series STARTNET.BAT before you run the PATHWORKS
   STARTNET.BAT.


Using WRQ's TCP/IP in the Same Environment as DECnet 4.x
========================================================

You can use the TCP/IP support provided with the Reflection Network Series
for Telnet sessions and FTP while continuing to use the PATHWORKS NetBIOS
support for LAN Manager access and for LAT. Use the following guidelines:

1.  Your PATHWORKS environment should be already set up and configured for
    LAT and DECnet transport.

2.  Run the Reflection Network Series SETUP program:

    a) Do not request the LAT protocol.

    b) Do not indicate that you use LAN Manager.

3.  After completing the Reflection Network Series SETUP program:

    a) Remove the line in AUTOEXEC.BAT that runs NETBIND.  This line,
	  inserted by the Reflection Network Series SETUP program, is
	  redundant. NETBIND is performed in the PATHWORKS startup file.
	  RNDIS and RNDIS/U should still be in AUTOEXEC.BAT.

    b) Confirm that the PROTOCOL.INI that contains the WRQNDIS parameters is
	  the same PROTOCOL.INI that is used by PATHWORKS. This should be done
	  automatically if you were already set up correctly for PATHWORKS.

4.  The PATHWORKS startup file must be run before the Reflection Network
    Series STARTNET.BAT.

***************************************************************************

FTP.EXE (Reflection for Windows Users)
======================================

FTP.EXE is a DOS-based FTP for users who do not have Reflection FTP, which
is Windows-based. 

You can run FTP.EXE under Windows by using FTP.PIF to run FTP.EXE in a DOS
box. An FTP session requires 2 TELMGR sessions and 2 CONMGR sessions.

FTP.EXE does not run with Windows Sockets--it requires TELMGR.EXE.


FTP Command Syntax
==================

To start the DOS FTP application, double-click on the FTP icon. After the
FTP prompt appears, you can issue the following FTP commands (case is not
significant):

account - Sends account password information to the host.

	Syntax: account <password>


append - Sends a file to the host, appending it to the host file.

	Syntax: append <pcfile> [to] [<hostfile>]


ascii - Changes the file transfer type to ASCII.

	Syntax: ascii


binary - Changes the file transfer type to binary.

	Syntax: binary


cd - Changes the remote (host) directory.

	Syntax: cd <remote directory>


close - Disconnects the FTP session and returns you to the FTP
	   prompt.

	Syntax: close


cooked-ascii - Changes the file transfer type to ASCII.  Also honors
			control-z as end of file. A control-z will not be sent to
			the host at the end of a file, and a control-z will be
			appended to the end of a file received from the host.

	Syntax: cooked-ascii

delete - Deletes a host file.

	Syntax: delete <hostfile>


dir - Requests a long directory listing from the host.

	Syntax: dir [<host directory>]


dos - Shells to DOS, leaving the FTP application in memory. To return to the
	 FTP application from DOS, type exit.

	Syntax: dos


exit - Disconnects the FTP session and exits the FTP application.

	Syntax: exit


get - Transfers a single file from the host to the PC.

	Syntax: get [<hostfile>] [to] <pcfile>


help - Provides a brief description of the available FTP commands.

	Syntax: help


ls - Requests a short directory listing from the host.

	Syntax: ls [<host directory>]


mget - Transfers multiple files from the host to the PC, using wildcards.

	Syntax: mget [<hostspec>] [to] <pcspec>

mput - Transfers multiple files from the PC to the host, using
	  wildcards.

	Syntax: mput <pcspec> [to] <hostspec>


open - Opens an FTP connection to the specified host.  If a hostname is
	  specified, a HOSTS file or a name server must be available for
	  name-to-address mapping. Otherwise, specify an IP address.

	Syntax: open <hostname>
	    open <ip address>


put - Transfers a single file from the PC to the host.

	Syntax: put <pcfile> [to] <hostfile>


pwd - Shows the current remote directory.

	Syntax: pwd


quit - Disconnects the FTP session and exits the FTP application.
	  Synonymous with exit.

	Syntax: quit


quote - Sends a string to the host.

	Syntax: quote <string>


tenex - Changes the file transfer type to local 8 (tenex).

	Syntax: tenex


user - Initiates a logon sequence.  Use this command if the FTP server does
	  not prompt you for a username, but requires one.

	Syntax: user <username>

***************************************************************************

RLATCP for LAT
==============

RLATCP is a diagnostic program used to collect information from the
Reflection Network Series LAT modules and display them on screen or in a
text file.  The format for RLATCP is:

	RLATCP [/?] [/NOPAUSE] [ > filename ]

	 /?            - Type this help message
	 /NOPAUSE      - Do not pause between screens
	 > filename    - Redirect output from display to disk file


To show information to the screen, type RLATCP.  To send information to a
file named RLATINFO.FIL, type RLATCP /NOPAUSE >RLATINFO.FIL

The information displayed when you run RLATCP fills several screens; by
default, there is a pause between each screen.  An example of RLATCP output
follows.  Comments about the display are enclosed in angle brackets (for
example, <comment>).

	RLAT Information


	 Connection Manager and LAT Manager information
	 Maximum Connection Manager sessions       = 4
	 Connection Manager sessions in use        = 0

	 <Note that Connection Manager session in use also>
	 <counts Telnet and NSVT sessions in the in use number.>


	 RLAT driver information
	  Driver signature                          = LAT
	  Driver version                            = 04.80
	  Interrupt number                          = 6A
	  Interrupt vector                          = 1C2E:0309

	  <Signature should always be LAT, version should always >
	  <be 4.80 or greater, the interrupt number is usually 6A;>
	  <it is set with the RLAT /INT switch.>

	 RDLL driver information
	  Driver signature                          = DLL
	  Driver version                            = 02.0C
	  Interrupt number                          = 6E
	  Interrupt vector                          = CE0E:02A3

	  <Signature should always be DLL, Interrupt number>
	  <is usually 6E; it is set with the RDLL /INT switch.>

	 Ethernet card ROM address                  = 00-00-C0-5A-EF-08
	 Ethernet card station address              = 00-00-C0-5A-EF-08

	 <Each card has a unique number burned into ROM.>
	 <The card can also have a register that is loaded>
	 <with the station address.  Normally, these two are>
	 <the same, but PATHWORKS changes the station address.>
	 <When doing network traces, specify the station address>
	 <if ROM address and stations address are different.>

	 RLAT Characteristics
	  Reflection Network Series Version         = 02.00
	  Maximum service table entries             = 15
	  Current service table entries             = 11
	  Number of separate nodes in table         = 4
	  Maximum number of Virtual Circuits        = 2
	  Maximum number of Sessions                = 16

	  <Maximum service table entries are set with the>
	  <RLAT /DIR:<n> command. Current service table entries>
	  <show how many service advertisements have been received.>
	  <If maximum and current entries values are the same,>
	  <the table is full and no more services will show up.>
	  <Number of nodes shows how many separate hosts and/or>
	  <terminal servers have been advertised. Number of
	  <Virtual Circuits is set using the RLAT /CKT switch.>
	  <Maximum number of Sessions is 17; cannot be increased.>

	  Pointer to table of SCB pointers          = 1F87:03AA
	  Pointer to table of VCB pointers:         = 1F87:1410
	  Size of a service table entry (bytes):    = 112
	  Pointer to start of service table:        = 1F87:0D00

	  <This information is used by RSN to get and set services.>

	 RLAT counters
	  Seconds since zeroed                      = 8402
	  Messages retransmitted                    = 1
	  Messages transmitted                      = 230
	  Messages received                         = 1956
	  Out of sequence messages                  = 1
	  Illegal messages received                 = 0
	  Illegal slots received                    = 0
	  Receive buffer not available              = 0
	  Transmit buffer not available             = 0


	  <The RLAT counters show network traffic and errors.>
	  <Under normal circumstances, the seconds and messages>
	  <received and transmitted will increase and the others>
	  <should stay at zero.>

RLAT service table details
Service Name     Rating  Ethernet Address   Node Name        Status
------------     ------  -----------------  ---------------- ------
LEE              255     00-00-C9-00-84-7E  SOUTH            Dynamic
SHERMAN          255     00-00-C9-00-84-7E  NORTH            Dynamic
GRANT            255     00-00-C9-00-84-7E  NORTH            Dynamic
MCCLELLAN        255     00-00-C9-00-84-7E  NORTH            Dynamic
STONEWALL        80      AA-00-04-00-05-04  SOUTH            Dynamic
LONGSTREET       3       00-00-B5-04-0F-F7  SOUTH            Dynamic
HOOD             0       00-00-B5-04-0F-F7  SOUTH            Dynamic
BURNSIDE         255     08-00-2B-0D-87-C1  NORTH            Dynamic
JEBSTUART        255     08-00-2B-0D-87-C1  SOUTH            Dynamic
HOOKER           255     08-00-2B-0D-87-C1  NORTH            Dynamic
MEADE            255     08-00-2B-0D-87-C1  NORTH            Dynamic


	  <Service table details, DEC's LATCP format.  The rating>
	  <shows how busy the service is. The Ethernet address is>
	  <the station address of the node advertising the service.>

Show Services Information
  Service              Node        Rating               Description
----------------  ---------------  ------  ------------------------------------
LEE               SOUTH             255    EC1 Brock envelop printer
SHERMAN           NORTH             255    EC1 Brock label printer
GRANT             NORTH             255    EC1 Brock letter printer
MCCLELLAN         NORTH             255    EC1 Brock misc printer
STONEWALL         SOUTH             80     VAX/VMS version 5.3-2 NODE
LONGSTREET        SOUTH             3      Bulletin Board
HOOD              SOUTH             0
BURNSIDE          NORTH             255    9600 Baud Hayes
JEBSTUART         SOUTH             255    9600 Baud Hayes
HOOKER            NORTH             255    Reverse Lat to HP3000
MEADE             NORTH             255    Reverse Lat to STONEWALL

	  <Shows information similar to the RLAT service table>
	  <details described above, but a description string>
	  <rather than the Ethernet address is displayed.  This>
	  <display is the same format as a DOS Reflection Show >
	  <Services command.>
