I have just checked here. Loaded BIOS, selected other, SSV3, ticked replace split oemtable strings and ran. Replaces string at 1ac72 OK. Misses the SLIC table at 5e51c. I will Ix -I think because, as a safety check, it checks the bytes at SLIC + Ah match the table/id string of the RSDT table.... as sometimes SLIC and even SLICv occur in the code and I don't want to break anything. I am sure this can be fixed. Andy
2.1 When ??? I used this tool about two weeks ago and selcted HP SLIC and it turned out to be SLIC 2.0. Is there something I'm doing wrong or has this tool been updated. Not clear in the first post. If it's for SLIC 2.1 it might be easier to state that or when it was changed. I don't want to reflash to get SLIC 2.0 results again. Last time I chose HP and it modded it 2.0 so I had to request a mod. SLIC is not complete term when there are two.
There are two folders in the tool. One for 2.0 SLICs and one for 2.1 SLICs. Depending ion which one you allow the tool to insert is the one you get. The tool doesn't care which one it uses, you just have to choose.. Be sure to clear cmos and load defaults after the flash also..
And i would also like to add that i also tried dell slic v2.1 and i was successful in activating both vista and xp with that option....thanks
Thanks andyp for the clarification...its only because of you that now i have a genuine xp as well as vista..and maybe also windows 7 when it comes...
Hi Andy, Thank you for your help, I tried 1.25 and SSV3 and the VISTA activated with the moded bios, then again i tried 1.26 SSV3 but still the old problem is there, some of the tables the OEM Table ID does not changed and VISTA refuse to activate. tjis is for your information. Regards
i think replace dummy slic is broken in late releases compared to e.g. 1.22. 1B is different for ssv3 for that ver. compared to latest. The only diff: OEMS _ASUS_OEMOEMS - old SLIC _ASUS_OEMSLIC - new