If EWF is active and you select "Automatically adjust clock for daylight
saving changes" in “Date and Time Properties / Time Zone� then everything is
ok till time comes for automatic clock adjustment. Then the time is adjusted
not only once but on every reboot. This happens till you execute “ewfmgr c:
-commit�. Then everything is ok till the next clock adjustment and so forth.
Is there a solution available except disabling this functionality?

Hi Gunter. This is a known issue with EWF, and the best available
workaround is to disable the auto-adjust option and adjust the time
manually, or base the machine's time on GMT.

--
Matt Kellner ((E-Mail Removed))
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================

"Günter" <(E-Mail Removed)> wrote in message
news:38AD922B-583E-4660-9B31-(E-Mail Removed)...
> If EWF is active and you select "Automatically adjust clock for daylight
> saving changes" in "Date and Time Properties / Time Zone" then everything
> is
> ok till time comes for automatic clock adjustment. Then the time is
> adjusted
> not only once but on every reboot. This happens till you execute "ewfmgr
> c:
> -commit". Then everything is ok till the next clock adjustment and so
> forth.
> Is there a solution available except disabling this functionality?

"Matt Kellner (MS)" <(E-Mail Removed)> wrote in message
news:uBPTjnR$(E-Mail Removed)...
> Hi Gunter. This is a known issue with EWF, and the best available
> workaround is to disable the auto-adjust option and adjust the time
> manually, or base the machine's time on GMT.

Since someone brought this up, is there any way in any Windows version to
tell it to offset the Windows system time from the RTC -- which is UTC?
Every Windows version seems to require you to assume the RTC is local, and
the Windows system time is to be synchronized with.

If so, that would remove this issue entirely, because the Windows system
would dynamically off-set at run-time (including handling daylight savings
appropriately based on a static configuration setting and the current date),
and never touch the RTC (except for corrections). That would make it act
like UNIX systems (which pretty much always offset dynamically per user,
because they were designed as timeshare systems and the users weren't always
local to the system).

I only vaugely remember an utility on the NT 4.0 Resource Kit that
supposedly did this, but I can't remember. Just curious if one exists
(especially for XPE, but also XP/2003 in general).

Hi,

There is a full workaround if you are making custom shell that show and use time:
http://groups.google.com/group/micro...387139782a5cc3
http://groups.google.com/group/micro...36922fb4c897ee

http://groups.google.com/group/micro...ylight+&qt_g=1

Regards,
Slobodan

"Bryan J. Smith" <(E-Mail Removed)> wrote in message news:OJDCeZS$(E-Mail Removed)...
> "Matt Kellner (MS)" <(E-Mail Removed)> wrote in message
> news:uBPTjnR$(E-Mail Removed)...
> > Hi Gunter. This is a known issue with EWF, and the best available
> > workaround is to disable the auto-adjust option and adjust the time
> > manually, or base the machine's time on GMT.
>
> Since someone brought this up, is there any way in any Windows version to
> tell it to offset the Windows system time from the RTC -- which is UTC?
> Every Windows version seems to require you to assume the RTC is local, and
> the Windows system time is to be synchronized with.
>
> If so, that would remove this issue entirely, because the Windows system
> would dynamically off-set at run-time (including handling daylight savings
> appropriately based on a static configuration setting and the current date),
> and never touch the RTC (except for corrections). That would make it act
> like UNIX systems (which pretty much always offset dynamically per user,
> because they were designed as timeshare systems and the users weren't always
> local to the system).
>
> I only vaugely remember an utility on the NT 4.0 Resource Kit that
> supposedly did this, but I can't remember. Just curious if one exists
> (especially for XPE, but also XP/2003 in general).
>
>

Thanks for your replies :-)

Heres Lyndas answer:

This is a problem that has been often discussed, and we are looking at
possible solutions to this for the next XPe release. However at this stage
there is no real solution other than disabling EWF, making the change and
committing it.
Some customers have reported their workarounds such as this one reported in
the newsgroup:

http://groups.google.com/group/micro...78bffca5b21729
http://groups.google.com/group/micro...853050abbd2ed8

Regards,
Günter