The Dynamic method is automatically suggested by the tool, I think because the BIOS has SLIC2.0 inside. I've modded now one BIOS with RW-Report and one without and the result are two BIOS with the same CRC. So why does the tool asks me, if I really wanna go on without a RW-Report, as it's not needed?
Yah... dummy AMI SLIC 2.0 R/W report is optional for most of the EFI's; but some others (Phoenix, Dell) need it. As this is an universal tool, so it incorporates the option of asking the user about r/w report.
Hi, Can the tool be used for modification HP ProBook 5330m bios (ver. F22) ? I heard there were problems with ProBook/EliteBook bioses. Guys from whitelist-removal threads concluded there is no an ability to patch modern probook/elitebook bioses at this moment. Also I would to know which patch should be applied to HP flashing utility in order to have moded bios flashing succeed? (and why the patch actually needed?) Also, what about a cryptography around these bioses? Should I know something important about that or tool handle it itself? Would be grateful for any help. Thank you, Chris
Encountering the same problem - file access to 'TEMP.MOD' denied (Phoenixtool196, DMI method) - on Win7/64 Ultimate SP1, disabling the AV for me was not the solution. Configuring all .EXEs in the Phoenixtool directory for "run this program as an administrator" (file properties / Compatibility) did solve the issue, though. And, by the way, my sincere thanks to AndyP for the great tool and of course to Tito and all the other unpaid advisers for their ongoing support!
hi, BIOS HOME member feedback, for asus mobo UEFI bios,some latest bios ver.3xxx don't use phoenixtool196/new module method to mod,when u flash to mobo sometime still don't have slic or seriously brick,be careful to use this method qtm
Wow.. Just read a chunk of this thread and am a bit overwhelmed.. Can somebody point out the definitive info for me trying to get my Dell Poweredge R510 SLIC happy? I have installed Server 2008 R2 on it in a on production environment. Thanks!
The problem definitively is caused by one or several of the 'security features' in NT 6.1 (Windows 7 / Server 2008R2). As I'm not interested in a religious debate I'm just listing what works for me on my servers and workstations (trying to turn the OS from a censor into a service provider for applications like it was in the old days): 1) UAC completely disabled 2) 'Administrator' account enabled & password protected 3) IE 'enhanced security' disabled 4) gpedit.msc: User Configuration / Administrative Templates / Windows Components / Attachment Manager / 'Do not preserve zone information in file attachments' = enabled (gets rid of blocked executables because 'from potentially unsafe' sources, files already tainted 'unsafe' need to be backup'ed/restored to/from a FAT32 medium to become clean again, ADS removers don't work as this 'unsafe' label is undocumented and hidden & -furthermore - the OS often does not report the 'blockade') 5) MS 'Defender' disabled Okay, sorry, I get carried away a bit. So: [1] and [4] may be at the root of your problem, elevated rights for executables ('run as administrator') of course may have to be applied also - even if you are a user with administrative rights (which I strongly suggest). Additional comment: To make the GUI usable I run 'Classical Shell' on all our systems. Hope that helps