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

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.
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's TCP Socket Interface.
WRQSLIP.EXE    WRQ SLIP driver.
WRQTCP.EXE     TCP/IP protocol.
WRQTICL.EXE    WRQ's NetIPC interface to TCP.

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

What's New in Version 2.10
WRQTICL and SHARE
Open View System Manager
Socket Application Development Support
LAN Workplace for DOS
LAN Manager and 3COM 3C523
LANTRACE and ODI
Installing TCP/IP with LAN Manager
  NetBEUI
  LAN Manager 2.1 or later
  Any other LAN Manager version
  NetBIOS Support with Windows for Workgroups
  LAN Manager and ODI
Reflection Network Series and PATHWORKS:  LAN Manager and DECNet
FTP.EXE
RLATCP for LAT

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

What's New in Version 2.10
==========================

*   ODI Support
    The Open Data Link Interface specification from Novell can be used as a
    multi-protocol interface whether or not you are using Novell NetWare.
*   Direct support for a wider variety of network cards.
*   Support in SETUP for moving from NDIS to the ODI specification.
*   Partial support in SETUP for additional network cards on supplied
    supplemental drivers disks.
*   New TRACE facility:  LANTRACE.EXE.
*   SLIP - Serial IP support for point-to-point serial connection using
    TCP/IP.

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

WRQTICL and SHARE
=================

If you are using WRQTICL and you must also run SHARE on your PC, SHARE must be
loaded first.

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

Open View System Manager
========================

You need Open View System Manager version 3.1 or higher to use the Reflection
Network Series.  Previous versions of Open View System Manager require
AdvanceLink and Network Services from Hewlett-Packard.

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

Socket Application Development Support
======================================

Applications can be written using a sockets developer's kit. WRQ will be
selling this kit in the future, but at this time the kit can be purchased from
Microsoft.  Call any LAN Manager Authorized Dealer and ask for Part
#0962744-005.

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

LAN Workplace for DOS
=====================

If you have LAN Workplace for DOS installed and configured on your machine, do
the following before running the Reflection Network Series SETUP program:

1. Locate LANWP.BAT, the batch file that loads LAN Workplace for DOS programs.

2. Comment out the line in LANWP.BAT that loads TCPIP.EXE.

3. Reboot your machine.

You cannot use the Reflection Network Series TCP/IP stack and the LAN
Workplace for DOS TCP/IP stack at the same time.

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

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.

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

Lantrace and ODI
================

If you are running LANTRACE on a machine configured for ODI, increase the 
number of event control blocks for RODI.EXE.  For example, type the following
to increase event control blocks from 10 (the default) to 32 (the maximum):
RODI /ECBS:32

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

Installing TCP/IP with LAN Manager
==================================

If you are upgrading from Reflection Network Series version 2.0 or 2.01 to
Reflection Network Series version 2.1 and not upgrading your LAN Manager
software, you do not need to re-install LAN Manager.  The Reflection Network
Series SETUP program will overwrite the appropriate files with the new version
2.10 files.

If you have a LAN Manager local area network, you may need to perform some
configuration procedures in addition to running the Reflection Network Series
SETUP program.

Use the following table to determine which procedures you need:

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

If you use this as your     And you use this
LAN Manager protocol...     version of LAN Manager...   See this section...

------------------------------------------------------------------------------

NetBEUI                     Any                         Installing the
							Reflection Network
							Series with NetBEUI

TCP/IP                      Microsoft LAN Manager       See the Reflection
			    Version 2.1 or later        Network Series
							Documentation

TCP/IP                      Any LAN Manager version     Manually Installing
			    EXCEPT Microsoft LAN        Reflection Network
			    Manager 2.1                 Series
							TCP/IP Support

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

NetBIOS Support

If you're using LAN Manager with TCP/IP transport, RNDIS.EXE should be loaded
with /LIFOS set to 8, for example:

C:\WRQNET\RNDIS /STACKS:5 /LIFOS:8

RNDIS is loaded in AUTOEXEC.BAT.

    Users of a pre-2.1 version of Microsoft's LAN Manager, or a version of LAN
    Manager from a different vendor (such as Hewlett-Packard or
    Ungermann-Bass) must manually update some files using the procedure
    described in "Manually Installing Reflection Network Series TCP/IP
    Support," below.

