Earlier daylight-saving time could pose problems

First there was Y2K. Then came the plagues of viruses and worms. Now computer experts must cope with an extra hour of sunshine.

On March 11 at 2 a.m., most of the nation will switch to daylight-saving time — three weeks sooner than normal, thanks to the Energy Policy Act of 2005.

While that additional hour may be good news for the winter-weary, the changeover could cause headaches for businesses and others who operate computer networks.

The issue isn't nearly as complex as the Y2K problem seven years ago when computer experts feared havoc in systems not programmed to read "2000." But this year's changeover has prompted warnings from analysts and spurred computer managers to assess their systems' vulnerabilities.

Experts say most consumers have little to fear, other than perhaps a missed appointment because their electronic calendars aren't reset to the correct time.

But businesses that haven't addressed the issue could face problems.

"There is some potential for business disruption," said Cameron Haight, an analyst for Gartner Inc. in Austin, Texas.

"It's nothing like the Y2K event where you had to search through all your applications for date fields. ... But anything that takes its time from an operating system will have some degree of risk."

Most potential pitfalls aren't enough to shut down a computer system but could range from minor annoyances to major hassles.

If, for instance, banks don't make the appropriate adjustments, ATM withdrawals or credit-card payments might be recorded at the wrong time.

Brokerages might execute automatic stock trades at the wrong hour. Airline flight schedules could be affected, especially if foreign carriers don't update their systems.

BlackBerry users could find that their handhelds incorrectly sync with their calendars, causing missed appointments. Companies using Internet-based phone systems could find voice mails logging an incorrect time.

Mike Dillon, chief technology officer at Sacramento-based Quest Technology, which installs and maintains computer systems, said as many as 100 of his clients face some glitches if the problem isn't addressed.

"Not everyone is scheduling enough time to patch all their systems," Dillon said. "A lot of people don't like to put patches on their servers because it could cause other problems."