> > 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
