AthlonXP 2600+
512mb Ram
Win XP
Thanks for any help.
Considering XP gets its time from the PC BIOS, I would say the problem lies
on the motherboard. Maybe try flashing to the newest BIOS?
@drian.
--
Hope this helps. Let us know.
Wes
"Ilya D." <il...@rogers.com> wrote in message
news:003d01c39d81$026fcfd0$a501...@phx.gbl...
Mack
>.
>
No!, only at startup, the time is then calculated from an interrupt
timer at 60 'ticks' a second. It is most likely a software problem. Do you
have uptodate AV software? Do you run Adaware or Spybot?
Mike.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.532 / Virus Database: 326 - Release Date: 27/10/2003
>
>Considering XP gets its time from the PC BIOS, I would say the problem lies
>on the motherboard. Maybe try flashing to the newest BIOS?
It only reads the start time from the BIOS clock when it boots. After
that it ignores the clock (except when you reset the time) and runs the
clock by counting timer interrupts, based on the oscillator driving the
main system bus (FSB). The clock rate will go wrong if the actual rate
of those is not the one the system expects. This problem seems to
happen quite often with Dell machines. Usually a steady rate of loss
like 10 minutes in an hour.
Another cause might be an over-clocking, pushing the FSB frequency up,
and hence reducing the interval
Try these steps:
1. Start->Run cmd.exe
2. net stop w32time
3. w32tm.exe /unregister
4. w32tm.exe /register
5. net start w32time
(note spellings w32tm and w32time in different commands)
--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. Al...@mvps.D8E8L.org (remove the D8 bit)
>Could be the CMOS battery needs replacing, this is usually
>the case if you are losing time, could be the same if
>you're gaining tho..........
No it is not. That will give you a wildly wrong time at boot - but has
no effect on the rate at which the windows clock runs after that