Forgot your password?
typodupeerror
Windows Operating Systems Software IT

Unofficial Win2K Daylight Saving Time Fix 299

Posted by kdawson
from the it's-about-time dept.
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."
This discussion has been archived. No new comments can be posted.

Unofficial Win2K Daylight Saving Time Fix

Comments Filter:
  • My fix? (Score:3, Funny)

    by Anonymous Coward on Thursday January 11, 2007 @02:31PM (#17561074)
    I use Zulu time.

    I haven't had an issue yet.
  • Yeah, right (Score:5, Funny)

    by zr-rifle (677585) <zedr AT zedr DOT com> on Thursday January 11, 2007 @02:33PM (#17561126) Homepage
    but what about us DOS users?
  • by celardore (844933) * on Thursday January 11, 2007 @02:33PM (#17561138)
    About time too!

    (Sorry...couldn't resist)
    • Re:and it's.... (Score:4, Insightful)

      by camperdave (969942) on Thursday January 11, 2007 @03:01PM (#17561776) Journal
      I think it's about time that we just split the difference, adjust the clock by half an hour, and leave it there.
      • Re: (Score:3, Interesting)

        by Steve001 (955086)

        The problem with not adjusting the clock is that there are forces that are working to move the clock both forward and backward. In the book "Spring Forward - The Annual Madness of Daylight Saving Time" by Michael Downing, he covers the issue. The back cover of the book lists those who support and oppose Daylight Saving Time (DST).

        Some of those in support of DST:

        • Golfers
        • Major League Baseball
        • Barbecue industry

        Some of those opposed to DST:

        • Farmers
        • Hollywood movie studios
        • Television and radio broad
  • Well... (Score:3, Informative)

    by minvaren (854254) on Thursday January 11, 2007 @02:34PM (#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.
  • clocks (Score:5, Interesting)

    by erbbysam (964606) on Thursday January 11, 2007 @02:35PM (#17561174) Homepage
    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.
  • by WalterGR (106787) on Thursday January 11, 2007 @02:36PM (#17561186) Homepage

    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.

    • by Atzanteol (99067) on Thursday January 11, 2007 @02:55PM (#17561638) Homepage

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

      • 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: (Score:3, Funny)

          by Atzanteol (99067)
          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.

        • by magicchex (898936)
          Um, I checked the first 3 links which all supported what he (truthfully) stated.
        • Re: (Score:3, Insightful)

          by bigdavex (155746)
          You are right. Let's call it a Hognocism [slashdot.org].
      • I can't believe /. has let so many comments slip by without notice.

        It's, "Daylight Saving [wikipedia.org] 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.

        • Sure it is. I have been putting my extra daylight into a savings account, and with the interest accumulated over the years, I have enough to live for at least 6 months without it until I can find some more daylight.
  • by Anonymous Coward
    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.
  • Not Entirely Stuck (Score:3, Informative)

    by Cygfrydd (957180) <`cygfrydd.llewellyn' `at' `gmail.com'> on Thursday January 11, 2007 @02:38PM (#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 (Score:2, Insightful)

    by JerkyBoy (455854) *
    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.
  • by random_dg (1002962) on Thursday January 11, 2007 @02:42PM (#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: (Score:2, Insightful)

      by multisync (218450)

      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.

      • Its become a common thing for MS to do lately. If there is a fix that only affects a handful of customers they will NOT release it publicly. You either have to get a support contract or call their support line and pay for the call. Its quite sickening, especially for a near monopoly organization. I've seen a number of updates on their website that would be nice to have but I'm not going to call them to get it...
  • by SpaceLifeForm (228190) on Thursday January 11, 2007 @02:43PM (#17561364)
    I knew it was just a matter of time.
  • 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?
    • Re: (Score:3, Insightful)

      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...
  • by slughead (592713) on Thursday January 11, 2007 @02:44PM (#17561384) Homepage Journal
    Direct from M$:

    Move to Arizona, Hawaii, or anywhere outside the US.
    • Re: (Score:3, Insightful)

      by Ichijo (607641)
      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.
  • 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.)
  • 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.

  • ...this is probably going to screw up all those bot-nets.
  • 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.
    • by gstoddart (321705) on Thursday January 11, 2007 @03:10PM (#17562002) Homepage
      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

  • 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 a
    • by ocbwilg (259828)
      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 a
  • Win2k (Score:2, Insightful)

    by QueePWNzor (1044224)
    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: (Score:2, Insightful)

      by Chacham (981)
      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.)
      • by jandrese (485)
        3.51 had serious hardware support issues that prevent it from taking the top spot in my book.
  • who cares? (Score:5, Funny)

    by cashman73 (855518) on Thursday January 11, 2007 @03:05PM (#17561894) Journal
    I live in Arizona, you insensitive clod!
  • 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, pleas
  • 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.
    • by freeweed (309734)
      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
  • The fix (Score:2, Informative)

    by Werrismys (764601)
    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.

  • History? (Score:3, Informative)

    by nurbles (801091) on Thursday January 11, 2007 @03:17PM (#17562158) Homepage

    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.

    • by pe1chl (90186)
      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 la
  • Oh dear. (Score:5, Funny)

    by Rob T Firefly (844560) on Thursday January 11, 2007 @03:22PM (#17562292) Homepage Journal
    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...
  • ... 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?

  • So what about Linux and the time change?
    • by Cheeze (12756)
      I don't think Microsoft cares about linux enough to make a patch.

      I bet you could do 5 minutes of research on your own and figure it out though. :P
    • by SgtPepper (5548)
      You're on your own, after all noone is accountable [msdn.com]. Don't you wish you had paid for your software now?
    • Re: (Score:3, Insightful)

      by rg3 (858575)
      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 [ubuntu.com]. So I would say that a simple update in the relevant data files and packages sho
  • You expect more than 7 years of support for a software package that costs $350?

    I'm guessing on the price, I couldn't find any one keeping history on Microsoft products. unlike Apple products where there are mobs of people tracking every piece of trivia.
  • by HappyDrgn (142428) on Thursday January 11, 2007 @04:45PM (#17563998) Homepage
    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 [dbaplace.com])
    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/ [microsoft.com]. 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.

nohup rm -fr /&

Working...