The question has been asked "Why the Cinderella Project?"
Well, the basic Theory behind the Cinderella Project is that for PC's using older software, the Y2K problem is not a terminal constraint.
This theory has yet to be disproved.
The Mainstream assumption that all Hardware must be upgraded and Software replaced may be valid in many Mainframe cases, but is not germane to the home user or small business.
For this reason Cinderella has been defined as a specific subset of Y2k activity. The primary ethic is "zero-cost".
The theory has been tested in a range of environments ranging from Dos 3.2 thru Dos 6.20, OS/2 and Win 95. The internal DOS binary date is after all correctly used, although Displays leave something to be desired.
The issue is really in which parameters to choose.
The "compliance" requirements (less strict perhaps than in Mainstream) have been carefully defined.
The essence is in testing by setting the clock forwards. 2000/02/29 is the current date of choice.
Apart from silly things (e.g. Windows 3.1 displays 2000 as "19:0") nothing serious or system threatening has yet been discovered.
The primary objective is to provide the small user with an alternative strategy. The deliverables are Information (for Awareness purposes), Technical briefings and Manual Procedures. The User evaluates his own machine using these tools and makes his own decision.
Work now continues to populate a matrix of older products regarding level of compliance.
The exercise of doing this on current or new products is left to the Mainstream people with their extended budgets.
A website for the purpose of distributing the free deliverables is under construction.
I trust this clarifies the Y2k Cinderella Project.