I've used the LENOVOTC-5M 2.1 to activate win 7 in my laptop, and LENOVOTC-5H 2.1 to activate it in my desktop pc, both with the 2.0 cert, maybe this helps, 'coz I see the first page that those SLIC's are marked with NO CERT
so the first post needs to be updated again? i agree the NO CERT is wrong for lots of those SLIC's listed. i know for sure at least DELL QA09 2.1 SLIC has key matching 2.0 DELL certificate.
Yep that is right, Suicide Solution altered the first post in this topic before i could answer his question (different timezone issue as i was asleep) ** If any moderator reads this before Suicide Solution shows up , please remove the PubKeyCompare.zip attachment from the first post **
i rechecked the ACRSYSACRPRDCT 2.1 slic with LOHR creator, and pubkey matches 2.0 cert after all... (this check was done with 1.0.0.4)
yes i know, but somehow the LOHR certificate was removed entirely from the zip, as the only one the others were just changed to ' no cert' just saying so it will be added back
There is no LOHR certificate, it the normal Vista 2.0 Certificate Suicide Solution altered the first post in this topic with invalid info produced by PubKeyCompare 1.0.0.3 ... so now the information on page 1 is invalid
I have to edit first page and remove pubkey compare tool due to bugs, as properly notified by FreeStyler.
Gentlemen! Is there a Gigabyte SLIC2.1, which can be used for activating both Vista & Win-7? I inserted a GBT SLIC from the archive of the 1-st message of this thread. No activation of Vista. But I inserted MSI SLIC and there is a successful activation of Vista and 7. Method - SSV3, MB - GA-MA770-DS3-rev.2.0. So, have you a correct GBT SLIC-2.1?
The Slic is correct. The reason MSI slic 2.1 worked for you is that the public key remained the same so you were able to use an old Vista cerificate. So far AFAIK the public keys have not been changed in HP, Lenovo, Dell and MSI and thus can be used together with the old certificates to activate W7. Gigabyte and Acer slics 2.1 have completely new public key and of course the old certificate (containing old public key) will not match. The problem is with the right certificates and not the slics.