The information in this article applies to:
SYMPTOMSWhen you run Rebuild.exe, the date may be displayed incorrectly after December 31, 1999. For example: the years 2000 through 2009 display as 10, the years 2010 through 2019 display as 11, the years 2020 through 2029 display as 12, and so on. RESOLUTIONTo resolve this problem, contact Microsoft Product Support Services to obtain the following fix. MS-DOSThis fix should have the following time stamp:
This hotfix has been posted to the following Internet location as
Dirsy2k.exe:
ftp://ftp.microsoft.com/bussys/mail/pcmail-public/All-Y2K/ Windows NTThis fix should have the following time stamp:
This hotfix has been posted to the following Internet location as
Dirsy2k.exe:
ftp://ftp.microsoft.com/bussys/mail/pcmail-public/All-Y2K/ OS/2This fix should have the following time stamp:
This hotfix has been posted to the following Internet location as
Dirsy2k.exe:
ftp://ftp.microsoft.com/bussys/mail/pcmail-public/All-Y2K/ STATUSMicrosoft has confirmed this to be a problem with Rebuild.exe for DOS. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Contact Microsoft Product Support Services for more information. MORE INFORMATIONFor additional information, please see the following articles in the Microsoft Knowledge Base: Q191886 Y2K: Reqmain.exe for DOS Displays the Incorrect Date after 1999 Q191887 Y2K: Srvmain.exe for DOS Displays Incorrect Date after 1999 Q191888 Y2K: DOS Dispatch Incorrectly Displays Year Q191905 Y2K: Key Dirsync Logs Display Incorrect Date after 1999 Q191907 Y2K: Import.exe Displays Incorrect Date after 1999 Additional query words: dirsync, dir-sync, Y2K, compliant, date
Keywords : kb2000 |
Last Reviewed: January 17, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |