[Fair Use: For Education and Research Purpose Only]

And you thought Y2K was all over

By SEAN O'SULLIVAN,Staff reporter

02/21/2000

For those who may have stockpiled bottled water, cans of Spam and batteries in anticipation of a widespread computer meltdown on Jan. 1: You've got one last chance to use your bunker.

It's "the Leap Year bug."

Call it the last hurrah for Y2K. Experts say this is the last of the anticipated computer glitches because of the new millennium. The potential problem comes because 2000 is an unconventional leap year, and some computer programs may not account for February's having 29 days.

The rule is that, when the year is divisible by 4, it is a leap year. The exception to the rule is the "00" year of a century, such as 1900. But the exception to the exception is a "00" year divisible by 400, such as the year 2000.

The President's Council on Year 2000 Conversion has delayed closing shop until the date has passed.

But fear not. The fix-it-up panic over Y2K -- where citizens, governments and businesses scrambled to update their computers -- probably has killed the Leap Year bug.

In testimony to Congress last month, John Koskinen, chairman of the Council on Year 2000, said he does not expect major national problems.

Most programs that fixed the year 2000 rollover also fixed the Leap Year bug, said Betsy Mackenzie, director of computer-system security at the University of Delaware.

Even if they didn't, she said, the worst problem she expected was that computer users may have to reset their machines' date on March 1.

On Feb. 29, affected machines will think it is March 1. The Y2K bug was expected to shut down computers and scramble data, thinking the year 2000 was 1900.

"It is not quite as ominous as Y2K," Mackenzie said. "I wouldn't make such a big deal out of it."

And once humankind gets past the Leap Year bug, Mackenzie said, there is one more surprise down the line.

Computer experts at UD noticed that a newly acquired statistics program might have trouble calculating a year with five digits.

"It has a year 20,000 problem," Mackenzie said.

So if the Leap Year bug fizzles, you can hold onto those bottles of water, cans of meat and batteries for Y20K.

Reach Sean O'Sullivan at 324-2777 or sosulliv@wilmingt.gannett.com http://www.delawareonline.com/news/2000/feb/story302212000.html

-- Dee (T1Colt556@aol.com), February 21, 2000

Answers

I opened canned veggies tonight, that I purchased in Dec. 98 (my stash of course). I labored long and hard over the expiration dates. Afeared, that we would collapse instantly, if said product was one day, from the "Labeled expiration date". Then I had the fortune to run across a set of the "Fox Fire" books. Long ago, people canned their foods, and did not die if they ate it six months, one year, or two years from conception. Expiration date is (in most cases) only another ploy to convince the consumer to toss it out and go buy another. Course they had more Faith, back then.

-- Info hog (g@theringinfo.com), February 21, 2000.

Info Hog -- you just figured this out? Most canned food will last for years. The problem is that after a while it starts to taste like S***

-- E.H. Porter (just@wondering.about it), February 21, 2000.

I found a can of B&W Boston Brown Bread in the back of my pantry that was 11 years old!!! I had written the date on it like I do with everything but this one got lost in the shuffle. I called the company's 800# & they said it would be just fine....and it was! I also found an open pakage of Marie Callender corn bread mix that was 5 yrs old. I made a batch of muffins with it as an experiment & they were OK too. They were a little less tasty than the fresh batch I made but they were edible. I think the expiration dates are mainly a legal liability thing for the food companies. Also, I think some of the food looses some nutritional value after a while. The key is to inspect EVERYTHING before you use it...even stuff that hasn't expired yet. Carolyn

-- Carolyn (94301@aol.com), February 22, 2000.

Good advice Carolyn.

-- Dee (T1Colt556@aol.com), February 22, 2000.