Installing the Reflection Network Series with NetBEUI
==============================================================================

    When using NetBEUI (NetBIOS Extended User Interface) as the only protocol
    for your local area network, you can use TCP/IP as the protocol for
    connecting to your host.  No additional changes are required.

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

Manually Installing Reflection Network Series TCP/IP Support

    Overview:
    In the procedures below, you'll install your LAN Manager software, then
    install the Reflection Network Series TCP/IP software and driver support.
    Afterwards, you'll need to edit your AUTOEXEC.BAT, CONFIG.SYS, and any
    other batch files created by the LAN Manager installation to ensure that
    the Reflection Network Series TCP/IP software is loaded INSTEAD OF the
    LAN Manager TCP/IP software.

    You'll also need to install the Reflection NetBIOS emulator programs in
    your Reflection Network Series directory (by default, WRQNET).

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

To install the Reflection Network Series TCP/IP programs:

1.  Make a backup copy of your AUTOEXEC.BAT and CONFIG.SYS files.

2.  Modify your original AUTOEXEC.BAT and CONFIG.SYS files so that they
    contain only a few basic lines.  If you have already installed network
    software (from LAN Manager or a previous version of the Reflection Network
    Series), try to remove all device drivers used by networking software or
    other non-essential programs.

    For example, your CONFIG.SYS file might look like this:

	BUFFERS = 30
	FILES = 30
	SHELL = C:\DOS\COMMAND.COM C:\DOS\ /E:800 /P
	LASTDRIVE = F

    A basic AUTOEXEC.BAT file might look like this:

	PATH = C:\DOS
	PROMPT $P$G

3.  Install your LAN Manager software, specifying that TCP/IP should NOT be
    used as the network protocol (if you can make this specification).  For
    example, if you use Microsoft LAN Manager Version 2.0, specify NetBEUI as
    the network transport; if you use Hewlett-Packard LAN Manager, you can
    specify NBP as the transport.

