***************************************************************************  
  
	   Reflection for Windows Version 5.00 README File  
     
***************************************************************************  
  
Contents:  
   Troubleshooting - Setup and Configuration  
   Upgrading from Prior Versions of Reflection  
   Using Different Versions of Reflection for Windows Concurrently 
   Changing Between HP and VT Emulation  
   Restrictions for Windows Sockets  
   Mapping the "\" Character  
   LK250 vs. LK450 Keyboard: Special Mode Indicator - Reflection 2 and 4  
   Effect of Using FTP's PC-TCP with Older Versions of WINSOCK  
   Using the ALL-IN-1 WPS Editor - Reflection 2 and 4  
   Using EDT with Display Rows Set Higher Than 24 - Reflection 2 and 4  
   Using HP MPE/XL Version 3.1 - Reflection 1  
   Using Reflection with Windows NT  
   Using Reflection with OS/2 
   Additional MCI 1-800 Dialing Plan Formats 
   Communications Port 4  
   Host/Service Names Longer than 63 Characters  
   Reflection and Telnet Using Novell's Winsock TCP Stack  
   Netware Printer Driver Error with Windows NT  
   640 by 480 Display Resolution at 120 DPI  
   CTERM GPF's in TRMLAXS  
   Serial Port with 8250 UART 
   Settings Files Greater than 64K 
   Error with Novell Arcserve Utility  
   Generating Sixels - Reflection 4  
   Script Recording with VMS Sessions  
   Information on Drivers
   Reflection Basic LatNode Keyword not supported by NLAT  
   Diagnostics  
 
 
 
************************************************** 
Reflection README File Troubleshooting-- Setup and Configuration 
 
Following is a list of general troubleshooting topics; reference the troubleshooting 
chapter in the Reflection User Guide for additional information.

- It is recommended that Smartdrv be running when you run the Setup program.

- 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. 
 
- If you use Version 2.04 of CTL3D.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. 
 
 
************************************************** 
Upgrading from Prior Versions of Reflection 
 
Version 5.0 has a new feature that allows you to just press the Enter key in the terminal 
window to get connected.  If you have the Reflection Network Series software or another 
WINSOCK TCP stack loaded, you'll be prompted for your host name, and the connection will 
be made.  If not, you'll be prompted for the connection information.  Customers who have 
used versions 4.11 and earlier will need to modify their REFLECT.INI file in order for 
this feature to work with version 5.0.  REFLECT.INI is located in the Windows directory. 
 
Look for the [Reflection <n> Connection Defaults] sections in REFLECT.INI (where <n> is 
the product you are using -- 1, 2, 4, or 1 VT for Reflection 1 as a VT emulator).  You 
probably have an entry like this: 
  
    [Reflection 2 Connection Defaults]  
    Port=COM1  
  
Change the Port= line to:  
    Port=None  
 
 
************************************************** 
Using Different Versions of Reflection for Windows Concurrently   
 
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 
5.00 version of Reflection, a new version of KEYINT.DLL must be installed. To obtain a new 
version of KEYINT.DLL download it from the WRQ BBS @ 206.217.0145 or contact WRQ technical 
support at 206.217.7000.  Copy it to the same directory where version 3.70 or 3.71 of 
Reflection resides. 
 
 
************************************************** 
Changing Between HP and VT Emulation 
 
Reflection 1, HP/VT
-------------------
 
In prior versions of Reflection 1, a number of settings were reset to default values when 
switching between the HP and VT emulations (for instance, from HP70092 to VT220-7).  In 
these versions, only one value was saved for these settings when a settings file was 
saved.  This means that if you were to change the value of BLOCK-SIZE while in VT mode, 
then switch to HP mode, change BLOCK-SIZE to a different value and save a settings file, 
that settings file would only contain the HP value.  If, after loading that settings file 
you were to switch to VT mode, BLOCK-SIZE would have its VT default value rather than the 
one you changed it to. 
 
In 5.0 separate HP and VT values are maintained for these settings. While this solves the 
above problem, there is the possibility that you may have old RCL files that won't work 
correctly with this scheme. An RCL file that attempts to set BLOCK-SIZE to its VT default 
value, and then switch to VT mode is an example. 
 
