Go back to the begining and like I said it's pretty simple, just one important file to rename or delete and an optional one to modify. The batch script executable was something I made so you would not have to do all the work which is available at the link in my previous post in this thread but only for 32 bit build 7100 becouse I just recently devised this method and havent had time to make one for 64 bit yet. Hope that helps.
so, i dont have on this path this file takeown /F "%SYSTEMROOT%\system32\sppcomapi.dll only takeown /F "%SYSTEMROOT%\system32\sppcomapi.dll.mui
I can't promise this will work for eveyone but hope it will work for the 32 bit systems with the version I just uploaded. I merely find a weakness in somthing and take advantage of it.
MADDOG33,AS YOU SEE, I HAVE 7600 CRACKED, BUT WHAT CAN I TOUCH FOR DELETE WATERMARK?, THE WIN 7 7600 run well,all run fine 100 % cracked, the windows stay in "eternum" 30 days xDDD
If you are talking about the messege at the lower right of desktop it is your user32dll.mui file located in windows\system32\en-us or instead of en-us whatever language you have. If you click on the file I uploaded it is in there but you have to run the patch or extract it with 7zip archiver. Forget everything I just said. It's easier to run the patch from the link I posted and restart your computer after should do it.
The only problem I will have with the 64 bit is the watermark becouse I can't edit resources on 64 bit files.
Could somebody please answer these questions for me and possibly some other poeple? I am a little confused about this and I have been reading. If I install the Windows 7 OEM RTM now and use it until the SLP keys/Cert are out, will I have to format/reinstall in order to do the Slic 2.1 Bios mod? Is an SLP key & cert needed in order to do the bios mod or could I do the mod now without them and put the key and cerificate in later? And can the bios mod be done with windows 7 already installed on the system or must I do the mod before installing the OS? Also will this make my Windows 7 operate the same as a "true validated" installation, thereby allowing me to download from Windows Update & Microsoft Website for things such as security updates, office updates, microsoft software etc? Sorry if I'm asking a lot here. I just would like to clear things up for myself and anybody else who isn't clear about these questions. Thanks everyone.
Adding a v2.1 SLIC to your BIOS will not adversely affect an existing installation of Windows 7, Vista, or XP. An OEM Cert/Key is not required in order to update your BIOS to a v2.1 SLIC (hence the frenzy currently going to update BIOS's in preparation for the availability of Windows 7 OEM Certs/Keys). If your BIOS contains a v2.1 SLIC, you should be able to activate Windows 7 by applying a Windows 7 OEM Certificate and matching Windows 7 OEM Key. Assuming you haven't corrupted your system with patches, cracks, activators, etc. that change files and/or registry entries, you should not have to reinstall Windows 7 before applying the OEM Cert/Key. Once activated, Windows 7 should work identically to a copy sold/shipped by that OEM and running on that OEM's hardware.
Maddog33, For the watermark, don't need to worry : simply use the Orbit30 toolkit 1.8 and click on 'remove watermark', reboot and all is ok, works for 32 and 64 bits. IMHO, just renaming the file "sppcomapi.dll" to "sppcomapi.dll.whatever" (don't delete it!), is just a temporary workaround, as future updates, or the windows file protection, could reinstall this file again. To avoid that, just create a .txt file with notepad (it can be empty, but i used to write "@exit" inside (without the quotes)), save it, then rename it sppcomapi.dll, set it as 'hidden' & 'read-only', and move it to C:\windows\system32 (32 bits) or C:\windows\syswow64 (64 bits) and voilà. That said, Maddog33, i don't know if your trick with this dll really works, or if it's just 'cosmetic', or if it could screw up everything, but it's clever, and why not so thank you for sharing.
you said you got it working; can you please run the script "slmgr.vbs -dlv" and post the screen want to see if there's any expiration as that script will show it