Boot Block BIOS flash doesn't work

Recommended by Wim's BIOS...

When you say you did not get UniFlash to work, did this mean you were trying to boot to it from CONFIG.SYS or AUTOEXEC.BAT?

Just that it sounds like were having trouble trying to get anything to work and once you got to a command prompt you went for the AWDFLASH. I only suspect that once you were at a command prompt that UNIFLASH would have worked just as well at that point as AWDFLASH.

Be interesting to hear from anyone who has good reason to think differently.

Ritchie wrote:

Be interesting to hear from anyone who has good reason to think differently.

10 posts up from yours states this post below, how he claims that
uniflash didn't detect the flash rom, might be what he means..

Japraiser wrote:

same here. Many Thanks for this piece of software:)... it really helped me out. The only problem i had to deal with now was that uniflash did not recognise my a7n8x-e deluxe flash chip. But when i inserted a floppy with awdflash (the real awdflash) in dos it worked perfectly well.

Although funny enough when I myself have had uniflash not detect a
flash rom, I'd find another similar rom mounted board with a different
chipset & use uniflash to do a hotflash...
Iv'e had cases in the past where uniflash wouldn't detect a flash rom
that I knew it had previously detected & flashed to on boards that had
different chipsets, it seems it's fussy with boards running certain
combinations of flash roms on particular chipsets, even when iv'e
checked to see if perhaps the chip was write protected via jumper.
Been a while now so not sure what the combination was, I bought a
burner 2 years ago now, never needed to hotflash since...

Hi,

I loved the awdblock utility so much, I registered on Wim's BIOS just to let you guys know what a wonderful forum this is.

I had the same problem: A7N8X Deluxe (no less) goes kaput when trying to flash with ASUS's own awdflash program. Ho hum, I thought, but Asus's support takes _forever_. I'm still waiting for a call from them. And to think that they're in the Bay Area as well! Sigh.

Anyway, long story short, I had the same problem: BootBlock 1.0 was trying to load awdflash.exe, and passing some parameter which is the name of the .bin file. Almost impossible to tell what is going on. So I created DRDOS boot disks (from bootdisk.org) and copied dos freak's awdblock utility. Dropped me to a command prompt. I flashed my bios with awdflash (version 2.3f) and with BIOS version 1008 (not 1009, that is beta for my motherboard).

Now my machine is back up, and I'm booted into Linux. Yay for me.

(If anyone needs my awdflash or bios boot rom, I'll put them up on my website soon. I'll post again after I do this.)

Thanks again, guys! You saved me time, hassle, money, and many strands of scalp hair.

And I learnt a *lot* in the process, so I'm indebted.