Guys, thanks for informative answers. Of course, I read the "Inside Windows 2000" book. Anyone who claims to be a good cracker shoud be a good system programmer. Or at least, to know sth about it...
Secondly. Needless to say I would also like to have the book you've mentioned! In my turn I can share the book called "Crackproof Your Software��The Best Ways to Protect
Your Software Against Crackers". It is pretty nice and contains some info. The format is "pdf".
Thirdly. I'm myself is one of the people who pretend to be the co-author of PE Tools by NEOx. It is a new generation process dumper, import rebuilder, resource rebuilder, relocation rebuilder, PE Sniffer and so on, so on... (BTW, available on wasm...) So I'm interested to make this software better, therefore I'm asking professionals

sope2001
Your link is nice - thank you. But all what it does it just hooks the API ReadProcessMemory and that's all - weak protection

dynio
Your horrible tails about Xtreme-Protector scared me
So, may be it makes sense to create the driver which will dump any given page in the memory.

So, guys. I've heard sth about the tricks (though information is not really complete ), but what your suggestions will be?