secr9tos just some suggestion.. a lot of user don't not know how to install the driver... it will be better if you will explain in detail on how to install the drivers in the first post, so more uers will be able to give feedback.
yes but it's not the Pre Final version.. I will wait for your new version with the updated driver and the watermark remover.. I know how to install the driver but I still want (and prefer) your one click program and want to test/see how it works.
I know it was only a suggestion a few posts back, but there is a community of readers who do not trust any third party programmer (even ourselves) to inject any form of encrypted data into our boot sector or allow it kernel access. On top of that we also have to trust that the encryption does not include any root-kit which can be as small as 3Kb these days, and that is just not a risk some of us are willing to take. Please leave the option for some of us to use a non-encrypted non-random named file. That sort of protection doesn't work for trojan/malware, why do people assume it will work now, many of us believe it is a pointless endeavor. (even though every newb seems to thinks it's so important) Microsoft will stop your driver based on it's GUID and a simple recompile will be needed for each service pack. They do not need to prove the driver file contains anything, (encrypted or not), they just need to make the service pack not allow installation to a driver with matching GUID (globally unique identifier for the newbs) Check out rootkit.com or google the stoned bootkit for greater details.
created a simple tool for installing ( x86 & x64 ) and also fixed a bug in the 32-bit version so... happy testing. After the test stage I'll publish the source code so no one needs to be afraid of rootkits.. but if so, send me a PM or post here and I'll upload the current source code... same for installer tool.
secr9tos the Pre final driver does not work for me ony my windows 7 pro x64 hebrew virtual machine. after I installled the driver with your tool, it does a system repair after restart (weird..) and then it show windows is not activated.. btw- what is the SLIC in the driver? I want to manually install the correct cert to see if that is the problem. I have also tried paymyrent tool, same problem. also tested the x86 driver and it did not work with your tool on my windows 7 ultimate x86 vm.. windows is not activated.
just take a look in the FAQ: The slic is acer2.1 since I own an acer machine but u can change it using PAYMYRENT's tool cause the slp is embedded. Btw.. can u post an RW-Everything or Slic Dump toolkit report for ur x86 system in case it does not work? Strange anyway 'cause I've tried the driver on two notebooks ( acpi1.0 - x86 & acpi2.0 -x64 ), VMware ( x86/x64 ) & VirtualBox ( x86/x64 ) and it works in all mentioned cases..
secr9tos OK I installed the x64 driver again on my windows 7 pro x64 hebrew machine using your installer tool.. and then I click yes to restart and I pressed F8 during boot to disable Driver Signature Enforcement.. (now it does not boot into repair mode) but my windows is still not activated.. then I installed only acer cert and acer pro oemslp key manually, but windows is still not activated (+windows not genuine watermark). so I guees it's some problem with the driver..
Thanks, I'll try to analyze and fix... EDIT: lol. two problems I've discovered so far. 1. RSDT base address + length = 0x55AF08D1 + 0x38 ( == 56 ) = 0x55AF0909 so there is no space to append another ptr!! 2. is this pic when the driver is applied or not?? If no the driver fails cause in case no space is available for another ptr it will make free space ( gathering the lowest table and realloc )... but this won't work in this case.. hehe this is funny^^
so what should I do? how do I check it? I have installed the driver with your tool and disable the Driver Signature Enforcement. (when I re-run your tool, it only offer me an option to uninstall the driver).
Can u please uninstall the driver, reboot and run slic dump toolkit again -> post screen? would be very kind of u... 'cause I think I know where the problem is ...
no cause x86 does not require signing and for testing on x64 press F8 at bootup and select "Disable Driver Signature Enforcement"
K I just need to remove some useless stuff from the code sample ( slic patch and such stuff ). Well with this sample u are able to edit PCI bus 0 - 255, Dev 0 - 31 & Func 0 - 7. just wait a little bit..