XPost: alt.os.windows-xp, aus.computers, microsoft.public.windowsxp.general
From: rod.speed.aaa@gmail.com
Rod Speed wrote:
> Whatcher? wrote
>> Rod Speed wrote
>>> Whatcher? wrote
>>>> Rod Speed wrote
>>>>> TyBreaker wrote
>>>>>> rod.speed@gmail.com wrote
>
>>>>>>> Weird. I've just noticed that my laptop always synchs up 5 mins
>>>>>>> later than the other systems on the lan and it has done that for
>>>>>>> months.
>
>>>>>>> While its normally connected to the lan by wireless, I get
>>>>>>> exactly the same result when its plugged into the lan too.
>
>>>>>>> Makes no difference which time server I use.
>
>>>>>>> Completely standard XP Home, and the manual resynchs
>>>>>>> are quite happy, just gets the time wrong by 5 mins.
>
>>>>>> I point my computers at au.pool.ntp.org and their web site
>>>>>> mentions that it is possible to come up with variations in time
>>>>>> by a few minutes because it depends on the accuracy of the
>>>>>> publicly managed servers in that pool.
>
>>>>> Cant be that, because all of the PCs/laptop are using the same
>>>>> time server and particularly the one which alarms when the
>>>>> ABC TV News starts, is always within a second of the real time.
>
>>>>>> I was thinking that one scenario could be that your laptop has
>>>>>> picked up it's time from an NTP server that isn't accurate.
>
>>>>> Nope, its the same one that the others use.
>
>>>> Just at a guess, your CMOS time and system time are always
>>>> different and every time you reboot, the CMOS time resets the
>>>> system time.
>
>>> Doesnt explain why doing a manual update using the internet
>>> time synch produces a system time thats 5 mins in advance.
>
>> It might actually
>
> Nope. Easy to prove that its not that by not
> rebooting the laptop and still seeing the problem.
>
>> but that goes WAY beyond my programming skills.
>
> Its got nothing to do with programming, just basic diagnosis.
>
> If the problem persists with manual internet time synchs
> without a reboot of the laptop, it can be the cmos time
I obviously meant it cant be the cmos time.
> because the cmos time isnt being used in that situation.
>> I think it depends on which takes priority.
>
> Nope, because there is no priority if you dont reboot.
>
>>> Guess one possibility come to think of it is that the internet time
>>> synch isnt actually updating the system time for some reason, in
>>> other words the time returned by the synch is just ignored.
>
>>> Hmm, just fixed it. To test that particular theory, I manually set
>>> the time to about 5 mins earlier than the correct time. Then did
>>> a manual synch with internet time, and its now got the correct time.
>
>>> So presumably it was binning the internet time for some reason
>>> until I manually set it earlier than the correct time. Weird.
>
>> So is it now ALWAYS OK?
>
> Yes. I'll do some more tests tomorrow to see whether the problem
> is just the difference between the system time and the internet time
> that sees the update ignored. In other words if the amount of time
> update is greater than a particular amount of time, it bins the net
> time.
> I know that it does that when the system time is days
> wrong, but in that case it does say that the synch has failed
> and its hard to see why it would do that with just 5 mins.
>
>> Eg, reboot and resync and is it correct?
>
> Yep. Tho if your possibility was what was happening, only a
> reboot would be needed to see a reversion to the bad time.
>
> Didnt happen with either a reboot or a resynch.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
