Dec 062017
This is an update for Norton PCAnywhere 2.0 for Windows. The second update and updates to 2.02. File dates are 04/95 and it includes many updated EXE AND DLL files.
File 20UP_A.EXE from The Programmer’s Corner in
Category Recently Uploaded Files
This is an update for Norton PCAnywhere 2.0 for Windows. The second update and updates to 2.02. File dates are 04/95 and it includes many updated EXE AND DLL files.
File Name File Size Zip Size Zip Type
AW_HOST.EXE 64013 32608 deflated
AW_V_GEN.OVL 6024 4896 deflated
AW_V_VGA.OVL 4590 3782 deflated
AWCM.DLL 7056 4719 deflated
AWCMBAN.DLL 5584 3822 deflated
AWCMIPX.DLL 12288 5507 deflated
AWCMTCP.DLL 6192 3416 deflated
AWCNF.DLL 78112 16641 deflated
AWCOMMON.DLL 78928 30023 deflated
AWCONPRC.DLL 84688 32182 deflated
AWDSP.DLL 4640 2013 deflated
AWDSP18.DLL 63872 16568 deflated
AWDSP41.DLL 61664 15764 deflated
AWDSPBW.DLL 61728 15812 deflated
AWDVR_D.OVL 2671 1676 deflated
AWDVR_E.OVL 7063 4347 deflated
AWHSCPRC.DLL 6080 3245 deflated
AWMODEM.MD6 173056 22432 deflated
AWPOPUP.DLL 4672 3010 deflated
AWREMACC.DLL 10944 7798 deflated
AWSCRPRC.DLL 96656 42750 deflated
AWSEQPRC.DLL 18000 8805 deflated
AWSESCTL.DLL 15040 7029 deflated
AWTERM.DLL 182736 76562 deflated
AWTERM.TM6 22528 5147 deflated
AWTIME.DLL 4160 2453 deflated
AWXFER.DLL 92448 40901 deflated
AWXFERUI.DLL 249296 106185 deflated
AWXFRPRC.DLL 52416 23578 deflated
README.TXT 4657 1943 deflated
SYMEVNT.386 54379 22165 deflated
SYMEVNT1.DLL 3888 2099 deflated
SYMKRNL5.DLL 112736 60436 deflated
VPCAW.386 19597 8049 deflated
WINAW.EXE 308272 109698 deflated
WINAW.REG 591 211 deflated
WINHOST.EXE 70816 29232 deflated

Download File 20UP_A.EXE Here

Contents of the README.TXT file


README.TXT--May 4, 1995
Copyright 1995 Symantec Corp. All Rights Reserved.

Release Notes
Norton pcANYWHERE for Windows
Version 2.0 pcANYWHERE Fixes
Execute 20UP_A.EXE to view files required to upgrade pcANYWHERE 2.0.

Copy all files into your pcANYWHERE 2.0 directory on your network.

The following files need to be copied to the \windows\system directory:

Copy all files into your pcANYWHERE 2.0 directory, except for the
following files which must be copied to your \windows\system directory:


If you are running under a shared network Windows installation,
copy all files into your pcANYWHERE 2.0 directory, except for
the following files which must be copied to the shared network Windows


- The TCP/IP connection type does not support gateways, as the gateway is a
DOS program and TCP/IP for pcANYWHERE 2.0 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

- 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.

- Sessopr Host commands will not work when running with 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. You should only use AWSEND.EXE if you are running the DOS
Host TSR.

- In the scripting language, an ON ERROR statement should only be followed
by a GOTO or a GOSUB statement.

- Printing remotely from a Host DOS Box requires that the Host DOS TSR be

- Drive mapping when 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 char's
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.

- The manual states on page A-22, CallOnlSvc, to use:
iStatus=winaw.callhost(0, "CompuServe")

it should state:
iStatus=winaw.callonlsvc(0, "CompuServe")

- Between builds 345 and 347 of Windows95, we have noticed an instability
in NetBIOS connections.

 December 6, 2017  Add comments

Leave a Reply