4.  After the LAN Manager installation is complete, edit the modified
    CONFIG.SYS and AUTOEXEC.BAT.  You may also need to edit some other
    batch files created by the installation program.

    Remove the lines from these files that load any TCP/IP device drivers
    (if you could not specify a different protocol in step 3 above), and any
    device drivers you won't be using (for example, NetBEUI or NBP drivers).
    Keep lines that set the path to the LAN Manager files, and the line that
    starts the network workstation.

    EXAMPLE 1: LAN Manager 2.0
    --------------------------

    With Microsoft LAN Manager Version 2.0 and NetBEUI only, your
    CONFIG.SYS and AUTOEXEC.BAT files look something like those listed below.
    Remove the line that loads the NetBEUI device driver from the CONFIG.SYS
    file.  No changes to AUTOEXEC.BAT are required.

    Microsoft LAN Manager 2.0 CONFIG.SYS----------------------

    BUFFERS = 30
    FILES = 30
    SHELL = C:\DOS\COMMAND.COM C:\DOS\ /E:800 /P
    LASTDRIVE = F

    DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS
    DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\MACWD\MACWD.DOS
    DEVICE=C:\LANMAN.DOS\DRIVERS\PROTOCOL\NETBEUI\NETBEUI.DOS

    ** The "MACWD.DOS" driver is specific to Western Digital cards.  If you
       have a different network card, this line will differ.


    Microsoft LAN Manager 2.0 AUTOEXEC.BAT--------------------

    PATH = C:\DOS
    PROMPT $P$G
    REM = LANMAN 2.0 = DO NOT MODIFY BETWEEN THESE LINES = LANMAN 2.0 =
    SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
    C:\LANMAN.DOS\DRIVERS\PROTMAN\NETBIND
    NET START WORKSTATION
    REM = LANMAN 2.0 = DO NOT MODIFY BETWEEN THESE LINES = LANMAN 2.0 =

    EXAMPLE 2:  HP LAN Manager
    --------------------------

    If you use Hewlett-Packard LAN Manager Version 1.1, TCP/IP is the only
    transport available.  After completing the installation program, remove
    all of the lines that load the HP TCP/IP drivers.

    After installation, your CONFIG.SYS and AUTOEXEC.BAT files might look like
    those shown below.

    Delete the line that loads TCPDRV.DOS from CONFIG.SYS.

    HP LAN Manager 1.1 CONFIG.SYS----------------------

    BUFFERS = 30
    FILES = 30
    SHELL = C:\DOS\COMMAND.COM C:\DOS\ /E:800 /P
    LASTDRIVE = F

    DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\PROTMAN.DOS
				/I:C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS
    DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\macwd.dos
    DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\NEMM.DOS
    DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\TCPDRV.DOS
				/I:C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS

    HP LAN Manager 1.1 AUTOEXEC.BAT--------------------

    PROMPT $P$G
    REM **LMx** top  HP Networking Products - Do not Remove *********
    SET PATH=C:\3OPEN\DOSWKSTA\LANMAN\NETPROG;C:\DOS
    command /C C:\3OPEN\DOSWKSTA\net_strt
    REM **LMx** bot  HP Networking Products - Do not Remove *********


    Edit NET_STRT.BAT, the batch file that was added to AUTOEXEC.BAT above.
    It is located in the C:\3OPEN\DOSWKSTA directory; a sample fragement is
    provided below.

    In this batch file, remove all the lines between the labels "begin Primary
    Transport" and "end Primary Transport." Keep the section that starts the
    LAN Manager service, especially the line "net start workstation."


    HP LAN Manager 1.1 NET_STRT.BAT file----------------

    REM **LMx** ======== HP PC INTEGRATION PRODUCTS =====
    REM ================ Do not modify this block =====
    echo off
    REM **LMx** ***************************************************
    REM **LMx** ***       begin Primary Transport               ***
    REM **LMx** ***************************************************
     C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\netbind
    if errorlevel 1 goto Error_NetBIOS
     C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\umb
     C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\tcptsr
    if errorlevel 1 goto Error_NetBIOS
     C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\tinyrfc C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS
    if errorlevel 1 goto Error_NetBIOS
    REM  C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\nmtsr
    if errorlevel 1 goto Error_NetBIOS
    REM  C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\probe
    if errorlevel 1 goto Error_NetBIOS
     C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\emsbfr
     C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\lmset /s
    REM **LMx** ***************************************************
    REM **LMx** ***       end Primary Transport                 ***
    REM **LMx** ***************************************************
    REM **LMx**
    REM **LMx** ***************************************************
    REM **LMx** ***       begin Secondary Transport             ***
    REM **LMx** ***************************************************
    REM **LMx** ***************************************************
    REM **LMx** ***       end Secondary Transport               ***
    REM **LMx** ***************************************************
    REM **LMx**
    REM **LMx** ***************************************************
    REM **LMx** ***       begin LAN Manager Service             ***
    REM **LMx** ***************************************************
    echo off
    break on
    net start workstation
    if errorlevel 1 goto Error_Workstation
    vfix
    rem This sets TimerCriticalSection in Windows SYSTEM.INI
    rem See Section 7 of your HP LAN Manager Technical Addendum
    winfix

5.  After editing the files, be sure to save them as text-only format.

6.  Run the Reflection Network Series SETUP program.  Select the NDIS option.

7.  When SETUP prompts for information about your local area network, answer
    "N" to the question about LAN Manager.

8.  After completing SETUP, edit CONFIG.SYS and AUTOEXEC.BAT to make sure that
    lines that load network device drivers are not duplicated.

    Next, check the modifications to AUTOEXEC.BAT made by the Reflection
    Network Series SETUP program.  It might look something like this:

      C:\WRQNET\RNDIS /STACKS:8 /IRQ:5 RECEIVES:8 /LIFOS:8
      C:\WRQNET\RNDIS /U
      C:\WRQNET\NETBIND
      PATH = C:\DOS
      PROMPT $P$G
      REM = LANMAN 2.0 = DO NOT MODIFY BETWEEN THESE LINES = LANMAN 2.0 =
      SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
      C:\LANMAN.DOS\DRIVERS\PROTMAN\NETBIND
      NET START WORKSTATION
      REM = LANMAN 2.0 = DO NOT MODIFY BETWEEN THESE LINES = LANMAN 2.0 =

    The Reflection Network Series SETUP program added the first two lines, but
    the command that runs the NETBIND program is duplicated a few lines below.
    You MUST delete the second of the two lines that runs NETBIND, or else
    conflicts will occur.  If only one "NETBIND" line is present in the file,
    leave it as is.

    In some cases, AUTOEXEC.BAT will not contain a NETBIND command.  Instead,
    NETBIND might be run from another batch file that gets invoked by
    AUTOEXEC.BAT.  For example, with HP LAN Manager, the NETBIND command is
    found in the NET_STRT.BAT file invoked from AUTOEXEC.BAT.

    Add the following line immediately before the NET START WORKSTATION line:

    CALL C:\WRQNET\STARTNET.BAT

