PW-NT__PW-W95__PW-W98 PWN0271A PATHWORKS 32 V7.1a Network Files ECO Summary
TITLE: PW-NT__PW-W95__PW-W98 PWN0271A PATHWORKS 32 V7.1a Network Files ECO Summary
Copyright (c) Compaq Computer Corporation 2000. All rights reserved.
Modification Date: 24-APR-2000
Modification Type: New Kit
Supersedes Network Files only of PW3271A_E01
PRODUCT: DIGITAL PATHWORKS 32
COMPONENT: Network Files Updates
OP/SYS: MS Windows 95
MS Windows 98
MS Windows NT Server and Workstation
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: PWN0271A
ECO Kits Superseded by This ECO Kit: PW3271A_E01,
Network components only
ECO Kit Approximate Size: 5,008 Blocks
2,564,096 Bytes
Kit Applies To: DIGITAL PATHWORKS 32 V7.1a
Network Files Updates
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Not Applicable
Installation Rating: INSTALL_UNKNOWN
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for network components of PATHWORKS 32 V7.1a on MS
Windows 95, MS Windows 98 and MS Windows NT Server/Workstation. This
PWN0271A kit addresses the following problems:
o This patch applies two previous fixes to the local language
versions of nftw32.exe:
- Copying a file from the PC to VMS, the file date was sent
as Greenwich time (UTC) rather than local time. Thus, the new
file on VMS has a modification time off by some number of hours
(except for UK customers). The fix will send the date properly.
- Prior to PW V7.1A, a user could perform an NFTW copy, specifying
File Type of Binary and Access Mode of Sequential. This function
was removed from NFTW in PW V7.1A. The function has been
restored to NFTW, at customer request.
Platforms: NT4.0 (Intel & Alpha), Windows 95/98
nftw32.exe v7.1.005
\alpha\app\decnet\nftw\\nftw32.exe \pw32\nftw32.exe
\i386\app\decnet\nftw\\nftw32.exe \pw32\nftw32.exe
\w95\app\decnet\nftw\\nftw32.exe \pw32\nftw32.exe
where is cz, de, or fr depending on language
o DLOOPCW.EXE not posting status if network link broken
Platforms: NT4.0 (Intel & Alpha), W95
decdnp.sys 7.1.106
\alpha\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
\i386\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
decdnp.vxd 7.1.106
\w95\protocol\decnet\decdnp.vxd \windows\system\decdnp.vxd
o decndis version number built with wrong version number (7.1.033) -
should be 7.1.034.
Platforms: NT4.0 (Intel & Alpha), Windows 95/98
decndis.sys 7.1.034
\alpha\common\decndis.sys \winnt\system32\drivers\decndis.sys
\i386\common\decndis.sys \winnt\system32\drivers\decndis.sys
decndis.vxd 7.1.034
\w95\common\decnd31.vxd \windows\decnd31.vxd
o Multi-threaded Winsock2 applications hangs when calls are made to
Winsock2 Extended DECNet functions Dnet_getacc(), dnet_getalias(),
dnet_htoa(), getnodebyname() or getnodebyaddr(). The hang failure
was typically observed if multiple threads of the application were
trying to find node information for a node that was not defined in
the local DECNet node database.
Platforms: NT4.0 (Intel & Alpha), Windows 95/98
pws2dnet.wsp 7.0.64
\alpha\protocol\decnet\pws2dnet.wsp \winnt\system32\pws2dnet.wsp
\i386\protocol\decnet\pws2dnet.wsp \winnt\system32\pws2dnet.wsp
\w95\protocol\decnet\pws2dnet.wsp \windows\system\pws2dnet.wsp
pws2dnetd.wsp 7.0.64
\alpha\debug\pws2dnetd.wsp -- debug versions ---
\i386\debug\pws2dnetd.wsp
\w95\debug\pws2dnetd.wsp
o The decdnp version number in the PW event log is wrong.
Platforms: NT4.0 (Intel & Alpha), W95
decdnp.sys 7.1.105
\alpha\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
\i386\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
decdnp.vxd 7.1.105
\w95\protocol\decnet\decdnp.vxd \windows\system\decdnp.vxd
o nftw32.exe doesn't copy a file when attributes set to variable
record size and max record size 2 bytes.
Platforms: NT4.0 (Intel & Alpha), W95
nftw32.exe 7.1.005
\alpha\app\decnet\nftw\nftw32.exe \pw32\nftw32.exe
\i386\app\decnet\nftw\nftw32.exe \pw32\nftw32.exe
\w95\app\decnet\nftw\nftw32.exe \pw32\nftw32.exe
NOTE: for local language versions, use the appropriate subdirectory:
e.g. \i386\app\decnet\nftw\de\nftw32.exe -- for german
dap32.dll 7.1.005
\alpha\app\decnet\nftw\dap32.dll \pw32\dap32.dll
\i386\app\decnet\nftw\dap32.dll \pw32\dap32.dll
\w95\app\decnet\nftw\dap32.dll \pw32\dap32.dll
o Link frozen with pipe quota 6 during async/non-blocking send( ).
Platforms: NT4.0 (Intel & Alpha), W95
decdnp.sys 7.1.105
\alpha\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
\i386\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
decdnp.vxd 7.1.105
\w95\protocol\decnet\decdnp.vxd \windows\system\decdnp.vxd
o Bad NetBIOS packet crashes any station with PW32 installed.
Platforms: NT4.0 (Intel & Alpha), W95
decdnp.sys 7.1.101
\alpha\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
\i386\protocol\decnet\decdnp.sys \winnt\system32\drivers\decdnp.sys
decdnp.vxd 7.1.101
\w95\protocol\decnet\decdnp.vxd \windows\system\decdnp.vxd
o Network adapter doesn't initialize correctly resulting in "Blue
Screen".
Platforms: W95
declat.vxd 9/15/99
\w95\protocol\lat\declat.vxd \windows\system\declat.vxd
o On NT4/SP4 or later, get error 'No TAPI device configured'
from remote connection manager when try to connect to a
service or create a connection.
Platforms: NT4.0 (Intel & Alpha)
pwcm32.exe 7.1.005
\alpha\app\pwcm\pwcm32.exe \pw32\pwcm32.exe
\i386\app\pwcm\pwcm32.exe \pw32\pwcm32.exe
o Installing PATHWORKS 32 on NT4.0 with Service Pack 4 can result
in Access Violations with some applications -- notably the
Autoprotect feature of Norton AntiVirus.
Platforms: NT4.0 (Intel & Alpha)
rpclts4.dll 7.2.005
\alpha\pwsdk\bin\rpclts4.dll \winnt\system32\rpclts4.dll
\i386\pwsdk\bin\rpclts4.dll \winnt\system32\rpclts4.dll
rpcltc4.dll 7.2.006
\alpha\pwsdk\bin\rpcltc4.dll \winnt\system32\rpcltc4.dll
\i386\pwsdk\bin\rpcltc4.dll \winnt\system32\rpcltc4.dll
Superseded kit PW3271A_E01 addressed the following problems:
o This kit provides Euro Currency Symbol support for POWERTERM
and eXcursion.
o Task to task problem between PC and OpenVMS Alpha when an
application tries to open 4 links, the last one connects
and disconnects continuously.
Platforms: NT4.0 (Intel & Alpha), Windows 95/98
pws2dnet.wsp 7.00.63
\alpha\protocol\decnet\pws2dnet.wsp
\i386\protocol\decnet\pws2dnet.wsp
\w95\protocol\decnet\pws2dnet.wsp
pws2dned.wsp 7.00.63
\alpha\debug\pws2dned.wsp
\i386\debug\pws2dned.wsp
\w95\debug\pws2dned.wsp
o Network adapter does not initialize correctly resulting in
"Blue Screen".
Platforms: NT4.0 (Intel & Alpha)
declat.sys 7.1.035
\alpha\protocol\lat\declat.sys
\winnt\system32\drivers\declat.sys
\i386\protocol\lat\declat.sys
\winnt\system32\drivers\declat.sys
o DECnet fails under heavy load; especially with Compaq Proliant
series of server computers with Intel's Netelligent/Netflex
Ethernet cards.
There could be many different symptoms such as:
-- Blue screen 0x0000000A,0x00000014,0x0000001c,0
x000000000,0x80115cdd
-- PWEVENT.LOG: NDIS0063N: Added 32 packets to the
Datalink buffer pool total=xxx
Platforms: NT4.0 (Intel & Alpha), Windows 95/98
decndis.sys 7.1.034
\alpha\common\decndis.sys
\winnt\system32\drivers\decndis.sys
\i386\common\decndis.sys
\winnt\system32\drivers\decndis.sys
decndis.vxd 7.1.034
\w95\common\decnd31.vxd
\windows\decnd31.vxd
o ScreenSaver dies with user32.dll initialization error.
Platforms: NT4.0 (Intel & Alpha)
\alpha\app\decnet\spawner\spawn32.exe
\winnt\system32\spawn32.exe
\i386\app\decnet\spawner\spawn32.exe
\winnt\system32\spawn32.exe
o DECnet/Winsock2 does not supply enough sockets.
Platforms: NT4.0 (Intel & Alpha), Windows 95/98
pwiocb32.dll 7.1.013
\alpha\app\decnet\pwiocb32.dll
\winnt\system32\pwiocb32.dll
\i386\common\pwiocb32.dll
\winnt\system32\pwiocb32.dll
o DECNET Winsock wsp does not return network status
(dofwn) when send() times out due to link failure.
Platforms: NT4.0 (Intel & Alpha)
decdnp.sys 7.1.100
\alpha\protocol\decnet\decdnp.sys
\winnt\system32\drivers\decdnp.sys
\i386\protocol\decnet\decdnp.sys
\winnt\system32\drivers\decdnp.sys
o When copying a file with NFTW32.EXE from PW32 to OpenVMS, the
time is set incorrectly on the output file. It appears 5 or
6 hours off.
Platforms: NT4.0 (Intel & Alpha), Windows 95/98
nftw32.exe 7.1.001
\alpha\app\decnet\nftw\nftw32.exe \pw32\nftw32.exe
\i386\app\decnet\nftw\nftw32.exe \pw32\nftw32.exe
\w95\app\decnet\nftw\nftw32.exe \pw32\nftw32.exe
dap32.exe 7.1.001
\alpha\app\decnet\nftw\dap32.dll \pw32\dap32.dll
\i386\app\decnet\nftw\dap32.dll \pw32\dap32.dll
\w95\app\decnet\nftw\dap32.dll \pw32\dap32.dll
INSTALLATION NOTES:
This is the patch kit for network components of PATHWORKS 32 version 7.1a.
This patch kit contains bug fixes as listed above to the base network
components of the PATHWORKS 32 software.
This kit is organized as a 'sparse CD-ROM image', i.e. a directory with
the same structure as the original released CD-ROM, but populated only
with files that have been patched since the release.
Patch kits are cumulative, each new kit contains all previous patches in
addition to the new patch(es); i.e. new patched files are added, or previous
files are modified.
There are two ways to install the patched files:
Full Installation An automated procedure to install all patches
Partial Installation A manual procedure to install selected patches
FULL INSTALLATION
=================
This procedure creates a full release image which is subsequently
installed over a current installation in much the same way as you
would upgrade or reinstall a regular CD-ROM release.
If you wish to patch several systems, you can create the release
image on a shared directory and install it on each system over the
network.
1. Create a release image by copying the original PATHWORKS 32
V7.1A CD-ROM to a shared directory.
2. Unzip the patch kit (pwn0271a.zip) to a temporary directory
and copy it over the release image. You may also be able to
unzip the patch directory directly over the release image.
Make sure you retain the directory structure of the unzipped
files.
3. Run autoplay.exe in the root of the release image and follow
the instructions as you would a normal installation to reinstall
PATHWORKS 32.
4. Restart your system.
PARTIAL INSTALLATION
====================
1. Unzip the patch kit (pwn0271a.zip) into a temporary directory.
Make sure you retain the directory structure of the unzipped files.
2. Read the patch descriptions above to determine which files you require.
The descriptions will tell you where the files are located in the patch
directory and where they normally reside in an installed system.
3. Copy the selected files from the patch directory to your system.
4. Restart your system.
TRADEMARK INFORMATION:
The following are trademarks of Compaq Computer Corporation:
DECnet DIGITAL PATHWORKS eXcursion
The following are trademarks of other companies referenced in
this document:
(R) Microsoft, Windows and Windows NT are registered
trademarks of Microsoft Corporation.
(R) PowerTerm is a registered trademark of Ericom Corporation.
(R) NetWare is a registered trademark of Novell Corporation.
(R) PKZIP and PKUNZIP are registered trademarks of PKWARE, Inc.
Trademarks of other companies mentioned appear for identification
purposes only and are the property of their respective companies.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
pwn0271a.README
pwn0271a.CHKSUM
pwn0271a.CVRLET_TXT
pwn0271a.exe
pwn0271a.CVRLET_TXT
|
