5744. Daylight Savings Time here has ended, and instead of the clock going
back one hour, it went back two. The time zone is correct, so I am assuming
this is a bug. When I ran the synchronization tool, it corrected it.

"Travis King" <(E-Mail Removed)> wrote in message
news:eAFdJS3%(E-Mail Removed)...
5744. Daylight Savings Time here has ended, and instead of the clock going
back one hour, it went back two. The time zone is correct, so I am assuming
this is a bug. When I ran the synchronization tool, it corrected it.
----------------------------------------------------------------------------
I had the same issue - build 5744 also

BChat

No problem here in the UK, my clock went back one hour to GMT

"BChat" <(E-Mail Removed)> wrote in message
news:ulyjCY3%(E-Mail Removed)...
> "Travis King" <(E-Mail Removed)> wrote in message
> news:eAFdJS3%(E-Mail Removed)...
> 5744. Daylight Savings Time here has ended, and instead of the clock
> going
> back one hour, it went back two. The time zone is correct, so I am
> assuming
> this is a bug. When I ran the synchronization tool, it corrected it.
> ----------------------------------------------------------------------------
> I had the same issue - build 5744 also
>
> BChat
>
>
>
>

Brian Wescombe wrote:
> No problem here in the UK, my clock went back one hour to GMT
>
> "BChat" <(E-Mail Removed)> wrote in message
> news:ulyjCY3%(E-Mail Removed)...
>> "Travis King" <(E-Mail Removed)> wrote in message
>> news:eAFdJS3%(E-Mail Removed)...
>> 5744. Daylight Savings Time here has ended, and instead of the clock
>> going
>> back one hour, it went back two. The time zone is correct, so I am
>> assuming
>> this is a bug. When I ran the synchronization tool, it corrected it.
>> ----------------------------------------------------------------------------
>>
>> I had the same issue - build 5744 also
>>
>> BChat
>>
>>
>>
>>
>
Fine here;also

Jeff

Please report this with the Microsoft Beta Client beta software.

regards
Robert
"Travis King" <(E-Mail Removed)> wrote in message
news:eAFdJS3%(E-Mail Removed)...
> 5744. Daylight Savings Time here has ended, and instead of the clock
> going back one hour, it went back two. The time zone is correct, so I am
> assuming this is a bug. When I ran the synchronization tool, it corrected
> it.

If you are dual booting, and have each operating system set to handle
daylight saving time, you will get two corrections. Each system you boot
into will change the clock one hour. I just went through this with my eldest
son.

It happens all the time.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Travis King" <(E-Mail Removed)> wrote in message
news:eAFdJS3%(E-Mail Removed)...
> 5744. Daylight Savings Time here has ended, and instead of the clock
> going back one hour, it went back two. The time zone is correct, so I am
> assuming this is a bug. When I ran the synchronization tool, it corrected
> it.

I was just going to mention that because I *was* on XP at the time of the
change last night.
"Richard Urban" <(E-Mail Removed)> wrote in message
news:%23WDeqm3%(E-Mail Removed)...
> If you are dual booting, and have each operating system set to handle
> daylight saving time, you will get two corrections. Each system you boot
> into will change the clock one hour. I just went through this with my
> eldest son.
>
> It happens all the time.
>
> --
>
> Regards,
>
> Richard Urban
> Microsoft MVP Windows Shell/User
> (For email, remove the obvious from my address)
>
> Quote from George Ankner:
> If you knew as much as you think you know,
> You would realize that you don't know what you thought you knew!
>
> "Travis King" <(E-Mail Removed)> wrote in message
> news:eAFdJS3%(E-Mail Removed)...
>> 5744. Daylight Savings Time here has ended, and instead of the clock
>> going back one hour, it went back two. The time zone is correct, so I am
>> assuming this is a bug. When I ran the synchronization tool, it
>> corrected it.
>
>

This solves the situation here - dual booting as well - thanks -
will set one OS NOT to handle clock changes

BChat

"Richard Urban" <(E-Mail Removed)> wrote in message
news:%23WDeqm3%(E-Mail Removed)...
If you are dual booting, and have each operating system set to handle
daylight saving time, you will get two corrections. Each system you boot
into will change the clock one hour. I just went through this with my eldest
son.

It happens all the time.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Travis King" <(E-Mail Removed)> wrote in message
news:eAFdJS3%(E-Mail Removed)...
> 5744. Daylight Savings Time here has ended, and instead of the clock
> going back one hour, it went back two. The time zone is correct, so I am
> assuming this is a bug. When I ran the synchronization tool, it corrected
> it.

No problem here. I'm dual booting.

Jan
MS MVP - Windows IE/OE [DTS/AumHa]
Data/Comp Technology
www.datacomptech.com
Smiles are meant to be shared,
that's why they're so contagious.

"Travis King" <(E-Mail Removed)> wrote in message
news:eAFdJS3%(E-Mail Removed)...
> 5744. Daylight Savings Time here has ended, and instead of the clock
> going back one hour, it went back two. The time zone is correct, so I am
> assuming this is a bug. When I ran the synchronization tool, it corrected
> it.

Same here, had to manually synch.

--
Peter
Toronto, Canada
XP Pro SP2 x 2 + Vista RC2 5744
P4 HT @ 3.0ghz, 700gb HDD, 2.0gb DDR
Creative SB Audigy 4 Sound, ATI Radeon 9550 Graphics
TS H429A + H552U CD/DVD Combi-Drives
Sony DRU820A x 2 DVD-RAM Combi-Drives
"Travis King" <(E-Mail Removed)> wrote in message
news:eAFdJS3%(E-Mail Removed)...
> 5744. Daylight Savings Time here has ended, and instead of the clock
> going back one hour, it went back two. The time zone is correct, so I am
> assuming this is a bug. When I ran the synchronization tool, it corrected
> it.