At 01:17 PM 3/14/03 -0800, Jim Reisert AD1C wrote: >Some time servers are bad, and Tardis will grab a bad time off them. Once I >logged a bunch of QSOs 91 minutes off because I got a bad time from a server. >It was only luck that I noticed the problem. > >There is a setting in Tardis called "Maximum Correction Allowed" which should >prevent this from happening, i.e. it would just ignore a bad server and >set the >time at the next interval.
This is a good point. For reasons I don't understand, some software, running in the background under windows, can also disrupt timekeeping. I use automachron for internet time -- a big feature for me when I was chasing a clock problem was its logging feature that would tell you hoe much of a correction had been applied each interval. I finally tracked my problem down to a redundant sound card mixer that was running in the background! The hardware it related to was disabled in the BIOS but it kept doing something disruptive anyway. 73, Pete N4ZR The World HF Contest Station Database was updated 23 Feb 03. Are you current? www.pvrc.org/wcsd/wcsdsearch.htm
