Cheat Engine

[Dark Byte]

CE 5.1+:
Run the kernel data retriever once, and make sure it finds the debugport. If it doesn't, and you are using Windows XP, set the debugport to 188. Start CE, enable kernelmode OpenProcessMemory, and from now on when you attach CE to a process it will ask you to detach the debugger.

[gb_ck]

Yay, thank you very much

But sometimes when i filled 0 to the address of peprocess plus the distance to the debugport already. CE still raise error 87. I have to do it again many times then i can debug the game.

Btw, hope u will release CE 5.0 . I can't wait...

[abc]

i tried this and it caused my pc to shut down straight away when i go back to the game and boot up again and when windows started up it asked me to send an error report

[Dark Byte]

in that case just add the debugport address as a 4 byte address and then make it 0 in the addresslist.
if you where making it 0 byte for byte and a debug event fired it would have gone to the wrong address and crashed windows. (but because a 4 byte replacement is a 'atomic' instruction the chance of this is a lot smaller)

also, make sure you edited the right address. changing any byte in the wrong spot will cause a windows crash

[topaino]

umm.... what do you mean by "physical address"?

I obviously have that small compatability problem you mentioned because all i see is the "??", but what exactly am i supposed to write down?

i dont see anything labled "physical address"

[Dark Byte]

I'll try to explain with images

when you've done all this I recommend you open the process at least twice using the normal open method (it seems physical memory sometimes stays enabled)

then you'll be able to attach the debugger

[Dark Byte]

EDIT: THIS IS FOR CE 5.0 ONLY

Also, try this fix

first close cheat engine
then run the kernelmodule unloader that comes with cheat engine, start->programs->cheat engine 5->kernel stuff->kernel module unloader (or just reboot)
Extract these files over the ones in your cheat engine folder (usually c:\program files\cheat engine\ )

and with luck you'll be able to read that memory and can then use the automated emthod of ce (always use kernelmode openprocess and have ran the kerneldata retriever at least once so it knows where the debugport is)

[topaino]

My program doesn't display that information

is there some setting i need to have on, or something?


also, i tried those files you posted but it didn't seem to do anything

[Dark Byte]

you need cheat engine 5.0
you need to be using a account with ADMIN rights.
use windows xp (NOT 64 bit)
copy those files over the files in your cheat engine folder.
if you have different versions of cheat engine installed uninstall all of them first (only use one version)
Also, enable kernelmode Read/Write processmemory

and close ce before you run the kernelmodule unloader and then reboot

[bitterbanana]

thanks a lot for this! I'll never need another nocd patch again.

you're damn smart. where did you learn all this?

[AwAiS]

At times, when the debugger doesn't successfully attach, a load of pop-ups come about.. but it can be prevented if you go to Settings and simply press Enter, before using the debugger.

[Dark Byte]

should be fixed in ce 5.1

[Zhoul]

[Zhoul]

Incase none of you have noticed yet: CE 5.2 will do this entire process for you when you try to attach to a program/game that already has it's own debugger attached. You will get a pop-up message asking if you'd like to detatch the 'other' debugger, before attaching your own.

DB = Teh r0cks

[weako]

what is debugger??
Teach me more about this pls