ENTROPY YEAR 2000 READINESS DISCLOSURE

In an effort to answer questions that you may have about Entropy's
Year 2000 readiness, we are issuing this Year 2000 Readiness
Disclosure. Due to the nature of the "millennium bug" and the fact
that Year 2000 compliance involves the interaction of many systems,
we do not believe that issuing blanket "Year 2000 Compliant"
statements are useful or appropriate, but rather we are trying to
educate you as to the way Entropy uses and interprets dates.
Entropy's databases store dates using independent time structures,
which support the distinction of any moment in time to the hundredth
of a second from January 1, 32767 BCE (Before Common Era) through
December 31, 32767 CE (Common Era).

Entropy interprets time input in a wide variety of ways as described
in the documentation. For each method, 2 digit years are assumed to be
19xx for values greater than or equal to 70 and 20xx for values less
than 70.  Years entered with 1 or 3 or more digits are assumed to be
the explicit year (e.g. 8, 080, 584, 2008, 10954, etc.).

Entropy displays twentieth and twenty-first century (BCE or CE) years
using a four digit 19xx or 20xx format, and, to avoid ambiguity, first
century (BCE or CE) years using a one (x) or three (0xx) digit format.

Certain functions of Entropy depend on operating system calls to
determine the current time (such as the the etime() directive, the
<?etime?> and <?elastmod?> eTags, and the last updated time for
databases and files). These functions may return invalid results
depending on the Year 2000 compliance of the hardware, software and
operating system Entropy is running under. You should contact your
other vendors to determine the Year 2000 compliance of your hardware,
operating systems and other software and systems to determine whether
they are Year 2000 ready in the same manner as Entropy and whether
Entropy will correctly operate in conjunction with these systems.

This Year 2000 Readiness Disclosure does not alter or amend the
Entropy license agreement or any of its provisions and should not be
construed as a warranty of any kind.

If you have any further questions, please contact us at
entropy@tsdi.com.