NTFS & FAT32 timezone offset
-
Our file server is running Win2K Server w/NTFS. All of the workstations are running Win98 or Win2K Pro w/FAT or FAT32. You know what's coming right ? How do you deal with the daylight saving time change that affects the file timestamps ? NTFS and FAT disagree about the file timestamp so when I try and synch-up local files back to the server w/FileSync all of the files on the server appear to be more recent by an hour since the daylight saving time change. From the Microsoft Knowledge Base: ---- Time Stamp Changes with Daylight Savings Last reviewed: November 10, 1997 Article ID: Q129574 The information in this article applies to: Microsoft Windows NT operating system version 3.1 Microsoft Windows NT Advanced Server version 3.1 Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0 Microsoft Windows NT Server versions 3.5, 3.51, and 4.0 SUMMARY When Windows NT automatically adjusts for daylight savings time, the times on files on Windows NT file system (NTFS) partitions and the events in the event logs are retroactively shifted by one hour, even though the files and event records were created before the daylight savings time change. NOTE: To configure Windows NT to automatically adjust for daylight savings time, run Control Panel, choose Date/Time, and select "Automatically Adjust for Daylight Saving Time." MORE INFORMATION This behavior occurs because of the way that Windows NT stores time information. All times displayed in Windows NT for event log events and files on NTFS partitions are computed as offsets to Greenwich Mean Time (GMT). When you set the time on your system, you are setting the value for GMT. When you select your local time zone for the system, the appropriate number of hours are added or subtracted to the stored GMT value. This adjusted time is displayed. When "Automatically Adjust for Daylight Saving Time" is selected, an additional hour is added to GMT during daylight savings time (the first Sunday in April through the last Sunday in October). If you are viewing another machine remotely across one or more time zones through Event Viewer, the times for events on the remote system appear relative to your local time. In other words, if you are viewing an event remotely that actually occurred at 8:00 PM Central Daylight Time, the time displayed for the event on your computer will be 6:00 PM when you view the event from the Pacific Daylight Time zone. When Windows95 or Windows NT clients access network resources they are passed the GMT time o
-
Our file server is running Win2K Server w/NTFS. All of the workstations are running Win98 or Win2K Pro w/FAT or FAT32. You know what's coming right ? How do you deal with the daylight saving time change that affects the file timestamps ? NTFS and FAT disagree about the file timestamp so when I try and synch-up local files back to the server w/FileSync all of the files on the server appear to be more recent by an hour since the daylight saving time change. From the Microsoft Knowledge Base: ---- Time Stamp Changes with Daylight Savings Last reviewed: November 10, 1997 Article ID: Q129574 The information in this article applies to: Microsoft Windows NT operating system version 3.1 Microsoft Windows NT Advanced Server version 3.1 Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0 Microsoft Windows NT Server versions 3.5, 3.51, and 4.0 SUMMARY When Windows NT automatically adjusts for daylight savings time, the times on files on Windows NT file system (NTFS) partitions and the events in the event logs are retroactively shifted by one hour, even though the files and event records were created before the daylight savings time change. NOTE: To configure Windows NT to automatically adjust for daylight savings time, run Control Panel, choose Date/Time, and select "Automatically Adjust for Daylight Saving Time." MORE INFORMATION This behavior occurs because of the way that Windows NT stores time information. All times displayed in Windows NT for event log events and files on NTFS partitions are computed as offsets to Greenwich Mean Time (GMT). When you set the time on your system, you are setting the value for GMT. When you select your local time zone for the system, the appropriate number of hours are added or subtracted to the stored GMT value. This adjusted time is displayed. When "Automatically Adjust for Daylight Saving Time" is selected, an additional hour is added to GMT during daylight savings time (the first Sunday in April through the last Sunday in October). If you are viewing another machine remotely across one or more time zones through Event Viewer, the times for events on the remote system appear relative to your local time. In other words, if you are viewing an event remotely that actually occurred at 8:00 PM Central Daylight Time, the time displayed for the event on your computer will be 6:00 PM when you view the event from the Pacific Daylight Time zone. When Windows95 or Windows NT clients access network resources they are passed the GMT time o
Not a real solution to your problem, but how about we wake up and realise that our cyclic time adjustments are silly? Right now, set your clock back a half and hour and be done with it. :eek: Ritch
-
Not a real solution to your problem, but how about we wake up and realise that our cyclic time adjustments are silly? Right now, set your clock back a half and hour and be done with it. :eek: Ritch
Yup - daylight savings just confuses the cows and causes excessive fading on curtains. cheers, Chris Maunder
-
Yup - daylight savings just confuses the cows and causes excessive fading on curtains. cheers, Chris Maunder
Personally, I prefer a 10 hour jet-lag. That way your're done with it in one swoop. I'm still not over DST. Heck, I'm here at 12:20am (11:20pm bioclock...) writing this thing. Who can sleep? Actually, who can wake up for work :eek: -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
-
Not a real solution to your problem, but how about we wake up and realise that our cyclic time adjustments are silly? Right now, set your clock back a half and hour and be done with it. :eek: Ritch
It sounds like a real solution to me .. :-)
-
Our file server is running Win2K Server w/NTFS. All of the workstations are running Win98 or Win2K Pro w/FAT or FAT32. You know what's coming right ? How do you deal with the daylight saving time change that affects the file timestamps ? NTFS and FAT disagree about the file timestamp so when I try and synch-up local files back to the server w/FileSync all of the files on the server appear to be more recent by an hour since the daylight saving time change. From the Microsoft Knowledge Base: ---- Time Stamp Changes with Daylight Savings Last reviewed: November 10, 1997 Article ID: Q129574 The information in this article applies to: Microsoft Windows NT operating system version 3.1 Microsoft Windows NT Advanced Server version 3.1 Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0 Microsoft Windows NT Server versions 3.5, 3.51, and 4.0 SUMMARY When Windows NT automatically adjusts for daylight savings time, the times on files on Windows NT file system (NTFS) partitions and the events in the event logs are retroactively shifted by one hour, even though the files and event records were created before the daylight savings time change. NOTE: To configure Windows NT to automatically adjust for daylight savings time, run Control Panel, choose Date/Time, and select "Automatically Adjust for Daylight Saving Time." MORE INFORMATION This behavior occurs because of the way that Windows NT stores time information. All times displayed in Windows NT for event log events and files on NTFS partitions are computed as offsets to Greenwich Mean Time (GMT). When you set the time on your system, you are setting the value for GMT. When you select your local time zone for the system, the appropriate number of hours are added or subtracted to the stored GMT value. This adjusted time is displayed. When "Automatically Adjust for Daylight Saving Time" is selected, an additional hour is added to GMT during daylight savings time (the first Sunday in April through the last Sunday in October). If you are viewing another machine remotely across one or more time zones through Event Viewer, the times for events on the remote system appear relative to your local time. In other words, if you are viewing an event remotely that actually occurred at 8:00 PM Central Daylight Time, the time displayed for the event on your computer will be 6:00 PM when you view the event from the Pacific Daylight Time zone. When Windows95 or Windows NT clients access network resources they are passed the GMT time o
something similar just bit me this weekend. if you get the timestamp for a file using fstat, it's a GMT and DST corrected time_t, yay. but if you want to set a timestamp on a file, you have to use the stupid Win32 SetFileTime function that wants MS's creepy FILETIME structure and that is either local time or GMT time, depending on 95,98,FAT, NTFS, etc.. total nightmare. -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com
-
Our file server is running Win2K Server w/NTFS. All of the workstations are running Win98 or Win2K Pro w/FAT or FAT32. You know what's coming right ? How do you deal with the daylight saving time change that affects the file timestamps ? NTFS and FAT disagree about the file timestamp so when I try and synch-up local files back to the server w/FileSync all of the files on the server appear to be more recent by an hour since the daylight saving time change. From the Microsoft Knowledge Base: ---- Time Stamp Changes with Daylight Savings Last reviewed: November 10, 1997 Article ID: Q129574 The information in this article applies to: Microsoft Windows NT operating system version 3.1 Microsoft Windows NT Advanced Server version 3.1 Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0 Microsoft Windows NT Server versions 3.5, 3.51, and 4.0 SUMMARY When Windows NT automatically adjusts for daylight savings time, the times on files on Windows NT file system (NTFS) partitions and the events in the event logs are retroactively shifted by one hour, even though the files and event records were created before the daylight savings time change. NOTE: To configure Windows NT to automatically adjust for daylight savings time, run Control Panel, choose Date/Time, and select "Automatically Adjust for Daylight Saving Time." MORE INFORMATION This behavior occurs because of the way that Windows NT stores time information. All times displayed in Windows NT for event log events and files on NTFS partitions are computed as offsets to Greenwich Mean Time (GMT). When you set the time on your system, you are setting the value for GMT. When you select your local time zone for the system, the appropriate number of hours are added or subtracted to the stored GMT value. This adjusted time is displayed. When "Automatically Adjust for Daylight Saving Time" is selected, an additional hour is added to GMT during daylight savings time (the first Sunday in April through the last Sunday in October). If you are viewing another machine remotely across one or more time zones through Event Viewer, the times for events on the remote system appear relative to your local time. In other words, if you are viewing an event remotely that actually occurred at 8:00 PM Central Daylight Time, the time displayed for the event on your computer will be 6:00 PM when you view the event from the Pacific Daylight Time zone. When Windows95 or Windows NT clients access network resources they are passed the GMT time o
I'm not sure if it would help to set one machine as time server, the other as time client - would it?
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
Linkify! || Fold With Us! || sighist