> All MS-DOS machines I've ever used ask for the date and time upon boot.
> This includes all 808x machines I've ever used.
My experience has been that any MS-DOS machine with no autoexec.bat will
prompt you for the time and date, of course any machine without a battery
powered clock will simply have the wrong date at power up, regardless of
it prompting you or not.
>
> So, yes... they do have built-in clocks. They just don't have any battery
> to store the time and date.
My assumption was that "clock" ment a battery backed real time clock,
there are optional clock cards available for these machines, I thought the
machines somehow calculated time by dividing CPU frequency, and that a
true clock was an option.
>
> I imagine it would be more a software issue (OS issue) than a hardware
> issue, though, whether or not they are y2k compliant.
Either way, I'm sure it is, if the year isn't stored in hardware somehow,
then software is all that's left to give you any trouble.
Dan
>
>
> On Thu, 24 Jun 1999, Dan Olson wrote:
>
> > > > Aren't most of the legacy systems going to have trouble Y2K? I am very
> > > > interested if you have a solution/answer because I have a ton of
> > > > 8088-10/12MHz systems collecting dust. These systems may be not heading
> > > > to dumpster if there such a solution.
> > > >
> > >
> > > I suspect the built in hardware clocks of these machines will not survive
> >
> > Built in clock? I have a good dozen 8088s around, including the IBM PC
> > that I'm using right now, and I don't think any have a built in clock.
> > They should all be 100% Y2K compliant because the only issue should be
> > software, and if that ends up being a problem, I'll just find software
> > that works.
> >
> > > the rollover, and may not work again afterwards, but assuming the machines
> > > can still boot after Y2K, ELKS does not rely on the CMOS clock. Any method
> >
> > Still boot? I don't see how having the wrong date would affect booting.
> > If the machine booted when new in 1981, then I'll set the date to 1981 and
> > it should operate as new :) The only issue that I know of would be
> > programs getting the wrong date or weekday due to an incorrect year being
> > reported by the OS.
> >
> > > or querying a central server. You could even set the clocks back 10 years
> > > deliberatly, and then configure ELKS to add 10 years to the time it reads
> > > from the hardware clock.
> >
> > There is actually an offset that will cause both the day of the week and
> > leap year to be correct. I don't recall the exact date, I want to say
> > it's 27 years back, but that might not be correct.
> >
> > Dan
> >
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Jonathan Hall * [EMAIL PROTECTED] * PGP public key available
> Systems Admin, Future Internet Services; Goessel, KS * (316) 367-2487
> http://www.futureks.net * PGP Key ID: FE 00 FD 51
> -= Running Debian GNU/Linux 2.0, kernel 2.0.36 =-
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
>
