ECO NUMBER: PW60AE01 ----------- PRODUCT: PATHWORKS for DOS -------- UPDATED PRODUCT: PATHWORKS for DOS 6.0A ---------------- APPRX BLCK SIZE: 11663 ---------------- ===================================================================== Cover Letter DIGITAL PATHWORKS V6.0A for DOS and Windows Year 2000 Ready ECO Kit ===================================================================== May 1998 This kit can be applied to computers with the following operating system version: DOS V5.x through V6.x Windows V3.1x Windows for Workgroups V3.1x This kit contains the following updated components to make PATHWORKS V6.0A for DOS and Windows Year 2000 Ready. Local language versions of updated files are included in this kit, in addition to the English version. FTP.EXE V6.0.002 - TCP/IP File Transfer Utility For DOS FTPW.EXE V6.0.008 - TCP/IP File Transfer Utility For Windows NFT.EXE V6.0.004 - DOS-based DECnet Network File Transfer Utility NFTW.EXE V6.0.019 - DECnet Network File Transfer For Windows RFA_DAP.DLL V6.0.006 - File Associated with NFTW.EXE FAL.EXE V6.0.001 - File Access Listener for DOS FALW.EXE V6.0.002 - File Access Listener for Windows LATCP.EXE V6.0.002 - LAT Control Program and Associated LATCP File PRINTQ.EXE V6.0.001 - Print Utility WINRCV.EXE V6.0.010 - Broadcast Message Receiver for Windows 3.1 MAIL.EXE V6.0.013 - Mail Utility for DOS and Associated Mail Files LMSRV.DLL V2.2.02 - LAN Manager Server Module of ManageWORKS LMUR.DLL V2.2.02 - LAN Manager User Module of ManageWORKS NWUSR.DLL V2.0.24 - NetWare User module of ManageWORKS DOSDIR.DLL V2.0.018 - File Associated with ManageWORKS DOSFILE.DLL V2.0.008 - File Associated with ManageWORKS PRINTJOB.DLL V2.0.013 - File Associated with ManageWORKS The other supported software on the PATHWORKS V6.0A for DOS and Windows media kit is Year 2000 Ready. The PATHWORKS V6.0A for DOS and Windows Year 2000 Ready ECO kit is available via the Internet. This is the Digital Electronic Services Web Page, which provides access to many DIGITAL patches. The web address is: http://www.support.compaq.com More information about the Year 2000 Ready status of PATHWORKS clients is available via the Internet. The Y2K web address is: http://www.openvms.digital.com/openvms/products/year-2000 ============== Installation ============== This ECO patch kit contains PC files in a self-extracting archive format (PW60AE01.EXE). To uncompress the kit: 1. Create an MS-DOS command prompt window. 2. Create a temporary directory on the PC's local hard drive. For example: C:\> MKDIR C:\TMP 3. Copy PW60AE01.EXE to the \TMP directory. 4. Expand the .EXE kit by typing the file name at the command line prompt followed by the "-d" option switch. (The "-d" must be lowercase; do not include the quotes). This switch preserves the directory structure within the kit. A target destination may be specified at the end of the command line. If no destination is specified, it will expand the files in the current directory. For example: C:\TMP> PW60AE01.EXE -d This will expand the file into its individual components with the directory structure intact and place them in the C:\TMP\ directory. 5. Follow directions in the README.TXT file (inside .EXE file) to install these updates to your PATHWORKS V6.0A client. *NOTE* If you are running the original version 6.0 of PATHWORKS for DOS and Windows, you must upgrade to 6.0A prior to installing these new files. ================== REVISION HISTORY ================== The PW60AE01 ECO kit fixes the following Year 2000 related problems: FTP.EXE V6.0.002 ================ 1- FTP was calculating a wrong date comparison. For example, a remote file ABC.TXT has a date stamp as 01-01-2000 and a file in the local directory is also called ABC.TXT, but with a date stamp of 01-01-1998. FTP compared the last two digits of the date stamps as 00 and 98 and concluded that the local file was the newer version, due to a miscalculation in date math. FTPW.EXE V6.0.008 ================= 1- The date was displayed incorrectly when the user selected View, All File Details. The date January 1, 2000 was displayed with a file date stamp with a three-digit year. For example, the year 2000 on the date stamp was shown as 01-01-100 or Jan-01-2013 would be shown as 01-01-113. This was due to a date overflow. NFT.EXE V6.0.004 ================ 1- When files dated in year 2000 or later were transferred to a VMS server, they were date stamped with a three-digit year value. This caused a failure and a DAP ERROR. This was corrected by changing the year value to two digits, so that year 2000 will appear as 00 and year 2001 will be interpreted as 01, etc. 2- When fix #1 listed above was made, the files dated 00 on the VMS server were date stamped using a 1980 year when copied on to the local node. This was caused by DOS considering 00 to be 1980. 3- After the date 18-Jan-2038, a date function returned erroneous results. Date stamps received by NFT dated *LATER* than 18-Jan-2038 will be copied with the last recognizable date by this function as 18-Jan-2038 on the VMS server. This fix was added as a precautionary measure in case erroneous file stamps were already stamped on customer files. NFTW.EXE V6.0.019 ================= 1- The files that are displayed in the local directory list box date stamped with years after 2000 displayed these years as 100, 101, 105, due to a date overflow. This was fixed to display these years as 00, 01, 05 for the years 2000, 2001, 2005, respectively. RFA_DAP.DLL V6.0.006 ==================== 1- RFA_DAP.DLL is the module that performs the internal file transfer in the NFTW utility. When the files dated in year 2000 or later were transferred to a VMS server, they were stamped with a three- digit year value, which caused a PROTOCOL ERROR and the transfer failed. This was corrected by changing the year value to two digits so that year 2000 would show up as 00 and 2001 as 01, etc. 2- When fix #1 listed above was made, the files dated 00 on the VMS server were date stamped using a 1980 year when copied on to the local PC. This was caused by DOS considering 00 to be 1980. 3- After the date 18-Jan-2038, a date function returned erroneous results. Date stamps received by NFT dated *LATER* than 18-Jan-2038 will be copied with the last recognizable date by this function as 18-Jan-2038 on the VMS server. This fix was added as a precautionary measure in case erroneous file stamps were already stamped on customer files. FAL.EXE V6.0.001 FALW.EXE V6.0.002 ================= 1- Performing a $dir/date locally to the PC starting with files which were date stamped in the year 2000 would indicate the year as a three-digit number. For example, the year 2000 as a date stamp was shown as 01-01-100 or Jan-01-2013 would be shown as 01-01-113. This was due to a date overflow. LATCP.EXE V6.0.002 LATCP.MSG ================== 1- The Show command in LATCP displayed the year as a five-digit number after January 1, 2000. It was displayed as 19100. This was due to the hardcoding of the century value '19' and concatenating it to the difference of the current date minus 1900. PRINTQ.EXE V6.0.001 =================== 1- This utility truncated dates starting in year 2000 due to a date overflow problem. The problem occured when a print job was executed with an instruction to delay the printing time by specifying the time until which it must hold. PRINTQ displayed this information starting in year 2000 incorrectly. WINRCV.EXE V6.0.010 =================== 1- If WINRCV was run on a system with a date on or later than 1-Jan-2000, messages were displayed with the year as a three- digit number, such that 1-Jan-2000 was displayed as 1/1/100, the year 2001 was 1/1/101, etc. MAIL.EXE V6.0.013 and Associated Mail Files MAIL.PIF MAILBRWS.DEF MAILCHK.EXE MAILDEF.EXE MAILEDIT.DEF MAILHELP.HDX MAILHELP.HLP MAILMSGS.MSG MAILPARS.EXE MAILSEND.EXE MAILSETU.EXE MAILSETU.MSG MAILSORT.EXE MAILUTIL.MSG MAILVIEW.DEF =========================================== 1- Starting in year 2000, Mail displays appeared with a three-digit year. For instance, the date January 26, 2001 was displayed as: 1 26-Jan-101 NODE::USER Message 2- Starting in year 2000, Mail concatenated '19' to a three-digit year in the local mail browser when the Save Outgoing option has been set. For instance, for mail sent on the date January 26, 2001, the following was displayed: From: NODE::USER 26-Jan-19101 hh:min To: NODE::USER CC: Subj: 3- Starting in year 2000, Mail displayed a [TIME NOT SET] message on the mail client screen in place of the current date and time. 4- Starting in year 2000, there was a year overflow in the local version of the mail file. 5- Starting in year 2000, there was a sorting problem with pieces of mail in the local mail browser. 6- Invalid arithmetic after year 2000. Two-digit years were being used for date calculations and it was found that by solving the year overflow problem, further problems have been solved. LMSRV.DLL V2.2.02 ================= 1- When the Properties of a LAN Manager server are shown within ManageWORKS, the Server Counter and the Workstation Counter would display dates with the year in a three-digit format. LMUR.DLL V2.2.02 ================ 1- When the Users of a LAN Manager server listed in the Browser View of ManageWORKS are double clicked, the Properties of that user are displayed in a dialog box. The Last Logon Time and Password Last Change Date of the user displayed the date starting in the year 2000 as 100 and for year 2001, it appeared as 101, etc. 2- Another problem in the same module is that when the user sets the Date of Expiration for the user on a server, if this year is 2000 or later, it was initially displayed using three digits (i.e., year 2000 as 100, 2003 as 103, etc.). When the user would edit this to set the date, it failed to update because the date was not recognized by the server. This occurred due to a date overflow. NWUSR.DLL V2.0.024 ================== 1- In the Browser View within ManageWORKS, when User Details are viewed on the NetWare server, the Last Logon Time for the user would be displayed incorrectly if the date fell on or later than January 1, 2000. For example, the year 2000 was displayed as 19100, the year 2001 was displayed as 19101, etc. Associated ManageWORKS Files DOSDIR.DLL V2.0.018 DOSFILE.DLL V2.0.008 PRINTJOB.DLL V2.0.013 ============================ 1- The Browser list box within ManageWORKS displayed date stamps for directories, files, and print jobs with years after 2000 as three-digit numbers, i.e., 100, 101, 105, etc. This was fixed to display these years as 00, 01, 05 for the years 2000, 2001, 2005 respectively. This was due to date overflows. Other Occurrences of Two-Digit Years ------------------------------------ There are several instances of two-digit years in file information or copyright information in some PATHWORKS client software. However, these dates are strictly cosmetic and in no way affect the software's ability to function properly. Caveat Regarding PATHWORKS V6.0A Client Unsupported Utilities ------------------------------------------------------------- Year 2000 investigations were not undertaken to address the client unsupported utilities--such as SHOW.EXE--which can be found in the DEBUG directory of the PATHWORKS V6.0A for DOS and Windows SSB software kit. That software is still provided on an "as is" basis, is still unsupported, and is NOT warrantied to be Year 2000 compliant. TRADEMARKS ---------- The following are trademarks of DIGITAL EQUIPMENT CORPORATION: DECnet DIGITAL PATHWORKS ManageWORKS The following are third-party trademarks: (R) Microsoft, Windows and Windows for Workgroups are registered trademarks of Microsoft 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. 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 1998. All Rights reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. This ECO has not been through an exhaustive field test process. Due to the experimental stage of this ECO/workaround, Digital makes no representations regarding its use or performance. The customer shall have the sole responsibility for adequate protection and back-up data used in conjunction with this ECO/workaround.