Cheat Engine

[navarone]

When I am using ollydbg to debugg something from the start (From OEP), the assembly codes in the beginning makes sense that the program is just starting up, like pushing lots of stuff into the stack or checking system registery etc..

After the program GUI appears, olly is automatically minimized and I have to trigger something so it starts debugging again.

If the program's GUI is on the screen, and it's doing something (like downloading a file) it means it's being processed and executing assembly codes, right?

Some games, after they start, clicking something like start game doesn't cause olly to start debugging again and I can't see what the program is doing

Am I doing something wrong or what?

[Haxory']

I think it's causing exceptions.

[navarone]

There's no specific program that does this actually.
Olly just minimizes itself after the program's gui appears.

When missing with the program, the stack and the registers are changing. They change so fast you can't see anything really. And it doesn't show any assembly lines being executed.

For ex:

When debugging a setup program, how I can see what lines of codes are being executed to check my serial that I have entered after clicking "next"?

[navarone]

bump lol >.<