Cheat Engine

[iPromise]

Sorry but I forgot to ask this question as well.

Is there a way to communicate with your driver without creating files but sending messages?

Also, is there a technique or function that one can utilize in kernel mode to view all the memory regions in the usermode application?

[Dark Byte]

You could try a socket, but internally that is also just a file
Alternatively you could make use of event objects that signal when there is data ready in a prepared memory block containing the message

For the memory try the kernel variant of virtualquerry or parse through the pagetable manually

[iPromise]

How do you communicate with DBK64?

[Dark Byte]

I use deviceiocontrol
first I open a filehandle (createfile) to the driver device and then send and receive data using deviceiocontrol

Alternatively if using an unsigned driver with combination of dbvm I use dbvm to elevate my usermode code to kernelmode and call the internal ioctrl dispatcher of my driver manually

and the abandoned CETC project uses sockets to initiate it's commands (reading/writing and scanning)

[iPromise]

would using sockets be more "cleaner"?

what would be the kernel versions of send / recv?

thanks.