New ASUS BIOS Format I just downloaded a BIOS update from the ASUS web site for my P9X79 motherboard. The BIOS image now ends in .CAP instead of .ROM and comes with a utility to convert the BIOS format from .ROM to .CAP. The instructions say that once the conversion is made you cannot go back. This change is supposedly made to support Windows 8. I'm not making this change until I hear from Andy, but I don't like the looks of this!!!
Hi Andy, I have a question... I've been out of the bios modding for a fair few months now so I'm what you could call rusty on the subject but I'm about to mod a HP notebook, a Presario C793vu it currently has f30 bios and Im doing the mod on f35. Should I update to f35 first then do rweverything then flash again with a modded f35 or can I just do the rweverything report on f30 for use with the f35 mod. Its an Insydeh20 bios. Thanks again..
Dear phrunt, Its always safe to flash the org bios before the modded one. You have to flash f35 first and create rweverything. Using this rweverything mod the f35 bios and flash it again (your first option). Regards Manu
Hi Good to hear from you I honestly wouldn't like to say..... there are other here who are more expert on the actual practical matters of flashing! Andy
The Phoenix v2.09 works with new BIOS .CAP? Can I follow the same old method with BIOS .CAP to make biosmod? TIA
I had tested forum bios.net.cn. with the version different mobo's, comparing them I see different a few byte. so I know how modify bios with MMtool. but i not like modify this
New ASUS BIOS Format (continued) After reading about the new .cap BIOS images in other threads I decided to take the plunge. I first loaded the conversion program into my P9X79 Deluxe motherboard and that went ok. After the update and a restart it ran two programs before it dropped into the BIOS setup screen. At that point I tried to update using my modded BIOS image that I had created using the dynamic method and all the defaults, and received a "Security Verification Failed" error. So it appears that they are trying to tighten things up with this new scheme. I then modded the BIOS image with version 2.09 of Andy's program. This time I did not select an SLP file and clicked on the advanced options button. It looked as if all the settings in advanced options defaulted to the values I was told to pick, so I didn't change anything, clicked on OK, and modded the BIOS. When it was complete I attempted to run a BIOS update again using ASUS Easyflash 2 (bupdater will not recognize .cap files) and it completed ok. I then restarted, set all my options in the BIOS, and everything seems to be running fine. I am pleased I was able to get through all this but it would sure be nice to see a short writeup about the best way to handle this security verification problem.