I had scripted logic to have a 3000 use the NTPDATE client to get time from 
our two Windows domain controllers, parse that response, and, if the 
adjustment was below a threshold, synchronize. It also handled the change to 
and from DST. We averaged one second loss per day, with one incident of an 
eighty second loss. I never got any complaints. I don't have access to said 
system, but another listmember did ask me for my job stream. Perhaps said 
listmember can send that on to you.

http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind0412c&L=hp3000-l&D=0&P=5627
http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind0508b&L=hp3000-l&O=D&P=7876
Note Larry Barnes correction of my mistake in the second link.

Greg Stigers 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *