clock setting

[bnix]

My clock on my machine always runs fast. Even after i
set it will quickly become about 10 min fast again. Is
there a way to fix this or some sort of update i need?

 

[Gerry]

Welcome to the land of PC's. They can run all these
wonderful programs, but keep the crapiest time. For
whatever reasons, PC's are not built with accurate time
sources. There is not much you can do to rectify this
problem. I have yet to see a PC that keeps accurate time.

 

[Ken Blake, MVP]

In

Welcome to the land of PC's. They can run all these
wonderful programs, but keep the crapiest time. For
whatever reasons, PC's are not built with accurate time
sources. There is not much you can do to rectify this
problem. I have yet to see a PC that keeps accurate time.

Not true. These days, it is trivially easy to keep accurate time.
My computer synchronizes itself to a time server every hour, and
it's *always* accurate to a fraction of a second.

True, I don't really require that level of accurcy, but it's easy
and painless to get.


Brix might want to try the following:

Open a command prompt window (Start | Run | cmd) and enter the
following commands:

net stop w32time
w32tm /unregister
w32tm /register
net start w32time

--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup

 

[Alex Nichol]

My clock on my machine always runs fast. Even after i
set it will quickly become about 10 min fast again. Is
there a way to fix this or some sort of update i need?

This problem seems to happen quite often, especially with Dell
machines. Usually a steady rate of loss or gain like 10 minutes in an
hour. 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]

Not true. These days, it is trivially easy to keep accurate time.
My computer synchronizes itself to a time server every hour, and
it's *always* accurate to a fraction of a second.

And the way the windows clock works, it is making an assumption about
the interval between timer interrupts - which may not be very accurate,
as the system oscillator used for them is not really intended as a
clock. But if you have the Date/Time - Internet time set to synchronise
regularly, it soon learns what the actual interval is, and adjusts to
it, so that soon it keeps quite good time without need to sync very
often (I do it every two days)