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

	   Reflection 1 for Windows Version 4.21 README File    
   
***************************************************************************

Contents:
   Changes in 4.21
   Changes and New Features in 4.2
   Installing Reflection
   Changes to System Files
   Upgrading Settings Files from Version 4.0 of Reflection
   Removing Files Used by Earlier Versions of Reflection
   Troubleshooting - Setup and Configuration
   Using Different Versions of Reflection for Windows Concurrently
   Uploading the Host File Transfer Program
   Restrictions for Windows Sockets
   Mapping the "\" Character
   The Diamond 24X Video Driver
   Effect of Using FTP's PC-TCP with Older Versions of WINSOCK
   Using DDE and Excel
   Using HP MPE/XL Version 3.1
   Using Reflection with Windows NT
   Using Reflection with OS/2
   Diagnostics

---------------
Changes in 4.21
---------------

Version 4.21 resolves the following problems that were occuring in 
version 4.2:

* Command files encrypted with the CRYPT.COM utility are now executed 
  correctly; this includes files executed by the WRQ product called 
  DeskDirect.

* Reflection version 4.21 will run on a 286 PC (version 4.2 required 
  a 386 or higher computer).

* You can now configure a workstation PC to run a server version of 
  Reflection, even when the workstation does not have "write access" 
  to the Reflection server directory.

-------------------------------
Changes and New Features in 4.2
-------------------------------

An outline of the 4.2 features is provided here. For additional 
information, refer to the documentation and on-line help.

* With the release of the MPE/iX version 5.0 operating system, 
  the HP 3000 will be POSIX .1 and .2 Compliant. Version 3.0 of 
  WRQ's native mode version of the PCLINK2 protocol includes the 
  following POSIX features:

   - Support for the POSIX file naming convention - long file names,
     hierarchical directories, special characters in file names,
     and case sensitivity in file names.  In Reflection, there is a 
     new list box in the File Transfer Setup dialog box called 
     MPE File Names.  The two options are MPE (the default) and POSIX.  

   - Native POSIX files have a new record format "stream," which is
     just a stream of bytes.  Files created under the POSIX shell
     or by POSIX programs have this format, by default.  In Reflection, 
     there is a new check box in the File Transfer Setup dialog box
     called Send As Stream.  By default, this check box is cleared.


* If Reflection finds either the Reflection Network Series for DOS
  version 2.0 or higher, Reflection Network Series for Windows 
  or an equivalent Windows Sockets compliant stack, you can now specify 
  a TCP/IP Host Names File for the VT-MGR and TELNET Connection Types.

  You can also set the Destination Port for VT-MGR and the following 
  additional options for Telnet:

      Telnet Terminal Type
      TCP Port
      Send LF After CR
      Initiate Option Negotiation 
      Request Binary
      Ctrl-Break Character 

* Version 4.2 has four new connection template names:

  Reflection 1 Connection Defaults
  Reflection 1 VT Connection Defaults
  Reflection 2 Connection Defaults
  Reflection 4 Connection Defaults

  These templates replace the pre-4.2 templates HP700/92 Defaults and 
  VT320 Defaults. If you are upgrading from an earlier version to this 
  4.2, the Setup program does not delete these existing default 
  templates. For example, when creating the Reflection 1 Connection 
  Defaults template, the existing connection template (HP700/92 Defaults) 
  merges into the new connection template, with the existing 
  settings taking precedence.

* In the Basic and New Connection dialog boxes, the default Connection 
  Type is now NONE (instead of COM1). This change was made because, in 
  many cases, COM1 was already in use by another Windows application or 
  a mouse. Therefore, you received the error message "COM1 is already 
  in use by Windows or another application" when your intention may not 
  even have been to connect to this datacomm port. 

  If you're upgrading from an earlier version of Reflection, the old    
  default Connection Type is retained when you upgrade to version 4.2; 
  that is, it will not revert to the new default of NONE.

