
Reflection 3270 and Reflection for the AS400 
(C)opyright 1993,1994 Walker Richer & Quinn, Inc.

******************************************************************
	       		     Contents 
******************************************************************
		
	* Setup and Configuration	
		Installing Reflection
		Changes to WIN.INI
		Changes to SYSTEM.INI
		Troubleshooting
		Starting Reflection

	* Switching Between NS/Router and PC Support

	* General Issues and Known Problems

 	* Special Notes for Reflection 3270 V4.0 Users
		Converting Scripts and Settings Files
		Converting Your Profiled V4.0 R8WIN.EXE 

	* Troubleshooting

	* DOS HLLAPI Support in Reflection 3270

	* Diagnostics
		SETUP.LOG
		DRWATSON.LOG
		Trace files

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

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

	1. Start Windows 3.1. 
	2. Insert Disk #1 in your floppy drive.
	3. Choose Run from the Program Manager File menu.
	4. Type <drive>\SETUP and press <Enter>.
	5. Follow the prompts to install Reflection.

Changes to WIN.INI
------------------
Setup modifies your WIN.INI by adding the following
information to the [Extensions] section:	
	RSF=<path>\R8WIN.EXE  ^.RSF
	
Changes to SYSTEM.INI
---------------------
RBASIC requires that file share locking be enabled to function
properly.  If file share locking is not already enabled,
the following line will be added to your SYSTEM.INI file
under the the [386Enh] section:
    DEVICE=VSHARE.386

Unless you install to a network server, VSHARE.386 is copied
to your WINDOWS\SYSTEM directory by SETUP.  If you install
to a network server, then VSHARE.386 must be installed on
each user's machine manually.

Troubleshooting
---------------
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.  The amount given by Setup is 
only an estimate.

If Setup does not complete successfully, use the batch file
MANSETUP.BAT and follow the procedure below to install Reflection:

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

	2. Change to the directory you created, for example, 
	   CD REFLECT.

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

        4. Copy MANSETUP.BAT from the floppy disk into your
           current directory.  For example:
                       
		 COPY A:MANSETUP.BAT

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

		MANSETUP A:

        6. Some of the files normally installed by SETUP belong in your
           WINDOWS\SYSTEM directory.  MANSETUP does not copy those files
           into the WINDOWS\SYSTEM directory.  You will need to do that
           manually.  Those files will be in the root level of the 
           directory you created in step 1.  Before you copy these files 
           check to see if they already exist in your WINDOWS\SYSTEM 
           directory, and if they do, only copy the ones we provide if 
           they are NEWER than the ones already in your WINDOWS\SYSTEM 
           directory.

        7.  Manually update your WIN.INI and SYSTEM.INI, as described 
            in the previous section.

The Setup utility creates a file called SETUP.LOG in your 
Reflection directory.  If you experience problems running Setup, be
prepared to send a copy of this file to WRQ.

Starting Reflection
-------------------
**NOTE: If you use the Reflection Network Series (RNS) Telnet 
	software, you must start RNS before starting Windows.  
	If you use PC Support, then load the PC Support Router 
	and PCSWIN before starting Windows.  

To Start Refection 3270/AS400:
	- If you created a Reflection 3270/AS400 icon during 
 	  Setup, double-click that icon to start Reflection.
	OR
	- Choose Run from the Program Manager File menu, type
          <path>\RIBM\R8WIN.EXE and press <Enter>.

To start Windows FTP:
	**NOTE:  Requires TELNET or Windows Sockets connection. 

	- If you chose to install the Reflection icon during 
	  Setup, an icon for FTP was also installed.  Start 
	  Reflection for Windows FTP by choosing the FTP Client 
          icon.
	OR
	- Choose Run from the Program Manager File menu. Then
	  type <path>\FTP\RFTP.EXE and press <Enter>.


******************************************************************
            Switching Between NS/Router and PC Support
******************************************************************
NS/Router is designed to preempt PC Support's router on installation.
This means that after you install NS/Router, any application that calls
the PC Support router will use NS/Router instead.  If NS/Router is
correctly installed and configured, most calling applications will
not notice the difference.  However, some applications (for example,
some versions of Rumba) appear to have problems using NS/Router.
Therefore, if you're installing NS/Router on a PC where the PC
Support router is already installed, it's important to understand
NS/Router's installation process and learn how to switch
between the PC Support router and the NS/Router.

During installation, NS/Router places EHNAPPC.DLL and
EHNRTRW.DLL in the \WINDOWS\SYSTEM directory.  PC
Support has two corresponding files with the same names in
its directory.

This can create a conflict because when Windows attempts to
load DLL files, it searches the \WINDOWS\SYSTEM directory
before searching your PATH, thus finding the NS/Router DLL
files first.  (PC Support installs its DLL files to its own directory
and depends on the PATH variable to find them.)

To use PC Support after installing NS/Router, do the following:

1.  Change to the \WINDOWS\SYSTEM directory.
2.  Rename EHN*.DLL to *.NSR.
3.  Exit Windows and restart.

To change back to using NS/Router, do the following:

1.  Change to the \WINDOWS\SYSTEM directory.
2.  Rename EHN*.NSR to *.DLL.
3.  Exit Windows and restart.

Note: switching between NS/Router and PC Support does not
involve changing anything in your PC Support directory.

******************************************************************
                General Issues and Known Problems
******************************************************************

Miscellaneous
--------------
* When working with a document in OV/400 in Basic Assistance mode,
  you may see parts of the scale line incorrectly displayed within
  the document.  If you have this problem, change to Intermediate
  Assistance mode.

* If you use the Reflection Basic MSGBOX or PRINT commands with a 
  version of CTL3D.DLL other than the version shipped with 
  this product (version 2.05), the display of characters 
  is limited to 512.

* If you load an application which calls EHLLAPI before you launch
  R8WIN.EXE, then you will need to edit your AUTOEXEC.BAT file and
  add to your path statement the location of the r8win dlls (the
  default path will be c:\reflect\ribm).


Transport 
---------
* If you are using WRQ Telnet and TCP/IP software (Reflection 
  Network Series), you might experience problems yielding to 
  other WRQ applications.  If this is the case, increase the 
  value of the NumTCPBuffers parameter (default is 5) in 
  NET.CFG (for ODI) or in PROTOCOL.INI (for NDIS).  
  Try increasing the value to 10. 

* Reflection includes support for Telnet running over 
  Windows Sockets compatible TCP/IP stacks.  The file that
  provides this support is RNTELNET.DLL.  It is copied to the 
  directory where Reflection is installed.  Use the WINSOCK.DLL 
  provided by your network vendor.  

    NOTE:  If you load the Telnet Connection TSR, Reflection will 
           use this TSR instead of the Windows Sockets compatible 
  	   TCP/IP.  
	
*  Verify that the number of TCP sessions allocated in your 
   PROTOCOL.INI and your STARTNET.BAT file (part of Reflection 
   Network Series) are greater than or equal to the maximum number 
   of Reflection 3270 or AS/400 connections you plan to use.

* The default Transport Type is Telnet. To choose a different 
  Transport Type, choose Session Setup from the Session menu  
  and select your Transport Type.

WINSOCK
-------
* If you use version 2.1.1 of the Wollongong WINSOCK stack, 
  Reflection will run slowly, and might even stop executing.

* The Winsock interface to Distinct TCP/IP may cause Reflection to 
  hang after multiple connect and disconnect operations. 


******************************************************************
 	   Special Notes for Reflection 3270 V4.0 Users
******************************************************************

Converting Scripts and Settings Files
-----------------------------------
Scripts and settings files created with Reflection 3270 V4.0 must 
be translated for use with Reflection 3270 v4.1.  

Run the supplied Reflection IBM Translator to update existing scripts 
and settings files. The Setup program installs this utility and adds 
an icon for it to Program Manager.

The Reflection IBM Translator does two things:

* Translates the names of various Reflection commands and settings.  
Some settings have been renamed for version 4.1

* Converts a version 4.0 Reflection Basic source file into a 
version 4.1 Reflection Basic file.  In version 4.0 there were two
versions of every Reflection Basic file: an ASCII source file 
(.RBS) and a compiled executable (.RBX).  For version 4.1 there is
only a single file, with an .RBS extension.  This is a binary file
but can be opened and modified in the Reflection Basic editor.

To run the Reflection IBM Translator follow these steps:

1. Click the Reflection IBM Translator icon.
2. Identify the file you want to convert.
3. Supply a name for the converted file.

Converting Your Profiled V4.0 R8WIN.EXE 
----------------------------
If you have used RPROFILE to customize the features available
to users of Reflection 3270 V4.0, you can update v4.1 with your
existing profile information.  To convert your profile information:

1. Click the RPROFILE icon.
2. From the Options menu, select Import Profile....
3. In the dialog box, indicate the path to your V4.0 
    profiled r8win.exe.

******************************************************************
		         Troubleshooting
******************************************************************

Effect of Using Reflection 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 Reflection FTP version 
1.0 and 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

The RFTP.INI file is located in the \WINDOWS directory.

******************************************************************
             DOS HLLAPI Support in Reflection 3270
******************************************************************

DOS HLLAPI Support allows a DOS HLLAPI program, running in a 
DOS window, to communicate with an IBM host through 
Reflection 3270 running under Windows.

This feature is only available under Windows 3.1 running in 
Enhanced mode, which requires at least a 386 CPU.  You can run 
the HLLAPI application in a DOS window or full screen.

For instructions on installing DOS HLLAPI, see the "HLLAPI Support"
appendix in the Technical Reference manual or in the on-line Help.

******************************************************************
		     	     Diagnostics
******************************************************************

There are several diagnostic tools in Reflection and in Windows 
that help WRQ resolve any problems you might encounter.

SETUP.LOG
---------
The Setup utility creates a file called SETUP.LOG in your 
Reflection directory.  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 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 (it is a 
good idea to make it part of your Startup group while you are  
testing).  Then 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.

Trace Files
-----------
If you are experiencing problems using a host application, WRQ may 
need copies of trace files to review activity between the
host/application and Reflection.  See the help file for 
information on creating and running trace files.



