Debugging Direct3D Fullscreen App

[ricnar456]

i´m debugging a direct x now with olly.

i use olly and have good results the method of work is very limited but i have good results.

1)never put a breakpoint of hardware bpx, this freeze your machine.
2)for use breakpints i made a litlle script in this form, i run the game, alt mas tab for switch to olly, run the script


var aux
start:

eob break
run

break:
log eax
log ebx
log ecx
log edx
log esp
log ebp
log esi
log edi
log eip
mov aux,esp
log [aux]
add aux,4
log [aux]
add aux,4
log [aux]
add aux,4
log [aux]
add aux,4
log [aux]
add aux,4
log [aux]
add aux,4
log [aux]
mov aux,0

jmp start

this make olly dont stop in the HE and continue running the game without freeze, next you can go out of the game woth alt mas tab and look the values stored in the log, plus if is a repetitive address the screen will swith to olly without freeze and you can pause the script and pause olly and continue working.
Is a very hard method but work for me

if you can make a good script than change eip and execute a loop in the program, your screen don´t freeze and you can switch to olly with alt + tab and return to the adress of the HE and continue tracing:

I make all dirty tricks how this and with more work, but always can crack direct X games with olly, only you need prevent olly stop completely in a BP o HE while you have the screen of the game in the monitor.
if you work without stop olly, and you can switch to olly, you can continue tracing.

Ricardo Narvaja