It dumps all the contents i,e bin files from your bios into folder called dump where your bios file is
Hey 911medic can you go into more detail as to why SSV2 for EEEPC? I have a 1005HA and according to the tool I had a sucessful mod using SSV2. However also according to the tool I had a sucessful mod using SSV3 and chosing the option to adjust location of SLIC? Just wondering what I should go with. Thanks!
SSv2 has been the usual mod due to some having code in the space where the SLIC goes in SSv3. If the code is not present, SSv3 should work also. The tool should not overwrite code in that area.
I think I do not have the time now. I can say it consists of a lot of resizing, moving modules, and hex editing. You should read the MSI SSv2 only mod thread and pick up the manual tips there before trying. We bricked a lot of boards figuring this out (not proud of this...). I think MSI are the trouble makers, ASUS seems to be following lately..
thanks for your respond well its an asus x83vb laptop after modefaing with andy tool it do have slic 2.1 but the rsdt didn't change so i think this is the problem
Hi I have not forgotten. Basically. Despite there being no _ASUS_Notebook string in the BIOS the RSDT oem/table id staill managed to be patched. Therefore it must be something in code. I am disassembling the 1B module. I have found a couple of suspicious areas I need a volunteer to flash a modded BIOS. 1) I cannot guarentee it will work 2) It could easily brick. It should be recoverable - as the 1B module is run after the bootblock - where the recovery code is. When I was testing the new asus lock removal on my board it hang a few times but was always reflashable via EZflash 3) I cannot guarantee the above. I am guessing (educated I hope!) about the code changes. It may have any number of effects. Make sure you KNOW (and ideally have practiced) recovery. If anyone is happy to do this then let me know. Andy