------------------------------------------------
Reflection 4 for Windows Version 4.1 README File
------------------------------------------------

Contents
   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
   Restrictions for Windows Sockets
   Mapping the "\" Character
   LK250 vs. LK450 Keyboard: Special Mode Indicator
   Generating Sixels
   Information on Video Drivers
   Change to Reflection (Internal) Executable Name
   Effect of Using FTP with Older Versions of WINSOCK
   Binary Transfers to a Printer Port
   Copying Reflection Graphics into Paintbrush
   Using the ALL-IN-1 WPS Editor
   Using EDT with Display Rows Set Higher Than 24
   Using DDE and Excel
   Using Reflection with Windows NT
   Using Reflection with OS/2
   Diagnostics
   Documentation Addenda


---------------------
Installing Reflection
---------------------
To install Reflection, use the supplied Setup program:
	1. Start Windows 3.1 (version 4.1 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 made to your existing copy of 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.


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

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

    REFLECT.INI also contains your keyboard type.  In the [Keyboard] 
    section:
	type = NORMAL | LK250 | LK450

    Specify LK250 if you use a Digital Equipment LK250 keyboard.  
    Specify LK450 if you use a Digital Equipment LK450 keyboard.  
    Specify NORMAL for all other keyboards.  For example:
	[Keyboard]
	type=NORMAL

* Changes to WIN.INI, if installing all the Reflection for Windows 
  products (Reflection 1, Reflection 2 and Reflection 4):
    - In the [Extensions] section:
	 RCL=<path>\R4WIN.EXE , ^.RCL
	 RC1=<path>\R1WIN.EXE , ^.RC1
	 RC2=<path>\R2WIN.EXE , ^.RC2
	 RC4=<path>\R4WIN.EXE , ^.RC4
	 R1W=<path>\R1WIN.EXE ^.R1W
	 R2W=<path>\R2WIN.EXE ^.R2W
	 R4W=<path>\R4WIN.EXE ^.R4W

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

Many files used by earlier versions of Reflection are either not used
by version 4.1 or have been renamed.  You can run a command file supplied
with version 4.1 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.

   The final dialog box shows you the names of all deleted and preserved
   files.


-----------------------------------------
Troubleshooting - Setup and Configuration
-----------------------------------------
Following are a list of general troubleshooting installation 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.1 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.1 
  and earlier versions of Reflection for Windows you must add the 
  following lines back to your WIN.INI file:
	R_ASCII=<path>\R_ASCII.FON
	R_GRAPH=<path>\R_GRAPH.FON
	R_MULTI=<path>\R_MULTI.FON
	R_TECH=<path>\R_TECH.FON

       The <path> is the location where Reflection version 4.1 
       is installed (not the earlier version).  If you accepted
       the default path during Setup, then this is C:\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.1:

   * 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.1 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.1 disks to your existing REFLECT.INI.
	  
   * If you do not have an existing copy of Reflection, copy the
	REFLECT.INI file from the 4.1 disks 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.1 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 
new 4.1 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.1.  

KEYINT.DLL, used in pre-4.0 versions of Reflection, has been 
replaced in version 4.1 with RKEYBRD.DLL.  If you want to run 
version 3.70 or 3.71 of Reflection 1 or Reflection 2 concurrently 
with a 4.1 version of Reflection 4, 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 reside.

The fonts provided with version 4.1 of Reflection 4 are not 
always compatible with earlier versions of Reflection 2 
(version 3.7 or 3.71).  If you use Reflection 4's fonts together 
with Reflection 2 version 3.71 or earlier, you may get Internal 
Integrity Check errors in Reflection 2 at certain screen
sizes.  One known case is when running VGA resolution with 
the display rows set to 132; you will get an error on FONT-WIDTH.  
If you choose to use Reflection 2's fonts with Reflection 4, 
then you will not be able to get an unscaled graphics image in 
Reflection 4.  The preceding section addresses font entries required 
for previous versions of Reflection.


--------------------------------
Restrictions for Windows Sockets
--------------------------------
Reflection version 4.1 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.


------------------------------------------------
LK250 vs. LK450 Keyboard: Special Mode Indicator
------------------------------------------------
The LK250 keyboard is in its special DEC mode when the light 
on the keyboard is on.  In contrast, the LK450 is in the special 
mode when the light is off.


-----------------
Generating Sixels
-----------------
You can use the Save As command from the File menu to save a graphic image 
as a sixel file on your PC.  In the Save File As dialog box, select
"Display Sixel (*.sxl)" from the Type of Save list box before clicking
on the Save button.

If the size of the terminal window is less than 800x480 pixels, 
the graphic image will be scaled.  It is a good idea to change 
your terminal display to an unscaled screen before saving the 
sixel image.  Choose Display from the Terminal menu, and select 
the Unscaled Screen (800x480) check box in the Terminal Display 
Setup dialog box.  This will result in a unscaled sixel file,
which can then be displayed on any size terminal window (the
image will scale to the appropriate size as it is being displayed).


----------------------------
Information on Video Drivers
----------------------------
Following is information on S3-based boards, Diamond 24X, and
coprocessor-based video cards.

S3-based boards
---------------
WRQ has found the display driver available from Microsoft as
the "S3 Display Driver Disk" is the best choice when using Reflection 4
for Windows ReGIS and Sixel graphics (Fahrenheit 1280, Diamond Stealth,
Dell built-in VGA).  Depending upon your resolution, this driver is
called CAR800.DRV, CAR1K.DRV, or CAR1280.DRV.  The disk image can be
found in the Microsoft Software Library as S3.EXE.

Diamond 24X
-----------
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.

Non Coprocessor-based Video Cards
---------------------------------
For these types of cards, which include standard VGAs, execute the
following command in the command window:

	SET GRAPHICS-FIX-SCREEN NO

This setting will speed up graphics painting.

-----------------------------------------------
Change to Reflection (Internal) Executable Name
-----------------------------------------------
Many of Reflection's executable and DLL files have been renamed in 
version 4.1: 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 R4WIN.EXE. The new internal name is
now RWN410E4.EXE, where <410> 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 R4WIN.EXE in the \RWIN directory, the file is still 
      in its easy-to-recognize format of R4WIN.EXE. 

If you have a command file or a DDE script that "calls" Reflection by 
its pre-4.1 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 R4WIN.EXE to RWN410E4.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.


-------------------------------------------
Copying Reflection Graphics into Paintbrush
-------------------------------------------
When you copy a graphic image with Reflection 4, a device independent 
bitmap and a copy of the color palette is placed on the Clipboard 
along with a device dependent bitmap.  Paintbrush only uses the 
information in the device dependent bitmap.  The result is that the 
colors in the Paintbrush image will change whenever the color palette 
changes, either by changing the colors in Reflection 4 or loading 
some other palette-aware application, such as WinGIF.  This is a 
Paintbrush problem.


-----------------------------
Using the ALL-IN-1 WPS Editor
-----------------------------
A new set command, FORCE-AUTO-REPEAT, was added to help ALL-IN-1
users optimize performance.  Normally, the WPS editor in ALL-IN-1
turns Auto Repeat on and off repeatedly while you type.  The default
for FORCE-AUTO-REPEAT is NO:  this causes Reflection to honor the
editor's request to turn Auto Repeat off and on.  To improve
performance in the WPS editor, try setting FORCE-AUTO-REPEAT to YES.
The result should be faster scrolling and cursor motion when using the 
arrow keys in WPS.


----------------------------------------------
Using EDT with Display Rows Set Higher Than 24
----------------------------------------------
The EDT editor does not support display rows higher than 24.  If you 
have Reflection set to display more than 24 rows, EDT will change it 
back to 24.  It will also change the scrolling region to 24 rows, 
which is less than the full terminal screen;  this will cause 
Reflection to stop saving display memory.

The TPU editor can be configured to use EDT keystrokes, and does not 
have the same display row limitations as EDT.


-------------------
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 Reflection with Windows NT
--------------------------------
If you are installing more than one Reflection product (e.g, 
Reflection 4 for Windows and Reflection 1 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.

   - The LK250 and LK450 keyboards are not supported.  They will 
	behave like standard 101-key keyboards. 

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 4 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 that ships 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.  
		       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 an 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 97:
  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 106:
  The table of supported networks should include the following entry:
  
     Supported Network                            Connection Type
     -----------------                            ---------------
     Leverage for NetWare, TES version 3.0              LAT

* Page 125:
  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 173:
  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 have parenthesis in the group name, enclose the entire 
  group name in quotation marks, e.g. "(Reflection)".


* Page 183:
  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 369:
  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).

* Page 386:
  The description for Default Scheme should read as follows:
    "When you choose the Default Scheme button, Reflection loads the
     color scheme (Terminal Defaults).  


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

The following additions or changes should be noted in the Reflection
VT Programmers Reference Manual:

* Page 24:
  The $UPI value returned for the serial number is a 19-character
  string (not a 20-character string).

* Page 169:
* The section on Tektronix Graphics should include the following
  description on how to change the color of Tektronix graphics:

    "Changing the Color of Tektronix Graphics"

    By default, when Reflection draws Tektronix graphics it uses Color Map
    0 for the background and Color Map 7 for the foreground (just as a
    VT340 terminal does).  If you want to change, or brighten, the color
    used for drawing Tektronix graphics:

    1.  Choose Color from the Terminal menu.

    2.  In the Terminal Color Setup dialog box, click on the Color Map
	button.

    3.  In the Terminal Color Map Setup dialog box, highlight the Color
	Map square number 7.

    4.  Choose a new color from the color grid.  For example, to brighten
	the color used, drag the vertical luminosity bar to the top.

    5.  When you're through, choose OK.  To retain this new color, either
	save it to a color scheme or choose Save from the File menu to
	save your settings file.

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

The following additions or changes should be noted to the Reflection
Quick Start Manual:

* Page 104:
  The list of online help troubleshooting topics, under Miscellaneous,
  should include "How to optimize ALL-IN-1 scrolling speed."  This help
  topic describes the use of the FORCE-AUTO-REPEAT command.
