From: Jan Niehusmann <jan@gondor.com>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA KT133 data corruption update
Date: Sat, 27 Oct 2001 15:17:19 +0200 [thread overview]
Message-ID: <20011027151719.A2289@gondor.com> (raw)
In-Reply-To: <1004179736.1615.19.camel@pelerin.serpentine.com>
In-Reply-To: <1004179736.1615.19.camel@pelerin.serpentine.com>
On Sat, Oct 27, 2001 at 03:48:56AM -0700, Bryan O'Sullivan wrote:
> After several months of begrudgingly putting up with my ASUS A7V
> motherboard corrupting roughly 1 byte per 100 million read during
> moderate to heavy PCI bus activity, I flashed VIA's 1009 BIOS this
> evening.
Please note that there have been broken versions of the 1009 BIOS
around. I know one person, and I read from serveral ones, who flashed
1009 to their A7V and were unable to start the computer afterwards.
(Hangs before/during POST).
Apparently ASUS has replaced the broken version with a working one
without updating the version number. But that's just a guess based on
recent success stories about 1009.
> I also discovered, of necessity, a halfway manageable process for
> creating a DOS boot floppy using Windows ME, which Microsoft would
> apparently prefer was not possible. I'll reproduce the steps here,
> since otherwise flashing a new BIOS is likely to be nightmarish for
> people stuck dual booting into WinME.
As I don't use Windows at all, FreeDOS has proven very useful for
flashing the bios. (www.freedos.org)
But, of course, no guarantees.
Jan
next prev parent reply other threads:[~2001-10-27 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-27 10:48 VIA KT133 data corruption update Bryan O'Sullivan
2001-10-27 12:22 ` Hans-Peter Jansen
2001-10-27 13:17 ` Jan Niehusmann [this message]
2001-10-27 15:11 ` Bryan O'Sullivan
2001-10-27 15:01 ` Tobias Ringstrom
2001-10-30 13:26 ` Sam Vilain
2001-10-30 13:39 ` Martin Eriksson
2001-10-30 14:19 ` Sam Vilain
-- strict thread matches above, loose matches on Subject: below --
2001-10-29 2:50 David Grant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011027151719.A2289@gondor.com \
--to=jan@gondor.com \
--cc=bos@serpentine.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.