Year 2000 Readiness Disclosure

In accordance with the provisions of the Year 2000 Information and Readiness Disclosure Act, statements in this document are hereby designated as Year 2000 Readiness Disclosures.

As you are all aware, there is a great deal of concern regarding the possible effects of date-related computer crashes at the turn of the millennium. We have reviewed our dependence on computer systems and software here at Keil and believe the following:

The millennium change will have little or no impact on key in-house systems.
Software currently in use has been tested and non-compliant systems will be updated prior to the middle of 1999.
Key suppliers, while possibly being affected, will likely have limited material impact on our ability to produce and ship product.
Our ability to access customer and vendor data will not be materially affected by the millennium date change. This includes our ability to provide technical support to end users of our products.

Definition of Y2K-Compliant

We define Y2K-compliance as:

Full functionality beyond the year 2000 with respect to the potential Year 2000 problems.
Correct processing of the date February 29, 2000.
Correct recognition of dates starting with the Year 2000, even after system reboot.
Ability to deal with a mixture of 19xx and 20xx dates.

The following limitations for the preceding apply:

The software must be installed on a workstation which is Year 2000 compliant, specifically a PC with a Year 2000-compliant BIOS installed and operating.
The operating system of the workstation must be Year 2000 compliant.

We have tested the following versions of our software and find them to be Year 2000 compliant:

8051 Products	Version
C51 ANSI C Compiler	V5.50 and later
A51 Macro Assembler	V5.50 and later
BL51 Linker/Locator	V3.70 and later
OH51 Object/HEX Converter	V2.1 and later
µVision-51 for Windows	V1.30 and later
dScope/51 for Windows	V1.5 and later

251 Products	Version
C251 ANSI C Compiler	V2.12 and later
A251 Macro Assembler	V1.4 and later
L251 Linker/Locator	V1.28 and later
OH251 Object/HEX Converter	V1.4 and later
µVision-251 for Windows	V1.30 and later
dScope/251 for Windows	V1.5 and later

166 Products	Version
C166 ANSI C Compiler	V3.11 and later
A166 Macro Assembler	V3.12 and later
L166 Linker/Locator	V3.12 and later
OH166 Object/HEX Converter	V2.0 and later
µVision-166 for Windows	V1.02 and later
dScope/166 for Windows	V1.5 and later

Notes Note

Please be aware that, as a tool to create software, there are NO automatic protection features or warnings to ensure that the code produced with these tools is Year 2000 compliant.

The test environment used consisted of a PC machine with an Intel Pentium™ Processor running Microsoft Windows 95™ Version 4.0 Build 950.

Getting Updated/Upgraded Software

If you have questions about whether your product is Y2K compliant, please contact our sales department about updates and upgrade pricing.