***************************************************************************
                
                Reflection Network Series for Windows
                          TCP Connection   
                           Version 5.01

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

Contents:
   What's New
   Help for GPF in GROWSTUB with Mosaic
   Troubleshooting Incomplete Setup
   Reflection Suite for TCP on a Server
   Other Setup Issues
       Cards with Plug-N-Play Options
       Cogent's EM960 Card
       US Robotics Modem and SLIP
       Madge ODI Driver - Extra File Needed
       Reboot Workstation Option
       HPJ2405A Network Card
   Note to Beta Testers of the Reflection Network Series

----------
What's New 
----------
This version Reflection Network Series for Windows contains many new 
features and enhancements. The following is a summary of only some of those 
features. For more details on these features and others, please refer to 
your documentation and online help.

*  NFS Client

   The Reflection Network Series now supports NFS (Network File System), a 
   system that provides transparent access to shared files. The NFS client 
   lets you connect to remote file systems and printers on NFS servers.

*  NetBIOS Support

   You can now use the Reflection Network Series TCP/IP as a transport for 
   Windows for Workgroups. The Setup program can configure NetBIOS for your
   machine, or you can use the Network Setup utility in Windows for 
   Workgroups to configure NetBIOS after completing Setup. 

*  Remote Boot Enhancements

   In addition to RARP and BOOTP, the Reflection Network Series now 
   supports DHCP (the Dynamic Host Configuration Protocol) as a Remote 
   Configuration option.

   All Remote Boot options (RARP, BOOTP, and DHCP) can now be requested as 
   part of Setup.

*  Installing and Running a Server-Based Version of the Reflection Network 
   Series

   If you have the appropriate license, you can set up a server version of 
   the software. After the software is installed on a network server, 
   system configuration files on your PC are created or modified to run the 
   server version. The server version allows multiple users to run the same 
   copy of the software at the same time. See the "Installation Guide" for 
   details.

*  Finger Client

   Use Finger to request information about a single user or all users on a 
   host. The information returned can include a login name, full user name,
   phone number, office number, office location, and other status 
   information.

*  TFTP Server

   TFTP is a file transfer protocol designed for systems with minimal
   capability and overhead. TFTP allows routers or diskless devices to 
   download software from your PC. Use the Network Configuration Utility to 
   set up your machine as a TFTP server.

*  Ping  - Resolve Name or IP Address, Find Route

   In addition to issuing a Ping request, you can use DNS to resolve a host 
   name or IP address even if the host is not running. Ping also includes 
   a Find Route option, which allows you to view the path that a Ping 
   request takes to get to a host.

*  Toolbars and Tooltips

   Most Reflection Network Series applications now have Toolbars and 
   Tooltips for easy access to frequently requested operations.

*  FTP Client Scripting

   A new Script menu allows you to record commands entered at the FTP 
   command line, save recorded commands to a script file, edit existing 
   scripts, and play back script files (executing the commands as though 
   they had been entered at the FTP command line).

   You can now start the FTP client with a runtime command that 
   automatically executes a single file transfer command or executes an FTP 
   script file that contains multiple commands. A record of the results of 
   the commands that are executed is stored in a log file.

*  LPR  - Print Redirection from Other Windows Applications

   You can now use LPR to print from a Windows application. To do this, set 
   up a "watch job" that lets you spool print jobs from Windows 
   applications to your LPR printer.

*  SNMP - Trap support

   An SNMP service can report network management information in discrete
   blocks of data called traps. Traps allow you to program your SNMP agent 
   to send information to a manager when exception events occur.

* WSOCKETS.DLL

   The Reflection Network Series now supports applications that use the
   Sockets portion of HP ARPA Services. Applications that can use this
   support include HP NewWave Mail and HP AllBase. (Other applications that 
   previously used this interface have converted to a Windows Sockets
   interface in recent releases.)

   The WSOCKETS interface is based on Berkeley sockets, used in a variety
   of applications before the Windows Sockets specification was developed.
   The Reflection Network Series module that provides this support is
   WSOCKETS.DLL. (This is not the same WSOCKETS.DLL shipped with the DOS
   version of the Reflection Network Series.)

------------------------------------
Help for GPF in GROWSTUB with Mosaic
------------------------------------
Enhanced Mosaic is a Courtesy Application shipped in the same package as 
the Reflection Network Series for Windows.  

When you start a Win32-based application using Win32s(TM) under Windows(TM)
3.1 or 3.11 or Windows for Workgroups, you may receive a general protection
fault (GPF) in POINTER.DLL caused by the Microsoft Mouse driver 9.01
GROWSTUB component. Microsoft has corrected this problem, so all you need
to do is download HD1061.EXE and replace the POINTER.DLL file.

Internet
     ftp ftp.microsoft.com
     Change to the SOFTLIB\MSLFILES directory
     Get HD1061.EXE

