This clock problem (year going backwards by four years) has now occured on two of my VRPCs (one -SE the other -SA). It seems to happen at midnight as discovered by the fact that TempDir creates a new directory named from the date(e.g. 27Mar08) and the time stamp was 00:00:04 (it does an OS_Word 14,3 every 5 seconds to see if the date has changed).
The significant issue here is that SyncClock is running but it does not do its job completely. The day, month, hour, minute, second, are all correctly sync'd to Windows but the year suddenly becomes 2004 instead of 2008. The Windows time remains correct. Restarting SyncClock and changing its interval makes no difference.
I've now modified TempDir to monitor the year and when it goes backwards it raises an alert and resets it to the correct year. However, the next step is to monitor other running tasks to try to nail the culprit. It seems likely that its something that activates at midnight and converts the time to ordinals and back, otherwise there is no way that just the year could change leaving everything else untouched. So far the only task that I can see that does this and sets the clock is SyncClock itself.
|