-=> Quoting mark lewis to Greg Mayman <=-

 GM> No, I'm not really surprised. When you consider the
 GM> amount of software that converted the year to two
 GM> figures by subtracting 1900, anything is possible.

 ml> this is true, too... i had stuff that i had tested and tested and
 ml> tested and still had problems... once i really started looking at it,
 ml> i was able to see where the problem really was and fix it... however,
 ml> i know that some of my stuff will break when 2100 rolls around but
 ml> that was a conscience decision to go that path...

Well *anything* DOS based will break on Jan 1, 2100. And if it doesn't,
it *has* to break on Jan 1, 2108.

You see, MS-DOS stores the file date as a 7-bit field. Which gives a
range of 0-127. It's the offset from 1980. 

Most file date handling stuff for DOS doesn't know what to do with
years past 2099. So the year display will get very weird then.

MS chose not to support dates past 2099, because 2100 *isn't* a leap
year. So come Mar 1, 2100 the computer would think it was Feb 29. Oops.

And of course, Dec 31, 2107 will be a *real* pain. Try setting a DOS
system to one of the "critical" dates and watch the fun. Note that you
can't use the Date command to set a date past Dec 31, 2099. You have to
write your own program to use the low level system calls.


--- FMailX 1.60