TIme Clock to fast

[Aaron]

The Time Clock on my computer is running to fast. Does
anybody have suggestions on how to fix this problem

[Kelly]

Hi Aaron,

Suggestions:

1. Start->Run cmd.exe
2. net stop w32time
3. w32tm /unregister [ignore error message]
4. w32tm /unregister
5. w32tm /register
6. net start w32time

--
All the Best,
Kelly

Microsoft-MVP Windows® XP

In memory of Robert McGregor (aka Koldbear)
http://www.btinternet.com/~winnoel/winhelp.htm

Troubleshooting Windows XP
http://www.kellys-korner-xp.com




"Aaron" > wrote in message
...
> The Time Clock on my computer is running to fast. Does
> anybody have suggestions on how to fix this problem

[Alex Nichol]

Andrew Hodes wrote:

>You might want to try updating the BIOS and replacing the system battery
>inside the chassis.

If it happens while windows is running it is, positively and
categorically, NOT the battery. And I am getting very tired of people
suggesting it is. Windows uses that click solely as a start point, and
battery trouble is indicated by the time being wildly wrong at boot.

This problem seems to happen quite often, especially with Dell
machines. Usually a steady rate of loss like 10 minutes in an hour, but
may be a gain. It appears to result from a conflict with the BIOS over
the interval between 'timer interrupts'. Windows maintains the clock by
counting these, so if the interval is not the expected one, the rate is
grossly out in this manner.

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. (remove the D8 bit)

[Andrew Hodes]

You might want to try updating the BIOS and replacing the system battery
inside the chassis. If neither of these help and the time is incorrect even
after a restart, there is some sort of a problem with hardware. If the time
is correct after a reboot, there could be a Windows problem.

--
Andrew Hodes
MCP, MCSA, MOS

"Aaron" > wrote in message
...
> The Time Clock on my computer is running to fast. Does
> anybody have suggestions on how to fix this problem

[Please reply to newsgroup.]

Alex Nichol wrote:

> Andrew Hodes wrote:
>
>
>>You might want to try updating the BIOS and replacing the system battery
>>inside the chassis.
>
>
> If it happens while windows is running it is, positively and
> categorically, NOT the battery. And I am getting very tired of people
> suggesting it is. Windows uses that click solely as a start point, and
> battery trouble is indicated by the time being wildly wrong at boot.
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour, but
> may be a gain. It appears to result from a conflict with the BIOS over
> the interval between 'timer interrupts'. Windows maintains the clock by
> counting these, so if the interval is not the expected one, the rate is
> grossly out in this manner.
>
> 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)

Just a question unrelated to XP - if you don't replace a dying battery
in an older computer, could the computer eventually not boot at all? I
have an old IBM PS/2 that had a dying battery and one day, it just sat
there when I turned on and didn't do anything - didn't read the drives
or flash the keyboard lights.

[Please reply to newsgroup.]

Alex Nichol wrote:

> Andrew Hodes wrote:
>
>
>>You might want to try updating the BIOS and replacing the system battery
>>inside the chassis.
>
>
> If it happens while windows is running it is, positively and
> categorically, NOT the battery. And I am getting very tired of people
> suggesting it is. Windows uses that click solely as a start point, and
> battery trouble is indicated by the time being wildly wrong at boot.
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour, but
> may be a gain. It appears to result from a conflict with the BIOS over
> the interval between 'timer interrupts'. Windows maintains the clock by
> counting these, so if the interval is not the expected one, the rate is
> grossly out in this manner.
>
> 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)

Just a question unrelated to XP - if you don't replace a dying battery
in an older computer, could the computer eventually not boot at all? I
have an old IBM PS/2 that had a dying battery and one day, it just sat
there when I turned on and didn't do anything - didn't read the drives
or flash the keyboard lights.

[Please reply to newsgroup.]

Alex Nichol wrote:

> Andrew Hodes wrote:
>
>
>>You might want to try updating the BIOS and replacing the system battery
>>inside the chassis.
>
>
> If it happens while windows is running it is, positively and
> categorically, NOT the battery. And I am getting very tired of people
> suggesting it is. Windows uses that click solely as a start point, and
> battery trouble is indicated by the time being wildly wrong at boot.
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour, but
> may be a gain. It appears to result from a conflict with the BIOS over
> the interval between 'timer interrupts'. Windows maintains the clock by
> counting these, so if the interval is not the expected one, the rate is
> grossly out in this manner.
>
> 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)

Just a question unrelated to XP - if you don't replace a dying battery
in an older computer, could the computer eventually not boot at all? I
have an old IBM PS/2 that had a dying battery and one day, it just sat
there when I turned on and didn't do anything - didn't read the drives
or flash the keyboard lights.

[Please reply to newsgroup.]

Alex Nichol wrote:

> Andrew Hodes wrote:
>
>
>>You might want to try updating the BIOS and replacing the system battery
>>inside the chassis.
>
>
> If it happens while windows is running it is, positively and
> categorically, NOT the battery. And I am getting very tired of people
> suggesting it is. Windows uses that click solely as a start point, and
> battery trouble is indicated by the time being wildly wrong at boot.
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour, but
> may be a gain. It appears to result from a conflict with the BIOS over
> the interval between 'timer interrupts'. Windows maintains the clock by
> counting these, so if the interval is not the expected one, the rate is
> grossly out in this manner.
>
> 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)

Just a question unrelated to XP - if you don't replace a dying battery
in an older computer, could the computer eventually not boot at all? I
have an old IBM PS/2 that had a dying battery and one day, it just sat
there when I turned on and didn't do anything - didn't read the drives
or flash the keyboard lights.

[Please reply to newsgroup.]

Alex Nichol wrote:

> Andrew Hodes wrote:
>
>
>>You might want to try updating the BIOS and replacing the system battery
>>inside the chassis.
>
>
> If it happens while windows is running it is, positively and
> categorically, NOT the battery. And I am getting very tired of people
> suggesting it is. Windows uses that click solely as a start point, and
> battery trouble is indicated by the time being wildly wrong at boot.
>
> This problem seems to happen quite often, especially with Dell
> machines. Usually a steady rate of loss like 10 minutes in an hour, but
> may be a gain. It appears to result from a conflict with the BIOS over
> the interval between 'timer interrupts'. Windows maintains the clock by
> counting these, so if the interval is not the expected one, the rate is
> grossly out in this manner.
>
> 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)

Just a question unrelated to XP - if you don't replace a dying battery
in an older computer, could the computer eventually not boot at all? I
have an old IBM PS/2 that had a dying battery and one day, it just sat
there when I turned on and didn't do anything - didn't read the drives
or flash the keyboard lights.