software crack

[traco]

I need to crack a homeinspection software. what would be the first step ?

[~~smart~fool~~]

look for a serial number or downloadable version already cracked.

Or be a good citizen and buy the shit.

[Xore]

Spend a lot of time learning assembly and how to use a disassembler. Then understand how cracking is done ( patching, serial phishing, keygenning, etc ), and put what you learned into play and crack it.

[Ezekiel]

I need to crack a homeinspection software. what would be the first step ?

Spend a year learning everything there is to know about assembly, then come back here.

[traco]

Thanks guys, this program is almost $1000 bucks. I would even hit someone off to do it. I have the demo on cd.

[W4nder]

I hesitate to start a new thread as I am new here and don't feel comfortable starting my first post with "please help me crack"...but what I need help with kind of falls in the same category as this thread.


I'm very very new at this, so please bear with me while I try and explain what I'm trying to ask.

I'm trying to get an understanding of basic terms and functions encountered in a disassembler. I've been working from the following tutorials:
http://www.woodmann.com/crackz/Tutorials/Flores1.htm
http://www.all-nettools.com/forum/showthread.php?t=3133
and
http://web.textfiles.com/computers/bburn1.txt

using those tutorials and a copy of winrar2.00 I was able to follow and more or less understand how to look up the registration error and find it's location then get the offset and use that to edit the jne from 74 to 75 to get the program to accept the incorrect password information.

The program I'm working with now isn't so straight forward. I get an error message that Registration failed, but when I pull up the string data references there is nothing that fits that discription. I've tried editing the offsets of various entries in the error list that I thought might possibly lead to the right area to no avail.

My question is this. If you're trying to crack a program, what are alternate methods (other than string data references) of finding the portion of the code responsible for generating the 'registration failed' message box?

Thank you for your help and patience...it is much appreciated.

[Newby_Programme]

I hesitate to start a new thread as I am new here and don't feel comfortable starting my first post with "please help me crack"...but what I need help with kind of falls in the same category as this thread.


I'm very very new at this, so please bear with me while I try and explain what I'm trying to ask.

I'm trying to get an understanding of basic terms and functions encountered in a disassembler. I've been working from the following tutorials:
http://www.woodmann.com/crackz/Tutorials/Flores1.htm
http://www.all-nettools.com/forum/showthread.php?t=3133
and
http://web.textfiles.com/computers/bburn1.txt

using those tutorials and a copy of winrar2.00 I was able to follow and more or less understand how to look up the registration error and find it's location then get the offset and use that to edit the jne from 74 to 75 to get the program to accept the incorrect password information.

The program I'm working with now isn't so straight forward. I get an error message that Registration failed, but when I pull up the string data references there is nothing that fits that discription. I've tried editing the offsets of various entries in the error list that I thought might possibly lead to the right area to no avail.

My question is this. If you're trying to crack a program, what are alternate methods (other than string data references) of finding the portion of the code responsible for generating the 'registration failed' message box?

Thank you for your help and patience...it is much appreciated.Make a new thread and post that in it.

Cause you stupid newb your gonna flood his topic out and get it pushed a side.

Stupid fucking newb.

[Ezekiel]

Newby, you're flaming people for no reason other than to boost your ego -- W4nder's post is related to this thread (software cracking) and he followed all the rules, wrote properly, etc. I'll give an infraction if this doesn't stop.

About the post by W4nder, I really don't know assembly so I can't help.