Hi, Anyone who know how to delete a rom file in bios using this tool? I tried delete that .rom in DUMP directory but after the bios rebuilt, that .rom file still remain Thanks
How does the module method work? Could someone explain to me what the difference is between the "Module" method and the "SSV2" method? The original post in this thread (and the readme.pdf) do not mention the "Module" method at all. I have a Zotac H67ITX, which uses an EFI AMI BIOS. The tool gives me an error with "Dynamic", but not with "Module" and "SSV2". I flashed my board with a BIOS that I modded using the "Module" method, and it seems to work okay (if there are any bugs/problems, I have not noticed them... yet). I haven't tried flashing it with a SSV2-modded BIOS. I want to know what the difference is, and if I made the right choice by using "Module" instead of "SSV2". (Also, if the first post could be updated with information about the "Module" method, it would make things a lot less confusing; thanks!)
@ Bodin, download link is working do not try to copy and past link into browser it wont work just click on link to download.
Hello everyone, Does anyone has experience with ASUS K53SV laptop ? i need help about mod bios file, thanks in advance.
So nobody can explain to me (or provide a link to an explanation of) how the Module method is different than the others?
I'll try - seriously - I've done so much in the tool over time I can't remember what some of it does :L There are 3 main code paths - One for Dell - One for Phoenix (old and new) - One for EFI (and Insyde) Exactly what happens varies for each one. Generally dynamic means an existing slic is updated and SSV2 means a NEW slic is inserted. Dell - Module - doesn't exist - SSV2 - a new SLIC is inserted in one of the first modules - Dynamic - an existing SLIC and any OEM/Table ID strings are updated Phoenix - Module - for interest only - uses the Phoenix tools PREPARE/CATENATE (old) and FI/FP (new) - this often screws the bios and causes bricks - SSV2 - a new SLIC is inserted in a new ACPIxx module - Dynamic - an existing SLIC is updated, OEM/Table ID strings updated, locks removed EFI - Module - a pubkey and marker are inserted as two new modules with a typical GUID (this was how Insyde was originially done - but still works for some EFIs) - SSV2 - a module is modifed with code to build a SLIC table at boot - Dynamic - an existing SLIC table is modified and strings updated Guys - if anyone feels this is wrong please correct me :L Andy