Time Change Tough on Some Tech
614913
By Edward D. Murphy staff writer  March 11, 2007, may not have the ominous overtones of Jan. 1, 2000, but the date could cause a few of the headaches that people worried would come with the new millennium.
584470
Enterprises face dual 2005 deadlines relating to RFID and supply-chain data synchronization. Those that haven&#39;t moved forward with a product-information-management strategy will be under-prepared to realize RFID&#39;s value.
414044
Smart phones will need a software update to know when to adjust to DST, but TiVo owners needn't worry about missing an episode of 24.
335646
By Andrew Kantor, The Roanoke Times, Va.  Mar. 10--Daylight-saving time arrives early this year, and some local companies are preparing for the potential pitfalls it brings.
145509
It's not just cell phones taking advantage of a time standard. The National Institute of Standards and Technology (NIST) in Boulder, Colo., sends out a radio signal that any properly equipped device in much of North America can pick up and use to set itself to the proper time.
644886
THERE is never a right time to buy technology. Something cheaper, faster and better specified will be on the market before you have even got your product out of its box.
501728
Jet lag isn't just caused by time zone shifts.
628025
This weekend's early switch to daylight-saving time was billed as a little re-enactment of the Y2K computer problem at the turn of the millennium. And as it happened, the daylight bug appeared to have equally minor results.
143482
Microsoft can change.  Just give it a few more decades.
277799
faq With the change coming later this year, follow these steps to help ensure that you're on time.
381893
By The Columbus Dispatch, Ohio  Feb. 20--Many people will remember the Y2K anxiety spawned by fears that the world's computers would be unprepared to make the date change from 1999 to 2000.
612406
(InfoWorld) - The new DST (daylight-saving time) is drawing near. Do you think you're ready? Run down this checklist to be sure. 1. Do a datacenter inventory. You need to know exactly which applications and systems you have running so that you can locate appropriate patches and fixes. 2. Find out what needs to be patched. That could take some time. Fortunately, many of the big-name vendors have prepared (even if you haven't). Below is a list of DST resource sites for various companies. Most, if not all, include lists of solutions that will be affected. Apple BlackBerry Cisco Dell Hewlett-Packard IBM Microsoft McAfee Novell Oracle Palm Red Hat Sun Symantec Also be sure to update your JRE (Java Runtime Engine), as apps running on older versions of JRE may report incorrect times. Info is available here. If one of your vendors isn't listed above, check out their Web site or call their help desk as soon as possible and ask about DST patches. 3. Devise a game plan. Mission-critical, time-sensitive applications should take priority, but also consider software -- such as firewalls -- that isn't time sensitive but that feeds time-sensitive information to other programs, such as security event management products. 4. Deploy patches or, where necessary, manual fixes. Use your centralized software management toolbox such as Microsoft Systems Management Server or Novell ZenWork Patch Management (if you have one). Otherwise, you'll have a lot of manual patching to do. 5. Test your patches and fixes. Be certain you come up with proper times and dates. You also have to check that your applications are interacting properly. 6. Make sure your partners and service providers are prepared. Just because you've done your due diligence and updated your systems doesn't mean one of your critical suppliers, for example, has. 7. Schedule IT personnel to come in on March 11. Try as you might to prepare, it's entirely possible something will slip through the cracks. Have IT staff on hand to check the status of systems, run tests, and fix problems.
244505
By Stephen Speckman Deseret Morning News  Computers can keep track of time just fine. That is, until we humans start to monkey around with how to set a clock.
571500
The technology company's move gives cause for pause until you take a closer look.
133929
For IT managers in the U.S., the early switch to daylight-saving time in March will require testing and potentially patching of all systems and applications that rely on time stamps.
447850
SAN FRANCISCO - Daylight-saving time begins Sunday, three weeks sooner than usual. Time to spin the dial on the kitchen clock - and to brace for computer problems. The early start wasn't programmed into many electronic devices. That's created plenty of work for Luis Rodriguez, a software director at IBM, and David Woelfle, an enterprise architect at Electronic Data Systems. The two tech experts have helped dozens of companies update computer systems for the change.
383301
With Daylight Saving Time going into effect this year on March 11, IT vendors are scrambling to prepare patches, work-arounds and other fixes for their products. Here's what some major vendors are doing.