Hi ShaG,

using GMI eip,CODEBASE
freezes olly and produces an error in ollyscript.dll at
44dc8de with error code C0000005.

Please note this is caused by asprotect protected target, it runs ok on non protected targets.

Regards.

Not good... maybe you can pm me the url so I can have a look?
Sounds like an serious error, so maybe v0.51 will come soon...

Tried GPA yet? I think this approach is more flexible then just API breakpoints...

My errorhandling sucked... v0.51 uploaded, with bugfixes and better errorhandling...Still the GMI problem remains in brites case.. Will look into it more... If someone else has similar problems plz msg me.

GMI now returns 0 in $RESULT if no data is found.

thanks Shag for the msg. , and your intuition for my intention is on the target
:)

Umm... Another bugfix done. =/

v0.52 available.

Shag, would it be possible for you to post these scripts written for certain protections be put on your website? I suggest this because eventually it's going to get too complicated to follow in this thread.

<edit>
I also heavily suggest starting a mailing list to inform devout followers of your plugin, e.g. improvements, updates etc.

pec oep finder
 

Guys, today I wrote oep finder for PECompact 1.84.
I think, it's unstable, but plz try it.

UPX 1.xx and UPX Protector 1.0 OEP Finder v0.1
 

This script based on SHaG for UPX oep finding.
Now this script support oep finding in UPX 1.xx and UPX Protector 1.0 -> Blind Angel.

here is a script that will find asprotect oep
that has stolen bytes, it willn't work on old asprotect with loops,or the expired targets. (You will enjoy the scenery of asprotect deleting the stolen bytes).

note: I used shr x, 74 because shr x,14
didn't work first time, now it did work, and I uploaded the ajusted attachment.

Note2:there is log y code I used it to test and I forgot to remove, you can delete this code if you want to.

britedream.

FSG 1.33 OEP Finder v0.1 !maybe unstable!
 

OEP finder for FSG 1.33. It work very quickly.
try it.

A maillist is now available. Check hxxp://ollyscript.apsvans.com .

What is the general opinion, should I publish scripts on the site? Dunno if that can mean legal trouble? And do you script authors want your scripts published?

BTW, I recommend marking OEP by using this command:
cmt "OEP"

This way its easier to see then going to the log.

[Edit by JMI: I've asked you before to please stop making your link clickable. We need to stop the newbies from making clickable links to software vendors.]

To ShaG
it will be nice if you can include in the next release jl and jg. Thanks.

britedream : Consider it done =)

BTW, do you want your scripts to be published on OllyScript site?

JM1 : Sorry, will not happen again.

That's all anyone is asking. ;)

Yours is a very useful site and "should" have clickable links, except for the problem with the newbies going crazy and "linking" this site to software vendors while they are discussing cracks or warez copies of that vendors software.

Regards,

Thanks for the positive response.

For my scripts , it is all yours.
regards.