Copyright: ® 1996-1998, Greenwich Mean Time. # Lite3.1
Citation: All rights reserved on this material. ® Greenwich Mean Time, 1996 - 1998.


Welcome

Greenwich Mean Time is the established global leader in alerting individuals, businesses and governmental agencies to the dangers associated with the year 2000 PC computer problem - or millennium bug as it is otherwise known.

Greenwich Mean Time has developed a number of software-based diagnostic tools that enable users to identify which year 2000 problems they have. These tools are represented in the marketplace by the Check 2000 brand, which identifies different product bundles developed to meet the widely varying needs of different customer groups.

Check 2000 is the worlds leading PC tool for assessing the risks to computers as the end of the century approaches. It investigates whether the basic input/output system (BIOS) will rollover from 1999 to 2000 and provides an on-screen display of the risks associated with the impact of year 2000 issues.

Check 2000 Lite:

•	Reports on whether the BIOS will rollover from 1999 to 2000.

•	Reports on whether the BIOS recognizes 2000 as a leap year.

•	Reports on whether the BIOS recognizes 2000 as a leap year.

Check 2000 Lite scans systems for selected hardware information, and tests the computers ability to handle date rollover into the next century and its accuracy in handling leap years.

Copyright © 1996  1998, Greenwich Mean Time Inc. All rights reserved.


Legal Issues

Documentation Copyright

No part of this document may be reproduced, transmitted, transcribed, or translated into any language or computer language, in any form or by any means, electronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Greenwich Mean Time. Greenwich Mean Time makes no representations about the suitability of the information contained in this document or related graphics for any purpose. All such documents and related graphics are provided as is without warranty of any kind. Greenwich Mean Time hereby disclaims all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement.

In no event shall Greenwich Mean Time be liable for any special, indirect or consequential damages. Nor any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information provided herein. This document and related graphics could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Greenwich Mean Time may make improvements and/or changes to the product(s) and/or the program(s) described herein at any time.

Trademarks

Check 2000 is a registered trademark of Greenwich Mean Time.

All other trademarks are the property of their respective owners.


Running Check 2000 Lite

Welcome Screen

•	The Check 2000 Lite Welcome screen gives details of the functions of Check 2000 Lite.

•	Click on Next to proceed to the scanning functions.


Hardware Detection

This phase of Check 2000 Lite automatically tests the BIOS for its handling of various date settings and rollovers.

•	Windows date setting.

•	BIOS ability to handle a date set to Jan 1, 1980.

•	BIOS ability to handle a date set to Jan 1, 2000.

•	BIOS ability to handle a date rollover from Sep 8, 1999.

•	BIOS ability to handle a date rollover from Dec 31, 1999.

•	BIOS ability to handle a date rollover from Feb 28, 2000.

•	BIOS ability to handle a date rollover from Feb 28, 2001.

Notes

Running Check 2000 Lite on a Windows NT 3.5x operating system will provide no valid BIOS information because of the built-in hardware protection mechanisms within Windows NT 3.5x.


BIOS Test Results

This screen shows the results of automatic tests performed by Check 2000 Lite to determine if the PC hardware functions abnormally when faced with dates in the next century. If the PC functions abnormally the results indicator turns red, whereas if it functions normally the results indicator turns green. An ideal situation is one in which all results indicators show green, indicating that the PC hardware functions normally.

If any of the results indicators turn red contact the PCs manufacturer and ask for a new version of the BIOS which is year 2000 safe. Technical help may be needed to install a new BIOS, and all valuable data should be backed up onto tape or disk before performing the upgrade.

For more information on this issue, please refer to the section dedicated to a deeper understanding of Date Testing and the Computer BIOS.


Date Testing and the Computer BIOS

All PCs run a Basic Input/Output System (BIOS) program before any operating system or other programs are started. The BIOS is designed to initialize the PC so that it becomes aware of its hardware configuration, such as hard and disk drives, video drivers and keyboard parameters. It also sets up the system date and time by reading values from the real time clock chip, which is battery powered (rechargeable) to keep a constant time reference for the PC.

