An intuitive user interface, no cryptical commands.Olly Dbg is a shareware, but you can download and use it for free. Emphasis on binary code analysis makes it particularly useful in cases where the source is unavailable. Start with static analysis in IDA, find a way to start the program in Olly and debug the startup process, or start with less invasive dynamic analysis (Cheat Engine).OllyDbg is a 32-bit assembler level analyzing debugger software for Microsoft® Windows®. Stealthing an invasive debugger to get it to attach to an already running protected process is not a nice approach. If you want to attach to a program with an antihack feature you would preferably partially or completely disable the antihack first. On a 64-bit OS, you would need to write your own driver, though with PatchGuard around even that will probably not be enough since they could be detecting your Olly by its window names/positions/hierarchy. If it isn't, try looking for other plugins that hide Olly. If you're on a 32-bit OS, PhantOm with driver enabled should be enough to protect your Olly. Also, the program might be injecting antihack.dll into your process instead of loading it (unlikely in this case). Alternatively, it could just be a delayed LoadLibrary call. Maybe the antihack.dll is loaded into a seperate process? Try monitoring process creation or just use taskmanager and see if there's a seperate process that is killing your Olly. 'they tell something about 'antihack.dll', for which, though, I don'tįound any reference to using Dependency walker and Pe Explorer' If there is a driver, load its binary into IDA and start reversing, and if you're on 32-bit grab an anti-rootkit program (GMER, kernel detective, XueTr) and remove their hooks. Use GMER/ EnumDeviceDrivers()/etc and check for drivers that 'antihack.dll' might be loading. What is the target program? Is it known to have an antihack? (If so, who makes it?) Are you on a 32-bit or 64-bit OS?

Open game in ollydbg