Forum Home
Press F1
 
Thread ID: 91022 2008-06-23 13:59:00 BIOS update stuffed motherboard technicianxp (6463) Press F1
Post ID Timestamp Content User
681562 2008-06-24 19:45:00 There have probably been more bioses killed in DOS using the wrong update file. PaulD (232)
681563 2008-06-24 23:01:00 Most BIOS flash programs will tell you IF the BIOS is the wrong one.

And will tell you that the checksum is wrong / and wont flash the BIOS. So, I doubt that

The only other way the BIOS would get corrupted, is if you downloaded a corrupted BIOS update, then flashed it
Speedy Gonzales (78)
681564 2008-06-24 23:17:00 Most BIOS flash programs will tell you IF the BIOS is the wrong one .



Then why are support forums so full of "I used the wrong file" problems?
PaulD (232)
681565 2008-06-24 23:29:00 Then why are support forums so full of "I used the wrong file" problems? Cant resist this - sorry -- Eye Dee Ten Tees :) wainuitech (129)
681566 2008-06-25 00:24:00 I've actually flashed the wrong file (but it was the right BIOS) .

It was one of the files, in the zipped file from the ASUS site .

It was because of Powerarchiver, it made the file that I was meant to flash one of its filetypes . Which I copied to a flash drive to flash the BIOS with .

I didnt realise this till later . It kept saying it was wrong, I flashed it anyway lol and killed it . Luckily, (the system was an ASUS mobo), and I managed to reflash it with Crashfree BIOS .

And got it up and going again . And its still going now (its the other PC here)
Speedy Gonzales (78)
681567 2008-06-25 03:07:00 There have probably been more bioses killed in DOS using the wrong update file.

My argument against windows flashers is that there are a lot more variables to take into account.

Windows, for one. Then all the drivers, programs etc that are loaded - even safe mode has to load some things.

And I'm not sure automatic systems can get it right all the time either. How many times have people been burned by drivers from windowsupdate? what if the windows BIOS update program IDs your board incorrectly due to some bug and downloads the wrong file itself? or the server is down and the program is stupid enough to flash your chip with a 404-error html file? What if the download is the right file but it becomes corrupted?


When flashing in DOS you're a lot safer in my view.

For a start, booting from a DOS-only floppy with no drivers will give you the most stable operating environment and one which is the least likely to interfere with any flashing process.

Then, almost all BIOS files are inside zip archives. This means it's almost certain to be intact, because if the file was corrupted during download - it won't extract

And like Speedy said - it's quite hard to flash the wrong file because most flashers will check and tell you if the file doesn't match.

That is, unless you're using Uniflash (my favourite ;) ). Then you really do need to know what you're doing. It flashes not only anything to anything, but also the bootblock as well. But if you're paranoid - you could use a UPS.

I've always been wary of windows flashers, ever since I was lazy and nuked my DVD drive with one and had to recover it in DOS. Luckily there WAS a DOS alternative. I know a lot of drives where windows flash programs are the only thing available :horrified
Agent_24 (57)
681568 2008-06-25 03:08:00 Don't you just love how these threads get completely off the point while still staying within the same topic? :D Agent_24 (57)
1 2 3