* Version 4.2 has added a couple of enhancements when connecting using
  NetWare for LAT (NLAT). With NLAT, you must attach to a Novell 
  Communication Executive server before you can access the LAT 
  services available from the server. A separate program, NLATCP.EXE, 
  included with version 4.2 of Reflection, performs this 
  Attach function. You can run NLATCP before starting Windows to have
  immediate access to services in Reflection.

  Another enhancement to version 4.2 is that NLAT now runs under the 
  OS/2 operating system.  You must run Win-OS/2 in standard mode.

* The On Exit group box options in the Connection Preferences dialog 
  box have been removed. The behavior in version 4.2 is to close all 
  connections (the original default setting) started in that 
  particular copy of Reflection when you exit (this will not affect 
  connections established in other copies of Reflection). 

* If you're connected using TCP over Windows Sockets, there is no limit 
  on the number of fast file transfers you can perform. (When 
  connecting over the DOS Reflection Network Series stack,there is a 
  limit of three fast file transfers.)

* There are keystrokes reserved for both Reflection (such as Alt-F, 
  to open the File menu) and for Windows (such as Ctrl-Esc, to 
  display the Task List). Attempting to remap these keystrokes in 
  Reflection, from either the Keyboard Map Options dialog box or 
  by using the command language keyword KEYMAP, results in an error 
  message. 

  Version 4.2 of Reflection includes a new SET parameter called 
  ALLOW-REMAP-WIN-KEYSTROKES. When set to YES, this allows you to use 
  the KEYMAP command to remap most of the reserved keystrokes.

* The printer you select in Reflection's Print Setup dialog box is saved 
  to a settings file. Changing printers in the dialog box has no effect 
  on the default printer used by other Windows applications. 

  In version 4.2, you can force Reflection to always use the default 
  printer specified under Windows by executing the following from the 
  command window: 

  SET PRINTER-DEFAULT ""

  Then, choose Save from the terminal window's File menu. 

* Reflection for Windows version 4.2 provides full support for a 
  new Windows networking product released in June 1994 from WRQ, 
  including support for fast file transfers. The new Reflection 
  Network Series for Windows is the optimum environment for running 
  networked Windows-based Reflection products with simultaneous 
  access to Windows Sockets compatible applications and to your 
  PC network. 

* The REFLECT.INI file has a new section called [Global Values]. This 
  section is created only if you enter a name in the TCP/IP Host Names
  File text box while making a Telnet or VT-MGR connection.  This text
  box only appears if the Reflection Network Series for Windows, 
  Reflection Network Series for DOS version 2.0 or higher, or an
  equivalent Windows Socket compliant stack is found. 
    
* Prior to this version, you could set a network session number up to 16. 
  With the 4.2 release, you can set the session number up to 
  255.  This setting is valid for IBM-ACS, INT-14, U.B., NASI, NET-VMS,
  and EICON connections only.

* By default, the terminal window title bar shows the name of the 
  current settings file. The name in the title bar is also the text you 
  see when you minimize Reflection. 

  You can change the text that appears in the title bar, and 
  consequently on the icon title, using the following SET parameter: 

  SET WINDOW-TITLE "<text, maximum 64 characters>"

* The VAXLINK2 file transfer program has a new switch, D<n>.  This 
  switch sets how, and if, Reflection should attempt to perform fast 
  file transfer.

* If you run Windows in 386 enhanced mode and the file VINT14.386 cannot 
  be found when you start Reflection, you now will be warned about this
  situation with a dialog box, however Reflection will start.  Prior to
  version 4.2, Reflection would refuse to run.  However without this 
  virtual device driver you won't be using Reflection's enhanced data 
  communications driver which provides better performance and causes less
  interrupt latency. Another side effect is the WRQ file transfer protocol
  won't be able to perform "fast file transfers" over certain networks.

* The following change was made to a parameter in the CONNECT command:
  
  CONNECT <node> USING TELNET

  Acceptable synonyms for TELNET are TEL-MGR and TELNET-MGR (used by 
  versions of Reflection prior to 4.2). 