Most PC BIOS programs have four digits allocated for recording the year (1998), but most only change the last two digits (98). Consequently, the majority of PCs tested have failed the basic rollover test, changing from 23:59:59 on 12/31/1999 to 00:00:01 on 01/01/1900, instead of correctly registering the new century as 01/01/2000. Most DOS based PCs rollover to 04/01/1980 or 01/04/1980. There are also problems with the fact that 2000 is a leap year, whereas 1900 was not, and many PCs don't register this correctly.

Every PC performs in a unique way. It's not uncommon to find two PCs from the same manufacturer, bought on the same day, running different BIOS versions. This BIOS date rollover problem is an issue simply because programs are dependent on being fed the correct date by the BIOS. If they receive incorrect date information normal working procedures will be seriously disrupted and even chronically impaired.

As with many PC year 2000 problems, it is very difficult to apportion blame or liability. Certainly, suppliers of DOS (and there are more than one) would be fairly justified in claiming that the year 2000 is not a problem with their programs as these operating systems work fine when fed with the correct date by the BIOS.

In many cases the BIOS manufacturer is not the same as the PC manufacturer, and mutual liability clauses between supplier and manufacturer serve to protect the entire supply chain to the user. This leaves the end-user in a vulnerable position, and one from which it is difficult to escape without hardware replacement. Most pre-Pentium PC hardware platforms don't change smoothly from 31 December 1999 to 1 January  2000. Many of the Pentium machines checked by Greenwich Mean Time also have problems, but at least some of these manufacturers have already created their own fixes and it is possible to fix the problem without affecting existing programs.

This hardware level problem is probably the simplest in the whole year 2000 arena to check and fix, but be wary of the BIOS fixing programs available on the Internet. Some are produced by professional programmers, and some by the PC hardware manufacturers, but some are less professionally created and it is recommended that a BIOS fixer is obtained from the relevant PC manufacturer, or from a software company that can provide ongoing support and service.

Greenwich Mean Times testing indicates that upward of 96% of machines that fail the 31 December 1999 to 1 January 2000 rollover test will receive relief from Greenwich Mean Times software fix. But if the machines additionally fail any other dates set or date rollover tests they should be phased out of use before the turn of the century.

All PCs must be checked. Every user must accept that it is their responsibility to check all PCs within their sphere of influence and be prepared for the fact that in some cases the BIOS cannot be repaired, only replaced. Also be aware that some of the checking tools available at no cost on the Internet may cause consequential damage to programs or data. Greenwich Mean Time advises tests are performed only after total system backup, preferably on non-production clean machines.


Why there is No Universal Fix

In the PC world no single manufacturer provides elements for every one of the layers described. There is no single manufacturer who is in a technological position to solve the whole problem. For example, key manufacturers of operating systems do not make BIOS, and key manufacturers of network interoperability software do not make operating systems.

Thus, there is no comprehensive fix for the problems that are arising. Each one of the variables must be approached individually from the PC owner's perspective and tackled from there.


Year 2000 Problem Overview

This section provides some additional background information on the year 2000 problem.

Implications of the Year 2000 for PC users

Definitions of Year 2000 Conformance

Some typical year 2000 problems include:

•	Dates in the Next Century

•	Ignoring Century

•	Limited Date Ranges

•	Days of the Week

•	Losing Date Information

•	Computation Errors

•	Date Controlled Behavior

•	Abnormal Program Termination


Implications of the Year 2000

Estimates of the number of software manufacturers in the world range from 25,000 to over 100,000. These companies have all taken their own decisions on how best to address the year 2000 problem and, of course, they have mostly taken different approaches. Because users tend to have multiple software programs on their PCs there is no individual fix that is going to sort out their whole environment.

The problems most likely to be encountered fall into five main levels:

1.	The Hardware Level

2.	The Operating System Level

3.	The Application Level

4.	The User Data Level

5.	The Exchange of User Data Level


The Hardware Level

Hardware problems stem from the original specification of the Motorola MC146818A Real Time Clock chip, first used in the PC/AT in 1983/1984. This component, which has been cloned by many manufacturers over the years, only uses two digits (yy) to denote the year. There is an optional century flag that can be stored in a spare memory location in CMOS memory. However, this century flag may or may not be used by the BIOS which is installed in any particular PC.

Consequently, that PC may simply be unable to rollover correctly to 1st January 2000. The Check 2000 BIOS tests will show if a PC fails this test. Greenwich Mean Time has taken all reasonable care and followed the current industry best practice to ensure that if a PC passes all Check 2000 BIOS tests the user may be confident that the PC will rollover correctly. However, Greenwich Mean Times lawyers have asked it to be made clear that no warranty is given that if a PC passes all these tests the user will not have a hardware problem.

Please read the section on Date Testing and the Computer BIOS .

Recent independent tests (July 1997) have shown that Check 2000 is the best Year 2000 BIOS checking software currently available.

See also, the section explaining why there is NO universal fix to this problem.


The Operating System Level

Most operating system level problems relate to issues referred from the BIOS. However there are a few recorded and acknowledged problems with the creation of files and documents in the year 2000, where the file create date may be 1/1/!* or some such invalid date. These files may then cause referred issues with other programs which attempt to validate the date stamps on files, with the likely result that such files will be rejected or cause the program to crash. Greenwich Mean Time has created examples of this under laboratory conditions. The PC was caused to freeze and required a reboot with the consequential loss of data. The problem can even affect the ability of a PC to compute time properly.

The question here is whether a users historical data files, spreadsheets and billing packages will work at all, never mind whether they will work properly.


The Application Level

64% of PC software programs exhibit potential year 2000 problems in normal usage mode. Problems at this level are many and vary in severity.


The User Data Level

User data may often seem to be correct when it is displayed on the screen but when investigated the actual stored information is found to be corrupt or flawed. This information can originate from the operating system or the system clock, but if the PC in question is one of the many whose internal clock will not automatically change to the 21st century when the year 2000 comes around, problems occur. For instance, when date sensitive programs are run before the date is reset, the resulting false date may propagate and cause some programs to perform wrong date-specific operations, such as deleting data relating to dates which are incorrectly assumed to be in the past.

This program issue is often not serious because in most (but not all) cases, it is possible to manually adjust the century by using the appropriate system date command.

For example, a DOS-based billing system will create invoices. The date of the invoice is read from the operating system and, where the BIOS rolls over to 1980, an invoice may be created in 2000 that actually seems to be dated in 1980. Worse still, if the PC rolls over to 1900, the invoice may be created as 1/1/00. While the user may print this invoice and even collect payment, the internal operation of this billing package correctly assigns this invoice to the year 1900 so this bill does not show up in the accounts for the year 2000. In such a case, who is responsible? This is a very gray area.


The Exchange of User Data Level

Part of the attraction of the PC culture is the ability of PC programs to exchange data, but this gives rise to yet another layer of the problem. One program can pass corrupt information to many others with unpredictable results. Date errors may crash the program, change data, or even cause data to be deleted as erroneous.


Definitions of Year 2000 Conformance

This section contains some typical definitions of year 2000 conformance. These should be used as a basis for the formulation of an organizations own internal conformance document, which in turn should be used as a general guide to external suppliers and internal developers. The sample conformance documents are:

•	The British Standards Institute Conformance Document

•	The US Federal Acquisition Regulations (FAR) Section 39 Final

This Isnt About Conformance

Although these conformance definitions serve as a valuable reference for the formulation of an organizations internal and external standards, it is worth repeating that the challenge being presented by the year 2000 is not one of conformance. It is a matter of risk management.


British Standards Institute Conformance Document

Preamble to the summer 1998 amendment

BSI DISC originally published PD2000-1 in January 1997 and it has been widely adopted. A review of the document was conducted by the responsible committee (BDD/1/3) in the spring of 1998 taking into account comments received. The committee considered that amendments to the fundamental conformity requirements were neither necessary nor desirable. The Definition and the four Rules are unchanged but, to add value to the document and aid its interpretation, the Amplification sections have been amended. This document, PD20001:1998, replaces the previous version of PD2000-1 but does not change its requirements. An additional document PD2000-4, entitled PD2000-1 in Action will provide further information on PD2000-1:1998 together with information on its use.

Paragraph numbers have been enhanced in the Amplification section to aid referencing and substantial revisions to the document are indicated by side lines against the changed text.

Introduction

This document addresses what is commonly known as Year 2000 conformity (also sometimes known as century or millennium compliance). It provides a definition of this expression and requirements that must be satisfied in equipment and products that use dates and times.

