MO> Mike O'Connor wrote:

[chomp quoted forwarded message(s)]

 MO> Solution,

 MO> IP=142.3.100.15
 MO> Latency = 0.144 sec
 MO> Local time is 525205504 seconds ahead
 MO> Time set from timelord.uregina.ca (UDP)
 MO> Summer time Sat Mar 10 17:46:40 2007
 MO> Done
 MO> Latency = 0.143 sec
 MO> Local time is     1 seconds behind
 MO> Time set from timelord.uregina.ca (UDP)
 MO> Summer time Sat Mar 10 17:46:57 2007
 MO> Done

i'm still using NIST for my time sync on my OS/2 box... however, NIST keeps
blowing my win98 boxes out of time and that's with the intelliadmin.com
patch for win98...

anyway, i ended up fixing up my TZ string and that promptly fixed up
time868... instead of 

  TZ=EST5EDT 

i now use the following based on info in the time868 help file...

  TZ=EST5EDT,3,2,0,7200,11,1,0,7200,3600

all 10 fields must be present for this format to work... for everyone in
the US, the only thing that may need to be changed is the EST5EDT if they
are not on New York time...

the above is done with a SET statement in CONFIG.SYS and, of course, a
reboot... as far as i can tell, everything is working as desired... now to
beat on an old linux box as well as a few win98 boxen...

)\/(ark