[Dx4win] Clock error

Sat, 26 Oct 2002 08:42:30 -0000

Pete:

I had a similar problem and it was driving me nuts. I thought it was a
defect on my ABIT motherboard. At the same time, I could not understand why
I was losing minutes per day when the timing is crystal-controlled.

The clue is that you only LOSE time.

In my case, I replaced the motherboard with an identical unit that had been
in my wife's computer, and got the same results. This initially led to the
conclusion that the MB design itself had a defect, but that still did not
sit right with me.

The light dawned when an old friend visited from the East Coast. That OF has
become a computer geek and works for an outfit that now hosts my domain.
While here,having heard me bitching about how poorly my computer ran in
general, he went in and cleaned up my registry, and threw out whatever
appeared not to be necessary for the current configuration. The computer
subsequently ran better, stopped failing to shut down correctly.....and the
clock returned to expected accuracy. Conclusion: some of the stuff he got
rid of must have been stealing cycles---a lot of cycles---and not just from
the real-time clock.

You therefore might try the same, but, if you are not computer-savvy, you
should either find someone who is willing to do this for you, or go to the
Microsoft site, find the procedure for editing the registry (with RegEdit, I
think) and be very, very careful.

73,

Garry, NI6T

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Pete Smith
> Sent: Friday, October 25, 2002 14:04
> To: [email protected]; [email protected]
> Subject: [Dx4win] Clock error
>
>
> Help -- the computer I use for TRLog and DX4WIN(a 200 MMX Pentium) has
> started losing about 12 seconds an hour in its real-time clock -- for
> example, I set it this morning from the Internet, and when I can back 3
> hours later it was 38 seconds slow.  Is this indicative of battery
> problems?  The computer has been on throughout.  I also wonder if perhaps
> some software that is running on the system -- maybe in
> background -- could
> be responsible.
>
> Any advice much appreciated.
>
> 73, Pete N4ZR
>
> _______________________________________________
> Dx4win mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/dx4win
>