REMOTELY POSSIBLE/32 Version 3.Ob October 25, 1996 Sections: I. New Features/Corrections History II. Product Overview III. Install/DeInstall IV. How to use Multi-takeover capability V. Limitations (NOTE: Please read RE: NT 4.0) VI. Technical Support I. NEW FEATURES/CORRECTIONS HISTORY New Features ~~~~~~~~~~~~ Added Remote Installation functionality between NT to NT. Added new security feature Logoff on Disconnect. Added support for NT 4.0 (Note: Need Release Candidate 1 or higher). Added support for NetBeui/NetBios protocol. Added new service to start/stop listen for call mode. Added support for command line function calls. Added ScaletoFit registry video option for multiple host viewing. Added PushPin registry option for setting the pushpin on during multiple connects. Added support for NT 4.0 TAPI interface to allow Dial-in/Dial-out connections. Corrections ~~~~~~~~~~~ Corrected color conversion problems on NT using greater than 256 color. Modified handling of duplicated license number. Corrected problem with Red Screen displaying on Viewer due to large number of font files on Host and Viewer. Fixed problem when selecting multiple files in Explorer. Reduced memory usage per connection on NT. (2.1c and Beta 3) II. PRODUCT OVERVIEW Avalan Technology's Remotely Possible/32 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Remotely Possible/32 is designed to provide remote control capability for Windows 95 and/or Windows NT, based on licensing purchased. Remotely Possible/32 can control a 16-bit Windows 3.x PC running Remotely Possible/LAN, Remotely Possible/Dial or Remotely Possible/Sockets (TCP/IP). When running Remotely Possible/32 on an NT system the Intel processor is currently supported. Download the Alpha version of Remotely Possible/32 3.0 beta for use on this processor. Any other processors are not supported at this time (ie. PowerPC, MIPS). Remotely Possible/32 offers the following new benefits over our 16 bit application: 32 bit Application Design Enhanced Performance Portability between 32 bit and 16 bit applications Improved Graphical User Interface User Customization Options Intuitive On-line Help System Ease of Use Remotely Possible/32 offers the following new features over our 16 bit application: Multiple simultaneous remote control, file transfer and chat sessions. Multiple program instances Hide application during remote control option Browse on multiple networks at one time. Flexible ribbon bar positioning Button bar display option Status bar display option Cursor position sensitive help Full compatibility with Remotely Possible Sockets File Transfer - Create/Remove Directory, Rename/Delete File Long File Name support Non-Intrusive Install Auto-Panning during Remote Control Host Mode "Baton Passing" used during training and interactive demonstrations. Host Pop Up password to prevent unauthorized sessions. Notification bell to get attention of remote user when running chat mode. We hope that you have an enjoyable experience with Remotely Possible/32. Please review the contents of this readme.txt file prior to installation, particularly the LIMITATIONS section. Windows 95, Windows NT and 32-bit applications require large amounts of memory. If your system has limited memory resources (such as a small amount of hard drive space for the swap file), Remotely Possible and other programs may exhibit abnormal behavior. We recommend maintaining at least 30 megabytes of free disk space that Windows may use for its swap file. III. INSTALL Install ~~~~~~~ During the installation process, Remotely Possible will determine disk space requirements and the operating system. The Remotely Possible install checks for at least 3MB of disk space and that you are running Windows 95 or NT. If either of these checks fail you will be unable to install Remotely Possible. Remotely Possible/32 installation defaults to the standard application install path for Windows 95 and Windows NT. x:\Program Files\Avalan\Remotely Possible. This path is user selectable but the default is recommended. PRESET.INI ~~~~~~~~~~ By using a file called preset.ini in the installation directory, you can customize the factory default preferences used when the application is loaded. This file is only read the first time an installation performed on a particular workstation. If Remotely Possible is already installed on the PC you must deinstall Remotely Possible and reinstall using the diskette that contains the preset.ini option. There is a file located in the root of the install disk called DEFAULT.INI, this contains Avalan's recommended default settings. Use the DEFAULT.INI as a template to customize your installation, add only the parameters you want to change to a file called PRESET.INI. Ex. DEFAULT.INI PRESET.INI [Guest] ... StartFull=1 StartFull=0 Start's Host in a Window on Connect rather than Full screen. DeInstall ~~~~~~~~~ Windows 95: You may now deinstall the product by running the UNWISE.EXE script from your program directory and selecting the INSTALL.LOG when prompted. Windows NT: To deinstall the product, select the Uninstall Remotely Possible option in the Remotely Possible/32 program folder. IV. HOW TO USE MULTI-TAKEOVER CAPABILITIES Multiple Host ~~~~~~~~~~~~~ Remotely Possible/32 offers an exciting new feature that allows a single PC to control more than one Host at the same time. This is referred to as Multi-Host capability. This feature is ideal for Help Desks, Systems Support and Call Centers. To start a second or third connection perform the following steps: 1. The default setting for the first connection is to start in full screen mode. This is denoted with a blinking square in the upper left hand corner and the Host takes up the entire screen on the Viewer. 2. Move the mouse up into the region with the blinking square and press the right mouse button. This will switch you back to your local PC's Remotely Possible/32 program, and the Host you are controlling appears in a window. 3. Start your next connection the same way you did the first. Select Connect to Remote, change to the appropriate connection type (Dial, IPX or TCP/IP), enter the connection information, select option to start on connect (Viewer, Chat, File Transfer). When running with multiple connections, you must use your local PC's Remotely Possible program screen to switch control between your connections by using the pull down connection window. Also, the push pin located at the far right on the connection toolbar is used to keep a connection visible when changing to a between connections. By cascading or tiling the multiple windows you can view two or more remote PCs simultaneously. Note: To make the Viewing of multiple hosts easier, you can default the "Push Pin" feature to an on position. Add the following entry to the registry: HKEY_USERS\.default\software\avalan\guest\PushPin=1 Multi-Viewer ~~~~~~~~~~~~ Remotely Possible/32 offers another exciting new feature that allows a single PC to be controlled/viewed by more than one Viewer at the same time. This is referred to as Multi-Viewer capability. This feature is ideal for classroom training and interactive demonstrations. To use this feature perform the following: 1. On the Host PC, select Change User Preferences, go to the Host tab and disable the option for Hide Remotely Possible. Place the Host in "Listening for a Call" mode. 2. On all Viewers to be used, select Change User Preferences, go to the Viewer tab and disable the option for "Hide Host's Remotely Possible Window". 3. Have two or more Viewers connect to the Host PC. 4. Once the second Viewer is connected the "Baton Passing" feature is enabled, and all additional connections are placed in monitor only mode. The teacher or chairperson has the ability to pass the keyboard and mouse control, "The Baton", to a particular Viewer. There are two methods of passing the baton: Windows 95, the Host uses the right mouse button on the icon in the system tray (bottom right). Windows NT, the Host uses the Host option on the main menu. Special conditions when running Multi-Viewer All Viewers participating in a Multi-Viewer connection should run the same number of colors, or first Viewer should have least number of colors. If the first Viewer disconnects, additional Viewer connections will be refused. If the Host disables "Listen for a Call" mode and then re-enables, no additional connections will be allowed. V. LIMITATIONS Limitations ~~~~~~~~~~~ WARNING: DO NOT INSTALL REMOTELY POSSIBLE/32 IF REACHOUT, PCAnywhere OR OTHER THIRD PARTY REMOTE CONTROL SOFTWARE PACKAGES EXIST ON YOUR SYSTEM. PLEASE DEINSTALL THESE BEFORE INSTALLING REMOTELY POSSIBLE/32. REMOTELY POSSIBLE/32-NT LIMITATIONS 1. Windows 95 Viewer needs to be running Remotely Possible/32 v2.0 or higher to connect to an NT Host. (Use the NT installation disk to upgrade your 95 PC.) 2. No Support for Windows 3.x running Sockets 2.0 as a Viewer to a Windows NT host. 3. Printer redirection is currently disabled. 4. Disable Host Keyboard and Mouse are currently not enabled. REMOTELY POSSIBLE/32-95 LIMITATIONS 1. No DOS Printer redirection. 2. Can not answer the phone properly if other applications are waiting for a call. (i.e. Winfax or Dial Up Server). VI. TECHNICAL SUPPORT Technical Support ~~~~~~~~~~~~~~~~~~~ Refer to the About Remotely Possible/32 box from the Help menu.