I have a similar situaltion with my p75. It sets date to somethere in 2094... cool ah? what I do is boot to DOS, set correct date and use loadlin to load linux. If I boot directly to linux and correct the date, time will decrease and as I found out not all programs like that. (you mount a partition in 2094 and write to it in 2000.)
Anyway, I can probably understand why 1999 is followed by 1980 (or 1984) but how it happened that after 1999 there is 2094? They tryed to make a Y2K compiant bios and could not? beats me... Just a thought, Lazar On Fri, 8 Dec 2000, Robert Guthrie wrote: > I actually use chrony, which is a good-enough solution for my wierd setup: > > One machine (a tyan motherboard with a cyrix p150+) has a non-y2k compliant > bios, which sets the date to 198x every time it's rebooted. I'm not > connected to the internet fulltime, so I have cronyd running on a 486 (which > IS y2k compliant... go figure), and when my cyrix machine reboots, it queries > the 486 in the boot sequence and resets the date to a fairly good date. It's > not the most accurate, nor is it probably the best package under most > circumstances, but it has it's place. Mostly, it was easy to set up my own > time server.