![]() |
||
|
Future Tense: The Year 2000 Problem on Your PC
Washington Post Staff Writer
Don't panic. Yes, the "Year 2000 Problem" is coming, and it's causing thousands of computer programmers to scramble to fix systems whose use of two-digit year shortcuts could make them confuse Jan. 1, 2000 01/01/00 with Jan. 1, 1900. But at home, it's not going to be a big deal.
Why? Basically, there isn't any really "mission-critical" stuff on home computers. We don't use our PCs to run nuclear power plants, we use them to run word processors and Web browsers. And so the worst-case "Y2K" consequences at home are annoying, not life-threatening. For instance, Y2K bugs could rearrange your financial data but they can't void your checking account. E-mail you send could be overlooked by recipients when their e-mail programs sort your message by its circa-1900 date stamp but it will still be delivered. Virus scanners could get cranky at seeing their virus-profile data appear 100 years out of date but viruses won't necessarily swarm over your system as a result. It's not exactly cause for existential dread. Testing, Testing . . .
If you use a PC, by contrast, you face a greater risk. Microsoft's recent operating systems (version 5.0 and up of DOS, Windows 3.1, Windows 95 and Windows 98) are, by themselves, basically Y2K-ready but they all depend on a PC's hardware to track the date and time. A PC, in turn, uses a "real-time clock" to keep precise time, which must then be interpreted by the BIOS (Basic Input/Output System, a small read-only memory chip) and handed off to the operating system. (Most real-time clocks are not Y2K-compliant, but that's all right, since no software ever touches their data directly.) The problem is that many BIOSes can't understand the century transition. If you bought your PC after early 1997, its BIOS is probably bi-century capable; if not, odds are you'll have trouble. The way to know for sure is to download a Y2K testing program. Try 2000 Toolbox Hardware Check, put out by longtime utility developer McAfee and PC Magazine. You can download a free copy at http://hotfiles.zdnet.com/ Dealing With It
The second approach the one used by most Y2K repair tools is to install a small program that runs every time your computer boots up and forces the BIOS into the proper century. Again, your computer's manufacturer should have this available for download at its Web site. (If you bought your computer from a custom-build "screwdriver shop," call the store and ask if it provides such a utility to its customers. It should.) The third option is selective apathy. Continue computing as before, but the first time you start up your machine in the year 2000 before you run any programs open the "Date/Time" control panel (in Windows 3.1, select "Control Panels" in the "Main" program group; in Windows 95, select "Control Panels" off the Start menu's "Settings" item). If your system flunked the century change, your system will say it's Jan. 1, 1980 (Microsoft operating systems assume the earliest possible date they could run is 1980). Reset that date to Jan. 1, 2000, then turn the machine off; wait a minute or two, then turn it on again and verify that the date change has taken hold.
In a tiny minority of cases, however, even that won't work; a few BIOSes simply won't recognize any century but the 20th. You might then have to replace hardware put in a new motherboard or just buy a new PC. Or perhaps it would make more sense to do nothing. "You may decide, 'who cares what the clock says' if you don't do anything with the machine but play solitaire," says Chris Weiss, chief technologist of Greenwich Mean Time-UTA, an Arlington-based Y2K software firm. "Let's get real: Lots of PCs aren't used as anything but a video game controller."
Comments? E-mail mailto:rob@twp.com
© Copyright 1998 The Washington Post Company |
||||||||||||||||||||