It is highly recommended that you get in contact with your system supplier and the BIOS manufacturer to understand the scope of this problem. If you have a BIOS that has a different kind of Year 2000 problem, you will likely need to contact the BIOS manufacturer.

Manually set date. If a desktop has the most common BIOS problem, and is running an operating system that does not automatically fix this problem, it is possible to manually set the date once and have the system work properly from that point forward. In fact, this will be the most common fix for the home user. For many large organizations where it is too time-consuming to touch every desktop, IS departments will disseminate to the end users the instructions necessary to manually set the system clock once after the year 2000. They will prepare their helpdesks for the flood of calls and will rely on their contingency planing of monitoring critical data feeds to ensure that all desktops have made the move properly.

Make use of Microsoft programmatic solutions. Windows NT 3.51 service pack 5, Windows NT 4.0, Windows NT 5.0, and Windows 98 have a BIOS fix for the most common problem. (See Question #10)

Make use of third-party programmatic solutions. Many companies produce products to assist in dealing with the BIOS problem. Microsoft provides a list of BIOS fix vendors in the Tools Guide located at http://www.microsoft.com/year2000.

Plan contingencies. Appropriate contingency planning for this problem will require the monitoring of critical data feeds. In many cases, applications will stamp a form or a transaction with the current system date. This will allow for monitoring on the back-end for BIOS failure dates (See Question #10) which will tell you that there are PCs which have not made the switch properly.