***************************************************************************
                
                Reflection Network Series for Windows
                          3000 Connection   
                         Version 5.0 - Beta

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

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

* Installation of Beta
* How to Reach Us
* What's New in Version 5.0 of the Reflection Network Series
* Installing Single Program Files
* NFS and Windows for Workgroups
* NFS Requirements for Network File Sharing
* Support for VMS Locking with NFS
* NFS and Windows Network Setup 
* Configuring PC Workstations to Run the Server Version
* Other Setup Issues
    Cards with Plug-N-Play Options
    Cogent's EM960 Card
    Using BootCon and Setup
    Reboot Workstation Option
    Using the Server-Based Install on Large Drives  
* Installing and Using SLIP
* RNDIS and RODI Defaults
* DRWATSON.LOG

--------------------
Installation of Beta
--------------------

The enclosed Reflection Network Series software is provided for your 
evaluation and testing purposes only, and is not intended for distribution.  
The software has a built-in timer that expires in 180 days after 
installation. You will receive an expiration notification 10 days before 
the expiration date. After the expiration date, you will no longer be able 
to run the Reflection Network Series. The default installation directory 
for this beta version is \RWIN_B. Accept this default - do not overwrite 
your production software with time-limited versions.

In particular, do not copy the Reflection Network Series version 5.0 beta 
into a directory containing your current copy of the Reflection Network 
Series for DOS. The Setup program will overwrite modules are required for 
operation of the Reflection Network Series for DOS.

The default program group is Reflection. Choose another group name if you 
do not want icons for beta software in your Reflection program group.  

---------------
How to Reach Us
---------------

If you have any questions, problems, or suggestions, there are several ways 
to reach us:

- Fax your questionnaires, problem reports, questions, and comments to:
  (206) 217-0082 Attn Jackie Clough.
- Internet: jackiec@wrq.com.
- Phone our beta hotline at (206) 217-7200.
- On CompuServe, type GO REFLECTION and leave a message for SYSOP in 
  message area 16: Beta Testers. Or, upload a file to library 16: 
  Beta Testers.
- European testers may contact Rosemarie Cronin in the WRQ Netherlands
  office by phone at 31.70.375.11.00 or by fax at 31.70.356.12.44.
- For sales questions, phone (206) 217-7100.

----------------------------------------------------------
What's New in Version 5.0 of the Reflection Network Series
----------------------------------------------------------

Version 5.0 of 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 beta 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 Beta "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.)

-------------------------------
Installing Single Program Files
-------------------------------

Most Reflection Network Series program files are stored on the distribution 
disks in compressed form.  Therefore, you cannot simply copy them to your 
hard drive using the DOS COPY command.

The EXPAND utility, available with Windows 3.1, can be executed from the 
DOS prompt. It lets you copy a single file from the Reflection Network 
Series distribution disks. You might need to use this utility if a file is 
accidentally deleted, or if you need copies of local files in order to run 
the server version. The syntax for this utility is:

EXPAND <path> <compressed name> \<expanded name>

The <compressed name> is the name shown when you type DIR in the path where 
the Reflection Network Series original files are stored (that is, either A: 
or B:).

A <compressed name> varies from its <expanded name> by only one character: 
the final character of a compressed file's extension is an underscore. For 
most files, the underscore is the third character.

Here are some typical filename extensions:

386  COM   PIF  EXE
DLL  HLP   DOC  INI

For example, with Reflection installed on your C drive, the following 
command decompresses the RNSTAT.HLP file from the distribution disk 
located in the A drive:

EXPAND A:\RNSTAT.HL_ C:\RWIN\RNSTAT.HLP

------------------------------
NFS and Windows for Workgroups
------------------------------

You may need to make manual modifications after running Setup if you have 
a Windows for Workgroups machine but you do NOT have Windows network 
enabled. Setup enables NFS based on the presence of WFWNET.DRV even though 
it is not in use.

An error message such as "File Error - unable to find pmspl.dll" indicates 
that you should make the changes described below.

1. Open SYSTEM.INI.
2. Search for the string "WFWNET.DRV" - this entry should not be present in 
   SYSTEM.INI.
3. In the [boot] section, confirm that you have the following:
        network.drv = rnwnet.drv
   You may also see an additional line if you're using NetWare:
        secondnet.drv = netware.drv
4. Exit SYSTEM.INI.
5. Rename WFWNET.DRV in your \WINDOWS\SYSTEM directory. For example:
        REN WFWNET.DRV WFWNET.SAV

If you later want to reconfigure your Windows for Workgroups system to
enable networking, you must change WFWNET.SAV back to WFWNET.DRV.

