FWIW, this observation may be related to the problem under discussion..
Volker Kuhlmann wrote:
A recurring issue I have with dual boot systems (Win + SuSE, Ubuntu, ..) is settling the time/date across all platforms. There is something significantly different about the way this record is stored in Win vs Linux.In your case, suddenly having time in the middle of the night is indicative for a time zone mismatch. Keep in mind that Billyware(TM) expects to go on local time whereever your are, resulting in a big screwup when you go international. A lot of software is then unable to handle this properly. You may need to configure samba to use the correct timezone. I have also observed that Billyware with about version 2000 shifted from local time to UTC when file servers are concerned, causing yet more chaos. On the positive, this might eentually fix the problem where the times on all the files in the other half of the year are out by one hour (as Billy isn't able to take of the daylight saving difference properly).
In your case it looks like you're having a time zone problem as well as a problem with timestamps not being copied. A time zone problem shows up as times being wrong by about 12 hours. Timestamps not being copied shows up as all files having the same time stamp (that of when they were copied).
I always go with the defaults/CLUG recommendation at installtime (local time + NZ/Ackd), but adjusting the time/date setting to be correct in Linux tends to throw the system clock back 12 hours (hence Roger's 3am?) under Windows. And vice versa, only then it's forward in Linux.
Is it a function of displayed time/date in Linux being different to the actual system clock reading, which gets recorded / rewritten at power down?
hth
Rik
