While browsing around Axcel216's website today, looking for new XP performance tweaks, I found an interesting tweak called "Disable Windows File Protection". I instantly clicked on it, and well, was a pretty lengthy, complicated process, full of hex editing, etc...
At the bottom of the tweak page was a link to an app that would do it all for you, and here is that link:
Now I have XP SP2, which according to the folks from X-Setup, cannot have it's file protection completely disabled, but this program does it, I promise you, it works, and works well.
So, for those of you, who like me, didn't know about this app, enjoy :)
I know for a fact that you posted before about disabling WFP, and at that time, I saw the program, people said that it doesn't work for the latest SP2. Gonna give it a try later, or when I have the time to. I tried X-Setup Pro before and it wouldn't work completely. Thanks for the find WinT.
You're welcome, and you're also right about my post from a while back. I had managed to get the protection down to a minimum, but not completely disabled. X-Setup did have some effect, but not a complete fix.
This little application just rules though, and as always, I love how it just runs one time, makes the patch, and you never have to run it again unless you for some reason, wish to re-enable WFP.
Ooh, I will have to give this a try tonight. Since the darn thing bucked my attempt to reshack the shell32, this might be exactly what I need. Thank you very much for sharing. :)
I've got a quick question, what happens if you hack with WFP off, and say you turn it on again, (just because of say, security issues like viruses or Trojans - something in this case) would it affect the files you hacked - like revert back to normal? - Not that I got any problems, Just curious.
Good question indeed, and honestly I don't know, however, my theory would be that it would NOT be able to revert any hacked files back to normal.
In fact, worst case scenario, you'de get a dialog box popping up asking if you wish to keep the "hacked" files, or replace them with new ones, which then, at least for my system, would require you to insert the XP CD itself.
Again though, not 100% sure on this, just my theory.