It has been prepared by British Standards Institution committee BDD/1/3 in response to demand from UK industry, commerce and the public sector.  It is the result of work from the following bodies whose contributions are gratefully acknowledged: BT, Cap Gemini, CCTA, PricewaterhouseCoopers, Halberstam Elias, ICL, National Health Service, National Westminster Bank. Additionally, BSI DISC acknowledges the support of the Electronics and Information Industries Forum (EIIF), Action 2000, Taskforce 2000 and Digital Equipment as well as the original bodies for their participation in the review of this document.

BSI DISC would also like to thank the following organizations for their support and encouragement in the development of this definition: Barclays Bank, British Airways, Cambridgeshire County Council, Computer Software Services Association, Department of Health, Ernst & Young, Federation of Small Businesses, IBM, ICI, National Power, Paymaster Agency, Prudential Assurance, Reuters, Tesco Stores.

While every care has been taken in developing this document, the contributing organizations accept no liability for any loss or damage caused, arising directly or indirectly, in connection with reliance on its contents except to the extent that such liability may not be excluded at law. Independent legal advice should be sought by any person or organization intending to enter into a contractual commitment relating to Year 2000 conformity requirements.

This entire document or the Definition section (including the four Rules) may be freely copied provided that the text is reproduced in full, the source acknowledged and the reference number of this document is quoted. It is recommended that the Amplification section be included. References to PD2000-1:1998 shall be interpreted as meaning the entire document.

THE DEFINITION

Year 2000 conformity shall mean that neither performance nor functionality is affected by dates prior to, during and after the year 2000.

In particular:

Rule 1	No value for current date will cause any interruption in operation.

Rule 2	Date-based functionality must behave consistently for dates prior to, during and after year 2000.

Rule 3	In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules.

Rule 4	Year 2000 must be recognized as a leap year.

AMPLIFICATION OF THE DEFINITION AND RULES

1. General Explanation

1.1	Problems can arise from some means of representing dates in computer equipment and products and from date-logic embedded in purchased goods or services, as the year 2000 approaches and during and after that year.  As a result, equipment or products, including embedded control logic, may fail completely, malfunction or cause data to be corrupted.

1.2	To avoid such problems, organizations must check, and modify if necessary, internally produced equipment and products and similarly check externally supplied equipment and products with their suppliers.  The purpose of this document is to allow such checks to be made on a basis of common understanding.

1.3	Where checks are made with external suppliers, care should be taken to distinguish between claims of conformity and the ability to demonstrate conformity.

2. Amplification of the definition

2.1	PD2000-1 (all editions) is solely concerned with the performance and functionality of a single version, release or system. It does not address differences in performance or functionality between different versions, releases or systems.

2.2	 Variations in performance immeasurably small in the context of use do not make a version, release or system non-conformant.

3. Amplification of the Rules

3.1	Rule 1

3.1.1	This rule is sometimes known as general integrity.

3.1.2 	If this requirement is satisfied, rollover between all significant time demarcations (e.g. days, months, years, centuries) will be performed correctly.

3.1.3	Current date means todays date as known to the equipment or product, i.e. the actual date of operation [NOTE  this refers to normal operation and does not prevent testing.]

3.2	Rule 2

3.2.1	This rule is sometimes known as date integrity.

3.2.2	This rule means that all equipment and products must calculate, manipulate and represent dates correctly for the purposes for which they were intended.

3.2.3 	The meaning of functionality includes both processes and the results of those processes.

3.2.4 	If desired, a reference point for date values and calculations may be added by organizations; e.g. as defined by the Gregorian calendar.

3.2.5	No equipment or product shall use particular date values for special meanings; e.g. "99" to signify "no end value" or  "end of file" or "00" to mean "not applicable" or "beginning of file" unless the values in question lie outside its possible date range.

3.3	Rule 3

3.3.1 	This rule is sometimes known as explicit/implicit century.

3.3.2	It covers two general approaches:

(a)	explicit representation of the year in dates: e.g. by using four-digits or by including a century indicator. In this case, a reference may be inserted (e.g. 4-digit years as allowed by ISO 8601:1988) and it may be necessary to allow for exceptions where domain-specific standards (e.g. standards relating to Electronic Data Interchange, Automatic Teller Machines or Bankers Automated Clearing Services) should have precedence.

