SYMANTEC--PETER NORTON GROUP README.TXT—April 19,1996 Copyright 1995 Symantec Corp. All Rights Reserved. Release Notes Norton pcANYWHERE for Windows Version 2.0 ------------------------------------------------------------------------------- NOTE: These files must be copied while your PC is in DOS mode. For Windows 95 users: 1. Restart your system by selecting Shutdown, then Restart the computer in MS-DOS mode, from the start menu. Windows 3.1x users: 1. Exit completely out of Windows by pressing Alt+F4 or clicking File, Exit. This should return you to the DOS prompt. General Installation: 1. When the PC comes back up in DOS mode, type: CD\ and press Enter to return to the root directory. 2. Create a temporary directory by typing: MD\update and press Enter. 3. Change to the directory 20UP_E.EXE is in. Copy 20UP_E.EXE to the update subdirectory by typing: Copy 20UP_E.EXE C:\update and press Enter. 4. Change to the update directory by typing: CD\update and press Enter. 5. Execute 20UP_E.EXE by typing: 20UP_E and press Enter. ADMINISTRATOR INSTALL Copy all files into your pcANYWHERE 2.0 directory on your network by typing: COPY *.* F:\WINAW and press Enter. WORKSTATION INSTALL If Windows runs from the local hard drive, the following files need to be copied to the \windows\system directory: AWDSP.DLL VPCAW.386 Type: Copy AWDSP.DLL VPCAW.386 c:\windows\system and press Enter The following files should ONLY be copied if the dates are LATER than the dates of the same files in the \windows\system directory: SYMEVNT.386 SYMEVNT1.DLL Type: Copy SYMEVNT?.* c:\windows\system and press Enter. NOTE: If you are using any other Symantec Windows 95 applications, you will also need to copy all Symevnt 16 and 32 bit programs to the \Program Files\Symantec subdirectory. As before, copy these files only if they have newer dates that the files already in this directory. These would be the files: SYMEVNT.386 SYMEVNT1.DLL S32EVNT1.DLL STANDARD INSTALL If Windows runs from the local hard drive, do this installation. Otherwise, complete the Shared Windows Installation. Copy all files into your pcANYWHERE 2.0 directory, except for the following files which must be copied to your \windows\system directory: AWDSP.DLL VPCAW.386 Type: Copy *.* C:\WINAW and press Enter Copy AWDSP.DLL VPCAW.386 c:\windows\System and press Enter The following files should ONLY be copied if the dates are LATER than the dates of the same files in the \windows\system directory: SYMEVNT.386 SYMEVNT1.DLL Type: Copy SYMEVNT?.* c:\windows\system and press Enter. NOTE: If you are using any other Symantec Windows 95 applications, you will also need to copy all Symevnt 16 and 32 bit programs to the \Program Files\Symantec subdirectory. As before, copy these files only if they have newer dates that the files already in this directory. These would be the files: SYMEVNT.386 SYMEVNT1.DLL S32EVNT1.DLL WINDOWS WORKSTATION If Windows is running from the Network hard drive, copy all files into your pcANYWHERE 2.0 directory, except for the following files which must be copied to the shared network Windows directory: AWDSP.DLL VPCAW.386 Type: Copy *.* c:\WINAW and press Enter. Copy AWDSP.DLL VPCAW.386 F:\Windows and press Enter The following files should ONLY be copied if the dates are LATER than the dates of the same files in the shared network Windows directory: SYMEVNT.386 SYMEVNT1.DLL Type: Copy SYMEVNT?.* c:\windows\system and press Enter. NOTE: If you are using any other Symantec Windows 95 applications, you will also need to copy all Symevnt 16 and 32 bit programs to the \Program Files\Symantec subdirectory. As before, copy these files only if they have newer dates that the files already in this directory. These would be the files: SYMEVNT.386 SYMEVNT1.DLL S32EVNT1.DLL Fixed in this Release -------------------------------------------------------------------------------------------------------------------------------- - Corrects various Drive Mapping issues while running Novell's VLMs. - Improves ZMODEM file transfer. - Corrects scripting issues found when using "On Disconnect", "$Error", "$Result", and "Session Retry" commands. - Allows the use of short or alias character names on the DNS server when using Frontier's TCPIP stack. - Corrects the issue of mouse click delays over TCPIP - Speeds up file transfer over TCPIP - If DIAL ONLSVC does not connect, after the "No answer" dialog appears, you would get an error "Error finding string in combo box" - Running a script using an assignment operator with the ON ERROR statement caused it to crash. - If the session disconnected in file transfer, the script would end. - The script would end if you connected to a modem, using the SESSION DIAL command, but the host was not running. - Decreases the amount of GDI resources reserved. - Corrects file name corruption when transferring a large number of files. Fixed in previous Releases -------------------------------------------------------------------------------------------------------------------------------- - Now supports up to 16.7 million color displays - High ASCII characters will now display correctly in the title bar. - Improved compatibility with the #9 GXE video card. The TimerCritical section needs to be set to 10000. - Fixed a problem with logging in while the master password dialog box is up. - Fixed a problem that caused the Access Server not to log properly. The error happened when the session was not ended from the online menu. - Allows the host to log the remote's computer information even if a session ends abnormally. - Fixed a problem in file transfer which caused an improper "No Files Found" message. The problem was caused by a sequence of Filtering and Synching. - Fixed a problem with file transfer and having a Master Password. It was not allowing uploads or downloads - Corrects the issue of corrupting database like files during file transfer. - Using the DOS TSR and NetWare Connect, transferring a large number of files or one large file, was causing the host to reboot. - The option Coldboot Always now works when ending a session by exiting Windows. - Fixed option in Advanced Modem Settings to only allow 1-999. The help for this was also fixed. The option is "Set seconds to wait after dial" - Fixed a problem with using Quick Connect for an Online Service. The error happened when the user clicked Cancel and the computer name field was left blank. - Removed incorrect help paragraph in Remote options referencing "Disable Windows Mouse". - Fixed Online Help section for Custom Modem - Fixed a problem with the DOS TSR and host security preference to Lock Host While Waiting. The host was not allowing it’s mode to be changed. - NetWare Connect was not displaying a port. - If you set lock the host keyboard, the remote was also locking. - OLE and CallOnlSvc were generating an "Invalid command line arguments" error message. - Fixed a problem with drive access and using configuration files from 5.02. - The host was locking up when trying to end a session using Netbios and Token Ring. - Frontier was not re-initializing after ending a session. - Allows use of command line options when using a network installation with everything shared along with a Master password in the @@@ configuration. - Corrects various low level intermittent problems that may occur when using pcANYWHERE and Windows For Workgroups. - Improved file transfer when using the Kermit protocol. - Corrects the issue of the file transfer button graying on systems running AW_HOST and Winhost after disconnecting while in Windows. The file transfer button is only active while in Windows. - Adds the capability of how pcANYWHERE will determine the computer name. By adding HOSTCOMPUTERNAMESELECTION=1 under the [HOST] section in the PCAW.INI file- pcANYWHERE will use your Banyan Street Talk Name as your computer name. By not adding that line to the PCAW.INI file- pcANYWHERE will use the computer name you chose during installation. - Host name is now defaulted to NetWare login name on network installs. - Now allows TCPIP connections over Dec Pathworks Additional Information ------------------------------------------------------------------------------- - The TCP/IP connection type does not support gateways, as the gateway is a DOS program and pcANYWHERE 2.0 TCP/IP only works under Windows. - The TCP/IP connection type allows users to insert the host's IP address for the Host Computer Name. Updating the host list is not necessary. - Users with Novell DOS 7.0 should update their VIPX.386 file with the latest version from Novell dated May 19, 1994 or later. - Users who have Windows 3.1 with VIPX.386 dated March 10, 1992 should upgrade to a newer version. The old version causes machines to reboot if an IPX host is waiting while exiting Windows. - When running the DOS Host TSR at over 9600 Baud in Windows you must add device=aw_vcd.386 to the [386Enh] section in the SYSTEM.INI replacing device=*vcd. You must also copy the aw_vcd.386 file from the WINAW install direc- tory to the WINDOWS/SYSTEM directory. - For the SessOpr Remote Send and SessOpr Host Send script commands, the first string parameter contains the source file name only. If you wish to specify the optional destination file name, a second string parameter is required. The script manual states that both file names are to be included in a single string parameter. - When using the ON ERROR script command, you should only follow it by the GOTO command or GOSUB command. ex: On Error GoSub @errmsg - Sessopr Host commands will not work when running with the PCAW Host DOS TSR. A possible work around would be to run the AWSEND.EXE program as the command to execute after connection. This program is available on the Symantec BBS at (541)484-6669. Only use AWSEND.EXE if you are running the DOS Host TSR. - For additional scripting information, download the sample script file, SAMPL2.SCR, from the Symantec BBS at (541) 484-6669, Compuserve, America Online, or ftp.symantec.com. - Printing remotely from a Host DOS Box requires that the Host DOS TSR be loaded. - Drive mapping when the DOS Host TSR is loaded. You may see network drives on the available drive list that are already mapped to network drives and are not available. - When running the DOS TSR, the Command to Execute After Connect function will not work unless you are using the -m=w (Wait for a call mode). - Remote operation setting: Use Local Fonts, is defaulted to ON. If characters don't display correctly on the remote or the display refresh is slow, the setting should be changed to OFF. - If you are having problems finding the remote drives in your drive windows (Microsoft's File Manager, Symantec's Norton Desktop for Windows Drive Window or any other type of drive/directory/file viewer) or are having a problem with any type of file operation on the remotely mapped drives try one of the following steps to rectify the situation: 1. Make the drive window the active window and press F5. This will cause a drive refresh to occur. This should fix most of the problems. 2. If the problems still persist, then select your O/S option for Connect Network Drive or Disconnect Network Drive. Once the dialog box appears, select the cancel button. This will cause a refresh of all of the drives. - After an administrator install, to avoid possible 'sharing violation' warnings, mark AWMODEM.MD6 as sharable. - With OLE2 support being improved, the manual setup of OLE2 in section A-21 is no longer necessary. Now REGEDIT is automatically updated to run pcANYWHERE through OLE. - The manual states on page A-22, CallOnlSvc, to use: iStatus=winaw.callhost(0, "CompuServe") it should state: iStatus=winaw.callonlsvc(0, "CompuServe") - If you have a #9GXE video card make sure you have TimerCriticalSection=10000 in the [386Enh] section in the SYSTEM.INI. - If you are using 16-bit color mode and are seeing problems with remote colors, add the following line to the PCAW.INI file. ColorFormat=555 ;This goes in the pcANYWHERE section - If you are running 256 colors or above and not receiving the full impact of those colors, add the following line to the PCAW.INI file: Video1=256 ;This goes in the [pcANYWHERE] section NOTE: This will require additional resource usage. - To improve performance in MS Windows 95, you may want to do the following Run REGEDIT.EXE Choose HKEY_CURRENT_USER/CONTROL PANEL/DESKTOP/WINDOWMETRICS Add a string for "MinAnimate", and give it a value of 0 Restart the machine. This will disable the exploding window effect - If you have installed any Symantec 32 bit applications, you must copy SYMEVNT1.DLL, SYMEVNT.386, AND S32EVNT1.DLL to C:\Program Files\Symantec