								09/02/95

Thank you for purchasing the finest remote control program available for
both DOS and Windows. We are pleased to announce that ReachOut is now
a part of the Stac Electronics family of storage and compression products.
Stac technical support is available Mon-Thu 8:00 a.m. to 8:00 p.m. and Fri. 
8:00 a.m to 6:00 p.m. Technical support is also available through Compuserve
in the "Stac" forum. Simply type "go stac", for responses within 24 hours.

Remember to send in your registration card now, this is important in
providing you with customer support and announcements of product upgrades.

Technical notes on using ReachOut are available in the file called
TECHNOTE.DOC. This will contain up to date information on using ReachOut
in various technical environments.

Fixes and patches for problems encountered with ReachOut will be made
available through the Stac forum on CompuServe (go stac) and
on the Stac-ReachOut BBS at 407-778-2407.

IMPORTANT NOTE: ReachOut 4.0 will by default add the line
TimerCriticalSection=10000 under the [386enh] section of SYSTEM.INI.
This is necessary if ReachOut Remote Access (drive mapping) or
Windows DOS boxes will be used in conjunction with remote control.
If you determine that this modification to SYSTEM.INI is not 
necessary, the line "nocriticalsection=1" under the [system] section
of REACHOUT.INI can be added to prevent ReachOut SETUP from making
the modification to SYSTEM.INI. REACHOUT.INI can be created on
disk #1 of the installation to prevent the changes at install time.

ReachOut 4.0 adds the following functionalities to our remote control
product:

I.  The Viewer module is now a true Windows application. This means that
    a Windows user can invoke the RO Viewer from within Windows and connect
    to a DOS or Windows Host, he can view that Host in a window of his
    desktop and continue to run other Windows applications.

II. Support for higher resolution video cards on the Windows Host. We now
    support up to 256 colors and 1280x1280 resolution.

III.No modifications are made to SYSTEM.INI or WIN.INI. This means that
    SYSTEM.INI can be modified freely to change device drivers without
    effecting your ReachOut installation. In fact, a ReachOut session
    can use Windows Setup to change a display driver installation while
    connected.

IV. There have been some significant speed improvement in the remote
    control of the Windows Host. If you are remote controlling a 
    Windows Host of the same resolution and number of colors as you did
    with ReachOut 3.2/3.3 then remote control will be faster.

    These speed improvements may not be noticed with the network version
    which was already lightening fast. Other factors influencing your
    remote control: whether you have a buffered COM port (UART), the 
    speed of your Viewer PC, speed of your modems/network, and the speed
    of your Host PC will all effect your overall remote control
    performance.

V.  A remote clipboard has been implemented to facilitate cutting and
    pasting between remote applications.

VI. A fully functional Windows file manager allows quick transfer of files
    between remote PCs by simply dragging and dropping. Entire directories
    can now be transferred with a simple command. Enhanced virus detection
    insures that transferred files are not infected.

VII.A Windows terminal emulation program is built into ReachOut to 
    facilitate connections through corporate front ends. The terminal
    emulation includes scripting, VT100 and ANSI emulations, X/Y/Z modem
    and Kermit file transfers for calling your favorite BBS.

******************************************************************************
    
  A number of fixes have been made to fix several Windows display
  driver problems with ReachOut v. 4.04. They are as follows:

  1. Cirrus Logic display driver on RO Host will now return correctly 
     from screen savers.

  2. ATI MACH 32 driver had numerous problems. Most of these could be
     fixed with RO 4.02 by getting an updatted driver from ATI. It is
     available on their BBS. We recommend you get the latest 2.3
     driver. If you have 2.2 you can make it work with ReachOut by
     making a modification to WIN.INI under the [mach] section:
		[mach]
		stretchblt=off
		devicebitmap=off

     Using the Mach 32 2.3 driver you must still modify WIN.INI
     under the [mach] section:
		[mach]
		devicebitmap=off

  3. The Compaq Concerto Pen Laptop will no longer hang when starting
     Windows with ReachOut loaded.
 
  4. The Diamond Viper will now work correctly as a Host with ReachOut.
     Previously the Viewer would not show any bitmaps of the Host.

  5. The Number 9 video drivers will now show correct colors when being
     viewed.

  6. Fix was made when a 256 color Viewer controls a 16 color Host. 
     Would show up as a GPF or trash at top of Window Paint.

  7. ATI MACH 64 driver must have the following in SYSTEM.INI:
		[macx]
		devicebitmap=off

o ReachOut v. 4.04 has resolved other reported bug fixes. Contact
  Stac-ReachOut technical support regarding the status of a specific
  fix.

o Windows SETUP utility support an option to configure the 
  modem dialing timeout. This timeout sets how long to wait after
  dialing to get a carrier detect before assuming it will not connect.

  This may need to be increased on connections that go overseas,
  use a credit card, or are turning on remote power/on devices.

o Added parameter to REACHOUT.INI under the [Rchexec] section
  to specify how long after carrier detect to wait and see if a 
  ReachOut host is there before loading the ReachOut Windows
  terminal emulator.  =0 means never load it.	syntax is:
                      [rchexec]
	              stetimeout=<#secs>