9.  Copy NB.EXE and NBNS.EXE from your Reflection Network Series distribution
    disks to the directory where you installed your Reflection Network Series
    software, for example:

	COPY A:\MSLANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\NB*.EXE

10. Using a word processor or text editor, edit STARTNET.BAT.  Add the
    following line:

	C:\WRQNET\NB

    For example:
	C:\WRQNET\RNDIS /STACKS:8 /IRQ:5 /RECEIVES:8 /LIFOS:8
	C:\WRQNET\CONMGR /S:12
	C:\WRQNET\TCP2PDIS /TEXTINI:C:\WRQNET\PROTOCOL.INI
	C:\WRQNET\WRQTCP
	C:\WRQNET\NB             <- added this line
	C:\WRQNET\TELMGR

    If you're configuring a NetBIOS name server instead of a workstation PC,
    add this line instead of the line above:

	C:\WRQNET\NBNS

    HP LAN Manager users should add the /HP switch to the line that loads NB
    or NBNS.

12. Save the batch file in text-only format.

13. Reboot your PC to have the changes to CONFIG.SYS and AUTOEXEC.BAT take
    effect.

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

Troubleshooting a Manually Configured LAN Manager Setup
=======================================================

    If your PC locks up or you can't get a host or LAN connection, the most
    common causes are conflicting device drivers or parameters used by device
    drivers.  Here are some things to check:

    * Check in CONFIG.SYS for lines that load the same device drivers twice,
      but from different directories.  For example, separate DEVICE lines may
      load PROTMAN.DOS or MACWD.DOS from a LAN Manager directory and from a
      WRQNET directory.  Remove any duplicate lines.

    * Check in AUTOEXEC.BAT or other batch files created by the LAN Manager or
      Reflection Network Series installation for lines that load NETBIND and
      TCP/IP drivers.  Make sure that different TCP/IP drivers are not being
      loaded from different directories.

    * If there are no duplicate lines in CONFIG.SYS or other files, you might
      try to modify the files to avoid mixing and matching device drivers
      installed by LAN Manager with drivers installed by the Reflection
      Network Series.  For example, if LAN Manager installs a PROTMAN.DOS
      driver and a NETBIND program, and the Reflection Network Series later
      installs its own NETBIND program, redirect the line that runs NETBIND so
      that the one installed by LAN Manager is used instead.  PROTMAN.DOS and
      NETBIND.EXE must be from the same installation in order to work
      correctly.

    * Sometimes conflicts arise in the PC when different network programs
      try to use the same interrupt request line (IRQ).  Check the file called
      PROTOCOL.INI, and inspect the IRQ, IOBASE, and RAMADDRESS values in the
      sections added by Reflection or LAN Manager.  Ensure that values are
      correct for your card.


 Microsoft LAN Manager 2.1 Users:
 ================================

      After you have completed the installation process that configures the
      Reflection Network Series TCP/IP stack as the transport for LAN Manager
      and you're using the basic rather than the enhanced version, you may see
      the following message when you reboot:

      Error:  Unable to find DRIVERNAME = WRQNDS1B$ section in PROTOCOL.INI

      You can disregard this message.  To avoid seeing this message each time
      you reboot, remove the line described below from your AUTOEXEC.BAT file.

			  LOAD WRQNDS1B

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

NetBIOS Support with Windows for Workgroups
===========================================

Use the steps below to configure Windows for Workgroups with the Reflection
Network Series TCP/IP stack as a transport.

Note: The Windows for Workgroups installation support in the Reflection
Network Series is designed to work with Microsoft Windows for Workgroups
version 3.10.  Future versions of Windows for Workgroups may have different
setup requirements.

1. Install Windows for Workgroups. Verify that you have access to your NetBEUI
   services.

2. Install the Reflection Network Series (TCP Connection, NS Connection, or
   3000 Connection). Select the NDIS option.

   If the SETUP program finds a LAN Manager for DOS configuration on your PC,
   you will be asked if you want to use Microsoft LAN Manager with WRQ's
   TCP/IP, with "Y" displayed as the default response.
   Change this to no ("N").

