******************************************************************************
                   Reflection X Product Information
                   (C)opyright 1993-94 Walker Richer & Quinn, Inc.
******************************************************************************

The original distribution disks contain files for Reflection X version 4.10.
These files are in compressed format.

Reflection X Main Application Files
===================================
READMERX.TXT            This file.
RX.EXE                  Main Reflection X program.
RXSTART.EXE             Reflection X Client Startup.
RXLIB.DLL               Reflection X Dynamic Link Library.

Setup Files
===========
RX.INF                  SETUP.EXE
SETUP.LST               SETUP.MST
MANSETUP.BAT            SETUP.INC
UTIL.MST                MSCUISTF.DLL
MSUILSTF.DLL            MSINSSTF.DLL
CUSTOM.MST              MSCOMSTF.DLL
NOTES.MST               MSTEST.EXE
CONFIG.MST              VER.DLL
EXPAND.EXE              RXWIN.INF
MSSHLSTF.DLL            MSDETSTF.DLL
COPYLIST.MST

Utility and Support Files
=========================
*.KMP                   Keyboard settings files.
*.DMP                   Keyboard settings files with DEC mapping.
RX.HLP                  Reflection X help file.
FONTMAN.EXE             Font compiler.
M*.DLL & M*.EXE         Network files.

Directories
===========
Three subdirectories are created during Setup:
FONTS                   Contains the Microsoft FON format font files.
XSETUP                  Contains the Setup files.
VMS                     Contains files for DECnet users.

***************************************************************************
                       Technical Assistance
***************************************************************************

There are a number of ways to reach us--they are listed here and in the online
help for Reflection X:

         - Phone our technical support staff at (206) 217-7000.

         - On CompuServe, type GO REFLECTION and leave a message for SYSOP
           in Message area 10:  Reflection X or upload a file to library
           10: Reflection X.

         - Sales questions can be answered via (206) 217-7100.


-----------
Diagnostics
-----------
There are several diagnostic tools in Reflection and in Windows that
will help WRQ resolve some of the problems you might experience while
using Reflection. The following is a list of these files and guidelines
on how to generate them, if necessary.


SETUP.LOG
=========
The Setup utility creates a file called SETUP.LOG in your Reflection
directory (C:\RWIN\SETUP.LOG for example).  If you experience
problems running Setup, be prepared to send a copy of this file to us.


LOGFILE.TXT
===========
Server errors and warnings that occur while running Reflection X are
captured in a user-specified log file.  If Log Font Activity is selected
in the Fonts category, the log file also records each font request and
indicates whether it was satisfied and with what font.  Refer to this
file by choosing SETTINGS, then SERVER; choose View to look at the file.
This file (LOGFILE.TXT) is erased each time you start Reflection X, so
you may want to save this file to send to WRQ with problem information.


ABOUT BOX
=========
Select About from the Reflection X menu.  Here you can determine what
IP address or node number the server thinks you are using, what transports
are currently available, what TCP/IP stack you are using, etc.

This feature may be useful, for example, if you attempting to use both
the DECnet and TCP/IP transports at the same time.  From the About Box,
you can determine if both transports are being recognized by the server.


DRWATSON.LOG
============
Dr. Watson is a diagnostic tool that comes with Windows.  Certain
system problems will call the Dr. Watson utility and generate a
file that is useful in debugging.

If you experience a problem that produces a General Protection Fault
in Reflection:
- Make sure that Dr. Watson is loaded.
- Attempt to reproduce the error.
- Dr. Watson should display a dialog box where you can enter a short
  description of what you were doing when the error occurred.
- This information is written to the file DRWATSON.LOG in the
  directory where Windows is installed.
- Be prepared to send a copy of this file to WRQ when you report
  the problem.

***************************************************************************
                                We've Moved
***************************************************************************

As of March 21, 1994, WRQ's new U.S. address, phone, and FAX numbers
are as follows:

Corporate address:
    Walker Richer & Quinn, Inc.
    1500 Dexter Avenue North
    Seattle, WA  98109

Phone numbers:
    Corporate:              206-217-7500
    Sales:                  800-872-2829 or 206-217-7100
    Technical support:      206-217-7000
    BBS:                    206-217-0145

Fax numbers:
    Accounting:             206-217-0681
    International:          206-217-0196
    Sales:                  206-217-0293
    Technical support:      206-217-9492

*******************************************************************************
                            Setup and Configuration
*******************************************************************************

Installing Reflection
---------------------
Use the Setup program to install Reflection.  There are two methods to choose
from:

Method 1 -- Run Setup from the Windows File menu.
        1. Select Run from the File menu.
        2. Type <drive\path>SETUP and press <Enter> to begin installation.

Method 2 -- Run Setup from the File Manager.
        1. Double-click the File Manager icon.
        2. In the File Manager, select <drive\path>SETUP.EXE.

Setup makes modifications to the Windows files SYSTEM.INI and WIN.INI.  If you
have an existing copy of Reflection X, changes are made to the RX.INI file.

Note:  Reflection X will not run under Windows 3.0.

*******************************************************************************
                      Known Problems and Workarounds
