__/ [ doug ] on Sunday 07 May 2006 22:29 \__
> "Marcus Houlden" <spam@xxxxxxxxxxxxxx> wrote in message
>> On Sun, 07 May 2006 16:59:12 GMT, doug <doug.morsit@xxxxxxxxxx>
>> wrote the following to uk.comp.misc:
>> > Help! the clock in the system tray has gone daft.sometimes fast,or
>> > and have to reset it every day. have done a virus scan which is clear.
>> > Am running XP,Athlon 2000,and Asus a7v333 mobo. computer is four years
>> > Could it be internal battery going duff or what?
>> Same motherboard as me, although I find the clock only tends to gain a
>> minute or two. A new battery goes for about £3 (size CR2032 from most
>> electrical shops) so it's worth a try.
> thanks for reply Marcus,no it`s not just a minute or two,it can be hours
> from previous day! it`s odd. will look at the battery issue. doug.
I believe that XP will (/can?) synchronise with a time server (e.g. one on
microsoft.com). This may explain why time is only partially retain (is it
ever corrected?). I suspect that the CMOS battery, which is cheap (and
often easy) to replace, is the culprit. These often last for about 5
years. Thereafter it's assumed that the lifecycle of the computer will
reach an end or the time become unimportant for antiquated, legacy
If you synchronise with a time server, your system clock will probably
become fully aligned once you start the operating system. Time will not be
retained when you shut it down, but it's somewhat of a cycle, if you see
what I mean... (the cost for network time is mainly CPU cycles, but depen-
ds on how frequently you poll for updates).
Roy S. Schestowitz | WARNING: /dev/null running out of space
http://Schestowitz.com | Open Prospects ¦ PGP-Key: 0x74572E8E
7:40am up 10 days 14:37, 7 users, load average: 0.63, 0.55, 0.66
http://iuron.com - knowledge engine, not a search engine