Creating a memory dump of engine.dll?
Hi, I'm trying to look at the memory of engine.dll so I can try that thing where NOPs are inserted to allow ClientCmd.
Anyways I can't seem to get this to work. Here's what I've tried.
I tried attaching OLLYDBG to vindictus.exe but hackshield detected it. I know I can run OLLYDBG on the DLL file without running vindictus.exe, but I read somewhere that it won't give the right information if the DLL is packed, and RDG Packer Detector says engine.dll is packed.
I tried attaching VS2010's debugger to the process and got an error that says "Unable to attach to the process. The requested operation is not supported." I don't think it's my VS having problems because I can attach to other processes.
I tried using Windows Task Manager's function to create a dump file. When I opened the file, it said "You cannot debug a 64-bit dump of a 32-bit process, you must collect a 32-bit dump of a 32-bit process." The task manager didn't really have any settings.
I got this Debug Diagnostic Tool from MSDN that's suppose to be able to make 32-bit dumps. When I tried to run it on vindictus.exe, it said "Error while dumping a process via 32-bit DbgHost. Unspecified error".
Anyways I was hoping someone can shed some insight on this situation. I know there are people here who know how to do this. *nudge*nudge*
Thanks in advance.