3. As part of SETUP, you'll also be asked will if you want to run STARTNET.BAT
   as part of AUTOEXEC.BAT; answer Yes.  The Reflection Network Series TCP/IP
   software must be loaded before starting Windows; running STARTNET.BAT from
   AUTOEXEC.BAT is an easy way to do it.

4. Copy the Reflection Network Series NetBIOS file, NB.EXE or NBNS.EXE, from
   your distribution disks to the directory where your Reflection Network
   Series software is installed.

5. Make the following modifications to AUTOEXEC.BAT:

   - Comment out ("REM") the line that loads NETBIND.  Windows for Workgroup
     NET START performs the NETBIND.

   - Move the line that loads your Reflection Network Series software
     (e.g., \WRQNET\STARTNET.BAT) after the line that loads Windows for
     Workgroups network files (NET START).  Note that the RNDIS driver must
     load and then unload before performing NET START.

   No modifications to CONFIG.SYS are necessary.

6. Make the following modifications to PROTOCOL.INI:

   - After the last transport line in the [network.setup] section, add the
     following line:

	  transport=wrqndis1,WRQNDIS1

   - After the last LANA number line in the [network.setup] section, add a
     line that references your network interface card, for example:

	  lana1=ms$w13ew,1,wrqndis1

     The LANA number may be other than "1" if other protocols are being before
     the TCP/IP stack.

     The device driver (shown as MS$W13EW in this example) is dependent on the
     type of network interface card you are using.

   - Verify that the following items in the [WRQNDIS1] section are set to the
     following values (or higher).

	  TCPSessions = 16
	  NumTCPBuffers=8
	  NBSessions = 10

   - Add the following line to the [WRQNDIS1] section:

	  Lanabase = 1

     The lanabase = value must match the lanax= entry in the [network.section]
     section.

7. Make the following modifications to SYSTEM.INI:

   - After the [386Enh] section add the following line:

	  V86ModeLanas=1

     If WRQNDIS1 has been given a different LANA number it should be used.

   - Increase the netheapsize = parameter in the [386enh] section from its
     default value (20) to 60.

8. Make the following modification to the WRQ STARTNET.BAT file:

   - Add NetBIOS to the end of the STARTNET with either NB.EXE or NBNS.EXE,
     for example:

	  C:\WRQNET\NB.EXE

The following are samples with the modifications outlined above.

***************************************************
AUTOEXEC.BAT file:

C:\WRQNET\RNDIS /STACKS:3 /IRQ:15 /LIFOS:8
C:\WRQNET\RNDIS /U
rem C:\WRQNET\NETBIND
C:\WFW\net start
CALL C:\WRQNET\STARTNET
echo off
path=C:\WFW;c:\dos;c:\windows
C:\WFW\mouse.COM /Y
C:\WFW\SMARTDRV.EXE
SET TEMP=C:\WINDOWS\TEMP
prompt $p$g

***************************************************
CONFIG.SYS:

device=C:\WFW\HIMEM.SYS
device=C:\WFW\EMM386.EXE noems x=c800-cbff i=cc00-efff
dos=high,umb
SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:512 /p
STACKS=9,256
device=C:\WFW\protman.dos /i:C:\WFW
device=C:\WFW\workgrp.sys     <----/n can be added here if you're not using
NetBEUI
device=C:\WFW\smcmac.dos
LASTDRIVE=Z

***************************************************
PROTOCOL.INI:

[network.setup]
version=0x3100
netcard=ms$w13ew,1,MS$W13EW
transport=ms$netbeui,MS$NETBEUI
transport=wrqndis1,WRQNDIS1
lana0=ms$w13ew,1,ms$netbeui
lana1=ms$w13ew,1,wrqndis1


[protman]
DriverName=PROTMAN$
PRIORITY=MS$NETBEUI

[MS$W13EW]
DriverName=SMCMAC$

[MS$NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=32
BINDINGS=MS$W13EW
LANABASE=0

;
; Reflection Network Series section
;
[WRQNDIS1]
  Drivername = WRQNDS1$
  Bindings = MS$W13EW
  IPAddress0 = <IP Address>
  DefaultGateway0 = <IP Address of default gateway>
  HostsPath = C:\WRQNET
  TCPSessions = 16
  NumTCPBuffers = 8
  NBSessions = 10
  LANABASE=1

***************************************************
STARTNET.BAT:

C:\WRQNET\RNDIS /STACKS:3 /IRQ:15 /LIFOS:8
C:\WRQNET\TCP2PDIS /TEXTINI:C:\WFW\PROTOCOL.INI
C:\WRQNET\WRQTCP
C:\WRQNET\CONMGR /SESSIONS:2
C:\WRQNET\TELMGR /SESSIONS:2
C:\WRQNET\NB

***************************************************
SYSTEM.INI:

[boot]
network.drv=wfwnet.drv

[386Enh]
;network=vnetbios.386,vnetsup.386,vredir.386,vwc.386
network=vnetbios.386,vnetsup.386,vredir.386,vserver.386,vbrowse.386,vwc.386
ebios=*ebios
woafont=dosapp.fon
keyboard=*vkd
netheapsize=60    --> Needs to be set around 60 for LAN Manager to work
V86ModeLanas=1    --> This must be the same as the lanabase setting in the
		      WRQNDIS1 section in PROTOCOL.INI

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

LAN Manager and ODI
===================

You can use ODI as your multiprotocol interface with LAN Manager if you do
not require NetBEUI.  If you are using NetBEUI as a transport for LAN Manager,
you must operate in an NDIS environment.

There is no automatic setup provided for LAN Manager over ODI.  Use the
guidelines below to manually configure this environment.

The example below assumes you have NOT previously configured LAN Manager to
use the Reflection Network Series TCP/IP stack as a transport.  If you have,
see "If You've Already Installed WRQ's TCP/IP" later in this file.

1.  Install LAN Manager.  Select TCP/IP as the transport.  Confirm that you
    can connect to your LAN Manager server.

2.  Use the Reflection Network Series SETUP program, and select the ODI
    option.  (You will be warned that an NDIS environment is already
    configured on your PC.)

    When you are asked if you want to run STARTNET.BAT as part of your
    standard bootup in AUTOEXEC.BAT, answer Yes.

    SETUP will modify the following:
    AUTOEXEC.BAT:  LSL and an ODI-compliant driver will be added, NETBIND will
		   be removed, and NET START WORKSTATION will be removed.
    CONFIG.SYS:    The lines that define PROTMAN.DOS and an NDIS-compliant
		   driver as devices will be removed.

3.  AUTOEXEC.BAT:
    Confirm that the NETBIND statement in the LAN Manager section has been
    deleted but the PATH statement is present, for example:

    REM = LANMAN 2.1 = DO NOT MODIFY BETWEEN THESE LINES = LANMAN 2.1   =
	       SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
(deleted)-->   C:\LANMAN.DOS\DRIVERS\PROTMAN\NETBIND
(deleted)-->   NET START WORKSTATION
    REM = LANMAN 2.1 = DO NOT MODIFY BETWEEN THESE LINES = LANMAN 2.1   =


4.  Copy NB.EXE or NBNS.EXE from the Reflection Network Series distribution
    disks.  Copy this to the your Reflection Network Series directory, then
    add lines to STARTNET.BAT, that load NB and run the LAN Manager NET START
    WORKSTATION command.  Also, add /LIFOS:8 to RODI.  The example below shows
    these changes:

    C:\WRQNET\RODI /STACKS:5 /LIFOS:8
    C:\WRQNET\TCP2PDIS /TEXTINI:C:\WRQNET\NET.CFG
    C:\WRQNET\WRQTCP
    C:\WRQNET\CONMGR /SESSIONS:5
    C:\WRQNET\TELMGR /SESSIONS:4
    C:\WRQNET\NB
    NET START WORKSTATION

    You may also want to have a NET LOGON line in STARTNET.BAT.

    If you want to be able to uninstall TELMGR, place the NB and NET START
    WORKSTATION lines before the line that loads TELMGR.

5.  Confirm that you can log on to your LAN Manager server,and that
    you can connect to your hosts from Reflection.

If You've Already Installed WRQ's TCP/IP
========================================

The same basic steps outlined above apply to this situation, but an additional
step is required to remove WRQ's NDIS-based LAN Manager support.  Remember to
confirm that you have not requested NetBEUI as an additional transport.

Your previous Reflection Network Series SETUP configuration added lines
similar to the following:

@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.1 ===
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
C:\LANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\RNDIS /STACKS:8
C:\LANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\RNDIS /U
C:\LANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\..\..\..\NETPROG\NETBIND
C:\LANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\RNDIS /STACKS:8
C:\LANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\TCP2PDIS /TEXTINI:..\..\..\PROTOCOL.INI
C:\LANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\WRQTCP
C:\LANMAN.DOS\DRIVERS\PROTOCOL\WRQNDS1\NB
NET START WORKSTATION
rem LOAD WRQNDS1
NET LOGON xxxx
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.1 ===


When you run SETUP and select ODI, the lines that load RNDIS, NETBIND and run
NET START WORKSTATION are removed, but the lines that load TCP2PDIS, WRQTCP,
and NB are NOT removed.  Remove these lines from AUTOEXEC.BAT; these programs
are now loaded as part of STARTNET.BAT.  Also, move the line that calls
STARTNET.BAT so that it is above the NET LOGON line.

Your AUTOEXEC.BAT file should look something like this:

CALL C:\WRQNET\STARTNET.BAT
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.1 ===
SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%
NET LOGON xxxx
@REM ====== LANMAN 2.1 === DO NOT MODIFY BETWEEN THESE LINES === LANMAN 2.1 ===

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

The Reflection Network Series and PATHWORKS
===========================================

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

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 is 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 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.
4.  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.

5.  Copy NB.EXE into \WRQNET from the Reflection Network Series disks.

6.  Edit the STARTNET.BAT that was created by the Reflection Network Series
    SETUP program:

    Add NB.EXE to STARTNET.BAT,and add the /HP switch, for example:

    C:\WRQNET\RNDIS /STACKS:7 /IRQ:<your IRQ> /LIFOS:8
    C:\WRQNET\TCP2PDIS /TEXTINI:C:\WRQNET\PROTOCOL.INI
    C:\WRQNET\WRQTCP
    C:\WRQNET\CONMGR /SESSIONS:4
    C:\WRQNET\TELMGR /SESSIONS:2
    C:\WRQNET\NB /HP

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

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)
======================================

