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

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


Contents
   4.11 Changes
   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
   Change to Reflection (Internal) Executable Name
   Effect of Using FTP with Older Versions of WINSOCK
   Binary Transfers to a Printer Port
   Using DDE and Excel
   Using HP MPE/XL Version 3.1
   Using Reflection with Windows NT
   Using Reflection with OS/2
   Diagnostics
   Documentation Addenda


------------
4.11 Changes
------------

*  The Reflection Setup program now gives you the option to continue
   with the installation procedure, even when Setup gives you the
   message that you do not have enough disk space.

*  You can now successfully use the Task List or the [Alt]+[Tab] keystroke
   to return to Reflection when you've shifted focus to another window under
   the following circumstances:

	- The Define Button dialog box is displayed.
	- A file transfer in progress completes before you return to 
	  Reflection.
	
*  A new version of Reflection FTP is shipping with version 4.11.  This
   addresses the problem of running a server version of Reflection, and
   allows more than one user to access the FTP application at one time.

*  You can now re-establish serial connections when running Reflection
   on a machine with the SMC UART serial chip.

*  You can now transfer binary files to a printer port (such as LPT1).

*  Receiving a Ctrl+X no longer causes the next character to be dropped.

*  When the cursor is on the start of a transmit-only field, an ESC J (clear
   from cursor position to end of display memory) received from the host now
   clears the field.

*  When the cursor is on the start of a transmit-only field, an ESC J or 
   ESC K (clear from cursor position to end of line) received from the host
   or the keyboard no longer turns this field into an unprotected field.

*  You can now [Tab] to and type information into a single character transmit-
   only field.

*  The ESC&q series of escape sequences now requires that Reflection 
   be configured as an HP 700/94 terminal.  These escape sequences are
   ignored by HP 700/92 terminals.

*  When starting a host-initiated transfer, Reflection now waits after 
   receiving the ESC&oB<send>... sequence for the host to transmit a DC1
   before sending the host startup sequence.  This corrects transfer problems
   experienced by Speedware users.
	  
*  Reflection now restores your original HP terminal type when you switch to 
   a VT terminal then revert back to HP emulation.

*  When in format mode, Reflection now stops in initial transmit-only fields 
   upon receipt of the ESC-H sequence.

*  Reflection no longer sends a block terminator after a short block transfer
   when the terminal is in line mode and the cursor is below display
   memory.  

*  Reflection now correctly paints applications using formatted block mode 
   screens larger than 24 lines.
   
*  WRQ has moved to a new location.  The on-line help, modem dialer and Event 
   Trace report for Reflection have been updated to reflect the new address 
   and phone numbers.  Modem dialer numbers are saved in the Reflection 
   settings file, so you won't see the new BBS number unless you run with 
   factory defaults.  To modify existing settings file, choose Dial from 
   the Connection menu, choose Configure for the WRQ Bulletin Board, and 
   change the phone number to 12062170145, then resave your settings file.  
   

---------------------
Installing Reflection
---------------------
To install Reflection use the supplied Setup program:

	1. Start Windows 3.1 (version 4.11 of Reflection will NOT
	   run under Windows 3.0).
	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 8192.


-----------------------
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.11 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.11 will use XMODEM when you load the settings file.

To correct this problem, follow these steps:
  - Load the settings file
  - Choose Transfer Setup from the File menu
  - Pick the correct value for Transfer Protocol
  - Click OK to dismiss the dialog
  - Save the settings file using the Save command on the File menu

Other version 4.0 settings are not affected.

-----------------------------------------------------
Removing Files Used by Earlier Versions of Reflection
-----------------------------------------------------
If you have an earlier version of Reflection installed that you do
not want to retain, then install version 4.11 in the same directory in
which you installed the older version.  Files such as the executable 
are overwritten by files of the same name for version 4.11..

Many files used by earlier versions of Reflection are either not used
by version 4.11 or have been renamed.  You can run a command file supplied
with version 4.11 to "clean up" the files not used by the new version:

1.  Choose Open from the terminal window's File menu.

2.  Select Command (*.rcl) from the List Files of Type list box.

3.  In the Files box, double-click on the file called CLEANUP.RCL.

4.  Follow the prompts through the command file.  You need to specify
    both the drive and directory of the earlier version of Reflection.
    Then, the command file prompts you to confirm the deletion of
    similar groups of files.


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

- 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.11 dynamically loads its font files.  If you 
  have an earlier version 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.11 
  with versions prior to 4.1 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.11
      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:

    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 installation
       process, where <drive> is the floppy disk drive.  For example:
       A:MANSETUP A:

  This process installs Reflection.  You must manually update your 
  WIN.INI and SYSTEM.INI, as described in the previous section. 

  Modifications must also be made to the file REFLECT.INI if you want 
  to take advantage of the additional predefined file transfer settings 
  available in version 4.11:

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

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

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.11 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.11 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.11 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.11 includes support for Telnet running over
Windows Sockets-compliant TCP/IP stacks.  The file that provides
this support is RNTELNET.DLL, located in the Reflection directory.
To connect to the stack, select the TELNET-MGR 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) 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-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.


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


