PW-DOS PW60ECO2 PATHWORKS for DOS and Windows V6.0 ECO Summary
Copyright (c) Digital Equipment Corporation 1996. All rights reserved.
PRODUCT: PATHWORKS for DOS and Windows, Version 6.0
OP/SYS: MS-DOS, Versions 5.0 through 6.22
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: PW60ECO2
ECO Kits Superseded by This ECO Kit: PW60EC01
ECO Kit Approximate Size: 8425 Blocks
4313509 Bytes
ECO KIT SUMMARY:
An ECO kit exists for PATHWORKS for DOS and Windows V6.0 on MS-DOS V5.0
through 6.22. This kit addresses the following problems:
* NOTICE * When components are grouped together as one fix,
THESE COMPONENTS MUST BE UPDATED TOGETHER.
CMTOKEN.DAT
===========
V6.0.71 1- Improve callback support for an asynchronous connection
with a SHIVA LanRover Network Access Server.
CTERM.EXE
=========
V6.0.026 1- Within VT320 Emulation (CTERM) and ALL-IN-1, escape
sequences are inserted when using backspace or cursor
keys several times.
V6.0.25 1- PATHWORKS CTERM receives a START READ message from a
Forest Network Resource CTERM host, specifying a read
buffer of four. When the F8 key is hit, an escape
sequence of 5 characters is generated. But PATHWORKS
CTERM never sends the sequence back to the host.
DBGLICLM.EXE
DBGLICNW.EXE
============
DBG6.0.042 1- Add Debug License components to kit.
DECCTRM.DLL
===========
1.0.005 1- VT320 not able to set display to 132 column mode when
connecting via CTERM.
DECDNP.VXD
DECDNPD.VXD
===========
V1.0.36 1- Protected mode DECnet always used LANA 0. A new keyword
LANABASE is introduced which addresses the problem on WFW
clients. DECnet can now occupy the LANA # of user's
choice.
V1.0.34 1- When performing multiple reads, the last read does not
complete.
V1.0.32 1- Lotus Notes does not operate over a wide-area network.
The application cannot establish the remote connection,
even if the name is defined correctly in the database.
2- Winsock applications that use the WSASelect or
WSAAsyncSelect calls fail with the error "E2BIG"
The application "DataTrieve" seems to bring out this
problem.
3- The FIND.NAME NetBIOS command has been corrected to
return the correct network address. It was not being
copied to the user's buffer when the response packets
were received.
V1.0.31 1- Problem connecting to SNA gateways via DOS 3270 terminal
emulator and RUMBA.
2- Problem getting license across DECnet areas with WFW
and Windows 95 clients, an Illegal Login Attempt was
logged by the client (use $ ACCOUNTING /ADDRESS command
to see error). DECnet destination object name for the
license server was being padded with spaces, the OpenVMS
server saw this as an object it did not have.
DECLICL.VXD
DECLICLD.VXD
============
V1.0A.042 1- Update protected mode license bits, see PWLICLM.EXE for
list of fixes.
DECND30.VXD
DECND30D.VXD
============
V1.0.11 1- Certain SMC Ethernet cards receive packets that were
not destined to the address identified in the "destination
address" portion of the packet. The hardware is supposed
to filter out these packets, but under extreme load it
does not. The protocol that receives these packets may
interpret the data as if it was intended for the local
node and send out "reject" packets to the originator,
which interferes with the operation of other nodes on
the network.
DECTNET.DLL
===========
0.1.003 1- Digital UNIX was unable to get Terminal ID from VT320,
reported terminal type unknown. Now identifies Terminal
ID as VT100.
DLLASYNC.EXE
============
V6.0.71 1- Connectivity problem with some PPP implementations (ie.
Netblazer from Telebit). PPP frames were being discarded.
DLLCAPI.EXE
===========
V6.0.9 1- Small PPP packets were corrupted on Eicon's Diva Cards.
V6.0.8 1- With AVM ISDN card, X.25 connections over ISDN can not be
closed because of incompatibility problem between
PATHWORKS DLLCAPI driver and AVM's CAPI driver. The
drivers fail to shut down the line.
DLLNDIS.EXE
DLLNDIST.EXE
============
V6.0.002 1- The PC client intermittently did not put source routing
information into packets that it sends.
V6.0.001 1- DOS PC using TCP/IP on Token Ring, looses the network
drive when copying to the network drive.
DLLODI.EXE
==========
V6.0.001 1- Using an ODI driver and loading LAST.EXE into EMS will
hang the PC.
DNP.EXE
DNPD.EXE
========
V6.0.217 1- Slow data transfer via DECnet/OSI from client to server.
FTPW.EXE
========
V6.0.006 1- FTPW puts a dot "." as a character in a local filename
that has no extension. This causes problems when
transferring to a UNIX system.
INSTLICL.DLL
INSTLICL.EXE
INSTLICD.DLL
============
V6.0.041 1- Update protected mode license bits, see PWLICLM.EXE for
list of fixes.
LAD.DRV
=======
V6.0.0.39 1- When a user attempts to connect to a Virtual Disk Service
on a PATHWORKS 4.x server that requires a Password, a
"General Network Error WINNET-2" is returned by the
PATHWORKS Network Connect Utility. This task functions
correctly if a Password is not required.
LMFS.DLL
LMPQ.DLL
LMUG.DLL
LMUR.DLL
========
2.2.01 1- Unable to administer permissions for users on file shares
pointing to subdirectories, with very long path.
LMUG.DLL
========
V2.2.01 1- No MEMBERS display under the GROUP entry in any language
version (ex. German) of ManageWORKS.
NCPSHOW.EXE
===========
V6.0.07 1- Async DECnet, the NCP Password was not encrypted.
NFT.EXE
=======
V6.0.002 1- NFT was not converting character sets when /ASCII
qualifier was used.
NFTW.EXE
========
V6.0.011 1- Cannot connect to PDP-11 running RSTS or to a Macintosh.
The error Invalid Filename appears when doing multiple
file transfers or deletes.
V6.0.008 1- NFTW could not connect to RSTS system.
NFTW.EXE (Portuguese Only Version)
==================================
V6.0.007 1- Portuguese version of NFTW.EXE GPF's when copying file
to local pc or server. This version located in the
directory \LANGUAGE\BR\PCAPP.
PATHWRKS.DRV
============
V6.0.0.47 1- WNetAddConnection() does not function properly to a
password protected share/service.
V6.0.0.46 1- Error occurs when the same network drive was last opened
in a previous file manager session. The error displayed
is "the device is being accessed by an active process".
2- In a configuration of WFWG/3.11 and PWRKS/6.0, when
Windows is started, it reports that "PWBKGND caused a
GPF in module PATHWRKS.DRV at 0017:0167".
3- When an NT Server performs a soft disconnect of a
file/print share, the file/print share is displayed
as a PW4.x connection when it was initially a Lanman
connection. This causes a "Network Error" status
message to be displayed by the print manager.
PWBKGND.EXE
===========
V6.0.0.3 1- Fix the following GPF when Windows starts up and
Directory Services (IDS) uses AutoConnects to
connect to shares.
PWBKGND.EXE in USER.EXE at 0001:8093
PWCM.EXE
========
V6.0.51 1- The Connection Manager did not take the time putting
parameters into account with ip/ppp/isdn templated.
PWCONFIG.DLL
============
V6.0.002 1- Modifying DEFAULT PROTOCOL in WFWG deletes DECPW.386
entry from SYSTEM.INI file.
PWLICLM.EXE
PWLICNW.EXE
PWLICLMT.EXE
PWLICNWT.EXE
============
V6.0.042 1- If a License PAK Property Value beyond PAK1 is defined,
the PAK names requested are shifted one character to
the left, and a hyphen is inserted after the third
character. For example, if the second PAK requested is
defined as DEC-PWLMDOSCC06.00, the error is "unable to
obtain license EC--PWLMDOSCC06.00".
V6.0.041 1- Failure in "look-ahead". Clients were not accepting
higher-version licenses provided by license servers.
For example, a client asking for a V5.1 CCS license
should accept a V6.0 CCS license license. This "look-
ahead" happens when the License Server is out of the
requested license but has a higher version license of
the same type.
V6.0.040 1- When a PATHWORKS V5.1 Client requested license validation
from a PATHWORKS for Digital UNIX/PATHWORKS for OSF
Server, PWLSADMIN could not read the PWLICLM.DAT file.
V6.0.039 1- "Persistent" connections (Windows 95 file services that
are to be re-connected on network login) would not work
on a dial-in network if the server required a client-based
license. The fix is to check for new network transports
every time a system broadcast message is sent. This
allows the Client License Transponder to react earlier
and prepare to answer license queries before the automatic
connections occur.
V6.0.038 1- Sync 5.1 and 6.0 version numbers.
V6.0.AN 1- If posting an NCB caused an immediate error, the error
was ignored. Since the NCB never goes to the PENDING
state the callback routine never gets called and the
state-machine stalls.
V6.0.AM 1- License Registrar can not get to License Transponder over
Dial-Up TCP/IP.
V6.0.AL 1- PAK names are truncated before the version.
2- PATHWORKS V6 over WFW the LICENSEGROUP and LICENSESERVER
values in the PATHWORKS Template were not used.
V6.0.AK 1- Extensive License allocation checks are added to this
version. Initial License connection may appear slow. Once
a license has been obtained, this delay should decrease.
2- Previous versions had problems with V5.1 Remote Boot when
looking for PWTPL environment variable, which is not used.
3- Microsoft RAS uses "DEST\0\0" as the permanent NetBIOS
Node Name for every client. We pick this up and use it
as a Client-ID on the expectation that it is unique on
the network. License Servers get confused when multiple
nodes use the same ID.
4- Using the /FILE switch to point to a license file requires
the license name, if entered as "PWxxxxxxxnn.nn" without
the "DEC" prefix it would fail. Change display and assume
"DEC" for any string starting with "PW".
V6.0.AJ 1- Could not get a V6.0 license when no V5.1 licenses were
available.
V6.0.AI 1- A problem with sending the "computer name" field to the
License Server as blank-padded to 16 characters. The result
is random names appearing after the real name in the
management display of the machine which owns that license.
V6.0.AH 1- Add code to allow "\n" characters in messages to fix
the problem with the help display (/? or /HELP).
V6.0.AB 1- The NetBIOS "Adapter Status" function (code 0x33) was
never implemented on PATHWORKS Async transports.
PWSETUP.EXE
PWSETUPX.EXE
============
V6.0.093 1- When a mandatory update occurs with a Workstation running
both NetWare and LANMAN, and the NWSERVICE macro is not
set, PWSETUP will pause even though all the information
is valid.
2- When a change is made to a template in ManageWORKS, and
the PC boots then runs UPDATE.EXE this error message was
displayed "bad command or file name".
PWWSETUP.HLP
============
V6.0a 1- Two items in the TCP/IP information section of the
help file were incorrect. These two items affected
the dialog box help for PATHWORKS Setup. The server
name should have been a NetBIOS name, rather than the
complete TCP/IP address. Server name has been changed
from "gateway.compsci.umars.edu" to "gateway". The domain
name in the dialog box help was also changed from
"pcmine.compsci.umars.edu" to "compsci.umars.edu"
QTUPDT.EXE
==========
V6.0.005 1- When configuring an X.32 connection with the X.32 ID
(Transpac) the connection was not started.
V6.0.004 1- For a X.32 template, the X.25 facilities set for the
DECnet or TCP/IP circuit with PWSETUP are not well
reflected in the PATHWORKS database.
RFA_DAP.DLL
===========
V6.0.005 1- Unable to transfer files containing Fortran Carriage
Controls.
2- GPF occurred when transferring large fixed length records
(4096 or greater).
V6.0.004 1- Incorrect ASCII file transfer - too many or too few
bytes on file transfer.
V6.0.003 1- NFT Windows pads file with carriage returns.
2- NFT Windows copy of VMS file with the record format
of Stream_LF leaves DOS file with extra LF.
RPLMGR.EXE
==========
V6.0.015 1- Remote boot manager was not correctly updating the
target server.
SETHOST.EXE
===========
V6.0.011 1- Running SETHOST.EXE then pressing three times the
function key "F3" will cause a COMPAQ PC to reboot.
SLOGIN.EXE
==========
V6.0.007 1- Slogin, password expiration message was not being
displayed for logon to netware v4.xx.
V6.0.006 1- Configuration: PATHWORKS NetWare #1 template, VLM's
loaded and logged in to a V4.x NetWare server. If the
user's password had expired and a grace login is in
effect, the user was never prompted with the
opportunity to change their NetWare password. The
password would then expire with no grace logins left.
SVNVIEW.DLL
===========
V2.2.020 1- When selecting "Display Object Status Colors" in the
hierarchical viewer's configuration dialog, all
displayed Workstation Manager objects will change to
"unknown object". Unselecting the check-box restores
the proper display.
TCPIP.EXE
TCPIPD.EXE
=========
V6.0.038 1- Smalltalk application reporting "winsock not running"
when attempting some send operations.
V6.0.034 1- Reported delays when an ICMP redirect was received on
Token Ring connection.
2- Fix for NetBIOS naming. When receiving a naming query
on destination port 137 (NETBIOS naming port) with source
port as XXX we replied to 137 (Standard NETBIOS naming
port) instead of responding to XXX.
V6.0.032 1- Includes support for Dynamic DNS configuration.
V6.0.031 1- RSH fails when connecting to UCX v3.3.
V6.0.030 1- When an application did a shutdown call with RCV disabled
we were dropping even ACK's for data which we were sending.
TN.EXE
======
V6.0.001 1- If the printer port is re-routed to the COM port and
DOS PRINTSCREEN is used while SETHOST is running a
TELNET connection, the system will hang.
VT320.EXE
=========
V6.0.010 1- After remapping the F10 key and pressing it, the first
key typed from the numeric keypad was lost.
V6.0.009 1- Printer Controller mode doesn't work while executing a
script using the TYPE UNTIL: command.
V6.0.008 1- Version 6.x of VT320 repaints the screen more slowly than
version 5.x under Windows95.
V6.0.005 1- VT320 keyboard remapping can not distinguish between the
Carriage Return key and Keypad Enter.
V6.0.004 1- Redefining the keypad ENTER key to be a carriage return
caused two carriage returns to be sent to the host.
VT320**.DLL
===========
V6.0.001 1- Add international strings and dialog boxes to VT320.
WINRCV.EXE
==========
6.0.0.9 1- BCAST.EXE did not work over DECnet to WINRCV with
PW/OSF.
WINSOCK.DLL
WINSOCKD.DLL
============
V6.0.62 1- Error messages occurred upon executing Comshare's
Execu-View application.
V6.0.61 1- MS/SQL server connection fails with ODBC error when
trying to access database table.
V6.0.60 1- Changed the order of the version check in WSAStartup(),
DECnet 32-bit application will be the first checked
against, followed by the regular version check conforming
to the WinSock Spec 1.1.
WSM.DLL
=======
1.20.087 1- Cannot access Workstation Management Database with any
language variant version of ManageWORKS (v2.2.005).
INSTALLATION NOTES:
This patch kit contains PC based files in a self-extracting format.
Follow the procedure below for using these files:
1. Create a directory on your PC for the expansion of this kit. The
kit when expanded will NOT fit on a floppy.
C:\MKDIR C:\TMP
2. If you received this patch as PW60_1.EXE, PW60_2.EXE, and
PW60_3.EXE copy these files to the C:\TMP directory and go on to
step 3.
If the file is PW60ECO2.EXE, expand this file by typing the name
at the DOS prompt followed by the directory just created. The
result will be three files (PW60_1.EXE, PW60_2.EXE, and
PW60_3.EXE) placed in the C:\TMP directory.
C:\PW60ECO2.EXE C:\TMP
3. For each file, type the file name followed by the "-d" option
switch (THE "-d" MUST BE LOWER CASE). This switch preserves the
directory structure of the archive file.
C:\TMP>PW60_1.EXE -d
C:\TMP>PW60_2.EXE -d
C:\TMP>PW60_3.EXE -d
4. Follow directions in AAREADME.TXT located in PW60_1.EXE to install
these updates to the PWV60 System File Share and the V6.0 Client.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
pw60eco2.README
pw60eco2.CHKSUM
pw60eco2.CVRLET_TXT
pw60eco2.exe
|