-----------------------------------------
NFS Requirements For Network File Sharing 
-----------------------------------------

Before you start sharing network files with your PC, you should:

* Install the NFS client on your PC.
* Know the hostnames of any file servers that you want to use.
* Know your username and password on the NFS server system.

On the file server side, all of the files and software necessary to allow 
you access to file sharing services should already be installed and 
configured:

* Configure your username and password in the appropriate authorization
  file.
* Ensure that the pathnames of file systems you want to use are configured
  in the list of file systems available to remote users (that the file
  systems are exported)

--------------------------------
Support for VMS Locking with NFS
--------------------------------

If you have a VMS system, running DEC VMS or Open VMS, see "Enable File
Locking" in the Reflection Network Configuration Utility online help for
information about configuring NFS file locking and file sharing.

---------------------
NFS and Windows Setup
---------------------

NFS and Windows Setup (Windows 3.1) 
------------------------------------
During Setup, you're asked if you want to configure NFS as your
Windows network.  If you answer yes, no further steps are required.  

If you answered no to this question and you later decide to use the 
Reflection Network Series NFS client as your Windows network, you can 
use the Windows Setup utility to install NFS. Windows Setup will integrate 
Reflection NFS with Windows networking. This allows you to execute all 
NFS operations on network drives through standard Windows tools (Control 
Panel, File Manager, and Print Manager).

When you run the Windows Setup utility, in the Network list, select 
Reflection NFS (version 5.0 without NetWare support) or, if your PC uses 
Novell NetWare, Reflection NFS (version 5.0 with NetWare support).  

If you are installing Reflection NFS with NetWare support, Setup prompts 
you to install the Novell NetWare disk with files VIPX.386 and 
VNETWARE.386. These files may be in your WINDOWS\SYSTEM directory or in 
the path where you installed NetWare. 

Note:  
-----
The Windows Setup utility sets up Reflection Network Series NFS as 
your Windows network driver. However, you may need to edit the LASTDRIVE 
statement in your CONFIG.SYS file manually in order to make more PC drive 
letters available to the NFS client. See the Installation Guide for 
information about editing the LASTDRIVE statement. 

Also, see the Installation Guide for a summary of the system files that are 
modified when you integrate NFS with Windows networking.

NFS and Windows For Workgroups Network Setup
--------------------------------------------
During Setup, you're asked if you want to configure NFS as your
secondary network.  If you answer yes, no further steps are required.  

If you answered no to this question and you later decide to use the 
Reflection Network Series NFS client as your secondary network, you can 
use the Network Setup utility to install NFS.  Network Setup will 
integrate Reflection NFS with Windows for Workgroups networking. This 
allows you to execute all NFS operations on network drives through standard 
Windows tools (Control Panel, File Manager, and Print Manager).

When you run the Network Setup utility, click the Networks button and 
select the Other radio button. Then specify the driver you want to 
install: Reflection NFS (version 5.0 without NetWare support) or, if your 
PC uses Novell NetWare, Reflection NFS (version 5.0 with NetWare support).  

If you are installing Reflection NFS with NetWare support, Setup prompts 
you to install the Novell NetWare disk with files VIPX.386 and 
VNETWARE.386. Click the Skip button.

Note:  The Windows Setup utility sets up Reflection Network Series NFS as 
your secondary Windows network driver. However, you may need to edit the 
LASTDRIVE statement in your CONFIG.SYS file. See the Installation Guide for 
information about editing the LASTDRIVE statement. 

Also, see the Installation Guide for a summary of the system files that are 
modified when you integrate NFS with Windows networking.

-----------------------------------------------------
Configuring PC Workstations to Run the Server Version
-----------------------------------------------------

The Reflection Network Series beta Installation Guide describes in Chapter 
3 how to use Setup to configure a PC workstation after you've installed a 
Server version. The information in this chapter is not correct. This 
version of Setup does not copy files to the local drive as part of this 
configuration process. Instead, use the procedure below. (This procedure
is similar to that described in the alpha version of the Reflection Network 
Series.)

In addition, the server directory description in the Installation Guide 
mentions an \RNS subdirectory under the \SETUP subdirectory:in this beta 
version, the setup files are located in the \SETUP subdirectory. 

After performing a complete installation of the Reflection Network Series 
onto the network server, you must run a workstation Setup program from each 
PC that will use the server version. This creates and configures the 
initialization files on the PC that are required to use the server-version 
software.

Run the Setup program located in the \SETUP subdirectory of the Reflection 
Network Series path on the network.

After supplying the required information, Setup configures the PC's system 
files (AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI, and PROTOCOL.INI or NET.CFG) 
for any changes needed to run the Reflection Network Series software.

