|
How2Crack:
I don't know how to say it more clearly than to quote a passage by Clandestiny of 06-11-2001 on the RCE Message Board on this subject:
Quote:
Run an API monitor to log the file operation API's. CreateFileA, ReadFile, OpenFile, _lopen, _hread, _lcreat, MapViewOfFile... those are the main ones.
There is a good chance that one or more of these API's will be used to open the file / map it into memory so it can be read and the CRC calcuation can be performed. Once you've found the when and where from the monitor, set a bpx on the suspicious function. SICE should "hopefully" break close to the CRC routine.
If not, a backtrace between CreateFile (or whatever API it uses) and the error MessageBox could be another useful tatic.
End Quote.
Regards.
__________________
JMI
|