A
avalonx
Can anyone tell me why clock runs slow despite synchronising ?
Thank for any help.
Thank for any help.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
M
Mamamegs
avalonx formulated on woensdag :
Could be the button battery on your mainboard running out.
Usually fairly easy to replace.
--
Mamamegs.
I reject your reality and substitute my own.
(Adam Savage)
www.vistabits.nl
MSN:
_*[email protected]*_
Can anyone tell me why clock runs slow despite synchronising ?
Thank for any help.
Could be the button battery on your mainboard running out.
Usually fairly easy to replace.
--
Mamamegs.
I reject your reality and substitute my own.
(Adam Savage)
www.vistabits.nl
MSN:
_*[email protected]*_
A
Adam Albright
Can anyone tell me why clock runs slow despite synchronising ?
Thank for any help.
Same here. Brand new (few month old MB) and the system clock loses 3
minutes a month no matter what I do.
D
Doug
I believe that there is a time clock you can connect to that works out the
error between successive synchronizations and applies a continuous
correction to the clock so that it becomes accurate. Only trouble is that I
can't remember its name. I think one had to install it as a server? Anyway a
Google search might find it. It claimed (if memory serves) to be the most
accurate way to keep all the PCs on a network in sync in circumstances where
small time differences could do damage.
Ah - I have it:
http://www.meinberg.de/english/sw/ntp.htm
Another thing to do is to shorten the time interval for synchronization from
the weekly default (every 604800 seconds) to daily (86400 seconds)
to do this go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval\
and change it from 604800 to (decimal) 86400 seconds.
see for example at the foot of:
http://www.worldtimeserver.com/atomic-clock/
You could even resync hourly!
Doug
error between successive synchronizations and applies a continuous
correction to the clock so that it becomes accurate. Only trouble is that I
can't remember its name. I think one had to install it as a server? Anyway a
Google search might find it. It claimed (if memory serves) to be the most
accurate way to keep all the PCs on a network in sync in circumstances where
small time differences could do damage.
Ah - I have it:
http://www.meinberg.de/english/sw/ntp.htm
Another thing to do is to shorten the time interval for synchronization from
the weekly default (every 604800 seconds) to daily (86400 seconds)
to do this go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval\
and change it from 604800 to (decimal) 86400 seconds.
see for example at the foot of:
http://www.worldtimeserver.com/atomic-clock/
You could even resync hourly!
Doug