armadillo extraction error ES1 demystified
 

just thought i'd share this cuz there is almost no specific answers out there as to what causes armadillos 'general extraction errors'

if you are one of those who have experienced the ES1 extraction error, this is caused by having initialized SuperBPM. it doesn't need to be running at the time, all it takes is to start it once and the service remains active. armadillo detects this and stops unpacking itself.

you can, in a variety of ways, change SuperBPM resources to rename the service... be creative. this will stop dillo from messing up.

Ehh... not exactly ;)

Try again or modify your first post (it's close to correct).

Regards.

i don't know what, exactly, i'm not correct about. perhaps the part about what arma does may be wrong. but the fact is if you run superbpm it stays resident and cant be stopped with a simple 'net stop' command. and also the fact is that once this is done arma will always give you that extraction error. and yet another fact is that you can alter superbpm in such a way that arma will continue to work even with it loaded. these are my findings and they happen to be all true in every instance i've tested.

if you have something contrary to share, by all means post away. as i stated before that i couldn't find anywhere, any 'real' information about what causes these extraction errors. just thought i'd share my findings. take them for what they are.

Thx for info bollygud, but there is no need to use SuperBPM when playing with ARM. :)

works for me bollygud.

Sure it works but that's not all in this topic (ES1 error). I cannot write why because there is one person at ExeTools (let's say my colleague) who wouldn't like me to write about this protector ;)

I bet you guys are able to complete this thread without my help.

Regards.

ok, so now i know what you were saying and perhaps my labeling this topic as ES1 demystified would be incorrect because apparantly there is more to this error than what i've discovered.

ES1 to me has only occured when superbpm was resident (and to previous post about it not being necessary... i know this, but if you use it with anything else and try to run arma later, you'll get this error).

if any of you have more details about what this error is then by all means post them.

btw dyn!o, your cryptic posts are exactly like what i was talking about in referrence to lack of information about this error. i was just trying to shed what little light i had on the subject since there seems to be almost zero public information on the subject. and again, if there is more details on this error, i'm sure that not only myself but many others would be interested in hearing what they are. for me, they've stopped since my sbpm fix.

tia

ES == Extraction Error....

It means exactly what it is... Error while decrypting sections because Armadillo corrupts its own key table once debugger/breakpoints are detected.

And that's a good definition of "ES1 extraction error".

Bollygud: my "criptic" posts were mada only to cause the completion of your first post, like Crusader did. Your suggestion (superbmp) was good but not complete.

Regards.

I agree that information on how armadillo detects and corrupts itself is very useful information. Where you able to determine how armadillo (Where in armadillo's code) was detecting it?

While I agree with bollygud, I agree with dyn!o more so. The fact that everytime someone runs into a problem, or has a question, instead of looking for the answer themselves...

...they look to whom I would like to think of as the gifted reversers. While I do feel that they could provide more information, the fact that they don't offer up their tit :eek: everytime we are thirsty for knowledge is probably for the best.

Regards...