When Setup is complete, you must make some manual changes. If you have 
an NDIS setup on your PC, these changes are required: the final dialog box 
in the Setup program does not offer the option to immediately reboot your 
machine in order to ensure that these changes are made.  

Making Manual Changes to Your System Files 
-------------------------------------------
The changes described below apply only if the Reflection Network Series 
software is installed on a network drive and your PC is configured to run 
the network-installed software. If you performed a complete installation 
of the Reflection Network Series onto a local drive, no changes are needed.

Manual Changes for an ODI Environment:
--------------------------------------
If you use an ODI network interface on your PC, Setup makes changes to your
system files. In addition, you may need to change the order that RODI is
loaded, as described below.

*  A line is added to your AUTOEXEC.BAT file to load the RODI.EXE driver 
   from the network drive. However, you must already be logged in to the 
   network before the RODI.EXE line is encountered. For example, the line 
   may read:

   F:\RWIN\RODI 

*  If you don't log in to your network drive until later in your 
   AUTOEXEC.BAT file, move the RODI line below the lines that log you in.

   If you don't log in to your network drive from your AUTOEXEC.BAT file 
   at all (for example, you run a separate batch file to log you in), move 
   the RODI line to the file that does log you in, making sure that the 
   RODI line is below the lines that log you in.

Lines are added to your SYSTEM.INI file to load the following modules
when Windows starts:

   RNVNET.386 
   RNVUTIL.386 
   RNVNFS.386 (for NFS)
   RNWNET.DRV (if NFS is your Windows Network) 
   RNVNB.386 and RNLOAD.DLL (for NetBIOS)

You must already be logged in to the network before running Windows so 
these drivers can load.

If you don't log in to your network until after you start Windows, it is 
best to change your login procedure so that you're already logged in to the 
Novell network before running Windows.

A path statement is added to the bottom of your AUTOEXEC.BAT file to 
include the Reflection Network Series network drive in the search path on 
your PC. You do not need to change this line, even if the drive in the 
path statement is not valid until after you log in to the network; once 
you log in, the network drive letter will become valid.

Manual Changes for an NDIS Environment:
---------------------------------------
If you use an NDIS network interface on your PC, Setup makes a number of 
changes to your system files. Before you can use the Reflection Network 
Series software, you must copy some files to your local PC, edit one or 
more of your system files, then reboot the PC to have the changes take 
effect.

Note:
-----
When configuring a PC workstation for an NDIS environment, Setup does not 
provide a reboot button in the final dialog box. You must make the changes 
described below before rebooting your PC. If you reboot before making the 
changes, you will not be able to access your network drive and you will 
need to restore your PC to its previous state to continue.

When you perform a network installation for an NDIS environment, Setup 
makes the following changes to your system files:

A path statement is added to the bottom of your AUTOEXEC.BAT file to 
include the Reflection Network Series network drive in the search path on 
your PC. You do not need to change this line, even if the drive in the 
path statement is not valid until after you log in to the network; once you 
log in, the network drive letter will become valid.

Setting Up Local Copies of RNDIS and IPX
----------------------------------------
Lines are added to your AUTOEXEC.BAT file to load the IPX.COM and RNDIS.EXE 
files that are installed on the network drive. You must modify these lines 
after finishing Setup and before rebooting your PC.   

It is not possible to load RNDIS and IPX.COM after starting Windows. You 
must copy the files to your local hard drive, then edit the system files to 
refer to a local directory instead of a network directory.

Although you probably have an IPX.COM file already present on your PC (and 
probably loaded from AUTOEXEC.BAT), you must use the customized IPX.COM 
file supplied with the Reflection Network Series instead.

If you use Windows for Workgroups, Setup does not install a new IPX.COM, 
and you should continue to use the IPX supplied with Windows for 
Workgroups. In the following procedure, do not copy the IPX.COM file to 
your local drive or make any changes for IPX.COM in your AUTOEXEC.BAT 
file.

1. Using the path specifications for IPX.COM and RNDIS.EXE in the 
   AUTOEXEC.BAT file created by Setup, locate these files on the network 
   drive and copy them to a directory in the search path on your local 
   hard drive. (If you use Windows for Workgroups, skip the instructions 
   for IPX.COM in this step and in the following steps.)

    For example, if you have a directory in your search path called 
    C:\NETWORK (the directory in which you store your local area network 
    drivers, perhaps), you might copy the files to this directory.

2.  After copying the files to your local drive, edit AUTOEXEC.BAT so that 
    the drive and path specifications refer to the local files instead of 
    the ones on the network. Make sure to save AUTOEXEC.BAT as text only.

