Trick to misleading debuggers...?
 

I've a prob with "OEM Logo Stamper Professional Edition v1.0a" (http://www.crdrc.org/download/olspe.exe). For the 1.00 version I found a serial using the point-h method, but it seems the author changed something in this new version (to mislead debuggers?). When I run the program after set a breakpoint for the Point-h or CallStack method or even on a simply NAG, OllyDbg now allways gives an "Inexact floating-point result" error, after a few seconds followed by an "Thread 00000970 terminated, exit code 0" error. I tried it with OllyDbg v1.10.2 and v1.10.3: same result. Anyone knows what happens and how to solve this prob?

Try breaking on some actual APIs instead of just point-h.

You can spy which APIs are happening with a program like AutoDebug.

Fixed
 

Thanks. I tried it on two pc's and only on my main pc registration ends up with a crash. I traced it using MSVBVM60 API and found that the program crashed after Olly showed the last four numbers of my hardware fingerprint. Maybe I've a blacklisted pc? :eek:

Anyway, I found the place where the program crashed, jumped over it and everything works ok now. Even found a new serial by using the point-h method.... :p

Hi TheDutchJewel,

So i'm not familar with the point-h method, but if it checks for a debugger, have you installed the hidedebugger plugin for ollydbg? Its available in the tutorial for asprotect. Get this and try again. May be you have it already...

Cheers, neogen

Hi neogen,

I have it installed. But it seems not to be a debug protection, because the error appears only on my main pc, also if I run it w/o Olly... So it has something to do with my pc only.

Happened with your hardware fingerprint, hmm that is weird, I've had a quick think about it, but I'm drawing a blank tDJ, ever thought about contacting them? Heh.

Sorry, but I don't understand this. Do you mean that I'll install a clean Windows to check if it's a software prob? I already restored my Ghost dump sometimes, but same prob. Or do you mean that I contacted them by mail or cookie or something? I never contacted that way to the author. But maybe one time I forgot to block my connection to them after which they have some info about me. No idea...

tDJ, no no no, I simply meant just contact them, tell the company that you found a bug (make something up), and that you are a software developer too, so you used a debugger, but the debugger kept crashing when it had your hardware fingerprint, but on another computer the debugger worked fine with it.