I also got some interesting feedback on other things you'd like to see us do about the Y2K issue.

Before I get into your suggestions, let me say that your support of our coverage of Y2K wasn't unanimous. A vocal, albeit small, minority suggested that we keep our noses to the grindstone and cover more nuts-and-bolts networking issues. One individual suggested that we cover more Unix/Linux and IPv6 stuff. Watch for coverage of IPv6 in our forthcoming State of the Internet feature. We're still debating the right way to cover Linux. It's clear that Linux has some momentum behind it and deserves some coverage.

Predictions and Warnings I particularly enjoyed the variety of concerns over the Y2K issue. One reader predicted that while I was vacationing in Florida, my house would be looted during a blackout and that there would be no ice, sunscreen or guava juice in Florida because of shipping snafus caused by the Y2K problem. The reader also pointed out--on a bit more serious note--that embedded systems were likely to fail, too, and we can assume that these are more critical than VCRs and microwave ovens.

A number of you also sent warnings about thinking of the Y2K problem as an issue for December 1999. While I'm not so naive to think that Y2K problems don't have to be considered now, you offered some great examples. One reader had received a credit card with an expiration date after 01/01/2000. The card was considered expired by various readers, and he was subsequently issued another card with an expiration date of September 1999. Interestingly, my California driver's license has an expiration date in the next millennium. I guess CDOT should get credit for being ahead of the game.

One concern that I hadn't given much thought to was about companies, mostly smaller ones, that don't upgrade their applications regularly. They're probably going to be significantly affected by the Y2K problem and are, very possibly, not thinking much about it at this point. However, as one reader pointed out, these smaller companies are really only inconvenienced by the Y2K problem. They can still run their operations on paper if need be. It's the big companies and federal government agencies that are likely to be shut down by Y2K problems.

The Feds Need a Fix Most large companies realize the risks and are willing to foot the bill for consultants and programmers to come in and fix the problem. The federal government is a different story. As much as Congress would love to legislate the problem away, it can't, and virtually every arm of the government will feel it. The IRS is probably the most reported example, since failure to address its problems could lead to the nation's first flat tax.

Two other systems mentioned by you--our readers--were the FAA air-traffic control system, which is based on outdated IBM computers, and the electrical power grids. Apparently, both systems have not received the attention required. This doesn't bode well for the ice cubes I'll need in Florida, but it does look like I may get a few extra days of vacation because of the messed-up flights.

Finally, one of our readers pointed out the most salient fact about the Y2K problem. He said there are now more lawyers at Y2K meetings than there are consultants and programmers. I guess that means the problem is real--and real expensive.

Look for the Y2K column in our features charts from now on, and as the date draws closer, stockpile water, train a good guard dog and stay off airplanes. Oh, and if you're brave, don't pay your taxes.

Art Wittmann can be reached at awittmann@nwc.com.