No two modded bios can be same; they should have different hashes... well I think u should follow qtm's advice to make a permanent slic mod
Ignore invalid RW file msg，u can flash the modded bios,it 100% working ============================================================ i can help u mod to permenant slic,after that u can update newer bios anytime w/o mod again,upload your mobo back up bios,tell me what brand slic u want.
Running the tool for ASUS UEFI BIOS I don't have the motherboard yet so I can't get a backup bios. I am assuming you mean a backup BIOS that I get using your tool. How does that permanent SLIC work? Doesn't every new BIOS downloaded from ASUS replace the previous one?
Running the tool for ASUS UEFI BIOS The first successful BIOS mod I ran using Windows Server 2008R2 which is 64 bit. Then I moved the files to a 32 bit computer running Windows 7 Ultimate. I ran the Phoenix BIOS modification again which completed successfully. When I did a binary compare of the SLIC BIOS file modified on the 64 bit computer to the once modified on the 32 bit computer they were identical. This is what I would expect unless different parameters were selected in Phoenix tool.
Running the tool for ASUS UEFI BIOS I understand what you are telling me completely. I just don't understand how or why that works I thought that a BIOS update replaced everything in the previous one. Can you just give me a brief explaination of why that works and what you do to the BIOS file to make it work? I looked at your BIOS backup program. I see it is about 2 years old. Can it successfully backup the new UEFI BIOS information on the new computers? In any event I cannot send you a backup file until I get the new motherboard.
Its been a little while now so i figured i would pop in and see if the problem with sli no longer working on the asus sabertooth 990fx board after slic mod was figured out? I have been runing the slic'd bios but i just got my hands on another 580... so i had to go back to the stock bios.
It is only the NVRAM method which doesn't need a RW report at the moment. I have changed 1.92 so there is a warning but you have the option to continue. Andy
One of the complexities of EFI is that the update can alter some areas and not others. Intel and its digital signing is the classic example of this, and is exceptionally complex (and I don't claim to fully understand..... just what I recall from middleton's efforts). I'm sure qtm will share what he can, when he can. I believe (although might be wrong) that an NVRAM mod is 'permenant' - ie. once done once, you can flash in the normal way and the SLIC is preserved. Andy
No bug with module method in 1.91 that i'm aware of. TEMP.MOD errors sometimes seem to occur with virus scanners etc. Andy
Which way to turn? I finally got my P8Z68 motherboard with the UEFI BIOS. I installed Windows 7 and ran the RW-Everything program to produce the ACPI report. I then used this report as input to run your program, version 1.91, and produce a modified BIOS. I have run your program using the following settings: 1. other, dynamic, and the RW report, 2. asus, dynamic, and the RW Report, 3. other, dynamic, using a dummy (empty) RW report, 4. asus, dynamic, and a dummy RW report, and a few other combinations. All of these executions finished successfully and produced a SLIC BIOS. All the results are different from each other and also different from a modified BIOS I downloaded from MDL earlier that supposedly worked. So my question (you can guess) is which one should I try to use? Is it possible that more than one of these modified BIOS files will work? What would be your recommended settings when I have a RW Report available?