From: Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: y2k problem and BIOS-Editor
Date: Tue, 04 Jan 2000 22:05:09 +0000
Organization: Customer of Planet Online
Lines: 17
Message-ID: <ner47s0irenapg8gardjdnbspd7btruj3n@4ax.com>
References: <200001032146 DOT WAA01332 AT acp3bf DOT physik DOT rwth-aachen DOT de> <3 DOT 0 DOT 6 DOT 16 DOT 20000104001017 DOT 359f1bf8 AT mail DOT cybercable DOT fr>
NNTP-Posting-Host: modem-126.argon.dialup.pol.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: newsg4.svr.pol.co.uk 947023776 31405 62.136.8.254 (4 Jan 2000 22:09:36 GMT)
NNTP-Posting-Date: 4 Jan 2000 22:09:36 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Newsreader: Forte Agent 1.7/32.534
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Michelle Konzack <starone AT cybercable DOT fr> wrote:

> I have 5 Linux-Machines...

Then this is not the best choice of group to ask in!  This problem
must have affected many users and is surely already being discussed in
the linux newsgroups with various proposed solutions.

You probably should read the man page for hwclock.  I had a similar
problem with the Award BIOS and the fix for me was to edit the file
/etc/rc.d/rc.sysinit and change the call to 'hwclock --hctosys' to add
the switch '--badyear'.  

> May be a specification for BIOS ???

IMHO, failing a software fix, replacing the mobos in all 5 machines
would be the most efficient option if you value your time at all.