I'm debugging a target that allows debugging all the way up to the splash screen before I get an error:

Unexpected event 00000002 in inejected code =>debugged program may get unstable and then I get the code is waiting 5 secs etc and I'm stuck. The EDX is displaying "CLIPBRDWNDCLSS", not sure if this helps or not but either way it locks up right there.

The target is using SHA1 and TEAN32 hashing functions as part of the release validation routine. Not sure if this is the root problem or not.

Is there a setting that I may not have set correctly to get around this. I think that if I can find out what is choking olly the injected code issue would not occur.

thanks

Chris

if you have enabled this in olly
try disenabling
debugging options --> security-->allow code injection blah to find wnd proc
also disable registers -->enumerate some thing sse blah
the above mentioned location is from my memory (if you didnt find it there search in debugging options the key word is sse mmx register

both these functionalities use code injection in ollydbg and if all threads
in your app are suspended they dont succeed so olly waits for ever

there is a big thread in this forum named code injection erros
look through it

Yes, you were absolutely correct, I had to disable to the option decode SSE registers. Problem totally solved........code injection errors gone.........I wonder if there will be an automatic option in version two to combat this issue

Thanks for the help

Chris