PW-DOS PW51ECO8 PATHWORKS for DOS and Windows V5.1 ECO Summary
Copyright (c) Digital Equipment Corporation 1994, 1996. All rights reserved.
**************************** IMPORTANT *****************************
* AS OF SEPTEMBER 15, 1996, PATHWORKS V5.1 IS NO LONGER SUPPORTED. *
* THIS IS THE LAST ECO KIT FOR VERSION 5.1. *
********************************************************************
PRODUCT: PATHWORKS for DOS and Windows, Version 5.1
OP/SYS: MS-DOS, Versions 5.0 through 6.22
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: PW51ECO8
ECO Kits Superseded by This ECO Kit: PWV51E07
PWV51E06
PWV51E05
PWV51E04
PWV51E03
PWV51E02
PWV51E01
ECO Kit Approximate Size: 7632 Blocks
3907441 Bytes
ECO KIT SUMMARY:
An ECO kit exists for PATHWORKS for DOS and Windows V5.1 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.
CTERM.EXE
=========
V6.0.26 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 five characters is generated. But PW CTERM
never sends the sequence back to the host.
V6.0.24 1- Fixed problem accessing CTERM functions by issuing
interrupts through INT 69H. Messages were going to
a wrong session when more than 6 sessions are opened
simultaneously.
V5.2.22 1- When using VMS Phone Utility with SETHOST CTERM, the
ring message was not displayed at the beginning of the
left margin. It appeared at the 80th column.
V5.2.01 1- In a SETHOST or VT320 CTERM session with SCO UNIX, it is
not possible to get German umlaut in multinational mode.
*NOTE* When having this problem, use /8BIT switch to
start CTERM.EXE (ex. C:\>CTERM /8BIT).
CUSTCNTL.DLL
LMFS.DLL
LMPQ.DLL
LMPS.DLL
LMSRV.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.
V1.0.1 1- In ManageWORKS V5.1, when changing permissions on a
print share, revoking permission for any user or group
removes the top entry in the list rather than the one
highlighted.
*NOTE* Refer to the "Specific Component Instructions
Section" of the AAREADME.TXT for more information.
DECCORE.VXD
DECLICL.IC
DECLICL.VXD
DECLICLD.VXD
INSTLICD.DLL
INSTLICL.DLL
INSTLICL.EXE
PWEL.EXE
PWLOG.EXE
PWLOG.HLP
PWMSG.HLP
============
N/A 1- Add Protected Mode License bits to kit.
DBGLICLM.EXE
DBGLICNW.EXE
============
DBG5.1.042 1- Add Debug License components to kit.
DECPW.386
=========
V5.2.00 1- The new DNR command 'gethostbyaddr' does not work with
V5.1, this version enables DNR GETHOSTBYADDR.
*NOTE* This component requires installation of DNR.EXE
V5.1.03 and WINSOCK.DLL V5.2.050 or later from
this kit.
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.000 1- Correct some remote boot hang problems.
V5.1.060 1- Previous version of DLLNDIS caused the PC to reboot
when using PKUNZIP.
V5.1.059 1- With 3C509 Ethernet adapters using NDIS drivers, the
system hangs if a DECBridge sends an 802.2 frame.
V5.1.057 1- With SMC and HP Ethernet adapters using NDIS drivers,
if broadcast is enabled, multicast fails.
DLLODI.EXE
==========
V6.0.001 1- Using ODI driver and loading LAST.EXE into EMS will
hang the PC.
V5.1.002 1- Problem copying files from NetWare drive to local drive
using ODI driver for 3C509 card with EMS.
DNP.EXE
DNPD.EXE
========
V6.0.217 1- Slow data transfer via DECnet/OSI from client to server.
V6.0.216 1- Fixed problem in a congestion situation. If a
CONNECT-CONFIRM message or the responding link service
message is lost (due to various reasons), the stack does
not recover.
V5.2.213 1- Fixed problem of releasing idle links when using
TeamLinks with DECnet as the underlying transport.
V5.2.211 1- Slow performance when copying files or running
some applications. Especially noticeable in Windows.
V5.2.210 1- Problem with having two Datalinks and wanting to run
TCP/IP over Ethernet and DECnet over ASYNC line.
T5.2.208 1- Performance problems with DNP in version 5.1 when using
NetBIOS applications.
T5.2.206 1- Running Attachmate EXTRA! for Windows and connecting
to an IBM host could cause a problem when trying to
re-establish a connection.
T5.2.202 1- When running Attachmate EXTRA! for Windows, trying
to exit Windows would display "the application is
still communicating on the network". Windows could
not restore the state of the network.
V5.1.196 1- A small timing window that can cause one PC to hang
when starting up a DNP session with another PC.
DNR.EXE
=======
V6.0.02 1- DNR.EXE is appending the domain information to non-local
host names, thus causing a long delay in connection.
V5.1.03 1- Nameserver failover did not work.
DWDOS.STR
DWDOS.VID
DWDOS.RGB
DWDOS286.EXE
DWDOS386.EXE
DWDOS387.EXE
DWLOGO.EXE
============
V5.1.ae 1- Screen corruption and DWDOS crashes when time passes
midnight on PC's using an S3 video driver.
V5.1.ad 1- Application hang (debugger revealed a General Protection
Fault) when passing a particular symbol.
2- Screen corruption and DWDOS crashes when time passes
midnight on PC's using a VESA video driver.
V5.1.ac 1- Files containing abs() calls changed to macros.
V5.1.ab 1- Long pauses of 20 seconds were observed with one or
more connections being dropped.
V5.1.aa 1- Diagonal lines "bending" to the vertical when an
application window is scrolled and the lines go
partially off the screen (clipping situation).
FAL.EXE
FALW.EXE
FALW.HLP
========
V5.2.002 1- From VMS, a DIR/SIZE of a PC running FAL would show zero
blocks of a 512 byte file. All multiples of 512 were
short a block with a DIR/SIZE.
V5.2.001 1- A temporary file was not being created when the COPY
process was invoked from VMS to the PC. When there was
a disconnection, the original file was only partially
copied.
FTP.DLL
-------
V6.0.000 1- Character conversion doesn't work when copying files from
VMS FTP server to PC client with FTPW.EXE.
FTP.EXE
=======
6.0.001 1- Client command FTP MGET required ".xxx" extension on
filenames.
FTPW.EXE
========
V6.0.006 1- FTPW puts a dot "." as a character in a local filename
that has no extention. This causes problems when
transferring to UNIX systems.
V5.1.004 1- FTPW unable to connect to the FTP server from The
Wollongong Group, Inc.
2- FTPW unable to connect to NeXT Step's FTP server.
*NOTE* This component requires installation of FTP.DLL
V5.1.004 or later from this kit.
INETNAME.EXE
============
V6.0.001 1- The 15th bit in the NetBIOS name table changes to \20.
During "INETNAME /L" command, NetBIOS names are read
from the NBHOSTS file and loaded into the NetBIOS name
table. If one of those names contains a space or '\20',
then the remaining characters (up to 16 characters) in
the name are ignored and are replaced with '\20'.
V5.1.002 1- INETNAME V5.1.002 introduced a problem where it no longer
read the NBHOSTS file. TCPIP.EXE shipped with this kit
now reads the NBHOSTS file automatically.
KEYBUILD.EXE
============
V3.30 1- Utility to rebuild key files if they are corrupted.
*NOTE* Refer to the "Specific Component Instructions
Section" of the AAREADME.TXT for more information.
LAD.DRV
========
V5.1.038 1- When a user attempts to connect to a VIRTUAL DISK SERVICE
on a PATHWORKS V4.2 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.
LAT.EXE
=======
V5.2.004 1- OSF/1 drops connection or exits application.
V5.1.002 1- LAT used 2 SCB table entries each time a session started
and only returned 1 when finished.
LDU.EXE
=======
V5.2.000 1- Can not change UAF password on VMS 5.0 server.
MAIL.EXE
MAILMSGS.EXE
============
V5.1.009 1- Node "CC::" was interpreted as "CC:"-- carbon copy
designator--in SEND operation.
V5.1.008 1- For certain addresses, the TO: field gets prematurely
truncated during REPLY or ANNOTATE.
V5.1.007 1- Implemented MAILSETU Startup Command file processing.
V5.1.006 1- REPLY to Internet mail from ULTRIX system using FROM
address rather than RETURN-PATH.
MOP.EXE
=======
V5.1.001 1- MOP Load/Dump Server could not load the new DECnis image.
NCPSHOW.EXE
===========
V6.0.07 1- Async DECnet NCP Password was not encrypted.
NETWKSTA.330
NETWKSTA.400
NETWKSTA.500
============
V2.2c+patches 1- The workstation would hang after 15 minutes of activity,
(such as copying files between a server and a workstation
or running Attachmate HLAPI code that polls the server).
2- MS-DOS enhanced workstations would run out of netbufs and
hang.
3- File seeks failed if there was an error flushing a buffer
when the seek was initiated.
4- An application produced occasional NET808 and NET805
errors during command processing.
5- The system would hang or reboot when trying to access a
file in a Windows application on a disconnected drive
when Windows was being run over the net, usually in a
Token Ring environment.
6- The command NET LOGOFF /Y returned the error NET2402 if
files were open on a connection. Subsequent attempts
returned the same error.
7- NETWKSTA required the use of SETVER to run with
MS-DOS 6.0. Code was changed, NETWKSTA now allows
MS-DOS 6.0 without SETVER in CONFIG.SYS file.
8- During SQL queries under RAS the machine would
occasionally lock-up, reboot, or report EMM Exception #06.
9- The DOSPeekNmPipe API returned an incorrect count for the
number of bytes in its buffer.
10- Pulling up print dialog boxes or exiting applications
caused Windows to hang or crash to an MS-DOS prompt.
This happens on Windows 3.1 PC's with very low memory
and running many applications off of a server.
11- DCA Microsoft Communication Server (Comm Server) MS-DOS
Client computer stops responding (hangs) when the Comm
Server service is removed from the network. The error
occurs when exiting the Comm Server MS-DOS Client 3270
emulator by pressing .
12- Using a Microsoft Lan Manager enhanced workstation loaded
into EMS may cause an MS-DOS critical error under Windows
3.1. This problem, which is intermittent and may occur
during workstation stress, is specific to the enhanced
redirector loaded into EMS running under Windows.
If you abort when a critical error is reported during a
large-file copy under Windows, the machine hangs if the
workstation service is loaded in EMS. If the machine
doesn't hang immediately, a network error occurs. Upon
disconnection, the system can retry successfully.
13- When a remoteboot workstation is starting the redirector
or when it is actively accessing the FIT translated RPL
volume (drive C:), and a multicast packet is received,
the system sometimes stops responding (hangs).
14- The Microsoft Lan Manager client workstation redirector
(NETWKSTA.EXE) can be loaded in the upper memory area
under MS-DOS 5.0 and 6.0, but not with version 6.2.
15- An application can fail because DosReadMailslot sometimes
returns a message that was not addressed to it. Generally
this occurs when mailslot traffic is heavy.
NFT.EXE
=======
V6.0.002 1- NFT was not converting character sets when NFT/ASCII
qualifier was used.
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 is located in the
directory \LANGUAGE\BR\PCAPP.
NFTW.EXE
========
V6.0.011 1- Can not 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.
V5.2.002 1- NFTW COPY with character conversion from VMS to PC would
not work to devices other than the drive where NFTW.EXE
resides.
*NOTE* The V5.1 NFTW.HLP file will not always correspond
correctly to this version of NFTW.EXE. This will
be fixed in V6.0 of PATHWORKS.
V5.1.001 1- Corrected multiple selection for COPY and DELETE.
2- Modify "Confirm" dialog to be optional after the first
file COPY or DELETE.
PATHWRKS.DRV
============
V5.1.0.10 1- The error "the device is being accessed by an active
process" was displayed when disconnecting a network
drive within File Manager when the same network drive
was last opened in a previous File Manager session.
2- 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.
PWLICLM.EXE
PWLICLMT.EXE
PWLICNW.EXE
PWLICNWT.EXE
============
V5.1.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".
V5.1.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.
V5.1.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.
V5.1.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.
V5.1.038 1- Sync 5.1 and 6.0 version numbers.
2- Correct some RAS license problems.
V5.1.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.
V5.1.AM 1- License Registrar can not get to License Transponder over
Dial-Up TCP/IP.
V5.1.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.
V5.1.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".
V5.1.AJ 1- Could not get a V6.0 license when no V5.1 licenses were
available.
V5.1.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.
V5.1.AH 1- Add code to allow "\n" characters in messages to fix
the problem with the help display (/? or /HELP).
V5.1.AB 1- The NetBIOS "Adapter Status" function (code 0x33) was
never implemented on PATHWORKS Async transports.
PWMGMT.EXE
V2.0.020
SVNVIEW.DLL
V2.0.010
===========
1- Menu processing can cause ManageWORKS to become confused.
2- Problem found in ordering of Displayed Components in
Options/Displayed components dialog.
3- Problems performing default action on double-click.
4- Problem printing a viewer to a printer (as opposed to
a file) would cause a General Protection Fault (GPF)
with more than one object selected.
QTUPDT.EXE
==========
V5.1.010 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- NFTW pads file with carriage returns.
2- NFTW COPY of VMS file with the record format of
Stream_LF leaves DOS file with extra line feeds.
V6.0.000 1- It was not possible to copy files from VAXELN to the
PC with NFT Windows; an unpredictable error occurred.
2- NFT DOS does not produce the same result as NFT Windows
when copying a file (with default values/switches) to
the PC. NFT Windows adds line feeds or blank lines to
the beginning of the file.
SETHOST.EXE
===========
V6.0.11 1- Running SETHOST.EXE then pressing three times the function
key "F3" would cause a COMPAQ PC to reboot.
V6.0.10 1- SETHOST did not work with NVT.EXE.
V5.1.ab 1- Correct Local Echo problem.
2- Specified modem speed of 38.4K doesn't work in script
file. Specify larger capacity variable type for speed
storage.
V5.1.aa 1- Restore the Network Protocol for each of the 4 sessions
defined and saved in SETHOST.DAT. Do not default to NET.
2- Restore previous cursor position on return to SETHOST
from MS-DOS.
SPAWNER
=======
V5.0.004 1- When an invalid object name or number was used, the
previous task was sent to spawner.
TCPIP.EXE
TCPIPD.EXE
==========
V6.0.038 1- Smalltalk Appliation reporting "winsock not running"
when attempting some send operations.
V6.0.034 1- Fix 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.
V6.0.029 1- The tcp_Send_reset fix corrected during the course of
investigating an RPL licensing problem.
V6.0.028 1- Add mib_clr_arptr suggested by Mobile group.
V6.0.027 1- Persistent timer fix.
V6.0.026 1- DefaultGw0=NULL fix. When no Gateway (GW) is specified
a message would appear which is now turned off.
V6.0.025 1- TNCP Set Line State Off had problems of hanging.
2- Change was made to avoid data corruption.
V6.0.024 1- An EXEC concept was introduced in TCPIP and the EXEC state
was always set to "ON". So now there are two variables,
INET_LSTATE represents the line state and INET_STATE
represents the EXEC state, which is always running. This
allows the NETBIOS dispatcher to allow all commands, even
if line state if "OFF".
2- When changing the IP address with TNCP SET IPADDRESS,
PING worked but USE command failed.
V6.0.023 1- Version numbers changed from 5.2.x to 6.0.x.
2- TNCP SET LINE STATE OFF would hang the system.
V5.2.021 1- Problem with RSH not displaying the output on the screen.
V5.2.020 1- Fixed memory initialization problem.
2- STACK segments have been reordered.
3- RSH problem when used with Mosaic.
4- TCPIP/U fixed.
V5.2.019 1- The PC momentarily hangs when accessing remote server.
2- Performance problems with TCP/IP in version 5.1 when using
NetBIOS applications.
V5.2.010 1- Fixed the NetBIOS problem where stack does not check
for MS name table when sending a datagram to server.
V5.2.009 1- Fixed the delay symptom found when VT320 is used through
TELNET.
V5.2.005 1- Missing GIF images when running Mosaic.
V5.1.016 1- When a system is booted with RPL remote boot having TCP/IP
as one of the transports, TCP/IP does not bother to look
for the environment variable nor read PWTCP.INI.
2- When Mosaic is used, occasionally there are TCP links
that stay in state 10 forever.
3- TCP/IP stack used incorrect node address to establish
connection to the queried node.
4- Non-blocking I/O socket's swrite() represents latency
problem.
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.
V5.2.003 1- Telnet not sending/receiving binary data (0xFF in
particular) correctly.
*NOTE* This version of TN.EXE requires TRMNLAXS.DLL
V5.02.002 or later provided in this patch kit.
V5.1.004 1- Telnet problems working with TransPATH 350. SETHOST.EXE
V5.1.ab from this patch kit also updated to correct this
problem.
TNCP.EXE
TNCPHELP.BIN
============
V5.2.001 1- Add line speed support of 38400.
TRMNLAXS.DLL
============
V5.02.002 1- GPF errors with TRMNLAXS.DLL. On some configurations,
launch VT320 with no *.INI file, select Communications,
select Net, and you get a GPF in TRMNLAXS.DLL.
V5.01.003 1- MODE commands to the comm port fail after VT320 is used
and possibly other symptoms related to interrupt 14 and
comm ports.
VT320.EXE
=========
V5.1.022 1- After remapping the F10 key and pressing it, the first
key typed from the numeric keypad was lost.
V5.1.021 1- Printer Controller mode does not work while executing a
script using the TYPE UNTIL: command.
V5.1.020 1- VT320 keyboard remapping can't distinguish between the
Carriage Return key and Keypad Enter.
V5.1.019 1- Redefining the keypad ENTER key to be a carriage return
caused 2 carriage returns to be sent to the host.
V5.1.018 1- Running VMS spreadsheet application 2020 in 132 mode
corrupts the screen.
V5.1.016 1- When using VT320 with COMPAQ printer drivers, VT320
changes to a different character set.
V5.1.015 1- Printing from ALL-IN-1 to an HP LaserJet printer results
in garbage data being sent to printer.
2- ALL-IN-1 word processing does not repaint the screen
correctly when you have underlined blank spaces.
V5.1.014 1- When using VT320 with CTERM, the VT320 process cannot
be terminated when VT320 has been made an icon. VT320
stops I/O processing when it's an icon. This does not
affect LAT or TELNET, just CTERM.
*NOTE* Refer to the "Specific Component Instructions
Section" of the AAREADME.TXT for more information.
V5.1.013 1- In certain cases, an extra blank page was being sent to
the printer at the end of a print job.
V5.1.012 1- Running applications using FMS forms caused VT320 to
enter an erratic state that eventually ends up in a GP
fault. If the invalid data was accessed, it eventually
caused the emulator to fault.
V5.1.011 1- Print Controller mode would not output data to a file or
printer.
V5.1.010 1- DTR and RTS were not being dropped when disconnecting a
modem.
V5.1.009 1- Problems with VT320 printing (mostly w/ HP LaserJet 4):
- Correct problem with HP LaserJet 4 fonts. VT320 now
uses default fonts for the HP LaserJet 4 in auto print
mode, printer controller mode and printscreen.
- The last page of a document would not eject from the
printer (again mostly HP LaserJet 4).
- The escape sequence to enter printer controller mode,
5i, would turn controller mode off if it was
already "ON". Now this sequence is ignored if printer
controller mode is "ON" (all printers).
2- Answerback string not sent when received with
Keyboard Action Mode set. Now sends answerback string even
when keyboard is locked.
3- Script log file opened in REPLACE mode instead of APPEND
mode. Script log files now opened with APPEND so new data
is added to end.
4- Keymap files not loaded when LOAD: script command executed.
Add Keymap_Init() call to LOAD script command.
5- Eject page when encountered when in Autoprint Mode.
6- CANCELing out of Print Mode dialog box does not reset
settings.
WINRCV.EXE
==========
V5.0.0.8 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.
V6.0.59 1- cc:Mail fails to work in Mobile mode with PATHWORKS
Winsock. Also, a fix is required from Lotus for
CCBKGRND.EXE to solve this problem.
2- Beta of Microsoft Exchange GPFaults at Winsock bind().
V5.2.053 1- Disabled sending of FD_CLOSE on a listening socket.
V5.2.051 1- Fixes a problem with some invalid returns when using
non-blocking I/O.
V5.2.050 1- Increased the number of blocking hooks to 64.
WSM_WP.DLL
==========
no version 1- All efforts to change the password of a Workstation
Manager Database failed without error or warning. That
is, it appeared that the password was changed, when in
fact it was not changed.
INSTALLATION NOTES:
This ECO 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 PW51_1.EXE, PW51_2.EXE, and
PW51_3.EXE, copy these files to the C:\TMP directory and go on to
step 3.
If the file is PW51ECO8.EXE, expand this file by typing the name
at the DOS prompt followed by the directory just created. The
result will be three files (PW51_1.EXE, PW51_2.EXE, and
PW51_3.EXE) placed in the C:\TMP directory.
A:\PW51ECO8.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>PW51_1.EXE -d
C:\TMP>PW51_2.EXE -d
C:\TMP>PW51_3.EXE -d
4. Follow directions in AAREADME.TXT located in PW51_1.EXE to install
these updates to the PWV51 System File Share and the V5.1 Client.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
pw51eco8.README
pw51eco8.CHKSUM
pw51eco8.CVRLET_TXT
pw51eco8.exe
|
