i posted at : new2cracking.cjb.net 2 old aspr tuts
an step by step tuts...
i'm sorry that i didn't post it before...

i must tnx u all ... because of u i know how to unpack ASPR
real g00d so this is 2 aspr tuts (old aspr )

and i will post also a step by step tut about how to unpack
ASPR 1.3 (the NeW) but this time with OllyDbg ..

i know i will say that i will post a step by step tut about
Flex but .. still no luck here ...
maybe soon maybe later...

TNX ALL !!!

You don't seem to have a method for finding the stolen bytes, or did I skim-read your documentation far to quickly? I was just interested whether or not you was using nikolatesla20's method, but it seems not.

I'm looking forward to seeing your new tut, and have hopes it will not be another TraceX tut, as I feel those are becoming too numerous anyway... (Did I just put me foot in me mouth?)

/Manko

"You don't seem to have a method for finding the stolen bytes, or did I skim-read your documentation far to quickly? I was just interested whether or not you was using nikolatesla20's method, but it seems not."

the new tut that i will post by using Olly as a Debugger will explain how to find the stolen bytes...

Great, LaBBa!

I know many people have requested tuts on cracking with OllyDbg, and tackling aspr with Olly is even better!
Keep up the good work! Can't wait to see it!

/Manko

Hope we can read this new tutorial soon !

It would be interesting to see the tut with Ollydbg, but I hope the "stolen bytes" recovery part isn't based on a signature search... Also, it would be nice to see if it works on the newer versions of Asprotect that destroy the stolen bytes by the time the program has got to OEP.

That's also possible with olly, but I found it harder to do. I can't get olly to break on the memory although the location is known. If I put a memory breakpoint I get bothered everytime aspr writes at that memory location which is a hell of a lot of times...

Not like that !! there is an easy way !! u will see!