Thanks for the help guys, atleast i know where i stand in all this now![]()
Thanks for the help guys, atleast i know where i stand in all this now![]()
You can also try IDDQD ^^
(not sure if i am the only one old enough to know what that is)
No one is too old for Doom!
I don't understand most of what other folks are talking about on this. But I have been using Process Guard and I have it set up not to allow wow to do any reading of my processes which in turn I can run just about anything i want with no worries of warden. I hope this helps. If not I apologize ahead of time.
i think thats an unnecessary precaution, as warden most likely mainly scans wow and searches for other processes as a secondary means of protection, if your program did anything other then read memory (which warden might still be able to notice) then warden would probably pick it up *assuming your doing something that warden is scanning for*.
Process Guard will not do a single thing to protect you. WoW does NOT scan outside its own process space except for a couple of small exceptions where it's looking for Glider. You can't stop WoW from scanning inside its own memory space so your efforts are futile.
I would have to say I stand corrected, I just installed CE again to verify if PG still works and unfortunately no matter what i did with PG as soon as I opened CE and then opened wow, it gave me the buzzer warning about CE.I appologize for the prior post.
Even if you did stop it from detecting the window title, process name, or whatever, you wouldn't be able to stop it detecting the DLL(s) CE injects into a process when it is attatched. So its pointless either way.