Beta

Slashdot: News for Nerds

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Unofficial Win2K Daylight Saving Time Fix

kdawson posted more than 7 years ago | from the it's-about-time dept.

Windows 299

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."

cancel ×

299 comments

My fix? (3, Funny)

Anonymous Coward | more than 7 years ago | (#17561074)

I use Zulu time.

I haven't had an issue yet.

Re:My fix? (5, Funny)

dsanfte (443781) | more than 7 years ago | (#17561098)

I used to do that too, but I found all the spears and animal skins cluttered up the server room.

Re:My fix? (1)

radarsat1 (786772) | more than 7 years ago | (#17561282)

I use Zulu time.


Right on, brotha! [zulunation.com]

My fix - avoid vendors that act like assholes. (0)

Anonymous Coward | more than 7 years ago | (#17561808)

Why would anyone do business with a vendor that treats people this way?

Or at a minimum treats their own products with some respect?

They already have a fix. It's clearly broken. And they're not fixing it!?! It's not like it'd cost them anything to do so. My bet is that they avoid fixing bugs on purpose just so they can charge suckers more for upgrades.

The only real fix is to get a vendor that doesn't act like such an asshole. Anything else is just a workaround.

Re:My fix - avoid vendors that act like assholes. (5, Insightful)

pixelpusher220 (529617) | more than 7 years ago | (#17561886)

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'll stretch it (0, Flamebait)

tepples (727027) | more than 7 years ago | (#17562614)

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.

If an operating system does not define a language for a government agency to express amendments to time zone rules so that the people can download and install patches from a web site operated by the government, then the operating system is broken.

Yeah, right (4, Funny)

zr-rifle (677585) | more than 7 years ago | (#17561126)

but what about us DOS users?

Re:Yeah, right (1)

$RANDOMLUSER (804576) | more than 7 years ago | (#17561372)

> but what about us DOS users?

Just put "time" and "date" commands in your autoexec.bat.

Re:Yeah, right (0)

Anonymous Coward | more than 7 years ago | (#17561454)

I don't know about you, but I bought a wrist watch.

Re:Yeah, right (3, Funny)

0racle (667029) | more than 7 years ago | (#17561546)

vas is dos?

Re:Yeah, right (5, Funny)

Aqua_boy17 (962670) | more than 7 years ago | (#17562414)

vas is dos?
I think it's from that german movie "DOS Boot".

Re:Yeah, right (0)

Anonymous Coward | more than 7 years ago | (#17561804)

DOS has no concept of timezone or DST, so no patch necessary. Though maybe you should switch to Linux.

and it's.... (4, Funny)

celardore (844933) | more than 7 years ago | (#17561138)

About time too!

(Sorry...couldn't resist)

Re:and it's.... (3, Insightful)

camperdave (969942) | more than 7 years ago | (#17561776)

I think it's about time that we just split the difference, adjust the clock by half an hour, and leave it there.

Well... (3, Informative)

minvaren (854254) | more than 7 years ago | (#17561152)

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.

Re:Well... (4, Informative)

silas_moeckel (234313) | more than 7 years ago | (#17561878)

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.

Re:Well... (1)

archen (447353) | more than 7 years ago | (#17561988)

I would think it would have to be since the assumption is that machines may be in different timezones in the same domain.

Re:Well... (0)

Anonymous Coward | more than 7 years ago | (#17562246)

DC's don't push daylight savings time information.

Hm... (1)

El Lobo (994537) | more than 7 years ago | (#17561154)

Windows 2k is...lets me see 6 years old... Well Adobe just gave us a big middle finger for a bug in their Photoshop CS that is 2 years old. Their answer? Upgrade to CS2 or find a workaround. No news here folk... Ford aint giving garantee for their 2000 models cars either.

Re:Hm... (2, Insightful)

Shakrai (717556) | more than 7 years ago | (#17561286)

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.

Re:Hm... (2, Insightful)

fyngyrz (762201) | more than 7 years ago | (#17561698)

Thank you Kia and Suzuki.

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. :)

Re:Hm... (0, Offtopic)

heinousjay (683506) | more than 7 years ago | (#17561744)

The few driving experiences I've had in a Kia have kept me from even wanting to ride in one. Have they improved the awful handling, poor ride, and general low build quality yet?

Re:Hm... (1)

tarp (95957) | more than 7 years ago | (#17561352)

This is not like Ford refusing to warranty their 2000 model cars. This would be like someone finding out that the 2000 model Ford cars speedometer malfunctions once the year hits 2007, and Ford refusing to provide a simple fix that keeps the speedometer functioning. Microsoft is way out of line for refusing to offer a patch to fix this problem.

Re:Hm... (4, Insightful)

breser (16790) | more than 7 years ago | (#17561568)

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.

Re:Hm... (4, Funny)

LordSkippy (140884) | more than 7 years ago | (#17562092)

The US switching to metric? If I had mod points, I'd mod you funny for that line.

Re:Hm... (0, Offtopic)

Misch (158807) | more than 7 years ago | (#17562188)

My parents were sold a Chevrolet Cavalier that was bound for Canada.

How could we tell? The speedometer and odometer were in metric (primary).

It was also a piece of crap. Too bad New York State didn't enact a Lemon Law until the next year.

Re:Hm... (1)

archen (447353) | more than 7 years ago | (#17562216)

While true to some extent this is a bit different. My understanding is that this could easily be fixed with a simple registry import - that's like what, 2kb worth of bandwidth from MS if they didn't just give a simple patch? I'd say your analogy would be more like Ford not fixing the speedometer when it was simply as easy as driving your car to a dealer and having him fix it by touching your car with a magic wand.

MS is just making this more inconvenient to "push" people to newer systems. Win2k is still under extended support until 2010 after all.

Your analogy is flawed (1)

paladinwannabe2 (889776) | more than 7 years ago | (#17561676)

It's more like the federal government declaring that a mile is now exactly 1.6 km, instead of 1.609344km. It's not Ford's fault that the definition of a mile has changed- they didn't issue faulty speedometers, the government changed things on them long after their speedometers were built, installed, and sold.

GMT (0, Redundant)

fullphaser (939696) | more than 7 years ago | (#17561172)

And this is why I always set things to Greenwich Mean Time.

Re:GMT (5, Funny)

eln (21727) | more than 7 years ago | (#17561316)

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.

Re:GMT (0)

Anonymous Coward | more than 7 years ago | (#17562306)

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 your case, wouldn't that be Windows 742.38175819222?

Re:GMT (0)

Anonymous Coward | more than 7 years ago | (#17562534)

I have all my clocks set to Metric Time.

Didn't The Hives introduce that system?

clocks (5, Interesting)

erbbysam (964606) | more than 7 years ago | (#17561174)

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".
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 :D.

Re:clocks (1)

Anonymous Coward | more than 7 years ago | (#17562800)

there: a place

they're: a contraction of "they" and "are"

their: possessive adjective, used to indicate ownership

You're post is painful to read.

(The previous line is ironic...)

It's not like there are no other options (5, Informative)

WalterGR (106787) | more than 7 years ago | (#17561186)

This knowledge base article [microsoft.com] 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.

Re:It's not like there are no other options (4, Funny)

Atzanteol (99067) | more than 7 years ago | (#17561638)

Grammar tip: "Effect" is a verb. "Affect" is a noun.

Slashdot has enough trouble with grammar without you confusing things. :-P

They can each be both, but the typical cases are "affect" as a verb, and "effect" as a noun. Linky [google.com] .

Re:It's not like there are no other options (0)

Anonymous Coward | more than 7 years ago | (#17561874)

YHBT. YHL. HAND.

Re:It's not like there are no other options (1)

Hognoxious (631665) | more than 7 years ago | (#17562284)

We should think of a witty name for the situation where someone postulates something, then supports it with a link that directly contradicts it.

Re:It's not like there are no other options (2, Funny)

Atzanteol (99067) | more than 7 years ago | (#17562488)

Eh? From the first link [writersblock.ca] in the google search I linked to:

"Affect" is usually a verb meaning "to influence".

...

"Effect" is usually a noun meaning "result".

There is a noun meaning for "affect" and a verb meaning for "effect", but they're uncommon. So you go ahead and come up with your clever term, and I'll come up with one for when one uses it inappropriately.

Re:It's not like there are no other options (1)

ibebanging (713982) | more than 7 years ago | (#17562370)

No kidding, It took me a total of 30 minutes to write a vbscript to change the keys. Besides, MS still provides security patches for Windows 2000, just not hotfixes for events not under their control - Energy Act 2005.

It's my date in a box (2, Funny)

Anonymous Coward | more than 7 years ago | (#17561222)

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.

Re:It's my date in a box (0)

GeckoX (259575) | more than 7 years ago | (#17561448)

ROFLMAO :)

I've been waiting for someone to pull that out somewhere, couldn't have chosen a better use. Think my wife made me watch that skit 50 times over the holidays ;)

Re:It's my date in a box (1, Funny)

multisync (218450) | more than 7 years ago | (#17562040)

I wasn't going to even watch that SNL because I wasn't too excited about JT as host and musical guest. Glad I did, it was one of the funniest shows I've seen in a while, and Dick in a box [videosift.com] was hilarious!

Not Entirely Stuck (3, Informative)

Cygfrydd (957180) | more than 7 years ago | (#17561234)

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.

I've got a fix (2, Insightful)

JerkyBoy (455854) | more than 7 years ago | (#17561310)

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.

Re:I've got a fix (0)

drinkypoo (153816) | more than 7 years ago | (#17561446)

All daylight savings time is and always has been retarded. Who cares what time something happens? Get up earlier (or later) and all is solved. It can only have been created to give some kind of economic benefit to some specific corporation or individual, like every other asinine change ever made by government.

Re:I've got a fix (2, Interesting)

CyberLord Seven (525173) | more than 7 years ago | (#17561664)

Daylight Savings Time was originally sold as a method to allow children to travel to school in the safety of daylight. There is not much you can do about that during the Fall and Winter months when the day is so short, but you can adjust the clocks to help children during the Spring and Summer months.

It had nothing to do with energy until...well, that's another topic.

Re:I've got a fix (0)

Anonymous Coward | more than 7 years ago | (#17561926)

Why do we have to change the clock rather than add/subtract an hour from our schedules? It's retarded.

Re:I've got a fix (2, Interesting)

jandrese (485) | more than 7 years ago | (#17562012)

Uh, you have that backwards. Daylight savings time was developed during wartime to conserve on energy by moving the daylight back towards the end of the day (people liked getting up late and staying up past dark back then too). So you might be thinking to yourself, that sounds great, why don't we do that all year long? The answer is the kids. We turn daylight savings time off in the winter because otherwise the kids have to go to school in the dark when the days grow short.

Think about it, most kids go to school pretty early in the morning, but get off in the mid afternoon. Shifting the daylight back certainly doesn't help them go to school in any more light, and there was never a problem on the other end unless you live very far North (in which case you're SOL anyway).

Re:I've got a fix (1)

Waffle Iron (339739) | more than 7 years ago | (#17562590)

Get up earlier (or later) and all is solved.

Since very few people's work or school schedules would change, the extra time in the morning would be a uselessly short interval with a looming workday ahead of it. Plus, in the real world, only maniacs get up before they absolutely have to.

You're getting ~100 extra hours of real-world useful daylight time in exchange for spending 3 minutes per year setting your clocks. It's a net benefit. A lot of people seem to love making contrarian complaints about DST, but it's really making a mountain out of a molehill.

DST in some countries changes every year... (5, Informative)

random_dg (1002962) | more than 7 years ago | (#17561328)

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

Re:DST in some countries changes every year... (2, Insightful)

multisync (218450) | more than 7 years ago | (#17562698)

And we don't complain to Microsoft for not providing us a fix for it.


The thing is, Microsoft has provided a fix, but only to customers with Extended Support [microsoft.com] .

I don't know if there is some technical reason why Microsoft is unable to simply make it available to everyone on the Windows Update website, but I suspect this is simply another opportunity for them to keep the old forced-upgrade treadmill running.

"Only" 1Mb (0)

Anonymous Coward | more than 7 years ago | (#17561342)

Hey - remember when you could do some trivial data changes in a few lines of code and a 1K executable? Or am I just old?

Re:"Only" 1Mb (1)

Rosco P. Coltrane (209368) | more than 7 years ago | (#17561506)

Hey - remember when you could do some trivial data changes in a few lines of code and a 1K executable? Or am I just old?

When was the last time you saw a 1K executable on Windows? The only one I can think of is the bootloader.

Re:"Only" 1Mb (1)

Kalriath (849904) | more than 7 years ago | (#17561800)

Oh, you are NOT talking about NTLDR... (250KB)

Re:"Only" 1Mb (0)

Anonymous Coward | more than 7 years ago | (#17561964)

He is probably talking about $BOOT

So, the Y2K problem finally shows up (4, Funny)

SpaceLifeForm (228190) | more than 7 years ago | (#17561364)

I knew it was just a matter of time.

Re:So, the Y2K problem finally shows up (1)

phall (23499) | more than 7 years ago | (#17562398)

Hey, lets start windows legacy project.

Why the 3rd party patch? (1)

TubeSteak (669689) | more than 7 years ago | (#17561374)

Only customers with an extended support agreement can get a Hotfix from Microsoft.
Unless this MS Hotfix is somehow tagged or customized... wouldn't we only need one extended support holder to put the patch out on the internets?

There IS an official fix (4, Funny)

slughead (592713) | more than 7 years ago | (#17561384)

Direct from M$:

Move to Arizona, Hawaii, or anywhere outside the US.

Re:There IS an official fix (1)

PhotoJim (813785) | more than 7 years ago | (#17561740)

Sorry to break it to you, but most of Canada observes DST too. But not us here in Saskatchewan. Too bad I don't still use NT or 2000. :)

Re:There IS an official fix (1)

slughead (592713) | more than 7 years ago | (#17561812)

Sorry to break it to you, but most of Canada observes DST too. But not us here in Saskatchewan. Too bad I don't still use NT or 2000. :)

Yeah but who cares about Canada?

All tucked away down there...

Re:There IS an official fix (2, Insightful)

Ichijo (607641) | more than 7 years ago | (#17562594)

Or just live on GMT/UTC time. If the Australians can have their winter in the middle of summer, then Californians can have their lunch at dinnertime.

True legacy (1)

TheSHAD0W (258774) | more than 7 years ago | (#17561392)

I know many people who simply can't afford new PCs are are stuck running Windows 95 & 98. Is there any way to correct these? (Aside from manually tweaking the clock.)

Re:True legacy (0)

Anonymous Coward | more than 7 years ago | (#17562038)

Easy. Tell them to rent a summer residence, 15 degrees eastward.

Re:True legacy (1)

sh0dan (762382) | more than 7 years ago | (#17562054)

I don't think tweaking the clock will be one of their biggest problems.

Re:True legacy (0, Redundant)

jandrese (485) | more than 7 years ago | (#17562444)

Easy solution: Try installing Linux.

MS Entourage 2004 on OS X has same problem. (1)

vertinox (846076) | more than 7 years ago | (#17561416)

Even with the latest 11.3.2 patch, all meetings made through March through April are one hour wrong.

http://support.microsoft.com/?kbid=924606 [microsoft.com]

And as always their glorious status of this bug:

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Microsoft is researching this problem and will post more information in this article when the information becomes available.
Which leaves many people who use Entourage in the corporate environment out to dry.

Re:MS Entourage 2004 on OS X has same problem. (0)

Anonymous Coward | more than 7 years ago | (#17561710)

Not showing up for those meetings save you one hour at a time. This is a *GOOD* side effect afterall.

You know... (1)

AltGrendel (175092) | more than 7 years ago | (#17561428)

...this is probably going to screw up all those bot-nets.

Re:You know... (1)

kasperd (592156) | more than 7 years ago | (#17562048)

...this is probably going to screw up all those bot-nets.
Why? A good botnet shouldn't rely on the clock of the bots. In fact it relies on the bots being machines with clueless administrators. So it would rely on as little as possible of the setup of the machine it is running on. It is not like the local clock is the best or only way to know what time it is, and botnet could work even without knowing what time it is.

What about XP? (1)

MyNameIsEarl (917015) | more than 7 years ago | (#17561452)

Any word on a fix or lack of for XP, or has this already been patched in a previous update?

Re:What about XP? (0)

Anonymous Coward | more than 7 years ago | (#17561984)

Windows XP SP2 and Windows Server 2003 were already updated through Windows Update. Windows XP SP1, Win2K and previous versions of Windows are no longer supported and must be fixed manually. See http://www.microsoft.com/windows/timezone/dst2007. mspx [microsoft.com] for details.

Most database vendors (Oracle,IBM) require patches to support the new DST. I haven't found anything on MSSQL yet. Anyone have an idea if it is affected by DST?

Re:What about XP? (1)

MTgeekMAN (700406) | more than 7 years ago | (#17562172)

There has been a patch for XP
here is a KB article with patches for XP and 2003 http://support.microsoft.com/kb/928388 [microsoft.com]

New Daylight Savings Time rules? (1)

Eggplant62 (120514) | more than 7 years ago | (#17561470)

News to me. Got links or references to share on that? If it hadn't been for this story, I'd have not known about that, thanks.

Re:New Daylight Savings Time rules? (4, Informative)

gstoddart (321705) | more than 7 years ago | (#17562002)

News to me. Got links or references to share on that? If it hadn't been for this story, I'd have not known about that, thanks.

Well, it was passed into law in August of 2005, so it's been around for a while. Here's a link [nist.gov] to the relevant bits. Following is the relevant changes:

* In 2006, DST will begin at 2 a.m. on the first Sunday of April (April 2, 2006) and Standard Time will begin at 2 a.m. on the last Sunday in October (October 29, 2006), as under the current rules.

        * However, beginning in 2007, DST will begin at 2 a.m. on the second Sunday in March (March 11, 2007) and Standard Time will begin at 2 a.m. on the first Sunday in November (November 4, 2007).


It actually got quite a bit of news coverage at the time. It's been on Slashdot several times [google.com] as well.

Cheers

It's For The Customer! (1)

blueZhift (652272) | more than 7 years ago | (#17561510)

Even though Microsoft may be within their rights to not support a 6 year old OS, it would be a good idea for them to roll out a patch for an annoyance like the DST change. It would be a sign of good will to past and hopefully future customers, and it just plain looks bad for unofficial sources to be offering patches for Windows. Even if the OS has gone past end of life, the Windows brand is Microsoft's bread and butter. They really can't just sit back and let anyone offer up patches for it. Besides, these aren't blue haired grandmas running Windows 2K. Some of these people/companies might just buy something if you treat them right.

Win2k (2, Insightful)

QueePWNzor (1044224) | more than 7 years ago | (#17561518)

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.

Re:Win2k (2, Insightful)

Chacham (981) | more than 7 years ago | (#17561792)

Win2k was the best MS OS ever.

Actually, i think 3.51 takes the cake. It was a solid machine, and was the first OS with the new interface (if installed from the CD as the "experimental" interface.)

Re:Win2k (1)

jandrese (485) | more than 7 years ago | (#17562600)

3.51 had serious hardware support issues that prevent it from taking the top spot in my book.

Third Party Solutions? (1)

KenAndCorey (581410) | more than 7 years ago | (#17561596)

We have been fighting with this Daylight Saving Time issue on Windows for our application over the past couple weeks. We are now using the Dynamic Time Zones as outlined by Microsoft and it is working fine. It works for 2004 and forward, but isn't so good for historical data.

I've been trying to find a third-party solutions that has historical information and will nicely plug into our C#2.0/SQL Server 2005 application but I've come up blank. Lots of solutions for Linux and C++, but nothing much for C#. Our application is world-wide, so a north-america-only solution will not work.

If you have solved these issues in C# and/or SQL Server, can you please give me your suggestions.

Ken

who cares? (4, Funny)

cashman73 (855518) | more than 7 years ago | (#17561894)

I live in Arizona, you insensitive clod!

How about... (-1, Offtopic)

Anonymous Coward | more than 7 years ago | (#17561970)

sucking on my big Alabama black snake

Use UTC, RealTimeIsUniversal=1 (1)

GodWasAnAlien (206300) | more than 7 years ago | (#17561980)

http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html [cam.ac.uk]

To tell Win2K that the hardware clock is UTC,
Set:
HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInfo rmation\RealTimeIsUniversal

Assuming that the hardware clock is local time is plainly a bad idea, and this bug is
unfixed in all versions of Windows.

"2006-07-04: Various Microsoft Windows Vista beta testers have told me that this next-generation operating system still is not capable of running the CMOS clock in UTC. If you are a Microsoft Vista beta tester, please use the opportunity to report this problem to Microsoft. Urge them to at least fully support the RealTimeIsUniversal=1 registry setting that is already partially implemented."

The timezone should only affect clock display, not the machine behavior.

Re:Use UTC, RealTimeIsUniversal=1 (2, Informative)

Sexy Commando (612371) | more than 7 years ago | (#17562254)

This blog post [msdn.com] explains the reason they keep local time.

Not only in the US... (1)

Bora Horza Gobuchol (585774) | more than 7 years ago | (#17562072)

It's important to note that the change to US daylight savings time does not only affect the US. Canada has changed its daylight savings to match the US [timetemperature.com] , due to the amount of trade that takes place between the two countries. It's not clear if Canada is addressed in the IntelliAdmin patch - it appears localised.

Re:Not only in the US... (1)

freeweed (309734) | more than 7 years ago | (#17562500)

Canada shares mostly the same time zones as the US, so we're *mostly* covered by this patch. There's nothing country-specific (other than some variable names) that I can see.

However, here are the time zones it covers:

It updates Daylight Saving Time (Yes it is Saving, not Savings) in these time zones:

-Alaska Standard Time Zone
-Central Standard Time Zone
-Eastern Standard Time Zone
-Mountain Standard Time Zone
-Pacific Standard Time Zone


Notably absent are the Atlantic time zone, and Newfoundland time zone. So it doesn't cover all of Canada.

3 cheers for NTP.

DLST and Cingular (1)

spotdog14 (877656) | more than 7 years ago | (#17562086)

Man, Cingular cannot even get my voicemail time right when daylight savings time kicks in normally, i just cant wait till this happens.

The fix (2, Informative)

Werrismys (764601) | more than 7 years ago | (#17562088)

1. turn off daylight time saving

2. net stop "windows time"

3. net time /setsntp:some.ntp.server

4. net start "windows time"


done. Works as long as the locale and tz on ntp server are set correctly.

Re:The fix (1, Insightful)

Anonymous Coward | more than 7 years ago | (#17562728)

You clearly do not know how NTP works!
Good luck with your solution...

History? (3, Informative)

nurbles (801091) | more than 7 years ago | (#17562158)

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.

Re:History? (1)

pe1chl (90186) | more than 7 years ago | (#17562796)

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.

It doesn't. But that is because MS Windows has never done this correctly, even when the DST date does not change.
Unix systems with a modern timezone library keep history about DST changes, and they can even be prepared for future algorithm changes as soon as they are decided, instead of having to be patched at exactly the right moment (after the last old-rule change and before the new rule takes effect).

It seems Windows users are not really interested.

Oh dear. (5, Funny)

Rob T Firefly (844560) | more than 7 years ago | (#17562292)

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...

As long as the patch can be uninstalled.... (1)

mark-t (151149) | more than 7 years ago | (#17562580)

... once they realize it how stupid an idea it was to change the dates for DST in the first place.

But hey, I guess they just gotta learn the hard way, don't they?

Re:As long as the patch can be uninstalled.... (1)

KenAndCorey (581410) | more than 7 years ago | (#17562684)

They haven't figured out that DST itself is a stupid concept, so they won't realize changing the dates is stupid either.

And even if they do, they'll claim it is a new and better way.

Simple Reg Fix... (1)

Sinbios (852437) | more than 7 years ago | (#17562608)

I've been looking into this issue, and all it takes is a simple registry patch, as outlined in the Microsoft article, which was simple enough to follow. I don't see why they had to make a program with an installer. Maybe to leave their name on the patched systems?

The ability to change it for many computers is interesting, but you have to pay for their Network Administrator program as well as install it on each computer. A better solution (which is what I've done) is to just implement the patch via Domain Group Policies.

Not Surprising, Microsoft Doesn't Care.. (1)

SgtPepper (5548) | more than 7 years ago | (#17562626)

Given their attitude [msdn.com] .

Not just a US Problem (0)

Anonymous Coward | more than 7 years ago | (#17562688)

This patch has to be applied to any computer that ever wants to travel into a part of the US / Canada.
For the person living in Arizona, if you ever travel to Texas during DST and you look for your system to beep so you get to that 8 AM meeting - you will never be on time. Now that you are in the Central Time Zone and your system is NOT patched - your are now 1 hour late / early for the meeting.

As for manual changing, that means you get to change it 4 times every year - once when it is right and then again when the OS thought it should change in the spring - and again in the fall. Now if jobs kick off at night to run and you are not precisely there to change the system clock then how many jobs might run twice. It also means that all systems must constantly - like every second - check the master system to see the clock change - think about the traffic required to constaly check when the time changes.

Add to the mix, the patch issued by MS in NOV 2006 does not work. If you install it on a system that has a system date at time of install AFTER March 11 2 AM 2007 - when it gets to the fall time change it goes into an enless loop of falling back from 2 AM to 1 AM. The only way it does NOT is if you let that system FIRST pass through the March 11 2 AM spring foward.
True for XP, 2003 servers (DC or member).

tom @ taphilo.com
www.taphilo.com

Expected? (0, Troll)

Coppit (2441) | more than 7 years ago | (#17562718)

Go easy on Microsoft. Way back in 2000 they didn't know how to properly count dates.

</sarcasm>
Load More Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account

Loading...