For example, you might change the lines in your AUTOEXEC.BAT file from 
this:

   F:\COMMON\WRQNET\RNDIS 
   .
   .
   .
   F:\COMMON\WRQNET\IPX.COM
   .
   .
   .
   to this:

   C:\NETWORK\RNDIS 
   .
   .
   .

   C:\NETWORK\IPX.COM
   .
   .
   .
3. Once you have copied the required files and made the changes to 
   AUTOEXEC.BAT, exit Windows if necessary and reboot your PC to have the 
   changes take effect. When you reboot, watch for any error messages to 
   make sure that the files load correctly.

If the drivers fail to load properly and you need to restore your PC to its 
previous state before you can access your network, the next section 
explains how to do this.

When you configure your PC for an NDIS environment and Setup completes, 
it's highly recommended that you make the changes described in the section 
above before rebooting your PC. If you reboot first, you will not be able 
to access your local area network, and therefore will not be able to copy 
the required files from the network drive to your local drive. In this 
case, you can restore your PC to its previous state, copy the files from 
the network or from the Reflection Network Series diskettes, make the 
changes to AUTOEXEC.BAT, then reboot.

To restore your PC to its previous state so you can access your local area 
network and copy the required files:

1. In the root directory of your PC, rename the AUTOEXEC.BAT file to a 
   unique name. If you do this in File Manager, for example, use the Rename 
   command in the File menu to change the name from AUTOEXEC.BAT to 
   AUTOEXEC.WRQ (or to some other unique name).

   Get a directory listing of all AUTOEXEC files and find the file with the 
   highest numbered extension; this is your previous AUTOEXEC.BAT file. For 
   example, if you have a few old versions of AUTOEXEC, the latest one 
   might be AUTOEXEC.003.

2. Rename the highest numbered AUTOEXEC file as AUTOEXEC.BAT.
3. In your Windows directory, rename your SYSTEM.INI file to a unique name; 
   for example, to SYSTEM.WRQ.

   Get a directory listing of all SYSTEM files and find the file with the 
   highest numbered extension; this is the file that Setup saved your 
   previous SYSTEM.INI file as. For example, this file may be called 
   SYSTEM.008.

   * Rename the highest numbered SYSTEM file as SYSTEM.INI.

   * Locate your PROTOCOL.INI file; rename it to PROTOCOL.WRQ.  

   * Rename the highest numbered PROTOCOL file as PROTOCOL.INI.

4. Exit Windows if necessary, then reboot your PC.

After you reboot, your PC should be in the same state it was before you ran
Setup, and you should be able to access your local area network. Once you
can do this, perform the manual changes described earlier, using the 
renamed copies of AUTOEXEC.BAT, SYSTEM.INI, and PROTOCOL.INI (the files
AUTOEXEC.WRQ, PROTOCOL .WRQ, and SYSTEM.WRQ in this example) for the
appropriate network drive and path information to modify.

Manually Configuring Your PC from the Distribution Disks 
--------------------------------------------------------
If you need to configure your PC with the above changes, and if you have 
access to the original Reflection Network Series distribution disks, you 
can copy the files required for an NDIS installation from the distribution 
disk, then make the required changes to AUTOEXEC.BAT and SYSTEM.INI, as 
described earlier. This step is an alternative to copying the files from a 
directory on the server: it is not required. It is provided in case you are 
not logged onto the server and you want to make modifications without 
logging on. 

Distribution Disk 1 contains uncompressed copies of the files needed for an 
NDIS environment - RNDIS.EXE and IPX.COM. Unlike the other files on the 
distribution disks, which are compressed, you can copy these files directly 
from the distribution disk to your hard drive. Once you have copied the 
files, you can then change the drive and path information in AUTOEXEC.BAT 
to refer to the local files. You may also need to run the ECONFIG program 
supplied with your network software to configure IPX for the correct 
network packet type; check with your system administrator for details.

Installing a Server Version: Users of the Reflection Suite for TCP
------------------------------------------------------------------
It is recommended that you install the beta version of the Reflection 
Network Series for Windows in a different directory on the server than the 
directory for the Reflection Suite for TCP.

If you're currently running a server version of the Reflection Suite for 
TCP version 4.5 and you have made that directory read-only, you'll need to 
modify the attributes of this directory before attempting to install the 
Reflection Network Series version 5.0 beta into the same directory. Type 
one of the following to change the attribute:

attrib -r *.*
or
flag *.* n

You'll need to use the procedure described in this README file in order to 
reconfigure your machine to use the server version.  

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

