The information in this article applies to:
SYMPTOMSAfter the automatic correction for Daylight Savings Time, monitoring programs comparing current time/date stamps to reference data that were not written using Win32 API calls which directly obtain/adjust to Universal Coordinated Time (UTC) will erroneously report time/date changes on files. Programs affected by this issue may include version-control software, database-synchronization software, software-distribution packages, backup software not written with NTFS-awareness, and so on. CAUSE
When Windows NT automatically adjusts for Daylight Savings Time, the
time/date stamp on files on NTFS volumes and the events in the event logs
appear to be shifted by one hour, even though the files and event records
were last created/changed prior to the Daylight Savings Time adjustment.
RESOLUTIONBy rewriting the affected application(s) to use the appropriate Win32 API calls, this problem can be corrected. Under NTFS, the Win32 API GetFileTime() returns the create time, last access time, and last write time for the specified file. The times returned are in Universal Coordinated Time (UTC). This is also the time that NTFS uses to calculate local time/date information. You can use FileTimeToLocalFileTime() to convert a UTC file time to a local time. However, if you automatically adjust for Daylight Savings Time, FileTimeToLocalFileTime() will adjust for Daylight Savings Time based on whether the current date should be adjusted for Daylight Savings Time, not based on whether the date returned by GetFileTime API call should be adjusted. Additional query words: GetFileTime
Keywords : kbprg nthowto NTSrvWkst |
Last Reviewed: January 25, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |