February 16, 2007 4:00 AM PST
Wake up to the 'daylight saving' bug
- Related Stories
-
Vista for the masses
April 4, 2007 -
Gadget owners beware: Daylight saving time has changed
February 16, 2007 -
Microsoft extends support for XP Home, XP Media Center
January 24, 2007 -
Daylight-saving change could confuse gadgets
August 8, 2005 -
Windows 2000 moves to the back burner
June 28, 2005 -
Lotus takes note of Y2K bug
January 10, 2000 -
A sprinkling of Y2K troubles
January 4, 2000
(continued from previous page)
Another problem: many businesses still use software for which Microsoft has ended the main support period. Windows 2000 and Windows XP prior to Service Pack 2 are no longer supported, for example. The same goes for older versions of Exchange and Windows Server. Microsoft offers "hotfixes," or patches targeting the specific daylight saving issue, for those systems for a flat $4,000 fee, Sweatt said.
And that's just Microsoft. Other vendors also have updates. Oracle is providing daylight saving fixes for several of its applications, its database and its Java Virtual Machine. In addition, Sun Microsystems' Java Runtime Environment also stores rules about DST observance all around the globe, and Sun recommends that people update Java to avoid trouble.
| Provider help These software makers are among those companies supplying online help with the DST shift. |
| IBM |
| Microsoft |
| Sun |
| Apple |
| Oracle (for customers only) |
While the operating system and Exchange are primary concerns, the Java update is causing the most headaches for Byle, the systems engineer at an insurance company. "Given that there are over 50 versions of Sun Java alone that could be in your environment, the OS and Exchange stuff doesn't seem too bad," he said.
Many application vendors, such as IBM and Oracle, include a custom version of Java in their applications. These also need to be updated for daylight saving time compliance. While many applications get their time information from the operating system, there are also applications that rely on additional software, such as Java, to stay on time.
Mac users also have to get on board. Apple said it fixed the daylight saving time problem for Mac OS X Tiger, the most recent edition of the operating system, in a February 2006 update. It posted a fix for Mac OS X Panther, an earlier version, on Thursday.

