Barry et al: I should have mentioned in my response that the first thing I did in my case was to replace the battery---and that changed nothing, which led to motherboard replacement, and, finally, registry cleaning. I used and use AtomTime, which correctly updated the clock---which then invariably wandered, until the Registry cleaning did the job for me.
Garry, NI6T > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Barry > Sent: Friday, October 25, 2002 14:36 > To: Pete Smith; dx4win@mailman.qth.net > Subject: Re: [Dx4win] Clock error > > > Pete, > The way you can tell if it's software bogging down the system vs. > hardware/battery is this: > Just before turning off the computer for the night, update the clock. > Next day, first thing when you turn it on, check the time. Is it > accurate? If so, it's not the battery. > > There are multiple clocks in the computer. The "main" clock is > hardware. The software clock accesses this info when you first turn > the computer on. Windows (on the task bar) and most software then > access one of the software clocks. One of my computers has this > problem, where some software bogs down the clock and it can be off by > minutes in a matter of hours. My solution was to use one of the > Internet time setting programs (Tardis, etc.) and have it reset the > clock every 15 minutes. If you are using WinXP, the Internet polling > of the time signal is built in and I believe defaults to every 3 > hours. There are ways to make this more frequent, though there's no > setting within XP. You have to use an external program that changes a > registry setting (no, I don't know what it is, offhand). > 73, > Barry W2UP > > > On 25 Oct 2002 at 10:03, Pete Smith wrote: > > > 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 > > Dx4win@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > -- > Barry Kutner, W2UP Internet: [EMAIL PROTECTED] > Newtown, PA Frankford Radio Club > > > _______________________________________________ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
