TImezones

> From: "Dave R." <dwragle at drbsystems dot com>
> Subject: Re: TImezones
> Date: Thu, 6 Apr 2006 17:10:17 -0400
> Newsgroups: microsoft.public.windowsxp.embedded
>
> "Larry Waibel" <lwaibel@no-spam-cox.net> wrote in message
> news:VA.0000030e.2cdcc40f@no-spam-cox.net...

> >I have my device set for a UTC timezone. If I do a 'time' command I
> >get, for
> > instance, an hour of 13. But when I look at events that are entered
> > in the
> > event log, it stamps the hour as 6. Even if the 'time' command is
> > adjusting
> > for local, if I'm in UTC timezone I was expecting that local and GMT
> > would be
> > the same. What am I missing? Thanks!

>
> I've not seen this behavior before - all of the machines I've had
> experience with show the same system and event log times regardless of
> the time zone or daylight saving time status. As far as I know, Windows
> treats the hardware clock as local time and doesn't do any adjusting.
>
> I tried to look at the registry settings for the UTC time zone, but my
> system doesn't have any time zones listed with UTC as a part of the name
> so I'm not sure what settings you are using. If you could post the
> values in the UTC time zone key under HKLM\SOFTWARE\Microsoft\Windows
> NT\CurrentVersion\Time Zones and the contents of the
> HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInfo rmation key it may be
> that something there will help figure out what is happening.
>
> Regards,
>
> Dave
>

> In article <OM13D6bWGHA.4768@TK2MSFTNGP05.phx.gbl>, Dave R. wrote:

>> From: "Dave R." <dwragle at drbsystems dot com>
>> Subject: Re: TImezones
>> Date: Thu, 6 Apr 2006 17:10:17 -0400
>> Newsgroups: microsoft.public.windowsxp.embedded
>>
>> "Larry Waibel" <lwaibel@no-spam-cox.net> wrote in message
>> news:VA.0000030e.2cdcc40f@no-spam-cox.net...

>> >I have my device set for a UTC timezone. If I do a 'time' command I
>> >get, for
>> > instance, an hour of 13. But when I look at events that are
>> > entered
>> > in the
>> > event log, it stamps the hour as 6. Even if the 'time' command is
>> > adjusting
>> > for local, if I'm in UTC timezone I was expecting that local and
>> > GMT
>> > would be
>> > the same. What am I missing? Thanks!

>>
>> I've not seen this behavior before - all of the machines I've had
>> experience with show the same system and event log times regardless
>> of
>> the time zone or daylight saving time status. As far as I know,
>> Windows
>> treats the hardware clock as local time and doesn't do any adjusting.
>>
>> I tried to look at the registry settings for the UTC time zone, but
>> my
>> system doesn't have any time zones listed with UTC as a part of the
>> name
>> so I'm not sure what settings you are using. If you could post the
>> values in the UTC time zone key under HKLM\SOFTWARE\Microsoft\Windows
>> NT\CurrentVersion\Time Zones and the contents of the
>> HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInfo rmation key it may
>> be
>> that something there will help figure out what is happening.
>>
>> Regards,
>>
>> Dave
>>

> Sorry, I kind of use GMT and UTC and Zulu interchangably;

> here's the contents of the .reg file I imported into my component:
>
> Windows Registry Editor Version 5.00
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\TimeZoneInformation]
> "Bias"=dword:00000000
> "StandardName"="GMT Standard Time"
> "StandardBias"=dword:00000000
> "StandardStart"=hex:00,00,0a,00,05,00,02,00,00,00, 00,00,00,00,00,00
> "DaylightName"="GMT Standard Time"
> "DaylightBias"=dword:00000000
> "DaylightStart"=hex:00,00,0a,00,05,00,02,00,00,00, 00,00,00,00,00,00
> "ActiveTimeBias"=dword:00000000
> "DisableAutoDaylightTimeSet"=dword:00000001

> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\TimeZoneInformation]

> > "Bias"=dword:00000000
> > "StandardName"="GMT Standard Time"
> > "StandardBias"=dword:00000000
> > "StandardStart"=hex:00,00,0a,00,05,00,02,00,00,00, 00,00,00,00,00,00
> > "DaylightName"="GMT Standard Time"
> > "DaylightBias"=dword:00000000
> > "DaylightStart"=hex:00,00,0a,00,05,00,02,00,00,00, 00,00,00,00,00,00
> > "ActiveTimeBias"=dword:00000000
> > "DisableAutoDaylightTimeSet"=dword:00000001

>
> Nothing here really looks like a problem. The only thing unusual I see
> is that you've not only set the three bias values to zero and disabled
> auto daylight time set, but have also set the start & end to be the same
> date & time. I can't imagine that would cause a problem, but you never
> know. It might be worth changing StandardStart to
> 00,00,0a,00,05,00,04,00,00,00,00,00,00,00,00,00 which would be 4am
> instead of 2am on the same date as DaylightStart and see if that has an
> effect.
>
> Let me know how that goes. If that doesn't do it, I'm not sure where
> else to look - hopefully one of the experts here will have an idea.
>
> Regards,
>
> Dave
>

> Nothing here really looks like a problem
>

> In article <#WBBN$NXGHA.196@TK2MSFTNGP04.phx.gbl>, Dave R. wrote:

>> Nothing here really looks like a problem
>>

> You're right, it was my bad! My target device has the timezone set
> for GMT.
> Because I'm trying to keep my footprint as small as possible I don't
> have
> support on the target for event log viewing. Instead I use the
> resource kit
> 'dumpel' to view it from my development system. Of course that system
> has a
> Pacific timezone. So it looks like 'dumpel' is seeing the GMT time in
> the
> log relative to my development's timezone. Thanks for the help in
> getting me
> to look at other reasons why I had the problem!
>