(b) 	the use of inferencing rules: e.g. two-digit years with a value greater than 50 imply 19xx, those with a value equal to or less than 50 imply 20xx. Rules for century inferencing as a whole must apply to all contexts in which the date is used, although different inferencing rules may apply to different date sets. Where any date element is represented without a century, the correct century shall be unambiguous for all manipulations involving that element.

3.4	Rule 4

3.4.1	A leap year is defined in ISO 8601:1988 (amended in 1991) as follows:

Year, leap:  In the Gregorian calendar, a year which has 366 days. A leap year is a year whose number is divisible by four an integral number of times, except that if it is a centennial year it shall be divisible by four hundred an integral number of times.

3.4.2	Thus, for example, 2000 is a leap year but 1900 is not.

4. General Notes

4.1	For Rules 1 and 2 in particular, it is recommended that the allowable ranges for values of current date and dates to be manipulated be documented, recognizing that all systems have some limitation on the valid date ranges. The ranges may relate to one or more of the feasible life spans of equipment or products or the span of dates required to be represented by the organization's business processes.

4.2	Tests for specifically critical dates may also be added (e.g. for leap years, end of year, etc.). Organizations may wish to append additional material in support of local requirements.

4.3	Where the term century is used, clear distinction should be made between the value" denoting the century (e.g. 20th) and its representation in dates (e.g. 19xx); similarly, 21st and 20xx.

This description comes from DISC, which is a part of the British Standards Institution:

www.bsi.org.uk/disc/year2000/2000.html

BSI, 389 Chiswick High Road, London W4 4AL

Tel: 0181 996 9000


US Federal Acquisition Regulations

US Federal Acquisition Regulations (FAR) - Section 39  Final

Year 2000 Compliance Definition

39.02	Definitions

Year 2000 compliant means, with respect to information technology, that the information technology accurately processes date/time data (including, but not limited to, calculating, comparing, and sequencing) from, into, and between the twentieth and twenty-first centuries, and the years 1999 and 2000 and leap year calculations, to the extent that other information technology, used in combination with the information technology being acquired, properly exchanges date/time data with it.

39.106	Year 2000 compliance

(a)	(a)	When acquiring information technology that will be required to perform date/time processing involving dates subsequent to December 31, 1999, agencies shall ensure that solicitations and contracts:

(1)	(1)	Require the information technology to be Year 2000 compliant; or

(2)	(2)	Require that non-compliant information technology be upgraded to be Year 2000 compliant prior to the earlier of (i) the earliest date on which the information technology may be required to perform date/time processing involving dates later than December 31, 1999, or (ii) December 31, 1999; and

(b)	(b)	As appropriate, describe existing information technology that will be used with the information technology to be acquired and identify whether the existing information technology is Year 2000 compliant.

http://y2k.policyworks.gov/y2kdefin.cfm


Dates in the Next Century

A typical year 2000 problem is that dates in the next century are impossible to enter or are rejected when encountered. Programs with this issue are confined to operating in the 20th century and will be completely unusable after 31st December 1999.

Example. The user is prompted to enter a date and is given the fields mm/dd/yy to enter. The program stores this as mm/dd/yy and assumes all yy entries refer to 19yy.


Ignoring Century

With this year 2000 problem the year can be stored only as two digits, and thus the century is not explicitly known. These programs may assume that dates of the form 1/1/00 are dates early in the twentieth century and can encounter problems arising from that assumption. Indirectly, programs of this type can be the cause of problems elsewhere in the system because when dates with no century information are passed, the receiving program may make a faulty inference about the century.

Example. The user is prompted to enter a date and given the fields mm/dd/yy to enter. The program stores this as mm/dd/yy and assumes nothing about the century to which this refers.


Limited Date Ranges

With this year 2000 problem the date is internally represented in a form that only allows specific years to be represented.

This type of problem is sometimes called a fixed windowing date scheme. The date storage format works from a base date in such a way that the range of possible dates includes the next century. A fixed window of available dates is created. At first glance such programs seem to be year 2000 compliant. However, there exists a potential for indirect problems leading up to the end of this century as other sources within the system might present the program with dates which appear to lie outside the range that this program can handle.

The program must infer which dates refer to the next century. Very often, the original programmer will have made an arbitrary decision as to which dates to infer as 19yy and which as 20yy. It is often not apparent which decision the programmer made.

