From the GB
'sticky':
BIOS Flashing
[:lorbat:3]First order of business:
DON'T use @BIOS!
EVER! Inevitably someone will 'crop up', and say "But I've
always used @BIOS, and
never had a problem!"
Usually,
"always" translates to: "I got away with it
twice!" I often liken this to playing Russian Roulette... You
might get away with pulling that trigger once, and only hear a 'click'... You
might get away with it a second time, too... But, by the third pull, the odds are starting to catch up with you - you
keep on pulling that trigger, you
WILL blow your brains out! The underlying problem would appear to be that, unlike the other BIOS flashing methods, an @BIOS flash gone awry can overwrite the BIOS' boot block, which is the piece of the BIOS that, among other things, is responsible for the 'dual BIOS recovery' function; i.e., if your BIOS gets trashed, but the boot block remains intact, the boot block 'checksums' the 'working copy' of the BIOS (in EEROM, that you
can flash), finds out it's bad, 'reverts' to the 'backup copy' (in ROM, that you
can't 'futz' with, short of a soldering iron!) and loads it, with a couple of 'flags' set, to remind it to tell you about the BIOS' problem, and offer you options to fix it... Once @BIOS trashes that boot block, your board is a
brick - useful only to prop open a door (and - a real, actual brick does a better job of that, too...)!! You're pretty much hoping for a 'graceful' RMA
This problem is
not limited to GB; other manufacturers have 'in the OS' flashing setups, and, so far as I know, are
also prone to difficulties that DOS or 'in-BIOS' flashing
just don't have...