Also on the list is the challenge of centrally updating mobile devices such as laptops and smart phones. Without a fix, calendars on those devices will show appointments at the incorrect time.
"My stupid calendar-synching phones--I haven't a clue how to automate the deployment updates to Windows mobile phones," said Susan Bradley, a network administrator at an accountancy firm in Fresno, Calif. "So far, I've had to manually update them, and I don't know how larger firms will handle this."
Also, networking hardware may not be ready for the daylight saving time change, which may impact the logging of activity such as who accesses the network and when, Bradley said. Some enterprise hardware makers, such as Cisco Systems and Juniper Networks, have provided online guidance for customers.
To soften the impact, Microsoft recommends users of its products to pay extra attention to meetings and appointments scheduled between March 11 and April 1, as well as between October 28 and November 4. (The daylight saving time change means the clock is going to be turned back on the first Sunday in November instead of the last Sunday in October.)
"Users should view any appointments that fall into these date ranges as suspect until they communicate with all meeting invitees to make sure that the item shows up correctly on everyone's calendar both internally and externally," Microsoft has advised.
At Bradley's accounting firm, the IT team is telling employees to confirm the time of an appointment in the subject line of every meeting request as a workaround.
"When I talk to folks, no one has a clue this is coming and is just assuming it will magically work," Bradley said.
See more CNET content tagged:
Y2K, Forrester Research Inc., Gartner Inc., SuSE, information technology
55 comments
Join the conversation! Add your comment (Log in or register)
You see what the MORON's in the House did today? What will these Genius' do next?
If you don't bother to understand what's going on around you, maybe you should "keep your mouth shut and just not raise your hand".
Sorry All~ Just my Rant!
than just fix the DST schedule. You can change the clock in a Mac
without a restart as much as you want. An OS update from Apple
always requires a restart.
On the other hand, they also deserves to pay top dollars for their incompetence!!
ajit kapoor
Sheesh!
talking about daylight savings time is actually standard time.
That's what we are using right now. In the spring, we switch to
daylight savings time.
Most people would prefer to be in daylight savings time all year
round, and since this change adds more days in daylight
savings, it's safe to assume most would be in favor of it. Add to
that the energy savings from the change, and Congress is
actually doing a good thing in this case!
Not a pretty thing when you play with time.
What will be a bigger nuisance for the typical home-user will be all of those clocks, VCR's, TVs, etc, that automatically change for DST. Now they will be wrong and you will have to adjust manually 4 times a year (once to start DST, once to undo the automatic change, once to undo the automatic stop, and once to manually stop DST). Not a disaster - just inconvenient.
Then there is the non-tech nuisances. Unless all other countries that use DST fall in line, it's going to become somewhat confusing to remember what the time change is between different zones.
My own opinion, that said there's a good chance this change will stick if you look at public opinion.
The following should work for most:
1) download a NTP daemon / service app (there is a Win32 version at <a class="jive-link-external" href="http://www.meinberg.de/english/sw/ntp.htm" target="_newWindow">http://www.meinberg.de/english/sw/ntp.htm</a> but I'm sure there are others out there)
2) turn off the auto adjust for DST setting in Time Settings
3) install the NTP service and configure to use the NTP Pool servers (<a class="jive-link-external" href="http://www.pool.ntp.org/" target="_newWindow">http://www.pool.ntp.org/</a>) for time sync [note: if you use the NTP app above it sets this automatically]
4) start NTP service
The main problem is that the older OS's noted just don't know when DST will happen now so just don't let them change anything. If you have your TZ set right then a good NTP client will take care of the rest over night.
Now I have not tested the above except that I do run quite a few systems with NTP updating their time. The DST setting is just to save time on syncing but once it sees that the system is way off it should change the time to match just as if you had set the clock wrong by an hour.
Good luck.
NTP servers use UTC time to set the clock and rely on the local machines to apply the offset for time zones/DST.
Some binaries are poorly-written enough to not use system clocks (Veritas, I'm talking to *you*) which in turn will require an individual patch, but otherwise I've seen no real big problems whatsoever on the *nix side of the house.
'course, folks in Arizona can simply ignore the whole thing... lucky $#@^!s :)
/P
Applications set to run automatically at certain times will not run at the appropriate times if the OS clock is not set properly. Many banks have thousands of servers where the clocks are synchronized from a central source.
Boo hoo is right - I hope I make it through the weekend in 2 weeks.
Applications set to run automatically at certain times will not run at the appropriate times if the OS clock is not set properly. Many banks have thousands of servers where the clocks are synchronized from a central source.
Boo hoo is right - I hope I make it through the weekend in 2 weeks.
They had NEARLY TWO YEARS to put fixes in place for their products, and they wait until THREE WEEKS before it happens to now 'patch' a few things and warn everyone that everything MIGHT be wrong so don't believe any date in ANY of their apps? What a bunch of crap!
M$ has a strangehold on what, 95% of the market and they wait til now to PARTIALLY patch stuff?? If this isn't an abuse of MONOPOLY power I don't know what is! Seriously why do they get away with this? Why wasn't this fixed 6 months ago let alone within a month of the passed legislation??
This is caused and only PROPEGATED by the monopoly. They definitely could have FORSEEN the possibility that savings time could change in the future and make everything store appropriately for an easy patch later? That's typical bad forsight in design that is typical for them! That was like assuming that the sea level will remain constant for the next 100 years and put their Activation Support computer 1 inch above sea level, only to drown and render all those fresh OS installs useless in a couple of years or so!
Your reasoning is flawed, your knowledge of the issues is lacking, and your rant is idiotic. And, anyone who inserts a dollar sign when spelling Microsoft is, indeed, a basher.
<a class="jive-link-external" href="http://www.sia.com/business_continuity/html/dst.html" target="_newWindow">http://www.sia.com/business_continuity/html/dst.html</a>
Exactly the same as the potential for the Y2K problem!
But the Y2K problem panned out to be no problem at all... thus shouldn't this too be gaffed off as another Y2K scare?
NOPE!!!
The ONLY reason the Y2K when over almost flawlessly was because of all the media attention it drew. It caused people to double-check and triple-check to ensure they wouldn't have a problem.
On the other hand... if Y2K wasn't publicized the way it was... it would have turned out to be a much bigger problem.
This is just another similar instance. As long as it's properly publicized and everybody does what's required... it too will blow off as just another scare.
But if people don't take action properly... then it could cause problems... but it's not going to be the end of the world... just a lot of confusion, inability to connect, late transfers, incorrect calendars... a few problems here and there!
But it could cause routers to drop all packets as having been expired causing a virtual Denial of Service with the inability to access anywhere on the internet unless both users and router vendors patch properly.
FWIW
Thank you G. W. B. Thank you congress for passing the stupid law he asked for.
The DST only should affect the clocks and nothing more.
any program that is affected by DST was and is written so badly that it deserves to be decompiled and trashed ASAP anyway.
Just think about it....
All DTS dose is move our ACTIVE day time 1 hour forward and back not the real time.
it is an artificial time frame so we can partake an extra day light at the end of the day.
I sow comment that "well I will need to get up earlier and use some electricity in the morning instead of in the evening so where the savings?" well the savings come in the evening, because when you get up you might use some light then, but later in the day you can keep the artificial light use to a minimum longer then if you would on real time. also the DTS is not only for power savings, it also gives you more daylight
for recreation and it is good thing/
I have seen comments that DST update trashed outlook.
this is a MS fault big time. no schedule or appointment need to be adjusted for DST.
if I have a meeting @ 2:00PM in New York it is still at 2:00PM in New York DTS or not
now my clock needs to change and reflect proper time though. and all internal calculation and checks
need to use my clock and UTC clock to be correct but any appointment and entries should stay the same. nothing is changed for them. if MS have screw-up this they need to fix it ASAP.