Seems to me that the last time I chased this, checking the HARDWARE
clock, the one on the motherboard (not the one in software set from
hardware during bootup), was a standard bios function, not
particularly mysterious. Not something you would want to do constantly
(it's slow), but every thirty seconds or every couple of minutes would
not be a bother. TR could just keep itself adjusted, regardless if
some java fragment has hosed the software clock.
73, Guy.
----- Original Message -----
From: "Pete Smith" <n4zr@contesting.com>
To: "Gary Ferdinand W2CS" <w2cs@bellsouth.net>; "Guy Olinger, K2AV"
<k2av@contesting.com>; "Jim Smith" <jimsmith@shaw.ca>; "trlog"
<trlog@contesting.com>
Sent: Tuesday, December 10, 2002 9:53 AM
Subject: RE: [TRLog] TRLog and serial ports, 2
> At 09:33 AM 12/10/02 -0500, Gary Ferdinand W2CS wrote:
> >I concur with Pete's comments. I, too, have a recalcitrant computer
that
> >loses gobs of time. I have installed atomic clock synch V2.6 and
it seems
> >to do a good job keeping me within a second or two of WWV. This
is, of
> >course, only relevant for those using windoze.
> >
> >On a lighter note, a sign posted on a major NC highway pointing
onto a
> >crossroad saying: "WANTED: ELECTRICITY 2 MILES -->"
> >
>
> Someone suggested to me privately that maybe Guy was suggesting
having TR
> check with the CMOS clock instead. If that was the idea, I think it
might
> have merit, but I'm not aware of any application that does that.
Far as I
> know, the only time it gets written to is during shutdown, and the
only
> time it gets read is during the boot-up sequence, when the CMOS time
is
> transferred to the operating system.
>
>
> 73, Pete N4ZR
> Sometimes a tower is just a tower
>
>
>
>
>
|