With the way the clock drift is happening, it sounds like a time zone setting problem. Both Linux and Windows XP will slowly adjust the clock to match the NTP server. Now, if the time zone setting is wrong, the system will gain/lose time as it runs, until it matches. Running the AtomTime95 program under windows would probably make things worse by fighting with the NTP program windows is already running. Making sure that the time zone is the same under both Windows and Linux, making sure it is the correct time zone, and not using AtomTime95 should fix the problem. Mikkel --
I'm confused about this one. I don't see time zone settings being the issue as that would cause the time to be off by an hour (or two, or whatever depending on the time zone) not drift by a few minutes to 100+ minutes over the course of a few hours. And Windows or Linux would not slowly adjust the clock to match NTP, it synchronizes with it and changes it to match. What would be the reason for Windows or Linux slowly changing the time to synch up with NTP? It's not a bad suggestion to check and make sure that they have the same time zone settings. But that would not account for clock "drifting". Jacques B.
