Simulated Real Time Clock Presents the Century Byte Representing 19 Instead of 20 in the 21st Century

ID: Q193376

The information in this article applies to:

SYMPTOMS

The simulated Real Time Clock (RTC) will always present the century byte representing 19 instead of 20 in the 21st Century. This causes MS-DOS-based programs that access the Real Time Clock to receive the wrong date. For example, the year 2000 is interpreted as the year 1900.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem.

To resolve this problem immediately, download the fix as described below. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/support/supportnet/default.asp
The English version of this fix should have the following file attributes or later: 

   Date      Time                 Size    File Name     Platform
   -------------------------------------------------------------
   09/25/98  03:44p               406,352 Ntvdm.exe     (x86)
   09/25/98  03:45p             1,700,624 Ntvdm.exe     (Alpha)

NOTE: Y2k351-i.exe and Y2k351-a.exe were updated on November 5, 1998.

This hotfix has been posted to the following Internet location as Y2k351-i.exe (x86) and Y2k351-a.exe (Alpha):

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/hotfixes-postSP5/y2k-fix/


NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. 


Keywords          : kb2000 kbbug3.51 kbfix3.51 
Version           : WinNT:3.51
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: February 19, 1999