		      Reflection Network Series for Windows
				TCP Connection
				 Version 4.0 

		  (C)opyright 1994 Walker Richer & Quinn Inc.


This file is renamed to README.TXT when it is copied to the hard drive
during Setup.

--------------------------------------------------------------------------                               
				 Contents
--------------------------------------------------------------------------                               

* General Issues
* Setup Issues
* Using BootCon and Setup
* Reboot Workstation
* Hiding the RNS Icon
* RNKILL Utility
* SLIP and SHARE
* No Fast File Transfer
* FTP Client
* IBMTOK.DOS or ELNK.DOS drivers 
* HP EtherTwist Plus ODI Driver
* Pathworks 5.0

--------------------------------------------------------------------------                               
			       General Issues
--------------------------------------------------------------------------                               

For more information on the files for the TCP Connection, refer to the 
file PACKRNST.LST on disk 1.

NOTE: The WINSOCK.DLL shipped with the Reflection Network Series for 
      Windows must be used with this product.  Make sure that you do NOT 
      have a WINSOCK.DLL in your Windows directory or your Windows System 
      directory.  Also, any directory that is placed in front of the 
      Reflection Network Series for Windows path cannot contain a 
      WINSOCK.DLL.  A non-WRQ WINSOCK.DLL in any of these locations will 
      not allow your Reflection Network Series software to run.

The following will not be available in the first release:

- NDIS to ODI conversion
- TCP/IP transport for LAN Manager (NetBIOS)
- BOOTCON & DOS multiboot support in Setup
- Support for Windows for Workgroups version 3.10 in Setup

--------------------------------------------------------------------------                               
			       Setup Issues
--------------------------------------------------------------------------                               

3Com 3C503 card - transceiver type
----------------------------------
Setup does not configure the transceiver type for the 3Com 3C503 card. 
For NDIS, use the TRANSCEIVER keyword to change the connection type to 
AUI (15 pin).  Manually add the line TRANSCEIVER = EXTERNAL in the 3C503 
section in PROTOCOL.INI.  For ODI, add the keyword CONNECTOR DIX to the
LINK DRIVER section in NET.CFG.  For examples, refer to PROTOCOL.SAM
and NETCFG.SAM on the Unsupported Drivers Disk.
 
Installing with 8 interfaces defined
------------------------------------
If you run Setup when installing over a working Reflection Network Series 
for Windows environment which has all 8 interfaces defined.  Pressing the 
OK button after selecting the interface to install doesn't allow you to
proceed with Setup.  To avoid this problem, remove one of the interfaces, 
and then run Setup.

Monolithic IPX and ODI Setup
----------------------------
If you have a version of IPX that is not configured for an ODI or an
NDIS environment (this is called a "monolithic" IPX), the Setup program
does not make all necessary modifications to AUTOEXEC.BAT when you select
the ODI option.  After completing Setup, do not reboot.  Edit AUTOEXEC.BAT
and make the following changes:

1.  Remove or remark out the line that loads IPX.COM.

2.  Add a line to load IPXODI.COM after the line that loads RODI.

    The Setup program copied IPXODI.COM to your Reflection Network Series
    directory.  The line that loads IPXODI should include the path
    to your Reflection Network Series directory (\WRQNET).

    For example:

    C:\WRQNET\LSL
    C:\WRQNET\<network driver>
    C:\WRQNET\RODI /STACKS:7
    C:\WRQNET\IPXODI

--------------------------------------------------------------------------                               
			    Using BootCon and Setup
--------------------------------------------------------------------------                               

Setup does not recognize BootCon or other multiple configurations.

--------------------------------------------------------------------------                               
			     Reboot Workstation
--------------------------------------------------------------------------                               

Some machines will not reboot when you select the Reboot Workstation 
option at the end of the Setup.  If the reboot does not work properly, 
reboot the machine manually.

--------------------------------------------------------------------------                               
			    Hiding the RNS Icon
--------------------------------------------------------------------------                               

System administrators who do not want users to have access to the 
information available from the RNS icon can add the following to 
RNAPPS.INI in the Windows directory:

[Task]
Visible=False

The RNS icon will not be displayed on the desktop when the Reflection 
Network Series software is loaded and "RNS" will not be available from 
the Task List.

--------------------------------------------------------------------------                               
			     RNKILL Utility
--------------------------------------------------------------------------                               

RNKILL.EXE, a utility on the first setup disk, is a tool for debugging
when the RNS icon does not shut down properly.  For example, when Windows 
Sockets applications experience a GP fault and WINSOCK.DLL is not unloaded 
by Windows, you can use this utility.  When this kind of error occurs, the 
RNS icon often remains on the desktop and can only be shut down by ending 
the current Windows session.  You can use RNKILL.EXE to unload both the RNS 
TCP/IP stack and WINSOCK.DLL.  To install RNKILL.EXE, place the first RNS 
product disk in the A: drive and type the following at the DOS prompt:

	expand a:rnkill.ex_ c:\wrqnet\rnkill.exe

You may have to substitute another directory for "c:\wrqnet".  The expand
command is in your Windows directory.

--------------------------------------------------------------------------                               
			      SLIP and SHARE
--------------------------------------------------------------------------                               

Using a SLIP connection with SHARE loaded will produce a sharing violation 
if you close the connection just before dialing or while dialing is in 
progress.  The SLIP connection will remain open, and you must exit
Windows to close the connection.  Subsequent releases of Reflection Basic 
will address this problem.

--------------------------------------------------------------------------                               
			    No Fast File Transfer
--------------------------------------------------------------------------                               

The Reflection Network Series for Windows does not support Fast File 
Transfer in versions 4.11 or earlier of Reflection 1, 2, or 4 for Windows.  
It is best to disable fast file transfer to decrease file transfer 
startup time in this situation.  Open the command window (Alt-Y) and type 
SET FAST-FILE-XFER NO.  Fast File Transfer will be available in version 
4.2 of Reflection for Windows.

--------------------------------------------------------------------------                               
				  FTP Client
--------------------------------------------------------------------------                               

We recommend that you use the FTP Client shipped with Reflection Network
Series for Windows if you are testing the FTP Server.  It provides more
functionality than the FTP Client shipped with other Reflection products.

--------------------------------------------------------------------------                               
		     IBMTOK.DOS or ELNK.DOS drivers
--------------------------------------------------------------------------                               

If you use a network card that uses the drivers IBMTOK.DOS or ELNK.DOS,
the card displayed as the default for Setup may not match your particular
card.  Several cards share these drivers.  You may accept the card that
is suggested; the correct driver will still be installed.  If you prefer, 
highlight the correct card in the network card list before proceeding 
with the install.  The cards that may be incorrectly identified are 
summarized below:

TokenLink 3C619                      IBMTOK.DOS suggested default card

Also applies to:
----------------
IBM Token-Ring 16/4 Adapter
Token-Ring 16/4 Adapter/A

3Com EtherLink 3C501                 ELNK.DOS suggested default card

Also applies to:
----------------
Hewlett-Packard Starlan 10 Link I
Hewlett-Packard ThinLAN (part #27210x)

Novell NE2100                        NE2100.DOS suggested default card

Also applies to:
----------------
HPJ2405 Ethertwist

--------------------------------------------------------------------------                               
		       HP EtherTwist Plus ODI Driver
--------------------------------------------------------------------------                               

If you use HP Ethertwist Plus in an ODI environment, you may see
erratic behavior, such as involuntarily exiting Windows, when starting
the Reflection Network Series software.  If you see this problem, use
the ODI driver shipped with the network card (HP3AT16T.COM) rather than
the driver shipped with the Reflection Network Series (HPISAODI.COM).

--------------------------------------------------------------------------                               
			       Pathworks 5.0 
--------------------------------------------------------------------------                               

Use the following guidelines to set up the Reflection Network Series in 
an environment that includes PATHWORKS 5.0.

1. PATHWORKS 5.0 must already be installed.  Confirm that your current 
   PATHWORKS configuration allows you to make the connections you require.

2. Install the Reflection Network Series.  The Reflection Network Series 
   setup program successfully detects that you are running in an NDIS 
   (rather than ODI) environment.

   The Reflection Network Series Setup program uses PROTMAN.DOS in 
   CONFIG.SYS to locate PROTOCOL.INI; if it isn't found, Setup does the 
   following:

   *  Generates a new PROTOCOL.INI in the Reflection Network Series 
      directory (WRQNET).

   *  Inserts lines in CONFIG.SYS for PROTMAN.DOS and your card driver, 
      and adds lines in AUTOEXEC.BAT that load RNDIS, and NETBIND.

   Since this does not match the PATHWORKS configuration, you'll need to 
   make some modifications after you complete Setup.

3. After you finish Setup, do NOT choose Reboot Workstation.  Exit Setup 
   and use a text editor to modify the following:

   * Remove the device lines in CONFIG.SYS for PROTMAN.DOS and for your 
     card driver, for example, DEPCA.

   * Remove the lines in AUTOEXEC.BAT that load RNDIS and NETBIND.

   * Copy the sections in the Reflection Network Series version of 
     PROTOCOL.INI that apply to Reflection Network Series protocols
     and add them to the PROTOCOL.INI in your Pathworks directory (\PW).
     All the sections in \WRQNET should be copied except for those
     that refer to your network card; for example, the [DEPCA] section.

4. Edit the PATHWORKS 5.0 template file, such as CFG0001.TPL.  This is 
   an ASCII configuration file.  Add a line to load RNDIS in the NETWORK 
   section just prior to the NETBIND line, for example:

   [Network]
     {LOADDRV} {+DEST}PROTMAN.DOS /I:{+DEST}
     {LOADDRV} {+DEST}DEPCA.DOS
     {LOADDRV} {+DEST}LAD.SYS
     {LOADDRV} {+DEST}LADDRV.SYS
     {+DEST}DLLNDIS.EXE
     c:\wrqnet\rndis.exe /irq:<n> /stacks:7  <--- Add this line
     {+DEST}NETBIND.COM
     {+DEST}SCHK.EXE /ndis
     {+DEST}DNP.EXE
     {+DEST}LAST.EXE /node:{COMPUTERNAME}
     {+DEST}SETNAME.EXE {COMPUTERNAME} /nologo
     {+DEST}REDIRD.500 /L:8 /S:6
     {+DEST}PWLICLMT.EXE /L:{LICCOUNT} /nologo
     {+DEST}PWLICLM.EXE {LICENSESERVER} /group:{LICENSEGROUP}
     {+DEST}SETLOGON.EXE {username} *

5. Edit RNAPPS.INI in your Windows directory.

  This is an ASCII file for used by the Reflection Network Series.
  If you do not have an RNAPPS.INI file, you can create one.
  The following section and keyword in RNAPPS.INI ensures that the
  PATHWORKS PROTOCOL.INI file can be located by all applications that 
  use the Reflection Network Series:

  [NetInit]
    InitFile=C:\PW\PROTOCOL.INI

6. Reboot your PC and confirm that you can make connections with 
   PATHWORKS and with the Reflection Network Series.