* New SET parameters are:
 
  SET ALLOW-REMAP-WIN-KEYSTROKES {YES | NO}
  SET NSVT-PORT {0 | 1537 | 1570}
  SET PRINTER-DEFAULT <value>
  SET TELNET-BINARY {YES | NO}
  SET TELNET-BREAK {YES | NO}
  SET TELNET-LF-AFTER-CR {YES | NO}
  SET TELNET-NEGOTIATION {YES | NO}
  SET TELNET-PORT <value> 
  SET TELNET-TERMINAL <value; maximum 9 characters>
  SET TRANSFER-MPE-FILENAMES {MPE | POSIX}
  SET TRANSFER-MPE-STREAM {YES | NO}
  SET WINDOW-TITLE

* The button palette, user keys, and the Paste command from the Edit 
  can now be used with the ACCEPT command language keyword.

* In block mode applications, you can now change a transmit-only field to
  normal, and vice versa.

* Files created by DOS on a Pathworks file service have a record 
  format of STREAM rather than the usual variable length or fixed
  length format.  To successfully download these files, first choose 
  Transfer Setup from the File menu and select VAX/VMS as the Host System 
  Type. Then choose Transfer from the File menu, click the Advanced button,
  and select the Use Block Reads on Receive check box (or you can 
  append the switch "/B" to the end of the host name in the WRQ File 
  Transfer dialog box.

* Windows Client users upgrading to version 4.11 or above of Reflection 
  for Windows will have duplicate copies of the files listed below.  They
  are copied to the Windows directory by HPASSIST (the Windows Client
  install program) and are copied to the Reflection directory by the
  Reflection for Windows Setup program.

	RCOM.DLL
	VINT14.386
	R_ROMAN8.FON
	R_ASCII.FON
	R_MULTI.FON
	R_TECH.FON
	R_GRAPH.FON
   
   In order to ensure that you are using the most recent version of these
   files, delete them from your Windows directory.

   You won't be able to run Reflection if you fail to remove the older 
   versions of these files.

*  Reflection for Windows version 4.2 is no longer tested for compatibility
   with Reflection Network Series for DOS version 1.11.  If you are having
   difficulties, please contact Walker Richer and Quinn.
	  
---------------------
Installing Reflection
---------------------
To install Reflection use the supplied Setup program:

	1. Start Windows 3.1.
	2. Choose Run from the Program Manager File menu.
	3. Type <drive:\>SETUP and press <Enter>.
	4. Follow the prompts to install Reflection.

Setup makes modifications to the Windows files SYSTEM.INI and
WIN.INI.  If you have an existing copy of Reflection, changes
are also made to the REFLECT.INI file.  Copies are made of the
original files and are backed up using numerical extensions.    

If you have modified the amount of space allocated for VINT14HEAPSIZE
in the SYSTEM.INI file and the modified value is less than 8192,
Setup changes it back to the default of 8192 (see the next section). 
VINT14HEAPSIZE is not modified if the value is greater than or 
equal to 8192.

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

If Setup does not complete successfully, you may use the batch file 
MANSETUP.BAT to install Reflection:

	1.  Create a directory for Reflection from the DOS prompt,
	    e.g., MD RWIN.

	2.  Change to the directory, e.g., CD \RWIN.

	3.  Put the first Reflection disk in the floppy drive.

	4.  Type <drive>:\MANSETUP <drive>: to start the manual 
	    install process, where <drive> is the floppy disk drive.
	    For example: type A:MANSETUP A:

This process installs Reflection.  You must manually update your WIN.INI
and SYSTEM.INI files, as described later.

Modification must also be made to the REFLECT.INI file if you want to take
advantage of the additional predefined settings available with 4.21:

	*  If you have an earlier version of Reflection and have not 
	   created connection templates or color schemes, copy the 
	   REFLECT.INI file from disk 1 over your existing REFLECT.INI.  
	   If you have created connection templates and color schemes 
	   and want to save them, you must cut and paste the new 
	   information from the DEFAULT.INI file on disk 1 to your 
	   existing REFLECT.INI.

	*  If you do not have an existing copy of Reflection, copy the 
	   REFLECT.INI file from disk 1 to your Windows directory.

-----------------------
Changes to System Files
-----------------------
* Changes to WIN.INI:
    In the [Extensions] section:
	 RCL=<path>\R1WIN.EXE , ^.RCL
	 RC1=<path>\R1WIN.EXE , ^.RC1
	 R1W=<path>\R1WIN.EXE ^.R1W

* Changes to WIN.INI if you're installing Reflection 1 for Windows
  and Reflection 2 for Windows (or Reflection 4, in which case all "R2"
  references change to "R4"):
    In the [Extensions] section:
	 RCL=<path>\R1WIN.EXE , ^.RCL
	 RC1=<path>\R1WIN.EXE , ^.RC1
	 RC2=<path>\R2WIN.EXE , ^.RC2
	 R1W=<path>\R1WIN.EXE ^.R1W
	 R2W=<path>\R2WIN.EXE ^.R2W

* Changes to SYSTEM.INI:
    In the [386Enh] section:
	 device=<path>\VINT14.386
	 VINT14HEAPSIZE=8192

* Changes to REFLECT.INI:
    DEFAULT.INI and REFLECT.INI, copied during Setup, contain
    predefined file transfer settings and color schemes.  If you
    have an existing version of Reflection for Windows, the contents
    of DEFAULT.INI are added to your existing REFLECT.INI file.

-------------------------------------------------------
Upgrading Settings Files from Version 4.0 of Reflection
-------------------------------------------------------
If you use a transfer protocol other than WRQ and have saved it
in a settings file in version 4.0, after installing 4.21 of Reflection the
settings file will display a different protocol.  For example, if
you saved a settings file in version 4.0 with the Transfer Protocol set
to Kermit, version 4.21 will use XMODEM when you load the settings file.

To correct this problem, follow these steps:

  1. Open the settings file.
  2. Choose Transfer Setup from the File menu.
  3. Select the correct value from the Transfer Protocol list box.
  4. Choose OK.
  5. Choose Save from the File menu.

Other version 4.0 settings are not affected.

-----------------------------------------
Troubleshooting - Setup and Configuration
-----------------------------------------
Following are a list of general troubleshooting topics:

- If you plan to install to an empty PATHWORKS drive, you must 
  create the directory where Reflection will be installed before 
  running Setup.  

- VSafe is a memory-resident program that constantly monitors your
  PC for activity that may indicate a virus. This utility is provided
  with MS-DOS 6.0.  If VSafe is loaded in memory you MUST unload 
  it before running the Reflection Setup program or any other Windows
  Setup programs.  Consult your MS-DOS 6.0 User's Guide for more
  information.  

- During Setup, if you receive a message telling you to free up 
  disk space before continuing, free up more than the amount 
  recommended in the message.  This amount given is only an estimate.

- Reflection version 4.21 dynamically loads its font files.  If you 
  have a version 4.0 or earlier of Reflection, the lines that 
  specified the location of your font files in the WIN.INI file 
  were removed by Setup.  If you plan to run Reflection for Windows 
  version 4.21,  4.0 or earlier versions of Reflection for Windows 
  you must add the following lines back to your WIN.INI file:
      R_LINE=<path>\R_LINE.FON
      R_ROMAN8=<path>\R_ROMAN8.FON

      The <path> is the location where Reflection version 4.21
      is installed (NOT the earlier version).  If you accepted the
      default path during Setup, then this is RWIN.

- If Setup does not complete successfully, use the batch file 
  MANSETUP.BAT to install Reflection as described earlier in this file.

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

- If you use Version 2.04 of the Microsoft 3D Windows Controls DLL, 
  it must be located in the Windows SYSTEM directory.  If you move 
  this file to the Reflection directory, you will receive an error 
  message when Reflection starts, stating that the 3D DLL is not 
  properly installed. 

- If you receive an error message while attempting to connect using
  the SET DATACOMM-PORT command, try using the CONNECT command instead.
  The former command is included in the Reflection for Windows products
  for compatibility with the Reflection for DOS product.  The CONNECT
  command is the method in which you should establish a connection using
  Reflection for Windows, since it allows you to include the following
  parameters:

    Syntax:
      Form 1:  CONNECT <connection name>
      Form 2:  CONNECT <datacomm node> USING <datacomm port>
	       [BAUD <value>] [PARITY <value>] [PASSWORD [<value> | {}]]
	       [SESSION# <value>] [NODE <name>] [DESTINATION <dest. port>]
	       [PORT <value>] [BREAK] [BINARY]

  See the online help for more information on the CONNECT command.


---------------------------------------------------------------
Using Different Versions of Reflection for Windows Concurrently
---------------------------------------------------------------
Version 4.21 DLLs are version specific with the exception of
RCOM.DLL.  If you are running a previous version of Reflection
for Windows, you should replace its RCOM.DLL and VINT14.386 with         
4.21 versions of these files.  This will eliminate possible conflicts 
that can arise when older versions of Reflection for Windows are loaded
prior to version 4.21.  

KEYINT.DLL, used in pre-4.0 versions of Reflection, was
replaced in version 4.0 with RKEYBRD.DLL.  If you want to run
version 3.70 or 3.71 of Reflection concurrently with a 4.21 version
of Reflection, a new version of KEYINT.DLL must be installed.
The new version of KEYINT.DLL is installed by Setup.  Copy it
to the same directory where version 3.70 or 3.71 of Reflection
resides.

The Reflection for Windows version 4.21 font files have additional
font sizes that are not available in versions 3.7 and 3.71. These
enhanced font sizes are not fully supported in version 3.7 or 3.71.
For example, if you use Reflection for Windows version 4.21 fonts
with version 3.71, you might receive an Internal Integrity Check
error if you use 132 column mode in Reflection and a VGA display
adapter.  The preceding section addresses font entries required 
for previous versions of Reflection.

----------------------------------------
Uploading the Host File Transfer Program
----------------------------------------
The upload program UPLOADHP.RCL attempts to use an existing copy
of PCLINK or PCLINK2 to upload the newest version of PCLINK2 to your
host.  If you have either PCLINK or PCLINK2 on your host and file
transfers require 7-BIT, then you must make this change prior to
running UPLOADHP.RCL.  For PCLINK, add ;PARM=1 to the host startup
sequence.  For PCLINK2, change the transfer link to 7-BIT (you can
do this in the File Transfer Setup dialog box).

If PCLINK or PCLINK2 do not exist on your host, UPLOADHP.RCL requires
a full 8-BIT path.  You must have a direct-connect line or a direct
modem line to your host.  Parity must be set to NONE.

If your host connection requires that your host prompt be set to
"^@" (for example, an X.25 connection), then you cannot use this
connection to upload a new copy of PCLINK2.  You must receive a
host prompt character, usually a ^Q, to successfully execute
UPLOADHP.RCL.  Try using a direct-connect line or a direct modem
line to your host.

--------------------------------
Restrictions for Windows Sockets
--------------------------------
Reflection version 4.21 includes support for Telnet running over
Windows Sockets compliant TCP/IP stacks.  The file providing
this support is RNTELNET.DLL, located in the Reflection directory.
To connect to the stack, select the TELNET Connection Type after
starting Reflection.  Use the WINSOCK.DLL provided by your
network vendor.

The following restrictions apply when using the Reflection 
Telnet DLL:

* You cannot have the Telnet Connection TSR (available with the 
  Reflection Network Series for DOS) loaded in memory.  For example, 
  do not run STARTTEL.BAT or TELMGR.EXE in STARTNET.BAT. If the TSR 
  is detected, Reflection will not utilize the Windows Socket's 
  compliant TCP/IP stack.
	
* When sending or receiving large binary files to high speed hosts 
  using Microsoft's TCP/IP for Windows for Workgroups version 1.0, 
  Reflection will display the message "Unable to transfer file--transfer
  link failed," and the session will be hung.  To resume your session, 
  select Close from the Connection menu.  To avoid this during file 
  transfers, change the Transfer Link to 7-Bit in the File Transfer 
  Setup dialog box.

* You may experience problems making Telnet connections using versions
  previous to 3.21 of Distinct or the Beame & Whiteside TCP stacks.  
  The following entry in the [Debug] section of the REFLECT.INI file 
  may resolve these problems.

	AsyncConnect=1

* If you use Pathworks version 5.0 and have a Windows Sockets TCP/IP stack,
  you need to make the change shown above (adding the AsyncConnect=1
  line, that is) to establish a Telnet Connection from Reflection.  If you
  don't add this line to the [Debug] section of the REFLECT.INI file,
  you'll receive the "Unable to connect" error message.


-------------------------
Mapping the "\" Character
-------------------------
If you map a key to contain a "\" character, change your
LITERAL-ESCAPE character to something other than "\".  For
example:
	SET LITERAL-ESCAPE "~"
	KEYMAP F12 to RCL "INVOKE C:\RWIN\RCL\LOGIN.RCL"

Once the key is mapped, you can set the literal escape back to the
default.

----------------------------
The Diamond 24X Video Driver
----------------------------
Some versions of the WSPDPBF.DRV driver for 1024x768x256 resolutions
may produce a General Protection Fault at 0001:0F38 during installation.  
This will happen with other applications that use the Microsoft Setup 
utility, such as Word for Windows.

The workaround is to install Reflection using some other resolution.
Resolutions known to work are any that use 16 colors and a 640x480
resolution with any number of colors.

Check with your card manufacturer for updated drivers that may 
correct these problems.  Drivers are often available on CompuServe 
or the Internet.


-----------------------------------------------------------
Effect of Using FTP's PC-TCP with Older Versions of WINSOCK
-----------------------------------------------------------
When using the FTP PC-TCP network interface, you may have trouble
opening a server connection if you are using a version of WINSOCK.DLL 
prior to version 1.06.  Choose Module Versions from the Reflection FTP 
Options menu to check the version number of your WINSOCK.DLL.  If 
WINSOCK.DLL is not at version 1.06 or later, add the following line to
the [FTP Initialize] section in the RFTP.INI file:
	
	AsynchConnect=No

-------------------
Using DDE and Excel
-------------------
If you use Dynamic Data Exchange to establish an advise-link
with Excel, you should not leave Excel menus pulled down too long.  
When you pull down an Excel menu, Excel stops accepting DDE messages 
and does not queue the messages in a buffer to be acknowledged after 
the menu goes away.  Consequently, if Excel doesn't respond to a 
DDE message from Reflection, Reflection will think that the 
conversation is no longer valid and terminate the program.  A
workaround is to set Reflection's DDE-TIMEOUT value higher.


---------------------------
Using HP MPE/XL Version 3.1
---------------------------
If you use MPE/XL version 3.1, connect using the Reflection
Network Series for DOS VT-MGR, and try to perform fast file transfers
to or from an HP 3000, you might experience a system halt. To resolve 
this problem, contact HP to receive their patch NSTBDV5.


--------------------------------
Using Reflection with Windows NT
--------------------------------
If you are installing more than one Reflection product (e.g, 
Reflection 1 for Windows and Reflection 2 for Windows), you may
want to shut down NT in between installations.  Otherwise, an error 
may be displayed when you run the second Setup program, stating that 
Setup could not open the .INF file for the first product you installed.

While Reflection is running, system monitoring programs such as 
Performance Monitor will show 100% CPU usage.  This is due to
Reflection's datacomm polling, which is also active when there is no 
connection. 

You can establish both serial and Telnet host connections using
Reflection under Windows NT.  To establish a Telnet connection, 
you must first install TCP/IP software shipped with Windows NT 
(use the Add Software option under Network Settings in the Control 
Panel to install TCP/IP). Note that the Windows NT Telnet service
is not required for Telnet connections since Reflection includes
its own Telnet support. 

Reflection's method of special keyboard handling is not supported
under Windows NT.  This can lead to several problems:

	- The SCANCODE feature for keyboard mapping will not work.

	 When using VT emulation, the NumLock key is mapped to PF1
	 (often referred to as the Gold key in VMS applications).  
	 Pressing NumLock under NT will cause the keyboard NumLock 
	 light to toggle.  In order to ensure that the editing 
	 keypad keys always send the appropriate VT keyboard 
	 equivalents, Reflection keeps track of the state of 
	 NumLock independently.  The Reflection NumLock state is 
	 shown by the Num indicator on the Reflection status line.  
	 To toggle the Reflection NumLock state, press the Num 
	 indicator or Shift-NumLock.

Using the SHELL command under Windows NT has the following limitations:  

	- When you use the SHELL command with no arguments, the command
	 works properly. However, a Reflection error dialog is displayed
	 in addition to the DOS prompt window.

	- Using SHELL with arguments will not work - the arguments are 
	 ignored and the command acts like you typed SHELL with no 
	 arguments.

WRQ is working to resolve these problems.


---------------------------
Using Reflection with OS/2
---------------------------
If you run Reflection 1 in seamless mode with a 256 color video driver, 
the color palette of the OS/2 desktop gets distorted after starting 
Reflection. When Reflection's startup mountain clears, you can 
restore the OS/2 palette by making the desktop active, then returning
to Reflection.

Using the SHELL command under OS/2 has the following limitations:  

	- When you use the SHELL command with no arguments, the command 
	 works properly. However, a Reflection error dialog is displayed
	 in addition to the DOS prompt window.

	- Using SHELL with arguments will not work - the arguments are
	 ignored and the command acts like you typed SHELL with no 
	 arguments.

If you are running under OS/2 2.1 and have a 16550 installed:

	Include the following line in your AUTOEXEC.BAT to enable 
	16550 support:

		MODE COM1:,,,BUFFER=ON

	This tells OS/2 that a 16550 is present. This differs from 
	release 2.0, where this modification was made in the 
	CONFIG.SYS file.

	The COMCHECK utility included with Reflection reports that 
	no 16550 is installed (OS/2 virtualizes the serial port and 
	handles the buffering itself), though it is used.


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


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 for debugging purposes.

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 you have Windows installed.
- Be prepared to send a copy of this file to WRQ when you report
  the problem.


WRQLOG.PC and WRQLOG.
=====================
If you are having problems with file transfers and are asked to
provide trace files of the transfers, follow the steps below
to generate them:

You can trace both the PC side and the host side of every file
transfer.
      * To record PC side file transfer activity:
	- Press Alt+Y to open the command window. Type SET TRACE 
	  YES followed by [Enter].
	- Perform a file transfer or host directory request.
	- A file is created on your PC called WRQLOG.PC in the
	  Reflection directory.
      * To record host side file transfer activity, go to the File
	File Transfer Setup dialog box and make the following changes:
	- Change your host startup sequence.
	  RUN PCLINK2 becomes RUN PCLINK2.PUB.SYS;PARM=2
	  VAXLINK2 becomes VAXLINK2 L
	  unxlink2 becomes unxlink2 -l
	- Perform file transfer or host directory request.
	- The file WRQLOG. is created on the host in the current
	  directory.

       * NOTE:  Trace files will not display anything if fast file
	 transfer is used.  Remember to SET FAST-FILE-XFER NO
	 before generating trace files.

Trace Files
===========
If you are experiencing problems using a host application, WRQ frequently
needs copies of trace files to review activity between the host application 
and Reflection.

There are several types of trace files.  The first is useful for most 
application problems:
	1. From the Options menu, choose Troubleshooting-Start Trace.
	2. Start your application and reproduce the problem you 
	   experienced.
	3. Once you have reproduced the problem, choose 
	   Troubleshooting-Stop Trace from the Options menu.
	4. You may be asked to provide an unprocessed trace file.  If 
	   that is the case, you are finished.
	5. To process the trace file, choose Troubleshooting-Process Trace
	   from the Options menu.

The second type of trace file is a DOS Reflection style trace file.
To generate a trace file:
- From the command window, type SET TRACE YES
				OPEN <filename>
- Start your application and reproduce the problem you experienced.
- Once you have reproduced the problem, type SET TRACE NO.
					     CLOSE DISK

 A file is generated called <filename>.




