Sorry, the correct address is www.c-dilla.co

The name of the protection is C'Dilla. If you're interested in the protection, go to www.cdilla.com for more information. Kop

Hi Chris! You're right! In your protection scheme you can "damage" anything, which belongs to your program, but you've to declare it somewhere in the documentation with 3pt font :-))) to be lawful. If someone copy a system, and like to use that, that's lame. If someone really want to use a system, what was copied, find someone in the "neighbourhood" to take a look at the program, and he tell about what he saw: I changed the name, then some files was deleted....nowadays, every copy is travelling on CDs, which is read only :-) So this deleting scheme is very weak, and easy to crack. If a programmer take a look at some commercial system, there was a lot of them, what was "uncrackable"...but there is no uncrackable protection. FlexLM licensing system for example is a good one, but the main parts are fully revealed by clever crackers....and the company can't change their existing sold licenses.....I hope you know what am I trying to point at.... Good luck in protecting! Kopi PS: search for "how to protect better" on the net...some crackers give helpful info on protection!!!! Crackers knows more about protecting, because they(we) see it from the reverse side :-))

Hi! I have bad news, but every developer know that. There is no uncrackable protection. I have experience in reverse engineering, and I have up-to-date info in this topic...if I can say that. 1. Yes you're right, the keygens/cracks are suxx for the developer. I agree with that. 2. It someone's shareware is being keygenned that's a good thing, that means something :-))) I can say two things: - Make dual releases, and no "save disabled" versions. Leave the SAVE in the menu, but REMOVE the code for saving. - Don't make your retail product available for download! It can make the spread of your program slower. - At the algorithm side. Think of an algorithm, which will not end in a strcmp for example. I mean: don't include the keygen algorithm itself in the program. Only secondary algorithm have to be implemented in the registration dialog - Make your registration more complex with a check code. For example: You ask for a name, company name, serial, check code. At the registration dialog, validate only a part of the key, and check for different parts of the key within the program, at different places (but not with one CheckKey function, because that can be easily be patched :-)) I make reverse engineering only as a hobbie, and not for profit, and I didn't make any releases to the warez scene, so don't blame me, I'd like to help the developers, because I learn a lot from this c00l site, from c00l programmers. Regards, Kop