Edited by MMctagg, 26 March 2008 - 08:15 AM.
My clock keeps resetting itself
Posted 26 March 2008 - 08:14 AM
Similar Topics: My clock keeps resetting itself x
Posted 26 March 2008 - 08:27 AM
Posted 26 March 2008 - 09:40 AM
Umm, not any more. We may not be used to the new changeover dates, but this is the now the norm - and more importantly, Microsoft released an update to the Daylight Savings module well before the new changes took effect.
In North America, we all set our clocks forward weeks earlier than usual...
On the contrary, it runs very well.
...so the automatic reset in the system doesn't run.
Therefore, as paws suggests, there is a problem with your system, not Windows. If the procedures he posted do not fix your problem, then you need to go out to Windows Update and make sure your computer is up to current patch and update levels.
And check the Timezone settings carefully, not just the DST box. I once thought I had selected (GMT -06:00) Central Time (US & Canada) but I was in a hurry and had actually selected (GMT -06:00) Central America. Not the same thing! And I checked that a couple times too, but each time I checked it, my mind saw -6 and Central and thought it was right.
Posted 27 March 2008 - 08:29 PM
Posted 27 March 2008 - 09:57 PM
Umm, no. Sorry. But that is not correct. The time servers are not wrong. Internet time all over the globe is syncronized to UTC - when XP syncs with a time server, the hour set then is based on your TimeZone settings. The problem with the time servers listed is it is hard to get a connection to them - perhaps because 1/2 Billion XP and Vista machines are hitting them - if they don't connect, they don't sync.
Both the Internet time servers with which this feature synchronizes the computer time are wrong. If this box is checked your computer periodically will automatically reset itself to the wrong time.
Because those servers are often unavailable, I use Dimension4 (D4) on my XP systems to keep my time accurate - but it still assumes the TimeZone settings are right. What makes it different is if it cannot connect, it will seek out another server, where XP's will just try again next week.
Posted 28 March 2008 - 03:54 PM
Posted 28 March 2008 - 05:18 PM
Posted 28 March 2008 - 09:02 PM
That's just it. The time servers have nothing to do with DST - it's all in the way the computer (regardless the Time Server used) is set up. This includes picking the correct setting for your time zone (for example, there are 3 times zones that are GMT -5 hours - include one for Eastern), and the correct settings for DST correction - assuming the computer is up to date with patches.
I am guessing it's that they don't play well with the new DST schedule.
And Tomk has a point - if your computer is on a network, the time may be set by a local domain controller, or some other network time source.
Posted 31 March 2008 - 06:35 AM
Posted 31 March 2008 - 10:57 AM
No it's not!
Wrong data is fed to my computer.
Wrong data is not being sent your machine! Either you are not synchronizing your system to a genuine "Internet" time server, or your machine is improperly configured for your local time zone.
Internet time servers do NOT send the time to your computers. Your computer queries the time server for the "value" of the current time - the same "value" as any of the 100s of millions of other machines out there from all over the world in every time zone does would get if queried at that moment.
If you are being served the wrong Internet time, then everyone in the whole world is getting the wrong time too. And that ain't happening!
So, if your computer is not converting the Universal Time Constant correctly for your time zone, then that is your computer messing up, NOT Internet time.
For those connected to a domain (often on company networks), please understand that regardless your settings, if your domain controller is your time server, that's the time your computer will always reset to.
Posted 31 March 2008 - 05:40 PM
Posted 31 March 2008 - 08:47 PM
You can say it all you want, it does not change a thing. You are still incorrect. Nobody is sending the wrong time to Sydney! It is not happening!!!! I am sorry but that is just the way it is!
let me say that again...Sydney ... receives wrong time .
There is no such thing as daylight savings time to an Internet time server.
Time servers do not care about time changes in different parts of the world.
Internet time NEVER goes on daylight savings time.
GMT is GMT.
Time servers don't care about Windows.
The time servers just report a value based on the UTC - NOT on Sydney time, NOT on New York time, NOT on Europe time. Your computer fetches the value - your computer converts the value to local time. If that is not happening, then again, the problem is on your end. You either have not correctly maintained your Windows to current updates, you are attached to a domain that uses the domain controller for time hacks, or your system is not setup correctly.
Now you can continue you insist that you are right and the rest of the world is wrong - no matter, but again, the wrong time is NOT being sent to Australia.
dreed - I agree with Tomk, and strongly recommend you read up on this a bit so you know a little bit about Internet time and how it works. Thanks, Tomk, I mentioned making sure all updates were applied first off, but did not provide a link.
Perhaps some additional reading would help too:
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users