Joda
June 23rd, 2001, 06:31
Hi all.
I hope this question wasnt posted b4, if it was plz give me the url and close the topic, so i dont waste space here with things already been discussed.
My problem is the following:
Most programs i try to crack (ye crack, i wouldnt call it reverse engeneering cauz i just have some fundamental ideas of programming, but cannot code in any language yet
) are not disassembleable (?) in WinDasm (at least 70-80%), so i have to use S-ICE on them.
But the problem with Sice is, that i always lose myself in the code. I set a breakpoint on let's say hmemcpy or createwindowexa or sth and then trace trace trace - check registers and memory and trace... And then its over, a nag appears and - ewps did i miss something?
So i try it a 2nd time and so on - until i give up - most of the time resulting in crippled programs, doing funny errors
.
Is there anything in general, that could help me to get a more structured, effective way in using Sice on programs?
This tracing doesnt get me anywhere - and just breakpointing on memory ranges that look interesting or APi functions doesnt help me too most of the time - perhaps its just because i'm so new to the cracking stuff, but maybe there are some ideas that could help me, i would appreciate it.
cya
Joda
I hope this question wasnt posted b4, if it was plz give me the url and close the topic, so i dont waste space here with things already been discussed.
My problem is the following:
Most programs i try to crack (ye crack, i wouldnt call it reverse engeneering cauz i just have some fundamental ideas of programming, but cannot code in any language yet

But the problem with Sice is, that i always lose myself in the code. I set a breakpoint on let's say hmemcpy or createwindowexa or sth and then trace trace trace - check registers and memory and trace... And then its over, a nag appears and - ewps did i miss something?
So i try it a 2nd time and so on - until i give up - most of the time resulting in crippled programs, doing funny errors

Is there anything in general, that could help me to get a more structured, effective way in using Sice on programs?
This tracing doesnt get me anywhere - and just breakpointing on memory ranges that look interesting or APi functions doesnt help me too most of the time - perhaps its just because i'm so new to the cracking stuff, but maybe there are some ideas that could help me, i would appreciate it.
cya
Joda