Mail Archives: opendos/1998/02/19/23:45:28
I tried it with doschk13.exe and drl702.exe and it still fails as it had
before! At least it doesn't come up as indicating the time as being as
correct as Wright-time does. I'd hoped that I could get rid of the RT but
year2000 is now still off in my config untill it can pass doschk13 as RT
does.
Mark
On 1998-02-19 b52g AT usa DOT net said:
b5>Cc: opendos AT delorie DOT com
b5>At 10:18 19/02/98 +0000, you wrote:
b5>>Hmm. I'm a little puzzled. Why does dos need a special y2K fix?
b5>>My understanding was that the software would work just fine up to
b5>>2059. A quick browsing of the source code shows this to be so.
b5>>(because of the way it handles dates and times) What's the y2k
b5>>fix? And, why is it necessary?
b5>The year 2000 support prevents the computer from going back to 1900
b5>if it is left running at 23:59 on dec 31, 1999.
b5>This is mostly just a convinience, but it can be very valuable for
b5>BBS systems and such that are left on all the time.
b5>Also, MSDOS (and other dos-a-likes, including DRDOS v6) will go
b5>back to 1980 when they are switched on again come the 1st January
b5>2000. The DRDOS 7 kernel has a fix to prevent this, and it will
b5>always go to the right date, even if the BIOS doesn't support it.
b5>This feature has been with DRDOS since the initial 7.02 alpha 1
b5>release, but there have been some interesting problems involving
b5>PCI cards, which have finally been fixed.
b5>DOS should work until the year 2035 or thereabouts, when the number
b5>of seconds since some date in the past overflows..
b5>Look around for some year-2000 checking programs. Try them with the
b5>year2000=off line in your config sys file, and see what happens.
b5>If you have any more questions, just ask.
- Raw text -