SET BLOCK-SIZE 478 
SET TERMINAL-TYPE VT220-7 
 
Assuming that Reflection 1 is in HP mode at the start, this RCL file would set the HP 
value of BLOCK-SIZE to 478, and then switch to VT220-7 mode, where the VT value for BLOCK-
SIZE would be loaded (the default, 478, unless a different VT value had been saved 
previously).  A subsequent switch back to HP mode would result in it having an incorrect 
BLOCK-SIZE of 478.  The solution is to simply eliminate the "SET BLOCK-SIZE 478" line. 
 
Settings of this type are: 
 
BLOCK-SIZE 
BLOCK-TERMINATOR 
DO-FORM-FEEDS 
HOST-CHARACTER-SET 
HOST-PROMPT 
HOST-START-OLD 
HOST-START-WRQ 
INHIBIT-DC2 
INHIBIT-EOL-WRAP 
INHIBIT-HANDSHAKE 
NUM-LOCK 
STRIP-NULLS-DELS 
SYSTEM-TYPE 
TRANSMIT-FUNCTIONS 
TRANSFER-FRAME-SIZE 
TRANSFER-WINDOW-SIZE 
TYPE-AHEAD 
 
 
Reflection 2 and Reflection 4, VT/ANSI
-------------------------------------- 
 
There are also settings in Reflection 2 and Reflection 4 for which separate values are 
maintained for the VT and ANSI emulations. There should be no problems with old RCL files, 
since ANSI emulation is new in this release. 
 
The settings are: 
 
AUTO-LINE-FEED 
AUTO-REPEAT 
BELL-ENABLED 
BREAK-ENABLED 
CURSOR-STYLE 
CURSOR-VISIBLE 
DISPLAY-CONTROL-CHARACTERS 
DISPLAY-MEMORY-BLOCKS 
DISPLAY-ROWS 
END-OF-LINE-WRAP 
HOST-CHARACTER-SET 
HOST-STATUS-LINE 
INVERSE-VIDEO 
LOCAL-ECHO 
MARGIN-BELL 
REMOTE-MODE 
TRANSMIT-XON-XOFF 
USE-ANSI-COLOR 
VT-BACKSPACE-SENDS 
VT-CURSOR-KEY-MODE 
VT-KEYPAD-MODE 
 
 
************************************************** 
Restrictions for Windows Sockets   
 
Reflection version 5.0 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 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 Disconnect from the Connection menu.  To avoid this during file transfers, 
  change the Transfer Link to 7-Bit on the WRQ/Reflection panel in the File Transfer Setup 
  dialog box. 
 
- You may experience problems making Telnet connections using versions prior 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. 
 
 
************************************************** 
Passing Escape Sequences to the Printer -- Reflection 2 and 4 
 
A new SET parameter has been added to version 5.0 called PRINTER-PASS-ESCAPE.  This allows 
escape sequences to be passed to a printer driver when Reflection 2 or 4 is in 
Controller/Passthru mode.  
 
 
************************************************** 
Mapping the "\" Character   
 
If you use the RCL KEYMAP command to 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.  (There is no 
Reflection Basic equivalent for the LITERAL-ESCAPE parameter.) 
 
Note:  You do not have to change the literal escape if you use the Keyboard Map Setup 
dialog box, or the Reflection Basic SetKeyMap command to map the key.  
 
 
************************************************** 
LK250 vs. LK450 Keyboard: Special Mode Indicator -- Reflection 2 and 4   
 
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. 
 
 
************************************************** 
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 in Reflection FTP 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 the ALL-IN-1 WPS Editor -- Reflection 2 and 4   
 
A new set command, FORCE-AUTO-REPEAT, was added in version 4.1 of Reflection 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. 
 
The Reflection Basic equivalent is .ForceAutoRepeat = True. 
 
 
************************************************** 
Using EDT with Display Rows Set Higher Than 24 -- Reflection 2 and 4   
 
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 HP MPE/XL Version 3.1 -- Reflection 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   
 
You can establish serial, Telnet and NS/VT 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.  To establish a NS/VT 
connection, you must also install the NS Open product from WRQ, part of the Reflection 
Network Series. 
 
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, click on the Num 
  indicator or press Shift-NumLock. 
 
 
