Slashdot Mirror
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 use Zulu time.
I haven't had an issue yet.
but what about us DOS users?
Hack your mind out of its sandbox.
About time too!
(Sorry...couldn't resist)
I suppose that's one way to say, "hurry up and migrate to XP^H^HVista."
Fortunately, the corporate users with a domain will still have a DC as an authoritative time source, and can just adjust the time on one server to keep everyone else in sync.
Big! Strong! Wow! Tada-O!
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
Step 1: Kick users off your box
Step 2: Change the time on your box
Step 3: Make her open the box.
It's my date in a box. Date in a box bay-beh.
According to the article, Win2k users can use the tzedit utility to edit the timezones, ostensibly to alter when/how DST occurs. My initial impulse was to say "what bastards!" (as is often the case with M$ related silliness), but this is only slightly ameliorated by this workaround. Just roll out a bloody patch, guys.
Ford aint giving garantee for their 2000 models cars either.
And Ford doesn't get my business either. 10 year / 100,000 miles. Thank you Kia and Suzuki.
And a big middle finger to Microsoft for this move.
I want peace on earth and goodwill toward man.
We are the United States Government! We don't do that sort of thing.
Don't do the new Daylight Savings Time. It will cost more to implement than the "energy" it is supposed to save. It will probably cripple parts of our infrastructure when it is implemented.
Always do right. This will gratify some people and astonish the rest. -- Mark Twain
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
Win2k was the best MS OS ever. But it's too bad that they're trying to eliminate it, because they want the $$ of XP/Vista. It's good to know that others are trying to stop Microsoft from annoying all who do not pay them. I wonder what Gates thinks of this; extended support costs money, and he hates others stopping him from getting it. Especially if it has source code attached.
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.
Warranty - and safety - are also the reasons I went with a Kia Sportage. Manufacturer support counts for a lot, the sense that they will stand behind their product. That's also why I've been an OSX user for the last few years. Microsoft would have to make huge changes for me to go back. Apple simply does a better job. There's a bonus, too; old Windows machines make great linux-based servers. :)
I've fallen off your lawn, and I can't get up.
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.
2. net stop "windows time"
3. net time
4. net start "windows time"
done. Works as long as the locale and tz on ntp server are set correctly.
'Once scientists, even the dim-witted social scientists, get muzzled, the Western Civilization is finished.' - oldhack
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
If Microsoft's patch will cause Windows XP (or Vista) to show the WRONG time for files saved near the DST change dates/times in years past, then it is NOT A FIX. This DST change has very, very deep effects on every single program that processes ANY dates/times before 2007 in the US. Program that went back before the current DST settings have already dealt with this (or decided to be wrong), but for those of us with no data older than Windows itself, we've never had to worry about this...until now.
For example, a power company wants to compare the power usage trend for, say, 5-6pm (when a large portion of people get out of and home from work) during late March for the years 2005-2008. If their software doesn't know to account for two different DST rules, then two of those years will be comparing the wrong hour of the day. And, FWIW, I chose this example specifically because it lends itself much more to local time than to UTC.
So, to patch this correctly, Windows will need to know which set of [at least two] DST rules to use (based on the year) when translating ANY time from 'system' (i.e. UTC) to 'local'. I don't see that happening, so I don't think that even the XP and Vista users will have a working OS, at least in the sense of correct time translation from UTC to local in the USA.
This blog post explains the reason they keep local time.
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?
It's, "Daylight Saving Time," not, "Daylight Savings Time." It's not like we're, "savings teh 1337 daylights." (daylight is singular)
At least the summary had it right.
Prove it.
Yes, but if you aren't going to respect the Microsoft license and you are going to trust random programs you download, why stop there? Just download a cracked XP or Vista...
But in the Solaris case, I was able to download the new timezone files from ftp://elsie.nci.nih.gov/pub/tzdata2007a.tar.gz and extract the contents (the only file I needed was northamerica), and ran "zic northamerica" -- all was taken care of.
[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?
Where's your Honda dealer?
Microsoft has always had a supported way of making your own changes to your timezone settings. It comes in a program called tzedit.exe and has existed since windows 95 at least. This requires no downloads from third parties. Here's the instructions (taken from: http://www.dbaplace.com/2007-dst-change/#comments)
Every version of Windows has a "resource kit", though Microsoft only supports Win98+ so you may need to hit old download sites for those ancient versions of Windows. You can download the resource kit from http://www.microsoft.com/windows/reskits/. Download this if you do not have it already.
Once the resource kit is downloaded and installed search your disk drive for tzedit.exe and run it.
Select your timezone from the list and click edit.
You'll have two boxes "Start Day" and "End Day" change these from what they are to what they need to be for the new change.
Click Ok, then Close.
To make the settings take effect restart, or select Date/Time from the control panel, choose a different timezone, save and close then repeat selecting your correct timezone this time.
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.
Considering MS already provides a tool that updates timezones, right back to NT4 all they're doing is not wanting to regression test on out of date systems. So tell me, are Redhat producing updates for 10 year old linux installs?
Comment removed based on user account deletion
First of all, it sets the hardware clock to local time rather than GMT, so it breaks other OSs when dual-booting. Second, it puts file timestamps in local time (at least on FAT), so if you change timezones your timestamps can get screwed up. And screwed up timestamps can actually break stuff -- backups, make, etc.
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
Apparently, glibc handles DST using some data files that describe the time changes depending on the time zone you select. They are usually located at /usr/share/zoneinfo, and they are also usually provided by a package. In my Slackware system, the package that provides, essentially, those data files is called glibc-zoneinfo. A quick search on packages.ubuntu.com reveals that the equivalent Ubuntu package, for example, is tzdata. So I would say that a simple update in the relevant data files and packages should do the job.
If someone has problems with your metric "80 past 2 on April 47th", I provide English date format
"3 piglets, 1/16 of stone and a horn after Matins, on 3 Sunday after Xmas"