Use FTP.PIF to run FTP.EXE in a DOS box.  An FTP session requires 2 TELMGR
sessions and 2 CONMGR sessions.

FTP.EXE is a DOS-based FTP for users who do not have Reflection FTP, shipped
with Reflection for Windows version 4.1 and above.  Reflection FTP is a
Windows-based FTP that includes support for moving, previewing and deleting
files using a drag-and-drop interface or a command line.

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

To start the stand-alone FTP application, 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
------------     ------  -----------------  ---------------- ------
EC1ENV           255     00-00-C9-00-84-7E  MOE              Dynamic
EC1LBL           255     00-00-C9-00-84-7E  MOE              Dynamic
EC1LET           255     00-00-C9-00-84-7E  MOE              Dynamic
EC1MISC          255     00-00-C9-00-84-7E  MOE              Dynamic
BUGS             80      AA-00-04-00-05-04  BUGS             Dynamic
BBS              3       00-00-B5-04-0F-F7  LAT_0000B5040FF7 Dynamic
BBSSLIP          0       00-00-B5-04-0F-F7  LAT_0000B5040FF7 Dynamic
MODEM1           255     08-00-2B-0D-87-C1  GUMBY            Dynamic
MODEM2           255     08-00-2B-0D-87-C1  GUMBY            Dynamic
REVHP            255     08-00-2B-0D-87-C1  GUMBY            Dynamic
REVVAX           255     08-00-2B-0D-87-C1  GUMBY            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
----------------  ---------------  ------  ------------------------------------
EC1ENV            MOE               255    EC1 Brock envelop printer
EC1LBL            MOE               255    EC1 Brock label printer
EC1LET            MOE               255    EC1 Brock letter printer
EC1MISC           MOE               255    EC1 Brock misc printer
BUGS              BUGS               80    VAX/VMS version 5.3-2 NODE
BBS               LAT_0000B5040FF7    3    WRQ Bulletin Board
BBSSLIP           LAT_0000B5040FF7    0
MODEM1            GUMBY             255    9600 Baud Hayes
MODEM2            GUMBY             255    9600 Baud Hayes
REVHP             GUMBY             255    Reverse Lat to HP3000
REVVAX            GUMBY             255    Reverse Lat to BUGS

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