Hi Yen, I flashed your mod using phoenix crisis recovery method, i did not get SLIC2.1 still the same situation "emulated HP SLIC2.0". I have a fresh copy of VISTA just installed 3hours back, without any aditives, from where this emulation came??????? Help Help Help Help, i became MAD!!!!!! ACPIscope report attached
OK, we need proof. Dump you current bios with rw-everything and upload it please: Dump the memory: press memory dump (third icon from the left side) press address button and enter: FFF00000, press OK. press save as binary, second icon of memdump window. enter length 100000, save and upload your dump of your current bios. Where is that slic20???? I've exchanged it with SLIC2.1 !!!
Is there some news from this acer slic 2.0 to 2.1 update Is there some news of this mod of this acer 5633wlmi notebook?
It's quite easy. HP found or uses a way to protect the address range where the SLIC 2.0 is located at your EEPROM chip where the bios is stored. I wanted to 'disable' the original SLIC at my second mod by renaming it to SLAC, but no chance! IMO the info is located at the platform data, where else? The platform data is appended after your biosfile. So every time you try to flash the mod, the original SLIC data at your EEPROM chip will not be updated. You understand? The platform data makes the flashtool not to update SLIC2.0! It doesn't allow to change a byte there. Your dump of the current bios proofs this exactly. The SLIC2.0 is NOT overwritten by the SLIC2.1 I've exchanged at my first mod. I've inserted the SLIC2.1 exactly at the same offset the SLIC2.0 was to make my first working mod. 911medic did a mod, too. I guess he used PBE to make it. PBE moved the offset of the SLIC2.0. So the platform data protected different code and didn't allow to update it. The result was a black screen!! If this method will be used by others as well, we will hardly find a way to apply a working mod. The only way to break this is to search for an older bios version and append its platform data to the mod assuming the protected address range is different at the old bios OR to analyse the platform data and to disable / crack the address range protection. This is the first case I've seen so far. Anyway I'm glad to hear that you've got two different SLICs. I've used a complete manually way to introduce the SLIC and it worked. This knowledge I may now use to make further mods. Unfortunately Vista /W7 complains about two SLICs and doesn't activate. What means that at your case: Try to find an older bios version and hopefully I can exchange the platform data and it will allow to update your SLIC. Another way is to program your EEPROM chip using another technique / flashtool. This was the reason why I wanted you to try the crisis recovery method. I thought the method would update the whole address range including the SLIC2.0, unfortunately it didn't. If not, I'm afraid I cant do anything for you at the moment. And I hope other bios programmer won't do the same. Please search for an older version of your bios. Hopefully you'll find it, I've tried, but I didn't. HP removed them from their sever, for that reason??? Could you please upload the Acpiscope report with 2 SLICs? Thank you!
Thank you Yen, First of all I googled for the old bios but i could not find any. did you make any mod recently for other similiar HP bios what is feedback. The acpiscope report is attached. Again thank you, hope the solution will popup soon