RSS
Didn't We Do This Already? IT Folks Worried About New Daylight Savings Time Screwing Up Appointments
from the sounds-familiar dept
Back in 2005, there were some worries going around that after Congress changed the dates for Daylight Savings switches, that computers wouldn't be able to handle it properly, creating a "mini-Y2K" effect (as if there ever were an actual Y2K effect). Of course, it was a total non-story because most computers can handle that sort of thing, and the few that can't can easily be corrected without too much trouble. However, as we get a step closer to this year's Daylight Savings time shift, it appears that the worries are back, with consultants getting the press to talk about the potential for (once again) a "mini-Y2K" while mentioning (of course) that their consulting firms can help. Even IT people are getting into the act, sending out emails warning about potential problems not just with scheduling meetings, but flights and even concerts (say what?). Overall, this problem is a non-starter, but don't be surprised to see more stories warning you, while pointing you at vocal consultants willing to help you solve this "problem."
I have an app...
Top 5 Reasons Why Mobile Analytics Is Important
App Developer Conversations: What Does The iPad Mini Mean For The App Economy?
I have an idea...
Finding Co-Founders in a Recovering Economy
App Developer Conversations: Successful Fundraising Techniques
I have a business...
Why and How Developers Use Mobile Payments: Infographic
To Understand The Data Move It Closer
Reader Comments (rss)
(Flattened / Threaded)
Non starter?
But it reminds me of a time that my wife was flying out of town on a Sunday morning. It was, of course, daylight Sunday but we neglected to adjust the clocks. She grabbed the limo and blithely headed for the airport, at the counter they suggested that she hurry a bit, she got on the plane and they immediately closed the door and left. It was a few hours later that she realized that she was an hour later (or earlier) than she thought she was!
At least I'll be able to use the "daylight chnage" excuse if I miss a meeting inside the change window!
[ reply to this | link to this | view in chronology ]
That would be
[ reply to this | link to this | view in chronology ]
computer industry
[ reply to this | link to this | view in chronology ]
The reason it was so minor was because most companies took the time to fix their systems beforehand.
[ reply to this | link to this | view in chronology ]
Dark mornings
[ reply to this | link to this | view in chronology ]
This is real...
Calendaring and scheduling will be incorrect for 2 windows of time before fixes are applied. One window in March and the other in November.
IT people don't sleep on this one. This time zone change is a problem for many large platforms used by several big companies. Contact your vendors and get the ball rolling because you don't have much time for planning and implementation.
[ reply to this | link to this | view in chronology ]
Re: This is real...
Non-scheduling software (most) can ignore this or depends on the OS user to change the time by one hour.
[ reply to this | link to this | view in chronology ]
Re: Re: This is real...
[ reply to this | link to this | view in chronology ]
Re: This is real...
[ reply to this | link to this | view in chronology ]
Grammar
[ reply to this | link to this | view in chronology ]
uh. how quickly we forget...
Right now, M$ is up to v9 of their DST patch, and its STILL causing so many problems that they wont remove it from the "optional" list. They havent even addressed exchange 2003, let alone announced if they will address exchange 2000.
How is this not a big problem? Because you werent personally affected by y2k?
[ reply to this | link to this | view in chronology ]
instead of changing
Pick one or the other and stick to it. Or, split the difference, let us make one final-and-forever half hour adjustment, and call it a day.
[ reply to this | link to this | view in chronology ]
Think of all those black boxes....
[ reply to this | link to this | view in chronology ]
Re: Think of all those black boxes....
Although I agree with the writer of the story, there were indeed many many postential issues that required us to patch ALL of the servers before this change happened.
[ reply to this | link to this | view in chronology ]
MS screwed up (again)
I'd like to know why we can't turn off DST and sync with a GPS. What is Arizona doing since they don't (didn't?) use DST?
OBTW, MS also suggested scheduling our meetings with a note about what the correct time is supposed to be. They suggested a quill and papyrus, too.
[ reply to this | link to this | view in chronology ]
Re: MS screwed up (again)
[ reply to this | link to this | view in chronology ]
MS screwed up (again)
I'd like to know why we can't turn off DST and sync with a GPS. What is Arizona doing since they don't (didn't?) use DST?
OBTW, MS also suggested scheduling our meetings with a note about what the correct time is supposed to be. They suggested a quill and papyrus, too.
[ reply to this | link to this | view in chronology ]
Re: MS screwed up (again)
[ reply to this | link to this | view in chronology ]
[ reply to this | link to this | view in chronology ]
My only problem...
[ reply to this | link to this | view in chronology ]
New DST Rules According to Microsoft
-PW
[ reply to this | link to this | view in chronology ]
Fucking farmers... making life harder for everyone else.
[ reply to this | link to this | view in chronology ]
Re:
Fucking farmers... making life harder for everyone else.
Most farmers do not support DST. DST is about saving energy in the residential side by making twilight later. Its a farce, promoted by idiots, and should be abolished. It does save energy, but the amount is so little as to not make any siginificant difference, and far more time money and energy is spent in trying to "adjust" twice a year.
Also, the negative impact it has on schoolchildren complete negate its benefits, let alone the increase in traffic accidents.
[ reply to this | link to this | view in chronology ]
Re: Re:
[ reply to this | link to this | view in chronology ]
Re: Re: Re:
DST is not only good for saving energy, it is also good for commerce. People are more willing to shop when it is still daylight.
Well, fine, if that's the real problem, then let's just abolish night.
[ reply to this | link to this | view in chronology ]
This is stupid
Aerospace and military use Zulu time - why can't You?
:P
[ reply to this | link to this | view in chronology ]
A Big Problem
See for yourself:
http://www.microsoft.com/windows/timezone/dst2007.mspx
[ reply to this | link to this | view in chronology ]
Re: A Big Problem
I just used the TZedit.exe utility and it took me about 30sec. to change. Remember it starts on the second Sunday of March and ends of the first Sunday of November.
[ reply to this | link to this | view in chronology ]
Fixed Date? Which DST are you running?
PST = GMT - 8
PDT = GMT - 7
[ reply to this | link to this | view in chronology ]
Use UTC & zoneinfo
It seems to me much of the time-related problems on Windows systems arise from two causes:
UNIX/Linux systems have kept system time in UTC for decades. One consequence of this is that they always know what time it is. And use of zoneinfo means they can always get updates from the source, without having to wait for vendor updates or resorting to low-level patching.
[ reply to this | link to this | view in chronology ]
solution
[ reply to this | link to this | view in chronology ]
DST follies
My beef is that when the MS patch is applied, any Notes calendar (repeating) made before the patch is applied move forward an hour and IBM has a crummy utility that you run on the mailbox after to fix it...if you are doing automated fixes on the workstation, how do you correlate workstation names and user names (products reference differently).
As for the win2000...yes another grab by ms. We used the code in the article and wrote our own automated patch. let's hope it works.
[ reply to this | link to this | view in chronology ]
Add Your Comment