Unofficial Win2K Daylight Saving Time Fix
Saturn2003a writes "Microsoft has stated that they will not be offering a patch for the new US Daylight Saving Time for Windows 2000 and earlier. Only customers with an extended support agreement can get a Hotfix from Microsoft. To get around this, IntelliAdmin has created an unofficial patch (source code provided) that will fix Daylight Saving Time on Windows 2000 and Windows NT machines."
I used to do that too, but I found all the spears and animal skins cluttered up the server room.
occultae nullus est respectus musicae - originally a Greek proverb
but what about us DOS users?
Hack your mind out of its sandbox.
About time too!
(Sorry...couldn't resist)
Think of the millions of clocks worldwide with automated systems b/c there authors didn't think that daylight savings time would change... sorta reminds me of something I saw in a "How not to program" book "don't set pi as a constant, you might have to update it". :D.
I work for a large clock company and there sending out many (20+) people throughout the country to reprogram the clock controllers so that there DST tables can be automatically updated in the future, nothing like more summertime
This knowledge base article from Microsoft describes how to use the Time Zone Editor utility (which you can download from that page) to adjust time zone settings.
If you need to update several computers, it also describes which registry keys to export. You can then import those registry keys in a logon script or whatever.
It's not like people/companies running Win2k are SOL.
The Online Slang Dictionary
I have all my clocks set to Metric Time.
Remember this moment, people: 80 past 2 on April 47th, the moment Microsoft finally kicked Windows 2000 to the curb.
In the country I live in DST is on a different date every year, and is based on when some
holiday happens to occur in the lunar calendar, so every year in our data centers we either
change the clocks manually, or rely on the Domain Controller on changing the time for
the servers and workstations in the domain.
And we don't complain to Microsoft for not providing us a fix for it.
-D
I knew it was just a matter of time.
You are being MICROattacked, from various angles, in a SOFT manner.
Direct from M$:
Move to Arizona, Hawaii, or anywhere outside the US.
Latewire
Nope, more like the US decided to switch to metric and people complaining that Ford won't replace their English unit speedometer with one that has more prominent markings for metric. In both cases, the product still works but external factors make it less convenient. With Ford you have to look at the smaller metric markings. With Microsoft, you have to manually update the clock for daylight savings time twice a year. Neither case is a malfunction.
Are you sure? Last I knew it used sntp to send around time data thats all in UTC with the local machines converting it to local time. I could be completely off though been a long time since I was forced to run windows.
No sir I dont like it.
I dislike M$ as much as the next /. poster, but saying W2K is 'broken' in this case is a bit of a stretch. The gov't changed the rules governing daylight savings time; it's not like it *wasn't* right before.
People in cars cause accidents....accidents in cars cause people
I live in Arizona, you insensitive clod!
Well, it was passed into law in August of 2005, so it's been around for a while. Here's a link to the relevant bits. Following is the relevant changes:
It actually got quite a bit of news coverage at the time. It's been on Slashdot several times as well.
Cheers
Lost at C:>. Found at C.
The US switching to metric? If I had mod points, I'd mod you funny for that line.
My karma is in a nose dive
I used Windows to control all my time-related issues once. But after one BSOD all of a sudden it was 1955, my parents accidentally never met, and my future mom started hitting on me. Ugh...
Slashdot Burying Stories About Slashdot Media Owned
download and install patches from a web site operated by the government
And now for another episode of, "Good Idea, Bad Idea"
Seriously... downloading patches from a website operated by the government?
[I]I dislike M$ as much as the next /. poster, but saying W2K is 'broken' in this case is a bit of a stretch. The gov't changed the rules governing daylight savings time; it's not like it *wasn't* right before.[/I]
It's not that W2K is broken that makes M$ an asshole in all of this. It's that they have a patch available for those who have paid for extended support, but they won't release it for the general public.
Since the cost to produce the patch has already been absorbed by M$, the only reason to withhold the patch is to make people frustrated with W2K to encourage them to upgrade. When you can readily fix something, but you don't, so that people will upgrade, well, then, your an asshole.
And you're saying that in reply to an article about an unofficial fix for it?
It is for anyone on a Windows network with mixed 2000 and XP installs using Active Directory. Kerberos (which Active Directory uses) will automatically deny access if the client's clock is more than 5 minutes off from the server's clock. If your server runs 2003 and your clients are 2000, or your server runs 2000 and your clients are XP, you will hit a problem.
There is a reason why every system clock in an Active Directory system is synchronized. If the server's clock is off from Atomic time, so will all of the clients.