These release notes provide the latest information regarding Remotely Possible/32 available at the time of release. For more information, see our website at http://www.avalan.com.
__________________________________
1) General Information
2) Technical Support
3) New Features
4) Install and Uninstall
5) Localization Issues
6) Open Issues
__________________________________
GENERAL INFORMATION
Remotely Possible/32 provides remote control capability for Windows 95 and/or Windows NT environments, 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).
This version of Remotely Possible/32 is designed for the Intel processor, if you have an Alpha processor contact Avalan to obtain Remotely Possible/32 4.0 for Alpha. Any other processors are not supported at this time (ie. PowerPC, MIPS).
TECHNICAL SUPPORT
Avalan Technology performs detailed in-house testing before releasing any version. Should you find a problem in Remotely Possible/32 or have any comments or suggestions, please contact Avalan at:
Fax Line: (508) 429-3179
Avalan BBS: (508) 429-3671
E-Mail: support@avalan.com
Voice Line: (508) 429-6482
Mon - Fri (8:30am - 6:30pm EST)
NEW FEATURES
- Explorer-like Browser for File Transfer
- New Security Options - Remotely Possible/32 Proprietary Security, RP/32 NT Local User Security, RP/32 NT Group/Domain User Security
- Easier recording with Record Tab
- Play back recorded files with Remotely Possible/Replay
- Improved installation wizards
INSTALL AND UNINSTALL
- When installing Remotely Possible/32 on a Windows NT system, the Standard installation installs RP/32 Proprietary Security mode. To install one of the Windows NT security modes, do a Custom installation or switch security modes after installation.
- The uninstall program removes NT Local User groups, but does not remove global groups.
LOCALIZATION ISSUES
- When running a localized version of Remotely Possible/32 on an English operating system, the operating system looks for English resources. You can solve this problem one of the following two ways:
1) Set the Regional Settings to the locale of your choice.
For example, if you want to run the French version of Remotely Possible/32 on an English operating system, do the following:
1. Choose Control Panel from the Start menu.
2. Double-click on the Regional Settings icon.
3. In the Regional Settings tab, choose French(Standard). You must restart your computer for the change to take effect.
4. After restarting your computer, re-launch Remotely Possible/32, and the French resources are displayed.
2) If you do not want to change your Regional Settings, simply rename rpfra.dll and rppfra.dll in Program Files\Avalan\Remotely Possible to rpenu.dll and rppenu.dll and restart Remotely Possible/32.
OPEN ISSUES
- The Blank Host screen option has no effect on a Windows NT 3.51 Host machine.
- Left-handed mice function as right-handed mice when controlling another machine.
- Dial connection drops when running a 16-bit application.
- When using the Dial protocol with the Wait for a Call option selected but without a modem selected, the Modem dialog box keeps circling the screen.
- If other applications such as fax software are in the waiting for a call mode, Remotely Possible/32 Dial does not answer call.
- Printer Redirection on Windows 95 produces an extra page for each print job.
- Unable to enter screen saver password when activated on a 95 host.
- Tool tips not displayed in Explorer File Transfer window on NT 4.0.
- When monitoring another PC with Toggle Monitor mode enabled, the Host hot keys are enabled. The Host hot keys, however, are not enabled when controlling the PC.
- A user who does not have administrator rights cannot start RP/32 as a service, which causes NT security modes to fail.
- When both local confirmation and callback are turned on, local confirmation is bypassed.
- Upon terminating a successful connection between two Windows NT 3.51 machines with the Host's wallpaper disabled, the Viewer machine displays the Windows NT logon screen as the default wallpaper. Logging off and then logging on again corrects this problem.
- When connecting to a remote machine running Windows NT 3.51 from a local machine running Windows NT 4.0, some applications display two mouse pointers. This problem occurs when using Microsoft Office products and Free Cell.
- When connecting to a remote machine running Windows 3.x from a local machine running Windows 95 or Windows NT, do not enable the Blank Host Screen option. Enabling this option causes the screen to become distorted and uncontrollable even after disconnecting. The display returns to normal after restarting the machine.
- When the host mode is enabled on a machine running Windows NT 4.0 with Service Pack 3, Internet Explorer 4.0 does not install properly. When you try to launch Internet Explorer 4.0, the monitor displays a blue screen. To launch Internet Explorer 4.0, make sure that Host mode is not enabled.
- On a Windows 95 Viewer with all protocols enabled (TCP, IPX, and NetBIOS) and with the Dial-Up Adapter installed, the viewer is not able to browse or connect to hosts using the NetBIOS protocol. If you unbind NetBIOS from the Dial-Up Adapter, you can browse and connect to hosts using the NetBIOS protocol.
- Printer redirection is currently not supported with ECP parallel printer ports.
- RP/32 icons are removed from local machine if abort is selected during a remote install.
- Local confirmation window is displayed in background.
- You may experience problems when remote controlling Internet Explorer 4.0.