Using BootCon and Setup
-----------------------
If you are using BootCon or other multiple configuration software, the
Reflection Network Series Setup program may not be able to successfully
configure your system. The Setup program warns you that a multiple
configuration environment has been detected, and suggests that you run 
Setup with system files for a single configuration. If you proceed with 
installation and the resulting configuration does not operate as expected, 
use the backup versions of your system files (AUTOEXEC.BAT, CONFIG.SYS, 
etc.) to create a single configuration version and then run Setup again.

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.

Using the Server-Based Install on Large Drives  
----------------------------------------------
In this beta release, you might see the message "Insufficient Disk Space" 
when installing the Reflection Network Series to a server, even though your 
server has enough space for the installation. If you receive this error 
message, call us and we will send you a patch to resolve this problem.  

-------------------------
Installing and Using SLIP
-------------------------

SLIP Setup - Default Settings Assumed
-------------------------------------
Setup does not provide the option to configure SLIP dialing and script
settings in this beta version. Your SLIP settings are limited to the Basic 
TCP/IP settings when you install. After completing Setup, your SLIP 
interface is configured for default values. Use the Interface category in
the Network Configuration utility to make necessary changes from these
defaults.

Using the TTY Window
--------------------
The SLIP connection process provides a TTY window when the connection 
script is unable to interpret the server response. This is a handy way to 
type in the necessary string so that the connection process can continue.  

If you use the TTY window to log into your SLIP server, you must close the 
window in order to the SLIP script to continue executing and to allow you 
to make a SLIP connection.  

Dynamic IP Addressing with SLIP
-------------------------------
The Basic TCP/IP Settings dialog box provides the option to use dynamic IP
address assignment for your SLIP connection. If you choose this option, 
use the following procedure to implement dynamic IP addressing:

1. After confirming the baud rate and com port assignments are correct,
   start a Reflection Network Series application (for example, Ping).
2. The SLIP default connection procedure will prompt you for a phone 
   number. After you type in the phone number, a TTY window is displayed.  
   You'll see your server login prompt and then a password prompt. Type in 
   the information necessary to log in.
3. Your SLIP server will then respond with an IP address. Make note of 
   this response  - you'll be using it to create a Connect Command File 
   that will automate dynamic IP address assignment. For example, your 
   SLIP server may send a string such as "Packet mode enabled for IP 
   address: 123.123.23.2"
4. Use Network Configuration Utility to create a Connect Command File.
   a. Click Browse by the Connect Command File text box on the SLIP
      Interface Settings dialog box.
   b. Move to the User subdirectory. You'll see several files with the
      extension .CCF; choose the file that is the best match for your SLIP 
      server.
   c. After the prompts and commands for login and password, click Add Row.  
      In the prompt text box, type in the final portion of the string you 
      noted in step 3 above (for example, "IP address:"). Position your 
      cursor in the Commands text box, click Insert Command. Choose the 
      command GetDynamicIPAddress.
   d. Make any other changes required for your server and save this
      Connect Command File.

The next time you connect to your SLIP server, the Connect Command File you 
created will prompt the Server to assign an IP address.

Other SLIP Options
------------------
If you want to start your SLIP dialing procedure as soon as you start the
Reflection Network Series, choose Connect At Startup (the default is 
Connect on Demand.)

Browsing for Connect Command Files
----------------------------------
When you search for Connect Command Files (extension .CCF), the browse
dialog box displays the Reflection Network Series directory. Move to the 
User subdirectory to select a sample Connect Command File.

-----------------------
RNDIS and RODI Defaults
-----------------------

Some default settings for RNDIS.EXE and RODI.EXE have changed with this 
version.  The RNDIS /RECEIVES default is now 16. and /LIFOS is 6. The 
RODI /ECBS default is now 20 and /LIFOS is 4.

------------
DRWATSON.LOG
------------

Dr. Watson is a diagnostic tool shipped with Windows. Certain system 
problems use the Dr. Watson utility and generate a file that is useful for 
debugging purposes.

If you experience a problem that produces a General Protection Fault in 
Reflection Network Series:

- Make sure that Dr. Watson is loaded.
- Delete the current DRWATSON.LOG file in the Windows directory.
  (If the log file is too large, Dr. Watson adds only abbreviated entries 
  to the log file.)
- Edit the DR. Watson section in WIN.INI, located in your Windows 
  directory.  Use the following values:

  [Dr. Watson]
  DisLen=12
  DisStack=10
  TrapZero=1

- Try to reproduce the error.
- When Dr. Watson displays a dialog box, enter a short description of what 
  you were doing when the error occurred.
- This information is written to the file DRWATSON.LOG in your Windows 
  directory.
- Be prepared to send a copy of this file to WRQ when you report the 
  problem.

