Vista changed Time Modified of files when the clocks went forwards

  • Thread starter Thread starter Evi
  • Start date Start date
E

Evi

Coming to work today after the clocks had been put forwards on Sunday for
British Summer Time and wishing to check if the files stored on my data pen
were up to date, I saw that Vista had put the Time Modified of all its files
exactly one hour forward. This is not a small problem with the program. Had
I not realised this, I could have assumed that the files on that PC were the
newer version (they weren't). It showed me as having ammended files after
the time I'm supposed to have left the office. (I hadn't)

I have XP at home and it did not do this to my files.

Luckily, I was able to check my files from the data within them. Luckily, I
don't work in an environment where this will be questioned.
Can you imagine the chaos this could have caused in a different workplace?
It is an appalling oversite in the programming of Vista.
Does anyone know if Windows 7 has the same bug.

Evi
 
Coming to work today after the clocks had been put forwards on Sunday for
British Summer Time and wishing to check if the files stored on my data pen
were up to date, I saw that Vista had put the Time Modified of all its files
exactly one hour forward. This is not a small problem with the program. Had
I not realised this, I could have assumed that the files on that PC were the
newer version (they weren't). It showed me as having ammended files after
the time I'm supposed to have left the office. (I hadn't)

I have XP at home and it did not do this to my files.

Luckily, I was able to check my files from the data within them. Luckily, I
don't work in an environment where this will be questioned.
Can you imagine the chaos this could have caused in a different workplace?
It is an appalling oversite in the programming of Vista.
Does anyone know if Windows 7 has the same bug.

Evi
Click to expand...

AFAIK, the internal time is in GMT (UTC?) for all users in all time zones.

The time you see is adjusted to reflect your own *current* time zone when
it is displayed, but the stored time is unchanged. There might be a
configuration item (but I doubt it) to leave the display time unchanged
when the file creation time/date was outside of DST.

If I'm correct, the only files affected will be those mode when DST was not
in effect, and the comparisons will work correctly anyway.

If the above is true, then touch.exe might create chaos if used.

In my view, this is a bug, of course.

BTW, I can't verify what happens on my computer, because I don't know the
correct times of any of my files to check them out: there's nothing
critical involved here and I haven't had to keep track.
 
If I'm correct, the only files affected will be those mode when DST was not
in effect
Click to expand...

Please replace "mode" by "made". I know enough not to trust my spell
checker, but I don't know enough to double check ;-)
 
Gene E. Bloch said:
Please replace "mode" by "made". I know enough not to trust my spell
checker, but I don't know enough to double check ;-)
Click to expand...

Thanks for the reply, Gene. The whole thing was strange.

Evi
 
Back
Top