CompuServe
     GO MSL
     Search for HD1061.EXE
     Display results and download

Microsoft Download Service (MSDL)
     Dial (206) 936-6735 to connect to MSDL
     Download HD1061.EXE

You can also order the latest mouse driver, v9.01b (p/n 135-099-309), from
Microsoft's Product Support Services at (206)635-7040 for a fee.

--------------------------------
Troubleshooting Incomplete Setup
--------------------------------
As you finish Setup, you may see a dialog box indicating Setup is not 
complete and that files currently in memory will be copied as you exit 
Windows. In most cases, clicking Continue will end your Windows session and 
then start Windows again. If Windows does not restart, you may need to 
perform an additional step.  Use these instructions only if you find 
problems running the Reflection Network Series after running Setup.

In your Reflection Network Series directory, check for the presence of
temporary files (*.TMP).  If they are present, run the batch file
_MSSETUP.BAT, also located in your Reflection Network Series directory. 
This will complete the Setup process.

------------------------------------
Reflection Suite for TCP on a Server
------------------------------------
Do not use the Configure Only option for the Reflection Suite for TCP after
installing version 5.01 of the Reflection Network Series.

If you have set up the Reflection Suite for TCP version 4.5 on a server, 
you can upgrade the Reflection Network Series portion of the product to 
version 5.01.  Follow these steps:

1.  Make sure you have implemented and tested your Reflection Suite for TCP
    implementation on the server.
2.  Install the Reflection Network Series version 5.01 on the server, using
    the instructions available in the Installation Guide.  Do NOT install
    this version in the same directory as your Reflection Suite for TCP
    software.
3.  Instruct users to always run the Configure Only option for the 
    Reflection Suite for TCP first; have them confirm that they can get a 
    connection to the host with Reflection 2.

    Next, users can run the Configure Only option for the Reflection 
    Network Series for Windows version 5.01 in the separate setup directory 
    on the server.

------------------
Other Setup Issues
------------------

Cards with Plug-N-Play Options
------------------------------
Newer cards with Plug-N-Play capability may be set with Plug-N-Play 
enabled. In order to use such a card with the Reflection Network Series for 
Windows, disable Plug-N-Play.

For example, if Plug-N-Play is enabled, the 3COM Etherlink3 card produces 
the message "Error 5735: Can't find network adaptor" when NETBIND is 
executed in an NDIS environment. With the 3COM 3C509B card, you may see 
"Error 33: unable to bind" for the same reason.

Cogent's EM960 Card
-------------------
If you use Cogent Data Technologies, manufacturer of said EM960 card, and 
find you cannot connect to your host or you're receiving traffic but can't
send packets, you need a new driver. Contact Cogent Technical Support.

Madge ODI Driver - Extra File Needed
------------------------------------
If you are installing a Madge driver for and ODI environment using the 
Reflection Network Series Setup program, do the following after you've 
finished running Setup and before rebooting your machine.  Copy 
MDGDOS21.BIN to the same directory that has the MADGEODI.COM file.  
MDGDOS21.BIN is included on the Reflection Network Series ODI drivers 
disk - you must decompress this file using the EXPAND utility. 

US Robotics Modem and SLIP
--------------------------
When using a US Robotics 14.4 modem with SLIP, do not choose the 14400 baud
option for your interface.  Try 9600 or 19200 instead. 

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.

HPJ2405A Network Card
---------------------
The Setup program assumes the driver NE2100.COM is to be used for the 
HPJ2405A network card.  However, AM2100.COM can also be used. If you are 
using AM2100.COM rather than NE2100.COM, run Setup and select Other 
Interface and type in AM2100.COM so that Setup can locate your driver. 

-----------------------------------------------------
Note to Beta Testers of the Reflection Network Series
-----------------------------------------------------
You may experience a problem starting a beta version of Reflection 1, 2, 4, 
or Reflection X after installing the shipping version of Reflection Network 
Series.  If so, please read the following.

You may have used the default beta directory (RWIN_B) for both the 
Reflection Network Series and one or more of the Reflection products listed 
above.  If you then install the Reflection Network Series into a different 
directory (the default non-beta directory is RWIN), the beta versions of 
Reflection will attempt to use some of the beta Reflection Network Series 
modules located in the same directory. You will probably receive a 
Reflection Network Series error message error dialog when you try to start 
a beta version of a Reflection product. 

To prevent this problem, do the following:

1.  Confirm that the shipping version of the Reflection Network Series is 
    installed by running a non-Reflection application.  For example, run 
    Ping to confirm that your host responds.
2.  The the RWIN_B directory, rename or delete WINSOCK.DLL and all modules 
    with RN as the first two characters (for example, DEL RN*.*).

This will force Reflection to use the shipping version of the Reflection
Network Series.
