Time change to bring computer glitches
For three weeks this March and April, Microsoft Corp. warns that users of its calendar programs "should view any appointments ... as suspect until they communicate with all meeting invitees." Wow, that's sort of jarring — is something treacherous afoot?
Actually, it's a potential problem in any software that was programmed before a 2005 law decreed that daylight-saving time would start three weeks earlier and end one week later, beginning this year. Congress decided that more early evening daylight would translate into energy savings.
Software created earlier is set to automatically advance its timekeeping by one hour on the first Sunday in April, not the second Sunday in March (that's March 11 this year).
The result is a glitch reminiscent of the Y2K bug, when cataclysmic crashes were feared if computers interpreted the year 2000 as 1900 and couldn't reconcile time appearing to move backward. This bug is much less threatening, but it could cause head-scratching episodes when some computers are an hour off.
The problem won't show up only in computers, of course. It will affect plenty of non-networked devices that store the time and automatically adjust for daylight saving, like some digital watches and clocks. But in those instances the result will be a nuisance (adjust the time manually or wait three weeks) rather than something that might throw a wrench in the works.
Cameron Haight, a Gartner Inc. analyst who has studied the potential effects of the daylight-saving bug, said it might force transactions occurring within one hour of midnight to be recorded on the wrong day. Computers might serve up erroneous information about multinational teleconference times and physical-world appointments.
"Organizations could face significant losses if they are not prepared," the Information Technology Association of America cautioned this week.
Dave Thewlis, who directs CalConnect, a consortium that develops technology standards for calendar and scheduling software, said it is hard to know how widespread the problem will be.
That's because the world is full of computer systems that have particular methods for accounting for time of day. In many, changing the rules around daylight saving is a snap, but in others, it may be more complex.
"There's no rule that says you have to represent time in a certain way if you write a program," Thewlis said. "How complicated it is to implement the change has to do with the original design, where code is located."
Further confounding matters, there are lots of old computer programs whose original vendors don't support them anymore, meaning there's no repair available. Some gadgets, such as VCR clocks, may not have any mechanism to update their software.
Also, the change originated in the United States and is being followed in Canada, but not most other nations. That could befuddle conferencing systems and other applications that run in multiple countries at once.
In our hyper-networked age with data synchronizing on the fly — each year, it seems, there are fewer clocks that we have to manually change for daylight-saving time — it might be hard to imagine that computers' time could fall out of whack. After all, computers seamlessly keep their clocks in line by occasionally checking with "time servers" run by the government and other parties.
But what those time servers provide is "Universal Time" or Greenwich Mean Time. You tell your computer where in the world it is, and it performs the requisite adjustment to Universal Time. PCs on Eastern Standard Time now are subtracting five hours from Universal Time, but in daylight-saving time they will subtract four.
A common fix is a "patch" that reprograms systems with the updated start and end dates for daylight-saving time. Some of these updates are targeted at specific systems, while others have wider implications — such as one from Sun Microsystems Inc. for older versions of the Java Runtime Environment, which often fuels applications on computers and Web pages.
Microsoft planned to send its daylight-saving patch to Windows PCs with the "automatic update" feature Tuesday. Users with automatic updates turned off should download the patch from Microsoft. (New machines running Windows Vista are immune, since Vista was finalized after the 2005 law passed.)
However, computers running anything older than the most recent version of Windows XP, known as Service Pack 2, no longer get this level of tech support. Owners of those PCs should go into the control panel and unclick the setting that tells the machine to automatically change the clock for daylight-saving time. They have to make the change themselves when the moment arrives. (This is a sizable population; according to Gartner, Windows 2000 alone was still running 14 percent of PCs worldwide last year.)
For people who store their appointments in Microsoft Outlook or other desktop-based calendar programs — rather than dynamic, Web-based programs such as Google Calendar — the situation gets trickier. Patches for calendar programs are available, but appointments entered before a patch was applied might still be registered in standard time rather than daylight time — off by an hour.
Microsoft advises heavy calendar users to go online and download a small program known as "tzmove" — Time Zone Move — that can retrofit all previously booked appointments to the new daylight-saving rules. Other vendors offer similar tools for their systems.
Of course, it's likely not everyone would take that step, said Rich Kaplan, a Microsoft customer service vice president who oversaw the company's Y2K efforts and heads daylight-saving preparations. Hence Microsoft's advice to be cautious about meetings between March 11 and April 1.
"Because if one person applied the update, and one person didn't," he said, "you could end up there at the wrong time."
WHITE HOUSE TRIAL CONTINUES
Libby trial sheds light on White House
WASHINGTON - Sworn testimony in the perjury trial of I. Lewis "Scooter" Libby has shone a spotlight on White House attempts to sell a gone-wrong war in Iraq to the nation and Vice President Dick Cheney's aggressive role in the effort.
Special prosecutor Patrick Fitzgerald rested his case against Cheney's former chief of staff on Thursday in a trial that has so far lasted 11 days. The defense planned to begin its presentation Monday.
The drama being played out in a Washington courtroom goes back in time to the early summer of 2003. The Bush administration was struggling to overcome growing evidence the mission in Iraq was anything but accomplished.
The claim about weapons of mass destruction that was used to justify the U.S.-led invasion in March 2003 had not been supported. Insurgent attacks were on the rise. Accusations were growing that the White House had distorted intelligence to rationalize the invasion.
Trial testimony so far — including eight hours of Libby's own audio-recordedd testimony to a grand jury in 2004 — suggest that a White House known as disciplined was anything but that.
What has emerged, instead, is:
_a vice president fixated on finding ways to debunk a former diplomat's claims that Bush misled the U.S. people in going to war and his suggestion Cheney might have played a role in suppressing contrary intelligence.
_a presidential press secretary kept in the dark on Iraq policy.
_top White House officials meeting daily to discuss the diplomat, former ambassador Joseph Wilson, and sometimes even his CIA-officer wife Valerie Plame.
Libby is accused of lying to the FBI and the grand jury about his talks with reporters concerning Plame. Libby got the White House press secretary to deny he was the source of the leak. He says he thought he first heard about Plame's CIA job from NBC's Tim Russert.
But after checking his own notes, he told the FBI and the grand jury Cheney himself told him Plame worked at CIA a month before the talk with Russert, but Libby says he forgot that in the crush of business.
Cheney already was helping manage the administration's response to allegations that it twisted intelligence to bolster its case on Iraq when Wilson's allegation — in a New York Times op-ed piece on July 6, 2003 — came into his cross hairs.
Cheney told Libby to speak with selected reporters to counter bad news. He developed talking points on the matter for the White House press office. He helped draft a statement by then-CIA Director George Tenet. He moved to declassify some intelligence material to bolster the case against Wilson.
Cheney even clipped Wilson's column out of the newspapers and scrawled by hand on it: "Have they done this sort of thing before? Send an ambassador to answer a question? Do we ordinarily send people out pro bono to work for us? Or did his wife send him on a junket?"
Cheney and Libby discussed the matter multiple times each day, according to Libby's grand jury testimony.
A former Cheney press aide, Cathie Martin, testified she proposed leaking some news exclusives but was kept partly in the dark when Cheney ordered Libby to leak part of a classified intelligence report. Later she arranged a luncheon for conservative columnists with Cheney to help bolster the administration's case.
"What didn't he touch? It's almost like there was almost nothing too trivial for the vice president to handle," said New York University professor Paul Light, an expert in the bureaucracy of the executive branch.
"The details suggest Cheney was almost a deputy president with a shadow operation. He had his own source of advice. He had his own source of access. He was making his own decisions," Light said.
Wilson had written that he had not discovered any evidence that Iraqi leader Saddam Hussein was seeking uranium in Africa. Wilson also asserted that the administration willfully ignored his findings.
Bush mentioned the unsubstantiated Africa connection in his State of the Union address in 2003. The White House and the CIA disavowed the 16-word assertion shortly after Wilson's criticism appeared in print.
A week after Wilson's article, his wife's CIA employment was disclosed in a column by Robert Novak, who wrote that two administration officials told him she suggested sending the former ambassador on the trip.
The disclosure led to a federal investigation into whether administration officials deliberately leaked her identity. Her job was classified and it is a crime to knowingly disclose classified information to unauthorized recipients.
Libby, 56, is not charged with that. He is charged with lying to the FBI and obstructing a grand jury investigation into the leak of Plame's identity. Libby is the only one charged in the case.
Cheney was upset by Wilson's suggestion that his trip was done at the vice president's behest and that the vice president had surely heard his conclusions well before Bush repeated the Niger story in his speech.
The CIA later said Wilson's mission was suggested by his wife but authorized by others. The agency said Wilson's fact-finding trip was in response to inquiries made by Cheney's office, the State Department and the Pentagon.
Testifying for the prosecution, former White House press secretary Ari Fleischer said he was surprised to find the administration was backing off the 16 words that he had been defending. He said it wasn't the first time he spoke of the administration's position with great certainty, only to find it had changed and nobody had bothered to let him know.
Fleischer acknowledged passing along Plame's identity to two reporters. But he testified he did not know at the time that her CIA job was classified.
According to prosecution testimony, Libby had conversations about Plame's identity with Cheney as well as with a Cheney spokeswoman, a undersecretary of state and two CIA officials before he talked to Russert. In addition, former New York Times reporter Judith Miller and former Time magazine reporter Matthew Cooper testified that Libby discussed Plame's CIA employment with them.
Russert, the final witness for the prosecution, flatly denied Libby's assertion that the two had discussed Plame before Novak's column appeared.
On the grand jury tapes, Libby also described steps that Cheney took to use parts of a 2002 National Intelligence Estimate, a classified assessment of Iraq's weapons capabilities, to rebut Wilson.
Among those not informed about this Cheney maneuver, according to the Libby tapes, were then-White House chief of staff Andrew H. Card Jr., then-CIA Director George J. Tenet and then-national security adviser Condoleezza Rice.
"What was interesting to me was what appears to be the total involvement of the vice president," said Stephen Hess, a presidential scholar who worked in the Eisenhower and Nixon White Houses. "If he's down to micromanaging news leaks and responses at that level, I found that quite astounding."
Meantime, it's become clear that Deputy Secretary of State Richard Armitage was the first to disclose Plame's work to reporters — Washington Post editor Bob Woodward and then Novak. Armitage says it was a mistake, claiming he didn't know her job was classified.
Ultimately, he, Fleischer and special presidential adviser Karl Rove all have acknowledged talking to reporters about her. According to testimony, at least six reporters were privately told by top administration officials of Plame's connection with the CIA.
Share with your friends: |