************************************************** 
Using Reflection with OS/2   
 
If you run Reflection 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. 
 
To use the RCL SHELL command with OS/2, just add the NOWAIT parameter. 
 
 
************************************************** 
Additional MCI 1-800 Dialing Plan Formats 
 
Reflection contains a default dialing plan format for MCI using the 1-800-950-1022 number. 
If you have a different MCI 1-800 number, you can still use the default dialing plan by 
just following the format. If you want to create a new MCI dialing plan for your specific 
1-800 number, you can copy and paste one of the following lines into the dialing format. 
 
<Dialout><CancelCallWaiting>1-800-888-8000<Delay><Tone><Prompt Enter  
MCI Calling Card><Delay><Delay><Delay><Delay><Delay><Delay><AreaCode> 
<LocalNumber> 
 
<Dialout><CancelCallWaiting>1-800-674-7000<Delay><Tone><Prompt Enter  
MCI Calling Card><Delay><Delay><Delay><Delay><Delay><Delay><AreaCode> 
<LocalNumber> 
 
 
<Dialout><CancelCallWaiting>1-800-674-7010<Delay><Tone><Prompt Enter  
MCI Calling Card><Delay><Delay><Delay><Delay><Delay><Delay><AreaCode> 
<LocalNumber> 
 
<Dialout><CancelCallWaiting>1-800-674-0700<Delay><Tone><Prompt Enter  
MCI Calling Card><Delay><Delay><Delay><Delay><Delay><Delay><AreaCode> 
<LocalNumber> 
 
 
************************************************** 
Communications Port 4   
 
When attempting to make a connection using COM4 with a Dell Onmiplex PC, the screen may 
turn red.  This is caused by the Omniplex using the same memory as COM port 4.  This is 
documented by Dell.  Other communication ports are fine. 
 
 
************************************************** 
Host/Service Names Longer than 63 Characters   
 
If you enter a host name (in the Host/Service Name dialog box or in Connection Setup) that 
exceeds the maximum of 63 characters, and are using the Reflection for Windows networking 
software, Reflection returns an error message and may cause a General Protection Fault. 
 
 
************************************************** 
Reflection and Telnet Using Novell's WINSOCK Stack   
 
If you receive a General Protection Fault when trying to make a Telnet connection using 
Novell's WINSOCK TCP stack, make sure the necessary VxD is defined in SYSTEM.INI.  In the 
[386Enh] section of SYSTEM.INI there should be the following entry:  
device=<path>\vtcpip.386 
 
 
************************************************** 
QEDIT -- Reflection 1 
 
There is a problem with version 4.3 of QEDIT from Robelle Consulting.  QEDIT does not 
recognize that Reflection 1 is able to support greater than 132 columns.  Therefore, when 
you go into visual mode, your display is limited to 132 columns. Robelle is aware of this 
problem. 
 
To work around this problem, execute the following command from the MPE colon prompt 
before starting QEDIT: 
 
     setjcw Rpcversion ,500 
 
 
************************************************** 
NetWare Printer Driver Error with Windows 
 
If you're running Reflection under Windows 3.11 on a Novell network with NETWARE.DRV 
version 2.00, you'll receive a GPF when you choose Print Setup from the File menu, choose 
the Network button, then choose the Options button.  To correct this, upgrade the 
NETWARE.DRV file.  Get the patch file WINUP9.EXE from Novell (this file can be downloaded 
from CompuServer:  type GO NETWIRE or GO NOVELL). 
 
 
************************************************** 
640 by 480 Display Resolution at 120 DPI   
 
When your display resolution is 640 by 480 and the display font size is 120 DPI, some 
Reflection dialog boxes are slightly clipped along one side. 
 
 
************************************************** 
CTERM GPFs in TRMNLAXS   
 
You may receive a General Protection Fault when closing down multiple CTERM connections.  
This is a known PATHWORKS problem. 
 
 
************************************************** 
Serial Port With 8250 UART  
 
Normally when the DCD state of your modem changes to false, Reflection will automatically 
disconnect the modem. If you have a modem connected to a serial port with an 8250 UART 
chip, the modem "auto disconnect" feature will not work.  To work around this problem, 
choose Disconnect from the Connection menu. 
 
 
************************************************** 
Settings File Greater than 64K 
 