*******************************************************************************

 *  Out of memory errors

    If you get an out of memory error, check to see if Windows is
    configured to use a temporary or a permanent swap file.  It is probably
    best to have a permanent swap file with adequate memory to load
    Reflection X.  See "Software Requirements" in your Technical Reference
    (in the chapter called "Installing Reflection X").

 *  16-color display

    The recommended Color Model choice for a 16-color display is
    StaticColor.  The StaticColor model is used for displays that have an
    unchangeable hardware color palette.  With this sort of palette, all
    color cells are read-only and all RGB values are preset.  X client
    requests for a certain color will be mapped to the color that most
    closely matches.

    To change the Color Model, choose Settings from the Reflection X menu
    and go to the Color category.

 *  HP Visual Editor

    The HP Visual Editor "ved" will not run if the setting for Selection
    Bound to Clipboard in Reflection X is PRIMARY.  Configure this setting
    in the Clipboard category of the Reflection X Settings dialog box.

 *  Windows Client Installation

    When you install Reflection X to a Windows Client machine, Setup
    may fail if you are installing to a drive without a writeable root
    directory.

    The Setup program creates a temporary directory on the boot drive
    of the local PC from which you are running Setup.  Since a boot
    drive of a WinClient machine may not be writeable, you may need to
    issue the following command:

                    MAP ROOT C:=<available directory>
    for example:
                    MAP ROOT C:=G:\USERS\PUBLIC\MYNAME

 *  DECnet and Reflection Network Series for Windows

    If you are attempting to run DECnet concurrently with TCP Connection
    for Windows, you MUST have the keyword USEVSL= set to 1 in your RX.INI
    file for DECnet and WRQ's TCP Connection to run concurrently.  If
    USEVSL=0 is set, then DECnet will not be an available transport for
    Reflection X.


*******************************************************************************
                      PC-NFS Version 4.0
*******************************************************************************

The following describes the PC-NFS "End User" files that are included on
your Reflection X disks.  These programs are essential to the operation of
applications written with the PC-NFS Programmer's Toolkit version 4.0.
This material was prepared by Sun Microsystems, Inc.  (C) 1992.


Introduction
============
The PC-NFS files are updated versions of several essential system files
that ship with PC-NFS version 4.0.  These new versions correct several
known problems with the operation of certain PC-NFS utilities; they replace
existing PC-NFS 4.0 files.  Users who have already upgraded to PC-NFS 4.0a
do not need these files.

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

1 -  List of included files
2 -  Installing the files using UPDATE.EXE
3 -  Checking version numbers to verify installation
4 -  Using the PC-NFS files

1) List of Included Files
   ======================
The PC-NFS files are as follows:

RTM.EXE         Version 4.0a    Resident transport module
RNMFILE.EXE     Version 4.0a    Resident name-service module
RNMNIS.EXE      Version 4.0a    Resident name-service module
RNMFILE.DLL     Version 4.0a    Resident name-service DLL
RNMNIS.DLL      Version 4.0a    Resident name-service DLL
RTMREM.EXE      Version 4.0a    Resident module unloader
RNMREM.EXE      Version 4.0a    Resident module unloader
TKLIB.DLL       Version 4.0a    Toolkit API library DLL
DNET.DLL        No version #    PC-NFS API library DLL
UPDATE.EXE      No version #    Installation program

2) Installation Using UPDATE.EXE
   =============================
The Reflection X Setup program installs the PC-NFS files to your Reflection
X directory.  Type the following at DOS prompt:

   UPDATE

The Update program searches the NFSPATH, NFSDRIVE:\nfs (PC-NFS 3.5 only),
and PATH directories.  If it finds an older version of the files RTM.EXE,
RNMNIS.EXE, RNMNIS.DLL, RNMFILE.EXE, RNMFILE.DLL, NETCONF, DNET.DLL, and
TKLIB.DLL, it offers you the option of replacing those files.  If you want
to save copies of the older versions of these files, answer "n" when you're
prompted to upgrade the file.

Whether you replace all, some, or none of the files, Update exits to DOS
when it is finished.

If Update finds none of the files in any of the directories it searches, it
will copy the files into every directory specified by NFSPATH.  This copy
operation could use a substantial amount of disk space if NFSPATH contains
a number of entries.  Having copies of different versions of the same
Toolkit module on your disk could lead to application execution errors
unless you carefully assign directory search paths.

Checking Version Numbers
========================
You can verify a successful installation of these PC-NFS files by using the
-V (version) parameter. For example, type:

   C:\NFS\RTM -V

If your files were successfully updated, you'll see the following:

   RTM.EXE version 4.0a

If you see "RTM.EXE version 3.0," you either chose to preserve the earlier
version of the RTM.EXE file during the Update program's operation, or the
Setup program did not copy the files to your PC.

If you think that the Update program did not successfully update your PC-NFS
files, run the program again.  Answer all the on-screen prompts carefully.

Using the Files
===============
Unless otherwise specified by a third-party application's instructions, the
only file that PC-NFS users load directly is the resident transport module,
RTM.EXE.  If you use PC-NFS version 4.0, refer to the PC-NFS Reference Manual's
chapter on PC-NFS commands, and the chapter on using Microsoft Windows for
information about using this module.  Also see "Sun PC-NFS" on page 39 in the
Reflection X Technical Reference that you received with this beta.

If you use PC-NFS and Microsoft Windows, you must load RTM.EXE before you
run Windows.  To load RTM, type the following at the DOS prompt:

   RTM

Or add RTM on a new line to your AUTOEXEC.BAT file so that RTM is automatically
loaded when you start up or reboot.