o Installation script file supports a "group=<group name>" parameter
  to specify which Windows group to add the ReachOut icons. Default is
  "reachout.grp".

  Script file allows '%' character to be passed into batch files so
  that the batch file can use the '%' character to substitute from DOS.

  Script language supports "icons=<*.exe,descrip;...>" commands to set
  the icons that should be added to the ReachOut group at end of install.

  Script language supports a "exit" command to exit Windows upon
  completion of the install.
 
  Script language supports a "nogroup" and "noreadme" command to skip
  by those functions during a scripted install.

  Script language supports a "execute=<path>\<program>" command to
  have Windows automatically exit, invoke a program from DOS, and
  then restart Windows at the end of the Install procedure.

  Script language supports a "nomodem" and "nocomm" command so
  that Install will not ask for a modem configuration or a
  com port configuration. It will assumed to be already configured
  in a default MODEM.RCH file that would be copied at installation.

  Can now invoke a script file from the DOS command line by typing
  "install <script file>". Windows will be launched to install with the
  script file.

  If the file called "roinst" is in the same directory as install 
  when it is invoked, then "roinst" will be used as a default
  script file.

  Technical support can provide details on the installation scripting
  language for those customers who are licensed for large installations
  of ReachOut.

o Added switch to RCHDOS command line to allow specification
  of which DOS LPT device should be redirected to the Viewer for
  printing. The default is that all LPT devices are redirected to Viewer
  when Viewer specifies LPT redirection. Switch syntax is: LPTICPT=<1-4>

o Changed Windows RAMAP utility to be able to run while online without
  a master password.

o The Windows Viewer now provides the ability to change the pop-up
  hot key from the default of <left-shift/right-shift>. This is can be
  changed under the Preferences menu of the Viewer.

o RAMAP command line parameters can remap drives. ex. "RAMAP E D" 
  takes current E: and sets to D:. "RAMAP -E" would completly unmap E.
  Can remap a drive that was unmapped with "RAMAP <map #> <drive letter>"
  ex. RAMAP 0 D:, the map # can be gotten by running RAMAP after a 
  drive has been unmapped. "RAMAP REFRESH" will bring online any drives
  that were not available at connect time.

  Also have command line parameter to refresh drives on Client to see
  if they have been brought online.

o The Windows Hostmenu.exe icon can be hidden by using the 
  'hide' parameter on the command line when it is invoked.

o In ReachOut.ini under the [rchexec] section, set "autoview=1"
  to force the Windows Viewer 'Connect" button to act the same as
  the 'View' button. That is, it will automatically View when connect
  completes.

o Can install a default REACHOUT.INI to the Windows directory
  at install time by simply copying it to the install diskettes
  or into the directory that install is run from.

o ReachOut v. 4.04 has added two new security features. The Host
  can use the SECURITY utility to to disable the Viewer input at
  connect time. The Viewer input will remain disabled until the
  Host re-enables it.

  The Host can use the SECURITY utility to secure itself from 
  intrusions if a connection was lost mistakenly (i.e. bad
  phone lines, modems drop, etc.). With this option selected
  any disconnect that occurs in a ReachOut session that is NOT
  initiated by either the Host or Viewer, will result in the 
  Host allowing only the previous user to re-connect. This
  protects any sensitive data/programs in operation at the
  time of the unwanted disconnect. WARNING: that host will be
  locked until the previous Viewer successfully re-connects.

o ReachOut v. 4.04 adds new auditing/security functionalities. ReachOut
  now has the ability to:

1. Specify the DOS directory path for where the audit tracking file
   should be created. This directory specification is done with the
   SECURITY.EXE utility.

2. The audit tracking file now has a default name of REACHOUT.AUD,
   previous versions of ReachOut had an audit tracking file called
   AUDITLOG.RCH. AUDITLOG.RCH can now be deleted or archived as it
   will no longer be used.

3. Multiple Hosts and Viewers can specify the same path for the audit
   tracking file (network drive). This will have the effect of
   combining all audit records into the same audit tracking file.
   Remember this will have the side effect of making the audit tracking
   file rather large, very quickly.

   An alternative would be to set a common path for all audit tracking
   files, but to enable the option in SECURITY.EXE to have "unique
   audit file names". This will force all Hosts and Viewer to create
   an audit tracking file in the same network drive but each file will
   be individually named according to the ReachOut computer name of the
   Host or Viewer.

4. Every entry in the audit tracking file will contain the computer name
   of the ReachOut system that made the entry. If the system is also
   running Netware it will include the NIC address. The NIC address will
   only be displayed when the audit file is output to a printer or
   put in an ASCII delimited format with "AUDIT TEXT=<filename>".

5. When a LogOn entry is made in the audit tracking file, and additional
   entry will be added that specifies the Netware username if the
   system is logged into Netware.

6. The LogOn entry will include the computer name of the Viewer ReachOut
   system that connected. It will also include the NIC address of the
   Viewer ReachOut system that connected if the Viewer system was 
   running Novell Netware. This NIC address would only be displayed
   when the audit log is printed or output as ASCII delimited text with
   "AUDIT TEXT=<filename>".

7. Terminal emulation will record "dial out" connections and "disconnect"
   with elapsed time as entries in the audit log.

