hi,

anyone ever heard of damaged stolen bytes ?

how can i recover them ??

grtz, johndoe1

there's something called "Search"" function on the board ..like google has ... have you ever used it?

DUH

yes, i did

and only this pops up

coz the words damaged + stolen + bytes is not found

( without the + signs offcourse )

and yes i know stolen bytes...
and how to recover them
there are great tutors in this forum

Personal flame removed

johndoe1:

Asking if you have searched is not a "personal attack" and it does not authorize you to make one. I have removed that portion of your post.

The problem is that "damaged stolen bytes" is a completely non-descriptive statement and no one knows from that statement alone what you suggest is the "damage" which you claim has been done to the "stolen bytes." If you have been reading the threads here and on the exetools forum, you would know that in many instances the stolen bytes, themselves, really are an artifact of the compiler that was used and may not even be necessary to make the program run correctly. If they are necessary for the program to run correctly, does it not stand to reason that you have not properly dumped the program, being either too early or too late for it to have offered the "undamaged stolen bytes"?

So lets have a better description of what, exactly, you mean by "damaged" without a reference to a specfic target or the posting of any code which identifies a specific target.

Regards,

stripper v2.05 b3
(c) by syd, kiev, 2002-2003

21:58:36 - loading modules..
- ASPack 2.xx (v1.00, full release)..
- ASProtect 1.xx (v1.03, full release)..

21:58:40 - open E:\Program Files\xxxxx\xxxxx\xxxxx.exe...
21:58:41 - executing.. may take for a few minutes.. be patient..
21:58:41 - asprotect detected..
Image Base :00400000
21:58:41 - dumping victim..
21:58:41 - processing import table..
ImportAddressTable RVA :00016038 - kernel32.dll
ImportAddressTable RVA :00016150 - user32.dll
ImportAddressTable RVA :00016024 - gdi32.dll
ImportAddressTable RVA :00016000 - advapi32.dll
ImportAddressTable RVA :00016140 - shell32.dll
21:58:41 - fixing import table..
ImportAddress RVA :00016040 - kernel32.dll!LockResource
ImportAddress RVA :000160a4 - kernel32.dll!GetCurrentProcessId
ImportAddress RVA :000160dc - kernel32.dll!GetCurrentProcess
ImportAddress RVA :000160ec - kernel32.dll!GetCommandLineA
ImportAddress RVA :00016124 - kernel32.dll!GetModuleHandleA
ImportAddress RVA :000161cc - user32.dll!DialogBoxParamA
21:58:43 - stolen bytes were damaged by alexey, look at last section..
EntryPoint RVA :0002d000
21:58:43 - saving unpacked file..
21:58:43 - file was unpacked successful..
21:58:43 - done..

since exist excuses never people makes mistakes ... your desperate entire post without details just pointed to another crack request . the poor details and words damaged in this would mean Stoled ASPR. bytes which has been discussed many times . but maybe you did searched at all.. but didn't read?. your flaming behaviour indicates that i'm right! anyway you wouldn't bother yourself responding in such way if i were wrong .. so a little guessing just gave me the idea you didn't search at all

Best Regards

If you know how and have read the exisiting tutorials, why are you using Syd's Stripper?

That basically defeats the purpose of posting in this forum.

More than likely Stripper is running into an error, its called a Software Bug , yeah imagine that.

The fact that the tool is reporting "Damaged Stolen Bytes" is really pointless, when you look at what the stolen bytes do.

In order for the program to function properly they must be executed to do what? BALANCE THE STACK

That is why they are not simply removed altogether, however thay may be masked executed in a masked form similar to

enter 0,0

is the same as:

PUSH EBP
MOV EBP,ESP

Which is basically the being of every program written in 'Most Languages'.

I can't say for sure that every compiler adds the same instructions.

The program always assumes that there are instructions on the stack waiting to be executed. Keep in mind that the Stolen Bytes can be anywhere from 2 to 10 line of instructions long. Again I think it depends on the compiler.

The compiler adds them during Assembly

My only suggestion is to Debug, and read some existing reading material, or if you are feeling really 'Spunky' and are actually expecting a reponse, you could try an email Syd and see what he means by "Damaged Stolen Bytes".

But I wouldn't get your hopes up about getting a reply.

If you are here to do your homework, stay awhile and study.
If your looking for a keygen or a patch, get on the bus.

I am absolutely SHOCKED to learn that software may have BUGS.

Regards,

Dood take a chill pill

I really don't feel as though I was being unrespectful,

Have a nice day