Message-Id: <1.5.4.32.19980220153842.0068ec74@pop.netaddress.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 20 Feb 1998 15:38:42 +0000 To: "peaslpw AT poa DOT mmc DOT org" From: J P Morris Subject: RE: questions please. Cc: opendos AT delorie DOT com Precedence: bulk At 09:16 20/02/98 -0500, you wrote: >Me too! Will this new fix negate the need for a BIOS upgrade for my 1987 >Compaq 386-25? If not, does anyone know of an add-in clock board that will >circumvent the BIOS problem? Hate to shut her down just because her clock >doesn't work anymore. She's a fine beast. > >Bo Yes, that's the point of the year 2000 code :-) The fix to the code stops some odd problems with PCI cards which you are not going to experience anyway on a 386. For most purposes the Caldera year 2000 code is fine. The RTC is the only weak spot I know of, and to be honest, I don't know of a single program that is going to look directly at the RTC. Even if there is a program that does this, that program itself will not be year 2000 compliant and that is out Caldera's hands. Anyway, the RTC problem will go away as soon as you next reboot the computer. > > >On Thursday, February 19, 1998 5:18 AM, Travis Siegel >[SMTP:tsiegel AT softcon DOT com] wrote: >> Hmm. I'm a little puzzled. Why does dos need a special y2K fix? My >> understanding was that the software would work just fine up to 2059. A >> quick browsing of the source code shows this to be so. (because of the >> way it handles dates and times) What's the y2k fix? And, why is it >> necessary? >> >> > >