On 5/8/05, Olin Lathrop wrote: > phil B wrote: > > I should have been a bit clearer. I am checking when > > I sync up the time. At that point the PC clock should > > be pretty close. > > No, that was my point. Take a look at the clock when you sync up. It > doesn't jump suddenly, unless maybe it's way off. In some cases anyway, the > system appears to try adjusting it smoothly. It may take a while for it to > get to the "correct" time. You'll be much better off checking with a real > reference. No, his method is fine for the accuracies he's talking about. At work I have a bunch of servers that syncronize time using NTP. They stay within a few milliseconds of each other. This is becuse the NTP daemon continuously varies the hardware clock speed to keep in sync with the reference, kind of like a very slow-running PLL. ( My machines run Linux, but I've noticed Windows XP comes with an NTP daemon too, now. I assume it works equally well. ) P.S. Phil, to get a quick fix on the time, issue "rdate time.nist.gov" on a Linux box. Error should be less than a second, because NTP takes network latency into account. Regards. Mark markrages@gmail -- You think that it is a secret, but it never has been one. - fortune cookie -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist