That's when Reid panicked. As it turns out, his situation is less dire than NEC's first message implied. His model PC hasn't been tested for Y2K compliance, so NEC has yet to decide on a fix. In the worst case, he'll have to manually reset the computer's internal date on January 1, 2000. Reid's uncertainty about his computer illustrates the Y2K problem's potential to strike fear in the hearts of computer users everywhere.
Some panic is inevitable, given the scope of the problem.
But solid information, plus a commitment by vendors to help customers through the maze of compatibility issues, can go a long way toward stabilizing this volatile issue. News Radio Fusion audio primers Computerworld Minute Information wanted Not surprisingly, consumers want to get their computing houses in order. The next-best alternative is to figure out whether each product you use is Y2K compliant. This is where hardware and software companies come in. Sure, you can buy a software tool to test your system's exposure to the millennium bug.