Example. Many programs only allow date entry within a specified range, and their manufacturers publish this range on their web sites. For instance, an accounts package may not accept dates after 2019.


Days of the Week

With this year 2000 problem programs assume that all dates and the current system date are in the 20th century when computing the day of the week, and are thus incorrect for dates after 1/1/2000. The consequences may be as harmless as incorrect date printouts, but serious consequences are also possible if the day of week is used in computations. Many programs perform specific actions based on the day of the week.

Accounting packages that automatically determine the accounting periods (months or quarters) based on the day of the week have been found to miscalculate. In fact, they often perform calculations based on the number of working days, which are, again, day-of-week dependent.

Example. Use a diary program to set a date for the first Monday in 2000. It should be January 3, but if the BIOS or operating system miscalculates, crucial meetings may well be missed.


Losing Date Information

With this year 2000 problem dates may be incorrectly or illogically stored when faced with unexpected data. This problem typically occurs when date fields are converted from one format to another, or when dates are imported into the program from other programs - or even from versions of the same program. The problem creates strange date outputs when these data are used in the programs, or are printed or exported.

The manufacturer of a product with this problem has confirmed that this example demonstrates its functioning. If you create a column of birth dates in a spreadsheet, such as 01/01/08, 01/01/09, 01/01/10, then the serial numbers allocated to these dates will be the serial numbers representing (in order) 01/01/2008, 01/01/2009, and 01/01/1910. This is because the manufacturer seems to have decided that in this version of the product, all two digit dates less than 10 must be in the 21st century and all dates greater than or equal to 10 must be in the 20th century. This date (10) is called the pivot date.

If you import this spreadsheet into a later version of the same product, the serial numbers will be imported, reconverted and shown on the screen as 01/01/2008, 01/01/2009, and 01/01/1910. However, if you type the date 01/01/10 into a clean new cell, a different serial number will be stored (this later version of software uses a different pivot date) and will be displayed as 01/01/2010.

Greenwich Mean Time has observed (and suggest users check for themselves) that you can easily create a spreadsheet where two seemingly identical dates - both shown as 01/01/10 - can actually represent dates 100 years apart, 01/01/1910 (imported from previous version) and 01/01/2010.


Computation Errors

Programs with issues such as this may perform date-related calculations that fail when faced with dates in the next century. An example might be a financial package that miscalculates the time period of an annuity when the limiting dates span the century change. Many other date-related computations may be affected in a similar way. The restriction is caused by limitations imposed by the program on date fields and storage formats. Statistical and reporting packages are particularly vulnerable to this type of issue.

Example. This is a simple date-based calculation to work out how long until a pension is due.

Today's date:	March 6, 1998

Pension due date:	May 8, 2015

How long?: 	Error! In calculation


Date Controlled Behavior

Programs having such issues often allow sorting, generate sequence numbers based on a specific date, or feature other date-related logic. Since the program cannot handle all dates correctly, this may lead to anything from incorrect output ordering to total data loss. Mail programs, schedulers, contact managers, and reminders, are frequently affected by this issue.

Example. An accounting package sorts invoices into a date order so that current invoices can be paid as soon the payment period arrives. This particular program is sure that an invoice dated 2000 is earlier than one dated 1999, which is why some invoices are not going to be paid on time.


Abnormal Program Termination

With this type of issue, fatal program errors can occur after 31st December 1999. These errors may arise because the program itself was not expecting dates in the next century, or because the program cannot gracefully deal with erroneous dates from other sources.

Example. Have you ever seen the famous General Protection Fault (GPF)? Well these problems look like that!


Contents

WELCOME

Welcome

Legal Issues

THE YEAR 2000 PROBLEM OVERVIEW

Year 2000 Problem Overview

Implications of the Year 2000

The Hardware Level

The Operating System Level

The Application Level

The User Data Level

The Exchange of User Data Level

Why there is No Universal Fix

Definitions of Year 2000 Conformance

British Standards Institute Conformance Document

US Federal Acquisition Regulations

Dates in the Next Century

Ignoring Century

Limited Date Ranges

Days of the Week

Losing Date Information

Computation Errors

Date Controlled Behavior

Abnormal Program Termination

CHECK 2000 LITE

Running Check 2000 Lite

Hardware Detection

UNDERSTANDING THE RESULTS

BIOS Test Results

Date Testing and the Computer BIOS