UC Berkeley Year 2000 Information Departmental and Personal Computers: Find and Resolve Y2K Problems
Home | Overview | Readiness Checklists | Computer Advisories | Software Tools | Specific Issues | Recharge Services | Peer Help | Search | Site Map | UCB Y2K Home

This page was last updated early during the year 2000 and some or all of its content may thus no longer be current or accurate.

Overview of the Y2K Problem on Microcomputers & Workstations

What kinds of Y2K problems will you need to resolve? Go


What kinds of Y2K problems will you need to resolve?
There are four major categories of Y2K problems that you may encounter - and will thus need to find and resolve - on departmental microcomputers and workstations and on personally-owned computers used for campus business:
Hardware

The various hardware components inside your microcomputer or workstation which keep track of the date and time.
Generally minor. Generally straightforward.

Nearly all PCs manufactured in 1996 and earlier - and even many newer PCs - will require a minor fix to correct a hardware problem that prevents their internal clocks from rolling over from 1999 to 2000.

Macintoshes and most workstations are claimed by their vendors to have Y2K compliant hardware.

Some very old PCs and workstations may require retirement or replacement due to Y2K compliance concerns because:
  • Their vendors no longer support these models; or
  • Non-compliant application programs must be replaced by newer programs that will not run on these older computers.
More information:
The Y2K Hardware Problem Affecting Many PCs Go
Operating systems

The core "traffic cop" software" running on your computers, which provides the environment in which your application programs can run. Examples include Windows 95 and NT, Solaris, and the Mac OS.
Generally minor. Generally straightforward.

Most PC and UNIX operating systems have minor Y2K issues. Apple claims that the Macintosh's Mac OS is Y2K compliant.

The Y2K problems which affect operating systems can typically be resolved by installing no-cost patches or updates from vendors. (After doing so, very minor Y2K glitches may still remain in a few operating systems.)

More information:
Platform-Specific Y2K Readiness Checklists Go
Application programs

Including both custom programs and commercial off-the-shelf (COTS) programs.
May range from minor to serious. Potentially complex and time-consuming.

Finding & resolving Y2K problems in custom programs, whether developed by the department or an outside vendor, can often involve significant amounts of work and may be costly.

Identifying Y2K issues within the many off-the-shelf programs typically installed on each computer can be tedious and time-consuming. Automated software tools may help speed this task, but are not a panacea.

For this reason, it may be essential to:
  • Identify the computers that are running programs critical to the department's or campus's mission.
  • Prioritize the most important programs used on each computer.
If an important program cannot be made Y2K compliant, the system requirements for a newer replacement program could potentially compel hardware and operating system upgrades or replacements.

More information:
Custom Applications: Finding & Resolving Y2K Problems Go

Commercial Off-the-Shelf Applications: An Overview of Y2K Compliance Issues Go
Commercial Off-the-Shelf Applications: Finding & Resolving Y2K Problems Go
Commercial Off-the-Shelf Applications: Resources for Identifying Y2K Compliance Go
Y2K Compliance Status of Selected Off-the-Shelf Applications Used at UC Berkeley Go

Software Tools for Finding & Resolving Y2K Problems Go
Data files & data sharing methods

Data files at risk for Y2K problems include spreadsheets, database files, and text files containing dates.

Data shared via such means as e-mail attachments, "SneakerNet" (carrying disks between computers), file servers, multiuser databases, client/server applications, and automated flows of data between programs can cause or propagate Y2K problems.
May range from minor to serious. Potentially complex and time-consuming.

Identifying Y2K issues within the many data files found on many computers can be tedious and time-consuming. Automated software tools may help speed this task, but are not a panacea.

For this reason, it may be essential to:
  • Identify the computers that are running programs critical to the department's or campus's mission.
  • Prioritize the most important data files used on each computer.
Identifying potential Y2K issues in the methods by which date-containing data is shared between computers - or even between programs on the same computer - can also be complex.

Departmental support providers may need to work closely with computer users to identify key data files and data sharing methods.

More information:
Data Files: Finding & Resolving Y2K Problems Go
Data Sharing Methods: Finding & Resolving Y2K Problems Go
Software Tools for Finding & Resolving Y2K Problems Go



Find something unclear? Missing? Incomplete? Inaccurate? Or even praiseworthy? Send us feedback about this Web site!

This site is provided by the campus Year 2000 Departmental Computers and Administrative Equipment Subcommittee at the University of California, Berkeley.

Copyright 1999 by the Regents of the University of California.
Disclaimer: The University assumes no liability if the information on this page is used for other than University purposes.