Re: DST in Windows


KenB wrote:
"John John" <audetweld@xxxxxxxxxxx> wrote in message news:%23lPiRvmZHHA.4620@xxxxxxxxxxxxxxxxxxxxxxx

KenB wrote:


"John John" <audetweld@xxxxxxxxxxx> wrote in message news:ORaa8ZlZHHA.4872@xxxxxxxxxxxxxxxxxxxxxxx


KenB wrote:


"John John" <audetweld@xxxxxxxxxxx> wrote in message news:%23jdO5ojZHHA.3628@xxxxxxxxxxxxxxxxxxxxxxx



KenB wrote:



Here's one for you:

What if you applied the patch, and see the correct time (and note that it says "Eastern Daylight Time" on the date/time applet) and then reboot?

I find the time displayed is 1hr off (backwards, so it's supposed to be 1:30, but displays 12:30).

So I go back into the Date/Time applet, and find that it says "Eastern Standard Time". Then I hit the Time Zone tab and change to another timezone, and back immediately to Eastern. I make sure the Daylight checkbox is checked. Hit Apply, and the time display correctly again, until the next reboot.

_After_ you do the above and enter the correct time open a command prompt and issue:

w32tm /resync /rediscover

What happens?

John



Just rebooted (had the correct time displayed as a result of doing the time zone re-application I wrote about. It shows the time as 10:44 (an hour earlier than it should be). If I issue the command you said, w32tm /resync /rediscover , it says "Sending resync command to local computer... The command completed seuccessfully." Yet, the time displayed is still an hour back.

If I do:
c:\w32tm /tz, I get:
Time zone: Current:TIME_ZONE_ID_STANDARD Bias: 300min (UTC=LocalTime+Bias)
[Standard Name:"Eastern Standard Time" Bias:0min Date:(M:10 D:5 DoW:0)]
[Daylight Name:"Eastern Daylight Time" Bias:-60min Date:(M:4 D:1 DoW:0)]
(this almost looks like the rule is set for month 4, day 1 (so April 1--the old rule)

If I do:
c:\w32tm /monitor, I get:
trcdc01.trc.CW.LOCAL [120.0.0.151]:
ICMP: 0ms delay.
NTP: +0.0192818s offset from trcdc02.trc.CW.LOCAL
RefID: trcdc02.trc.CW.LOCAL [120.0.0.158]
trcdc02.trc.CW.LOCAL *** PDC *** [120.0.0.158]:
ICMP: 0ms delay.
NTP: +0.0000000s offset from trcdc02.trc.CW.LOCAL
RefID: shlroot01.cw.local [10.7.226.125]

Opening tzedit shows the correct rules (Daylight Saving Time Start date/time Second Sunday of March at 2a, end at First Sunday November at 2a).

Let me know if this helps you out... or if there's anythign else I should be looking at.

I'm going to have to think about this and do some searching. I was thinking that the computers might be synchronizing to different servers, that could have explained why some machines were off and others not.

In the meantime use tzedit again and look at the ""Eastern Daylight Time" Daylight Bias: It should be +1:00 hours. The information posted above seems to show it as being set at -1:00 hours (Bias:-60min).

John



Odd... If I manually do the re-application of time zone, and display the correct time, TZEdit shows the right rule (+1:00), but wm32tm /tz shows -60... there's a discrepancy /somewhere/

I appreciate your efforts in finding the solution on this... it's baffling to me!

That isn't the problem. The Bias are shown "reversed" with w32tm. Using tzedit shows GMT offset as -5:00 hours and Daylight offset as +1:00 hours; w32tm shows it the other way around: 300min for GMT offset and -60min for DST Bias. More or less comes to the same thing, just that the tools display it differently.

These machines do not appear to be properly patched. W32tm should return:

[Standard Name:”Eastern Standard Time” Bias:0min Date:(M:11 D:1 DoW:0)]
[Daylight Name:”Eastern Daylight Time” Bias:-60min Date:(M:3 D:2 DoW:0)]

Compare these keys on a faulty machine:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Eastern Standard Time]
"Display"="(GMT-05:00) Eastern Time (US & Canada)"
"Dlt"="Eastern Daylight Time"
"Std"="Eastern Standard Time"
"MapID"="38,39"
"Index"=dword:00000023
"TZI"=hex:2c,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,00,00,00,01,00,02,00,00,\
00,00,00,00,00,00,00,03,00,00,00,02,00,02,00,00,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Eastern Standard Time\Dynamic DST]
"FirstEntry"=dword:000007d6
"LastEntry"=dword:000007d7
"2006"=hex:2c,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0a,00,00,00,05,00,02,00,\
00,00,00,00,00,00,00,00,04,00,00,00,01,00,02,00,00,00,00,00,00,00
"2007"=hex:2c,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,00,00,00,01,00,02,00,\
00,00,00,00,00,00,00,00,03,00,00,00,02,00,02,00,00,00,00,00,00,00

These are the proper Eastern Standard Time values for a properly patched machine. From a known good machine you can export the complete key and subkeys at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones

and import it into the registry of a faulty machine. Then reapply the time zone settings via the Date/Time applet and see if things correct themselves.

John


John-

Checked my machine in a state where it's displaying an hour behind (says 3:19p when it should be 4:19p) All the reg keys matched up to what you posted... weird! What's scarier--what's to happen 4/1, when DST was supposed to happen? --but that's for another posting ;0

Thanks

Ken

Let's move up to the next registry key in the Windows time zone settings:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

This is the key that holds the *current* time zone settings for the computer. When you select or change the time zone the information is read from the key mentioned in my other post and _copied_ to the key above. If changes are made in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones key the CurrentControlSet key has to be "refreshed" to reflect the changes.

To make sure that the key contains no incorrect values and that the values are properly recorded we will delete it then recreate it. Delete the key and then use the Date/Time applet and reselect and reapply your time zone. That will recreate the key and values for your time zone. The values in this key should be _exactly_ identical to a known good machines in the same time zone. Compare the key and values against those from a good machine. Save (export) the key after you set the time zone then check that the contents haven't changed after you reboot the machine.

It is imperative that the keys and values in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones

be correct! The newly created CurrentControlSet key will copy the instruction from that key!

After you do this run the w32tm /tz command again and check the settings.

John
.

Relevant Pages

  • Re: DST in Windows
    ... What if you applied the patch, and see the correct time (and note that it says "Eastern Daylight Time" on the date/time applet) and then reboot? ... Just rebooted (had the correct time displayed as a result of doing the time zone re-application I wrote about. ...
    (microsoft.public.windowsxp.general)
  • Re: DST in Windows
    ... What if you applied the patch, and see the correct time (and note that it says "Eastern Daylight Time" on the date/time applet) and then reboot? ... Hit Apply, and the time display correctly again, until the next reboot. ... Just rebooted (had the correct time displayed as a result of doing the time zone re-application I wrote about. ...
    (microsoft.public.windowsxp.general)
  • Re: DST in Windows
    ... So I go back into the Date/Time applet, ... the Daylight checkbox is checked. ... correctly again, until the next reboot. ... the time zone re-application I wrote about. ...
    (microsoft.public.windowsxp.general)
  • Re: DST in Windows
    ... What if you applied the patch, and see the correct time (and note that it says "Eastern Daylight Time" on the date/time applet) and then reboot? ...
    (microsoft.public.windowsxp.general)
  • Re: DST in Windows
    ... Then I hit the Time Zone tab and change to another ... I make sure the Daylight ... until the next reboot. ...
    (microsoft.public.windowsxp.general)
Loading