Year 2000 FAQs
Q: What if my BIOS/software/hardware is not Y2K-compliant?
A: It depends on purpose of the system. You should be mostly concerned about finance/accounting, database software and systems used as servers, while consequences for stand-alone PCs should be less serious. An easy way to fix a stand-alone PC with an incompatible BIOS is to set the date manually in the year 2000 if it fails to make an automatic roll-over. (see AMI simple Y2K fix above)
Q: Why does my system with a Y2K-compliant FIC motherboard fail Y2K test? I use X utility.
A: Use the free NSTL utility (see the table above) to verify Y2K compliance of the board. The utility you are using now probably accesses RTC directly, which is inappropriate. The proper way for software to obtain system time is through BIOS.
Q: Is there any simple way to determine if my BIOS can handle post-2000 dates?
A: The best is to use one of shareware utilities widely available on then Net. In absence of those, you can set your date to Dec 31 1999, 12:58 p.m. Shut your machine down for five minutes, reboot and check the computer clock. (after checking, reset the date setting back to the present). You can repeat the procedure without shutting the system down, but in both cases beware that moving back in forth in time is much safer with a dedicated software utility (for AMI BIOS, get AMI2000.com).
Q: My BIOS fails Rollover Test (Direct I/O). So does this mean my system is the Y2000-incompatible?
A: Operating systems and software applications in great majority of cases obtain system time via BIOS and that is why the Rollover Test (Direct I/O) is not something you should be concerned about - only applications and operating systems that access Real Time Clock (RTC) directly are in danger. Check your OS documentation and applications. Hypothetically a problem would happen if during rollover your system is powered on and there is an application that obtains time from RTC.
Another test (Real Time Clock Rollover Test (BIOS)) will be completed successfully. Some demo utilities are designed to "aggressively" promote the Y2000 awareness and therefore detect incompatibility "problems" even when these are very unlikely to occur.
Q: Is X software Y2000-compliant?
A: Please check
with the X software manufacturer. Here we can only mention that Windows 3.51, Windows 4.0
(with proper fixes) and Windows98 will be able to recognize the most common BIOS problem -
BIOS failing to properly display century bits in system date (so 2000
becomes 1900). The three operating systems will recognize this failure
and automatically correct the year value in system clock. This fix will work only during
the year 2000. Check Microsoft's Web site for patches and updates for your applications.
For other applications, you should be aware that they work with other applications who supply them with dates. For example, your Access database might have some OLE-links to incompatible software applications. Or you might have written some macros that use incompatible date format.
Therefore make sure that all parts of your critical system environment can handle four digit year dates.
Q: What about 486 and old Socket 7 motherboards which aren't Y2K-compatible?
A: Like other vendors, FIC does not provide full support for outdated products. Customers are not advised no leave Y2K-sensitive applications running on non-compliant systems. However, FIC does provide BETA BIOS updates for most 486- and early Pentium-based motherboards. For more information, see 486 FAQs.