On Fri, Mar 02, 2007 at 03:43:07PM +0100, Stefan Reinauer wrote:
Looks great to me. The warning was kind of useless, since I got this a couple of times, while flashing worked nicely every time.
Ah, so you wrote that :) Then you also know what board that write protect had to be disabled for there :) I gathered someplace that this was needed for some asus board, right?
My other KM400 based system (Asus A7V400-MX) refuses to have its ROM identified, while it uses the same well-supported VT8235/SST39SF020A combination as found on the EPIA Ms. This behaviour didn't get altered by that patch.
I tested various combinations for the io pins, yet didn't get anywhere, all i haven't tried yet is reboot the machine (in the off chance that that changes anything). Mind you, this testing was done more than a month ago, when i ordered the willem and wrote that patch, but i can freely access that machine at all times.
This motherboards BIOS is supposed to have a "CrashFree" BIOS, and i have a hard time finding out what that actually is supposed to do. I have a hard time looking through the marketing, and some bits have already fallen off the web.
Here's the marketing from Asus' site: "CrashFree BIOS allows users to restore BIOS data from a floppy diskette even when BIOS code and data are corrupted during upgrade or invaded by virus. Unlike other competing vendors' products, ASUS motherboards now enable users to enjoy this protection feature without the need to pay for an extra ROM."
There have been several of these crashfree things in the course of a few years, all are more or less equally obscure.
Luc Verhaegen.