Re: SetTimeZoneInformation and file time stamps
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Wed, 28 Mar 2007 09:05:10 -0700
It's entirely up to the filesystem for a given piece of hardware how times
are stored. They could be stored in local time, rather than GMT, for
convenience. That wouldn't occur to me if I were writing the filesystem
driver, but there's no requirement that the filesystem work a certain way.
Since you're stuck with things as they are, you should go everything
possible to assure that the time zone doesn't change between copying a file
where the time has significance to you and using that time to decide if a
copy is needed (or forget the filesytem time entirely and do a CRC, as well
as a time check, to decide if a new file is to be copied).
Paul T.
<portnawake@xxxxxxxxx> wrote in message
news:1175059499.790221.7950@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Paul for taking time to consider my problem.
A few precisions:
\Windows is the RAM filesystem,
Whether the TZI is saved in the registry or is set through
SetTimeZoneInformation, I would expect the changes to affect the whole
system, not just some parts of the filesystem and not the other. I
don't care if the time zone affects the time stamps that is returned,
but it shouldn't be dependent on where the files are located. There's
something in the OS architecture that I don't get!
Thanks
Alex
On Mar 28, 10:07 am, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
Seems like the right thing to do is to have the correct time zone saved
in
the registry, rather than setting it each time with another call to
SetTimeZoneInformation(). My guess is that the semantics of the time
stamp
on the CF card don't match those of the time stamp in the local
filesystem,
whatever that is (RAM filesystem? Flash filesystem?) It seems, though,
that if you copy the file and then check the file while the time zone
settings are the same, you should get a good compare. With the time zone
set in the registry, it seems like you're pretty much automatically going
to
be copying the file and comparing the file information with the same
settings in effect, even if a boot occurs in between.
Paul T.
.
- Follow-Ups:
- Re: SetTimeZoneInformation and file time stamps
- From: portnawake
- Re: SetTimeZoneInformation and file time stamps
- References:
- SetTimeZoneInformation and file time stamps
- From: portnawake
- Re: SetTimeZoneInformation and file time stamps
- From: Paul G. Tobey [eMVP]
- Re: SetTimeZoneInformation and file time stamps
- From: portnawake
- SetTimeZoneInformation and file time stamps
- Prev by Date: windows CE 5.0 and usb kitl
- Next by Date: Re: eboot and FFUART
- Previous by thread: Re: SetTimeZoneInformation and file time stamps
- Next by thread: Re: SetTimeZoneInformation and file time stamps
- Index(es):
Relevant Pages
|