-----------------------------------------------
Change to Reflection (Internal) Executable Name
-----------------------------------------------
Many of Reflection's executable and DLL files have been renamed in 
version 4.11: the file names are now version-specific. A change was 
also made to the "internal name" of Reflection's executable file, 
which used to be in the format R1WIN.EXE. The new internal name is 
now RWN411E1.EXE, where <411> is the version number and <E> represents
an English version.


Note:  This new naming convention for the Reflection executable file is
       only used by programs internally, and is of no consequence to most
       users.  For example, if you choose Module Versions from the 
       Options-Troubleshooting cascading menu, or type DIR R1WIN.EXE in the 
       \RWIN directory, the file is still in its easy-to-recognize format 
       of R1WIN.EXE. 

If you have a command file or a DDE script that "calls" Reflection by 
its pre-4.11 internal executable name, you need to modify this script 
in one of two ways: 

* Since the internal naming scheme for files is always subject to 
  change, you should never use the name of an executable file in a call 
  from another program. Applications offer a variety of ways to call 
  other programs. For example, from Excel you can call a specific 
  window. Therefore, it is recommended that you modify all scripts that 
  call a Reflection executable file by its name to call, as an example, 
  the Reflection window instead. 

* If you still want to call Reflection by its executable name, change 
  all references to the new name as described above. Change all instances
  of R1WIN.EXE to RWN410E1.EXE.


--------------------------------------------------
Effect of Using FTP 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


-------------------------------
Binary Transfer to Printer Port
-------------------------------
If you're using the WRQ protocol to receive a binary file to your 
printer port (e.g. c:\lpt1 is the local filename), you will receive 
an error message that the disk is full if the file contains a Ctrl-Z.  
Simply ignore this message, and the contents up to the Ctrl-Z will print.


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

Consequently, you should not install multiple Reflection for Windows 
products from the system console of an NT server.

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, and is normal for this release. 

In the Connection Preferences dialog box, do not set the Suspend
Current Connection preference on exit.  This will cause a General 
Protection Fault on exit.  

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 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 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:
	    - SET TRACE YES (you don't have to open or close a file).
	    - 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:
	    - 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, we frequently
need 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.
- From the Options menu, choose Troubleshooting-Start Trace.
- Start your application and reproduce the problem you experienced.
- Once you have reproduced the problem, choose Troubleshooting-Stop 
  Trace from the Options menu.
- You may be asked to provide an unprocessed trace file.  If that is 
  the case, you are finished.
- 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.
This is useful if the application uses graphics.  To generate a trace
file:
- From the Command window, type "SET TRACE YES"
				"OPEN <filename>"
- Then, 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>.

Capture files are also useful when trying to trace problems running
graphics applications.  To generate a capture file:
- From the Command window, type "SET CAPTURE YES"
				"OPEN <filename>"
- Then, start your application and reproduce the problem you 
  experienced.
- Once you have reproduced the problem, type "SET CAPTURE NO"
					     "CLOSE DISK"
A file is generated called <filename>.


---------------------
Documentation Addenda
---------------------
The following additions or changes should be noted to the Reflection
Technical Reference Manual:

* Page 18:
  The new SET parameter that reads SET PRINTER-PASSTHRU-CONVERSION
  should read SET PRINTER-PASSTHRU-CONV

* Page 85:
  In the description of the SET ENHANCED-SERIAL-DATACOMM, it should
  be noted that changing this parameter affects subsequent serial
  transmissions; it does not change the datacomm driver being used
  for an active serial connection.

* Page 94:
  The table of supported networks should include the following entry:
  
     Supported Network                            Connection Type
     -----------------                            ---------------
     Leverage for NetWare, TES version 3.0              LAT

* Page 115:
  The following NLAT switches are available as described, however their
  descriptions do not appear when you type NLAT/? from the DOS prompt:
   /IRQ:<n>
   /LIFOS:<n>
   /LIFOSIZE:<n>

  In addition, a /SESSIONS switch has been added; the default is 2.

* Page 179:
  In the Save Settings As Icon dialog box, do NOT use parenthesis
  when naming the icon in the Description text box.  Doing so does
  not produce an error, however, an icon is not created.  If you
  want to include parenthesis in the group name, enclose the entire 
  group name in quotation marks, e.g. "(Reflection)".

* Page 190:
  The description for Copy Table should warn that only tables in which
  columns are separated by vertical white space will be copied correctly.
  If two columns in a table overlap, as often happens in VMS directory
  listings, Reflection will merge the overlapped columns.  Such tables
  should be copied in portions to work around this limitation.

* Page 368:
  When the Use Screen Font check box is selected, you have the ability
  to print line drawing characters.  It should be noted, however, that
  this does not give you the ability to copy line drawing characters to
  the Clipboard (the characters are automatically converted by Windows to
  ANSI before being placed on the Clipboard).