Reflection now limits settings files to a size of 64K bytes in order to speed up the 
loading of settings files at startup. If you have a pre-v5.0 settings files which has a 
size greater than 64K bytes, it will not load under version 5.0. You can save most of the 
pre-version 5.0 settings files to smaller files and reconstruct this settings file in 
v5.0.  To do this, first save the pre-version 5.0 settings to components files: 
 
1. Start the pre-version 5.0 copy of Reflection. 
 
2. Open the settings files. 
 
3. If you have a customized color scheme, save it as a color scheme in the Color Setup 
   dialog box. 
 
4. If you have a button palette, save it to a separate settings file. Press Alt+Y to open 
   the command window, then type the following: 
 
     SAVE BUTTONS <Filename> 
 
5. To save the values of most SET parameters to a file, type the following from the 
   command window: 
 
     SAVE 
     V COMMANDS 
     MSAVE CONFIG.RCL 
 
6. Close the pre-version 5.0 copy of Reflection. 
 
Now, you need to "reconstruct" this settings file in version 5.0: 
 
1. Start the version 5.0 copy of Reflection. 
 
2. Choose the Defaults command from the Setup menu. 
 
3. Choose Color from the Setup menu, and load the pre-5.0 color scheme. 
 
4. Choose Open from the File menu, and load the button-palette-only settings file. 
 
5. Load and execute the file containing the SET parameters (CONFIG.RCL), from the command 
   window. 
 
6. Choose Save As from the terminal window's File menu, and save this new settings file. 
 
 
************************************************** 
Error With Novell Arcserve Utility 
 
If you are using Novell's Arcserve utility for backing up a PC to a NetWare server, you 
may receive an error.  To workaround this problem, temporarily comment out the 
device=<path>\VINT14.386 line in your SYSTEM.INI file.  Use the ";" character at the start 
of the line to comment it out.  Restart Windows are resaving the file. 
 
 
************************************************** 
Information on Drivers Dell S3 drivers   
 
Problems have been found using the Dell S3 display drivers (version 1.31) that cause a 
General Protection Fault in Reflection.  To workaround this problem, get a new version of 
the S3 driver or try a different one. 
 
************************************************** 
Information on Drivers 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. 
 
 
************************************************** 
Information on Drivers Non Coprocessor-based Video Cards (Reflection 4) 
 
For these types of cards, including standard VGAs, execute one of the following commands: 
 
     RB command line:  .GraphicsFixScreen = False 
 
     Command window:  SET GRAPHICS-FIX-SCREEN NO 
 
This setting will speed up graphics painting. 


**************************************************
Reflection Basic LatNode Keyword not supported by NLAT

You cannot allocate more NLAT sessions by using the Reflection Basic LatNode keyword.

 
************************************************** 
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. Click on one of the 
following file names to see 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\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: 
 
1. Press Alt+L to open the command line.  
 
2. Enter the following command: 
 
     Application.StartTrace "WRQLOG." 
 
3. Perform a file transfer or host directory request. 
 
4. A file is created on your PC called WRQLOG.PC in the User directory. 
 
- To record host side file transfer activity, go to the File Transfer Setup dialog box, 
  WRQ/Reflection panel, and make the following changes: 
 
1. Change the Startup Command based on your Reflection product and emulation mode:  for 
   HP emulation append ;PARM=2 to the command, for VT emulation append L, and for UNIX hosts 
   change unxlink2 to unxlink2 -l. 
 
2. Perform the file transfer or host directory request. 
 
3. The file WRQLOG. is created on the host in the current directory. 
 
Trace files will not display anything if fast file transfer is used.  So you must disable 
it by setting the Fast File Transfer list box to Never (this is located on the 
WRQ/Reflection panel in the File Transfer Setup dialog box). 
 
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 one given is useful for most application 
problems: 
 
1. From the Connection menu, choose Trace-Start Trace. 
 
2. Start your application and reproduce the problem you experienced. 
 
3. Once you have reproduced the problem, choose Trace-Stop Trace from the Connection 
   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 Trace-Process Trace from the Connection menu. 
