Runing Windows XP - the clock is slow. I replaced the attery and it's still
slow.
It hesitates after every 5 seconds. We have to set the clock every time we
log in. It wil not sync toany source and report: 'An error occurred when
tying to sync".
Any ideas??

Macabee wrote:
> Runing Windows XP - the clock is slow. I replaced the attery and
> it's still slow.
> It hesitates after every 5 seconds. We have to set the clock every
> time we log in. It wil not sync toany source and report: 'An
> error occurred when tying to sync".
> Any ideas??

Turn on the computer - go into the BIOS immediately, check that the time is
accurate and leave it there for an hour. Come back - time still accurate?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

Mine was precise to the second for hours last night, after I checked BIOS,
then I removed and replaced the small battery (it read 2.8 volts). Now that
I'm connected to the internet again, I've already lost a minute. I guess
that's better than several days behind or months ahead, which it has done
recently. (XP Pro. All updates. Service pack 3. IBM T22.)

"Shenan Stanley" wrote:

> Macabee wrote:
> > Runing Windows XP - the clock is slow. I replaced the attery and
> > it's still slow.
> > It hesitates after every 5 seconds. We have to set the clock every
> > time we log in. It wil not sync toany source and report: 'An
> > error occurred when tying to sync".
> > Any ideas??
>
> Turn on the computer - go into the BIOS immediately, check that the time is
> accurate and leave it there for an hour. Come back - time still accurate?
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
>
>

On Aug 27, 9:26*pm, PX3473 <PX3...@discussions.microsoft.com> wrote:
> Mine was precise to the second for hours last night, after I checked BIOS,
> then I removed and replaced the small *battery (it read 2.8 volts). Nowthat
> I'm connected to the internet again, I've already lost a minute. I guess
> that's better than several days behind or months ahead, which it has done
> recently. (XP Pro. All updates. Service pack 3. IBM T22.)
>
> "Shenan Stanley" wrote:
> > Macabee wrote:
> > > Runing Windows XP - the clock is slow. *I replaced the attery and
> > > it's still slow.
> > > It hesitates after every 5 seconds. *We have to set the clock every
> > > time we log in. *It wil not sync toany source and report: *'An
> > > error occurred when tying to sync".
> > > Any ideas??
>
> > Turn on the computer - go into the BIOS immediately, check that the time is
> > accurate and leave it there for an hour. *Come back - time still accurate?
>
> > --
> > Shenan Stanley
> > * * *MS-MVP
> > --
> > How To Ask Questions The Smart Way
> >http://www.catb.org/~esr/faqs/smart-questions.html

It has been known since the first PC system clock ever was that the
system will loose time. System clocks are designed to schedule
processes internally and not to keep exact time. Various Windows
applications can affect the time.