Systems were built with the anticipated life span of five to seven years. But, in our company, the average software is 20 years old. It is mainly the older models and software that will be affected. But, in order to determine for sure whether or not a computer is year 2000 compliant, the best way is to run a test by setting the clock for a few minutes before the year 2000. If the hardware is noncompliant, the software must either be prepared or replaced.
Testing can be a problem, however, when a number of systems are interrelated.
It would be basically impossible for a bank to shut down its ATMs for one day, refusing service to people who want to withdraw money. According to Smallberg, there are systems available for companies to rent in order to test their own computers, but they're all booked up through the next couple of years. With less than two years left, organizations and companies are frantically trying to devise a plan to prevent computer meltdown. Unless other companies and businesses also adopt similar agendas to convert any noncompliant systems, a virtual nightmare will ring in the new year. The reason why many haven't done anything to prepare is because they haven't moved out of the denial stage.