Quote Originally Posted by oscar3d View Post
To be honest, I'm also waiting for the final bios 504. I will try the battery thing on the weekend, but why should be do that hazzle in the first place? Anyway, deosn't CMOS get cleared by default when you update with EZ Flash tool?

When I got the problem with Express Gate (after using Asus Update) I did try flashing it back using EZ Flash to the original BIOS that came with the CD. Turned out that this didn't work either, and the Logo screen said "P5E3 Deluxe" but without the "WI/FI Ap@n" extension.

When I fixed Express Gate on my machine, I used the USB device that holds Express Gate content.

Note: This device only appears in the BIOS, after you screw up Express Gate.

Inside I found two BIOS ROM files:

1) P5E3xxxxxx.rom (the interesting thing is that the name of this bios says something like "epgate" at the end. Suggesting that it has express gate enabled.
2) P5Kxxxxxxx.rom

I used the first one, and then my machine flashed back to BIOS 0132, older version. But recovered express gate.

That's why I don't want to update until I have either a new non-beta BIOS, or I have confirmation from Asus on what's really going on.

ACE76, I hear you, from now on I will never use Asus Update. But even using EZ Flash tool, to update, I will lose Express Gate again. I will try on the weekend.
I don't think i's just Asus software implementation of flashing BIOSes...it's basically all mobo company software for doing this is suspect...I have read in so many other threads across so many different forums of people having nightmare problems when attempting to flash their BIOSes from within Windows...I personally have always done it with a floppy or the BIOS like Asus has that option....at least we know that doing it that way is much more safe...not 100% as nothing is 100% safe...but people are just better off doing with either a floppy or through the BIOS if that option is available.

I am probably just going ot hold off on even trying to flash my BIOS now until I see a final revision on that 504 firmware....better safe than sorry I guess.