[PW-DOS]V5 PWV51E04 PATHWORKS V5.1 for DOS and Windows AAREADME.TXT Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Digital Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: PATHWORKS [TM] for DOS and Windows [TM], Version 5.1 ECO 4 OP/SYS: MS-DOS [R], Version 3.3, 4.0, 5.0, 6.0 SOURCE: Digital Equipment Corporation INFORMATION: This kit supersedes ECO kit PWV51E03. Included here is the AAREADME.TXT file for the ECO 04 update of PATHWORKS V5.1 for DOS and Windows. The update is available as an ECO (patch) kit. An evaluation of how these symptoms may affect your site should be done before applying this kit to your system. The ECO kit details may be found in the following article in the "ECO-SUMMARY" database: *PW-DOS] PWV51E04 PATHWORKS for DOS and Windows V5.1 ECO Summary ECO KIT ORDERING INSTRUCTIONS: If you are not familiar with how to request kits electronically, please open the DIA or DSNLINK database and review the article entitled: [AES] How To Electronically Request ECO (Patch) Kits Using Service Tools This kit may be ordered using the 'Invoke' function while reading the ECO Summary article. AAREADME.TXT =============================================================================== DIGITAL PATHWORKS for DOS and Windows V5.1 Client Patch Kit Page 1 =============================================================================== This patch has been provided by PATHWORKS Engineering in conjunction with the Digital Customer Support Center. DISCLAIMER This ECO has not been through an exhaustive field test process. Due to the experimental stage of this software ECO/workaround, Digital makes no representations regarding its use, or performance. The customer shall have the sole responsibility for adequate protection, including back-up data used in conjunction with the above software ECO/workaround. ==================================================================== Patch Information: PWV51E04.EXE (Self-extracting PKZIP file) Version Information: PATHWORKS V5.1 for DOS and Windows CompuServe (GO DECPCI): PW51_1.EXE, PW51_2.EXE, and PW51_3.EXE OP/SYS: MS-DOS =============================================================================== ** IMPORTANT ** Digital strongly recommends that the PATHWORKS V5.1 kit be installed before installing any components in this kit. V5.1 has been shipped directly to customers with (MDDS) service contracts. Some V6.x components are in this kit and will safely coexist with V5.1 components. ============== KIT CONTENTS ============== AAREADME.TXT (this file) contains the following sections: 1 Disk Contents 2 Pre-Installation Questions 3 Installation on the PWV51 System File Share 4 Installation on the V5.1 Client 5 Specific Component Instructions 6 File Revision History =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 2 =============================================================================== =============== DISK CONTENTS =============== # New addition to this kit. $ New addition to V5.1. * Changed since last version of this kit. ---------------------------------------------------------------------------- File Version File Size Directory Structure ---------------------------------------------------------------------------- $ CUSTCNTL.DLL 1.0.1 15920 \pcapp * CTERM.EXE 6.0.024 69519 \pcapp # DBGLICLM.EXE DBG5.1.AK 240464 \debug # DBGLICNW.EXE DBG5.1.AK 243908 \debug DECPW.386 5.2.00 15092 \windows\system * DLLNDIS.EXE 6.0.000 14755 \pw * " " " \lmdos\drivers\protocol\pathwrks * DLLNDIST.EXE 6.0.000 16586 \pw * " " " \lmdos\drivers\protocol\pathwrks DLLODI.EXE 5.1.002 20608 \netware * DNP.EXE 6.0.216 48372 \pcapp * DNPD.EXE 6.0.216 57802 \debug * DNR.EXE 6.0.02 37428 \pcapp DWDOS.RGB 5.1.ae 18021 \xserver DWDOS.STR 5.1.ae 122827 \xserver DWDOS.VID 5.1.ae 2642 \xserver DWDOS286.EXE 5.1.ae 761945 \xserver DWDOS386.EXE 5.1.ae 897821 \xserver DWDOS387.EXE 5.1.ae 1234607 \xserver DWLOGO.EXE 5.1.ae 10958 \xserver FAL.EXE 5.2.002 74109 \pcapp FALW.EXE 5.2.002 164864 \pcapp FALW.HLP N/A 23283 \pcapp * FTP.DLL 6.0.000 136576 \pcapp FTPW.EXE 5.1.004 175648 \pcapp * INETNAME.EXE 6.0.001 36021 \pcapp KEYBUILD.EXE 3.30 154484 \debug LAT.EXE 5.2.004 28876 \pcapp LDU.EXE 5.2.000 106895 \pcapp LMFS.DLL 1.0.1 84432 \pcapp LMPQ.DLL 1.0.1 71376 \pcapp LMPS.DLL 1.0.1 86224 \pcapp LMSRV.DLL 1.0.1 83856 \pcapp =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 3 =============================================================================== ====================== DISK CONTENTS cont'd ====================== # New addition to this kit. $ New addition to V5.1. * Changed since last version of this kit. ---------------------------------------------------------------------------- File Version File Size Directory Structure ---------------------------------------------------------------------------- MAIL.EXE 5.1.009 267795 \pcapp MAILMSGS.MSG 5.1.009 13796 \pcapp MOP.EXE 5.1.001 53395 \pcapp * NETWKSTA.330 2.2c+patches 109704 \lmdos\netwksta * NETWKSTA.400 2.2c+patches 110616 \lmdos\netwksta * NETWKSTA.500 2.2c+patches 110616 \lmdos\netwksta NFTW.EXE 5.2.002 92752 \pcapp # PWLICLM.EXE 5.1.AK 85071 \pcapp # PWLICLMT.EXE 5.1.AK 6607 \pcapp # PWLICNW.EXE 5.1.AK 81641 \netware # PWLICNWT.EXE 5.1.AK 4903 \netware PWMGMT.EXE 2.0.020 136736 \pcapp # RFA_DAP.DLL 6.0.000 57632 \pcapp SETHOST.EXE 5.1.ab 257807 \pcapp SPAWNER.EXE 5.0.004 39565 \pcapp SVNVIEW.DLL 2.0.010 106880 \pcapp * TCPIP.EXE 6.0.029 59100 \pcapp * TCPIPD.EXE 6.0.029 67938 \debug TN.EXE 5.2.003 52497 \pcapp TNCP.EXE 5.2.001 65175 \pcapp TNCPHELP.BIN N/A 14911 \pcapp TRMNLAXS.DLL 5.02.002 12288 \pcapp * VT320.EXE 5.1.018 232384 \pcapp * WINSOCK.DLL 6.0.59 61952 \pcapp # WINSOCKD.DLL 6.0.59 370584 \debug WSM_WP.DLL N/A 26208 \pcapp =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 4 =============================================================================== ============================ PRE-INSTALLATION QUESTIONS ============================ Does this patch kit replace the PATHWORKS for DOS and Windows Client V5.1? -------------------------------------------------------------------- No. This patch kit ONLY contains bug fixes for V5.1. Files in this patch kit will supersede those included in the PATHWORKS V5.1 for DOS and Windows Client and PWV51E02/3 (previous versions of this kit). What is the correct order of installation for V5.x Client and its updates? -------------------------------------------------------------------------- If you have installed... now upgrade with... V5.0 V5.1 then the updates from this kit. V5.0A V5.1 then the updates from this kit. V5.1 the updates from this kit. How can I get V5.1? ------------------- V5.1 may be purchased from an authorized Digital Distributor, or is provided as an update and shipped directly to customers with (MDDS) service contracts. Which components should be updated on my system? ------------------------------------------------ UPDATE ONLY THE COMPONENTS WITH WHICH YOU HAVE EXPERIENCED PROBLEMS. These components have been changed to fix specific problems and have not been through rigorous interactive testing. Which versions of the components should be used if I have multiple versions? ---------------------------------------------------------------------------- All patches, fixes, and updates are cumulative in the way version numbers are assigned. Unless otherwise stated, always use the component with the LATEST VERSION NUMBER. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 5 =============================================================================== ============================================= INSTALLATION ON THE PWV51 SYSTEM FILE SHARE ============================================= 1) Connect to the PATHWORKS for DOS and Windows System File Share (e.g. PWV51) with WRITE access privileges. Syntax may vary depending upon redirector being used. Please refer to V5 Client Installation Documentation for connection command syntax. 2) Backup the files to be replaced by renaming them with the file extension of "*.old". 3) Copy the needed files from this kit to the server. Files in this distribution are in the same directories as they should appear on the server. 4) Installation to the PWV51 System file service is now complete. 5) Proceed to the next section to update the clients. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 6 =============================================================================== ================================= INSTALLATION ON THE V5.1 CLIENT ================================= This task can be accomplished by updating Clients manually or by setting the Mandatory Update Flag in the Workstation Manager Utility (ManageWORKS). *NOTE* We recommended that this process be done on a test bed at your site before implementing patch updates on all Clients. - To update each Client manually there are two choices: 1) Run PWSETUP (from an updated v5.1 Share). -or- 2) Use the DOS COPY command to move the updated files to each Client. - To update multiple Clients by using ManageWORKS: 1) Go to the "PATHWORKS Windows Application" group within MS-Windows. 2) Highlight and expand the "ManageWORKS" icon. If the Browser is not present, click on "Viewer" and in the "Open Viewer" box choose "Browser". 3) Highlight and expand "Workstation Manager". 4) Highlight and expand "Workstation Databases". If entering for the first time you will be prompted for a password to the database. 5) Choose the Database desired. If no Databases are present, then a "Workstation Manager - Insert or Create Database" box will be displayed. Select "Insert" to bring up an existing Database, or select "Create" to build the Workstation Management Database for the first time. 6) Highlight the Group (i.e. ALL WORKSTATIONS). 7) From the ManageWORKS tool bar, select "Actions" then click on "Set Mandatory Update Flags". *NOTE* This procedure only updates the components in the Template used by the client at its next reboot, the Mandatory Update Flag is then cleared. If your Clients have multiple templates, the Mandatory Update Flag must be set on each Template. **************************************************************************** For more information, view these topics in ManageWORKS HELP: -Workstation Manager Help -Manage Workstations Groups -Set or Clear Mandatory Update Flags for a Workstation Group -Set or Clear Mandatory Update Flags for a Workstation -Set or Clear Mandatory Update Flags for a Template =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 7 =============================================================================== ================================= SPECIFIC COMPONENT INSTRUCTIONS ================================= This section contains information about new components or lists additional tasks necessary for updating certain components. COMPONENT INSTRUCTIONS ------------------------------------------------------------------------------ CUSTCNTL.DLL This is a new file to PATHWORKS V5.1. If a 5.1 client updated with this patch kit is using ManageWORKS to connect to a 5.1 Server, that Server must have CUSTCNTL.DLL installed. If not, a FILE ERROR CANNOT FIND CUSTCNTL.DLL may be seen when running ManageWORKS from this client. DBGLICLM.EXE Creates a License Debug logfile. Use only if requested to do DBGLICNW.EXE so by Digital Support. V5.1.AK Debug installation instructions: Edit the *.tpl file being used and change PWLICLM.EXE or PWLICNW.EXE with their Debug counterparts DBGLICLM.EXE or DBGLICNW.EXE. Copy these files from this patch kit or the \DEBUG directory (if installed), to your PC's \PW directory. Reboot the PC to create a log file. The output log file will be in the current directory with the corresponding name: DBGLICLM.EXE -> PWLICLM.LOG DBGLICNW.EXE -> PWLICNW.LOG DECPW.386 This component requires installation of DNR.EXE V5.1.03 and V5.2.00 WINSOCK.DLL V5.2.050 or later from this kit. KEYBUILD.EXE With V5.1, WMD (Workstation Management Database) uses V3.30 "key" instead of "set" commands to store one-to-many and many-to-many relations. KEYBUILD.EXE is a utility program to rebuild key files for WMD (Workstation Management Database). It is useful when: 1) DBCHECK reports errors in one or more WSMDB.K0x key files, 2) compact key file size. This program does not alter any data in database. *NOTE* No one should access the database when this program runs. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 8 =============================================================================== ======================================== SPECIFIC COMPONENT INSTRUCTIONS cont'd ======================================== COMPONENT INSTRUCTIONS ------------------------------------------------------------------------------ PWLICLM.EXE Extensive License allocation checks are added to this PWLICLMT.EXE version. Initial License connection may appear slow. PWLICNW.EXE Once a license has been obtained this delay should PWLICNWT.EXE decrease. V5.1.AK TN.EXE This version of TN.EXE requires TRMNLAXS.DLL V5.02.002 V5.2.002 or later provided in this kit. VT320.EXE To keep the VT320 processing data after it has become an icon, (from 5.1.014) save the VT320 settings in your current .INI file. This will add the entry PauseOnMinimize=1 to the [Misc] section of the configuration file. Using an editor, change the setting from 1 to 0. This will cause VT320 to continue I/O processing even after it has been made an icon. (from V5.1.009) A previous patch set the screen mode to its proper default of DARK. If you notice the foreground and background colors have switched with the latest VT320, use the Display Setup dialog box to change the Background from LIGHT to DARK. This will reset the colors and saving these settings will eliminate the problem. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 9 =============================================================================== ================== REVISION HISTORY ================== * NOTICE * When components listed in this section are grouped together as one fix, THESE COMPONENTS MUST BE UPDATE TOGETHER. ------------------------------------------------------------------------ CTERM.EXE ========= V6.0.024 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(NEW) LMFS.DLL LMPQ.DLL LMPS.DLL LMSRV.DLL ============ 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 this document for more information. DBGLICLM.EXE DBGLICNW.EXE ============ DBG5.1.AK 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. =============================================================================== PATHWORKS for DOS and Windows V5.0A Client Patch Kit page 10 =============================================================================== ========================= REVISION HISTORY cont'd ========================= DLLNDIS.EXE DLLNDIST.EXE ============ 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 ========== 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.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 noticable 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. =============================================================================== PATHWORKS for DOS and Windows V5.0A Client Patch Kit page 11 =============================================================================== ========================= REVISION HISTORY cont'd ========================= DNR.EXE ======= V6.0.002 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. DWDOS286.EXE DWDOS386.EXE DWDOS387.EXE DWDOS.STR DWDOS.VID DWDOS.RGB 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 12 =============================================================================== ========================= REVISION HISTORY cont'd ========================= FTP.DLL ------- V6.0.0 1- Character conversion doesn't work when copying files from VMS FTP server to PC client with FTPW.EXE. FTPW.EXE ======== 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 this document for more information. 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 13 =============================================================================== ========================= REVISION HISTORY cont'd ========================= 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. 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 14 =============================================================================== ========================= REVISION HISTORY cont'd ========================= NETWKSTA.330 NETWKSTA.400 NETWKSTA.500 cont'd =================== 2.2c+patches 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 hang 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. NFTW.EXE ======== 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 15 =============================================================================== ========================= REVISION HISTORY cont'd ========================= PWLICLM.EXE PWLICLMT.EXE PWLICNW.EXE PWLICNWT.EXE ============ V5.1.AK 1- Previous versions had problems with V5.1 Remote Boot when looking for PWTPL environment variable, which is not used. 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 Server expects to find a NULL terminator in that 16th character field. The result is random names appearing after the real name in the management display of the machine which owns that license. This was changed to put a NULL terminator in the field. 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. RFA_DAP.DLL ----------- 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 16 =============================================================================== ========================= REVISION HISTORY cont'd ========================= SETHOST.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.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- Persistant 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. A change was made in MIB_SET_IPADDRESS. 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 17 =============================================================================== ========================= REVISION HISTORY cont'd ========================= TCPIP.EXE TCPIPD.EXE cont'd ================= 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 ====== 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 18 =============================================================================== ========================= REVISION HISTORY cont'd ========================= 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.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 this document 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 19 =============================================================================== ========================= REVISION HISTORY cont'd ========================= VT320.EXE cont'd ================ 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. WINSOCK.DLL WINSOCKD.DLL ============= 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 ========== 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. =============================================================================== PATHWORKS for DOS and Windows V5.1 Client Patch Kit page 20 =============================================================================== TRADEMARKS ---------- The following are trademarks of Digital Equipment Corporation: ALL-IN-1 DECbridge DECnis FMS LAT ManageWORKS OpenVMS PATHWORKS TeamLinks ULTRIX VAX VAXELN VMS VT The following are third-party trademarks: (TM)Ethernet is a trademark of Xerox. (TM)Mosaic is a trademark of the University of Illinois. (TM)NetBIOS is a trademark of Micro Computer Systems, Inc. (TM)SCO is a trademark of Santa Cruz Operations, Inc. (TM)TransPATH is a trademark of Vitalink Communications Corporation. (TM)Windows and Windows NT are trademarks of Microsoft Corporation. (R) 3Com is a registered trademark of 3Com, Inc. (R) Attachmate and EXTRA! are registered trademarks of Attachmate Corporation. (R) cc:Mail is a registered trademark of cc:Mail, Inc. (R) COMPAQ is a registered trademark of Compaq Computer Corporation (R) CompuServe is a registered trademark of CompuServe, Inc. (R) DCA is a registered trademark of Digital Communications Associates (R) HP and HP LaserJet are registered trademarks of Hewlett-Packard Company. (R) IBM is a registered trademark of International Business Machines (R) Lotus is a registered trademark of Lotus Development Corporation (R) Microsoft, MS-DOS, MS, MS-Word, Microsoft Windows for Workgroups and Lan Manager are registered trademarks of Microsoft Corporation. (R) NetWare is a registered trademark of Novell, Inc. (R) NeXT is a registered trademark of NeXT, Inc. (R) OSF/1 is a registered trademark of Open Software Foundation, Inc. (R) PKZIP and PKUNZIP are registered trademarks of PKWARE, Inc. (R) SMC is a registered trademark of Standard Microsystems Corporation. Trademarks of other companies mentioned appear for identification purposes only and are the property of their respective companies. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, as applicable. Copyright (c) Digital Equipment Corporation, 1992 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation.