Windows Thread, System clock running very fast in Technical; We can't rule that out.
I'm sure that in the past I've found old PCs that have been stuck on ...
7th August 2008, 02:06 PM #16
We can't rule that out.
I'm sure that in the past I've found old PCs that have been stuck on shelves for a long period unused with RTCs showing dates well into the future - months or years. Whenever I've seen it I've always thought "Uh Oh... battery's going".
When the battery dies altogether, the RTC is likely to default back to a date in the past, usually the date the BIOS was written, so they'll have, say, 1988 for the date. They wouldn't default to some arbitary date in 2010 for example. Finding an ancient PC with a RTC date in 2010 has always meant to me 'low battery'.
I've always believed, rightly or wrongly, that when a battery drops its voltage, the RTC can speed up. If HP support agree then that's good enough for me.
Can I retract my retraction? I was riddled with self-doubt earlier, but have been bolstered by SOSAGES.
7th August 2008, 02:26 PM #17
sorry i didn't get around to replying. i set the server time yesterday, synched this pc and it seems to have kept it. cant believe it was something as simple as the server time being off.
so much going on around here that i'm forgetting the basics!!
thank you to everyone for your help
7th August 2008, 02:31 PM #18
The Kerberos time has a tolerance of about 5 minutes I think, so if the client and the server are out the client will catch up, but without jumping (as this will invalidate your current Kerberos tickets). That's why you see it moving quicker than normal.
7th August 2008, 02:32 PM #19
aha, that sounds like what it was doing
7th August 2008, 02:36 PM #20
It would depend on how badly the output waveform is distorted, as the system will probably count high to low edges if the waveform is distorted enough it could be sufficient to trip the count logic more often than it is supposed to. The crystal could also be damaged as you say, a crack in the crystal will change its output frequency. I remember reading about people modding old crystal oscillators by opening them and chipping off small amounts of the crystal to speed up the clock effectively overclocking the device. This would be stupidly hard now as the crystals are much smaller, especially for pc bus speeds.
Originally Posted by OverWorked
7th August 2008, 02:42 PM #21
You can see how far out you are with:
where somedc is a valid domain controller or other NTP source.
w32tm /stripchart /computer:<somedc>
8th August 2008, 11:03 AM #22
no problem - everyone makes mistakes but I'm impressed that you did think it through and remembered all the details. It certainly makes sense that the waveform will get distorted (listen to a battery powered amp when the batteries are going flat) and if something needs nice sharp edges then it will have problems if it doesn't get them.
Originally Posted by OverWorked
8th August 2008, 12:36 PM #23
In your login script, syncs your clock with the DC's clock.
net time \\DC-NAME-01 /set /y
8th August 2008, 01:59 PM #24
May be better to use it in the machine startup script - by default users don't have the right to change the system time.
Also, the "net time" command is deprecated - in common with all the other old Lan Manager commands they may not be supported in the future. You can replace it with w32tm /resync
By speckytecky in forum Educational Software
Last Post: 15th July 2009, 12:35 PM
By strawberry in forum Windows
Last Post: 21st November 2007, 10:11 AM
By Scruff in forum General Chat
Last Post: 15th June 2007, 08:58 PM
By dezt in forum Wireless Networks
Last Post: 6th November 2006, 11:09 PM
By Dos_Box in forum General Chat
Last Post: 21st July 2006, 05:00 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)