let me guess u installed it backwards and POOOOF!
OK, that did happen to me but that in itself wasn't the disaster. I guess, it was the whole slew of blunders together which made the whole ordeal a thing of stupidity.
I know better than to mess with something that is already working but...
First I pull that blunder I mentioned. While trying to come up with a disaster recovery plan I in fact destroy the very BIOS I was trying to guard.
Fine, I order the new BIOS chip from Abit USA. In the meantime I take the old BIOS chip and try Uniflash using another motherboard. This is hotflashing but with a generic flash utility. I run into the problem that BIOS ROMs are different sizes. I try several command line switches for Uniflash. Nothing seemed to work. Uniflash wanted the exact manufacturer and EEPROM model. I didn't have the latter. There were numerous combinations to try. I probably missed some. Anyway, frustrated at some point I find an EEPROM switch on the FIC 503+ motherboard (the doner mobo). Big mistake!!! This turns out to be a +5 volt/+12 volt switch. That BIOS goes up in smoke. (Smoke literally came out of the EEPROM!!!!) End of fiasco number two.
Fiasco number 3. Abit comes through and delivers the replacement on time. (I'm trying to package up the KT7 as an Xmas gift for my nephew and only have days to get everything back in order). Now I decide that Abit installed a BIOS version other than the one I requested or maybe it was the one I requested but it wasn't the latest. So I decide my first failed flash was just a fluke and choose to try again.
After what has already happened I'm a little paranoid but I've been flashing BIOSes for years with only the one incident. So I go ahead...
I then learned that all this time I had a corrupt copy of Awardflash. I get the same beeps I got the first time but this time I should have been able to see the error if there was one. There wasn't, just a program crash, in the middle of the flash!!! Bam...I have another corrupt BIOS!
I order another chip from Abit...
Running out of time, I attempt to contact Abit USA. They are closed, two-week plant shutdown! My nephew's computer isn't going to be ready for Xmas!
Finally the 2nd replacement arrives. It's now two weeks after Xmas. I still don't have the BIOS version I wanted but now I have a spare BIOS EEPROM. So I hotflash it. Not much problem except I dropped one the chip inside the computer while it was running. Fortunately, nothing happened!
Now I have two BIOS chips with the old BIOS on it.
I put a loop of tape lengthwise around the EEPROMs. This is so I could lift them out of the socket easily during the hotflashing. In the final step I remove the tape but, of course, I mounted one of the EEPROMs backwards!!! Poof (no smoke this time) but another EEPROMs is now dead!
I still had the wrong BIOS version on the other chip &%$%$&!!!
I gave up!
I put my nephew's system together. It worked. My nephew got it two weeks late but he was happy. I never attempted to flash the BIOS on that system again!!!
Funny thing is I used to be one of those people who would only flash the BIOS if, and only if, the update had a fix for a particular problem, which I was actually experiencing. Otherwise, I would leave it alone.
Somewhere along the way I got into the "BIOS of the month" club for the KT7. I would change the BIOS for no reason at all except that it was new.
I've gone back to my old ways. I Don't change the BIOS unless it is necessary!
I've always been someone who had to learn things the hard way but this time it took 3 or 4 mistakes for me to learn!
I hope someone can learn something (and have a good laugh) from just reading this and not experience anything that I experienced.
<b>56K, slow and steady does not win the race on internet!</b><P ID="edit"><FONT SIZE=-1><EM>Edited by phsstpok on 01/29/04 07:02 PM.</EM></FONT></P>