One can only assume that the changes have already been updated on your internet connected computer via automatic update.
I just started listening to the Buzz Out Loud Podcast, and really enjoy it ? thanks for the entertainment. I had a question you all might have some insight into ? maybe not - and I apologize if this is 'off-message' (please kindly point me to the right c|net blog/forum if there's a more applicable one).
Molly blogged about this way back in 2005 (http://reviews.cnet.com/4531-10921_7-6284847.html) ? but there's been very little info since. In a nutshell - this year Daylight Saving Time dates in the US are changing (we ?spring ahead? 3 weeks earlier, and ?fall back? 1 week later).
Having recently started researching this (admittedly, quite late), I am absolutely amazed at the lack of concern out there ? as well as the amount of incorrect information. While the impact for most people will be very minor, I am starting to believe this may have a more significant impact than Y2K. Not because the problem is bigger (far from it), but because nobody is paying attention to it. So, while planes won?t fall from the sky or ATM machines quit working (remember when that happened over Y2K? )... I do think that there will be widespread minor annoyances (such as appointments being an hour off).
The most frightening part about this is the incorrect information being blogged. IMHO, the worst offenders are the ?just use NTP? crew who are either missing the point of the problem or who don't understand how NTP actually works. Plus, any blog posting or article that supports comments inevitably results in the ?just abolish daylight saving time? rants which are annoying and aren?t helping to solve the problem (please don't post those here - while many may agree with you, we aren't likely swaying any governments today).
To see the problem first-hand ? open your calendaring program. Open an appointment from the affected time (after March 11 at 2:00am and before April 1). Save this as an iCalendar format (you can ?forward as iCalendar? from Outlook, then save the .ics file attachment without actually sending the message -- I believe other calendar programs work similarly). Do the same thing for an appointment AFTER April 1.
Now, open the two .ics files in an ASCII text editor and compare. Look for the ?DTSTART:? and ?DTEND:? lines. These will be in UTC. Are they correct? If they aren?t, you will have a problem 3/12. Patches are being made available, but I think without some sense of urgency in the tech community at large, many people will fail to properly patch systems and March 12 will be a very annoying day in the life of IT.
Being a computer guy I am mostly paying attention to the systems I am involved in. I am also curious about the gadgets, though. Those brilliant gadgets that set their own clock (some VCRs, clock radios, standalone clocks, etc.) ? are they brilliant enough to handle this, or are they going to have a problem?
The last time a major change was made in the US regarding the observance of daylight saving time was 1986 (a time I remember well - while at least 1/3rd of the BOL crew may not have been born yet). We were far less dependent on computer systems, and we had far less systems that automatically adjusted their representation of time to reflect daylight saving time. Given today?s tech climate, this could be a rather significant, yet frighteningly underrated, event.
I feel like an alarmist when I talk to people about this, but I'm really not. I mean, those canned goods stock-piled in my basement were just on sale for a really good price. But, the more I talk to people about the problem, the more I think this could be quite significant.