Windows Clock is Very Fast

[Ruffiano]

The windows clock seems to be a bit fast. I have it set
to update itself, but that only occurs once a week.
Though, after doing a manual update, after 30 min, it'll
be an hour or so fast again. Is there a way to up the
update time to every 5 min or something? I just installed
a new nForce2 motherboard and noticed the problem, it
just occured to me to check the systems clock in the bios
and see if the problem matches, I am not sure if the
windows clock just reads from that or not, either way.

 

[Matt Coy]

Ruffiano,

Try Doug Knox's utility to do just that:

http://www.dougknox.com/xp/utils/xp_inet_time.htm

 

[Jason Tsang]

Try this

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


This is a very common issue that Dell computers have (though other makes may
have the same problem too).

DELL imaged the OS from one machine and installed in on a batch of machines
notably with different CPU speeds. Information about the imaged machine's
processor clock is stored in the registry. The defect is that windows
should detect that the processor is different and should refresh the
registry entry. The steps above force that to happen.

 

[William Phelps]

-----Original Message-----
....
Try these steps:

1. Start->Run cmd.exe
2. net stop w32time
3. w32tm.exe /unregister
4. w32tm.exe /register
5. net start w32time

....

Would you or anyone else know of a similar fix for
previous versions of Windows like 98 or Me?
Until all the ISVs get up to date, some systems need to
run the older versions.

William

 

[Alex Nichol]

Would you or anyone else know of a similar fix for
previous versions of Windows like 98 or Me?
Until all the ISVs get up to date, some systems need to
run the older versions.

AFAIK there is none - but if you have queries on these systems ask in
*their* newsgroups, eg
microsoft.public.win98.gen_discussion
microsoft.public.windowsme.general