Hello Garfield,
Well, all developers work on their own cryptic algorythms. If the algorythms were shared and known, most applications would be cracked without any effort. At least, hackers have to reverse engineer a little bit our compiled code to figure out where the algorythm is stored and bypass it.
More or less, here is what you have to do:
1. Find somewhere on the web an encryption (an easy and quick one, no need to spend hundreds of hours on this topic, your application will be cracked anyway!) algorythm, or design yours (much more fun!).
2. Manage that the HotSync name, being somehow converted by your algorythm ends up in some cryptic code, that will be the reg key for the user.
3. Store the information somewhere in the device, either in a file or in the Preferences.
I personally hate registration keys. I like to buy full working software, whatever I do with my devices. For instance, I use from time to time my old Vx (to test compatibility with older devices) and I chose some test user. Sometimes, I need to work with a shareware for a few days or weeks in this device. Do you think I like to find back my reg key, hotsync the device with the same user ID as my main device, etc... ?
This is why all my shareware applications are sold as full working versions. Of course, I know some people then forward them to their relatives or to some underground web sites.
These will even sometimes complain to me, asking for upgrades!
But I don't want good willing people suffer because of idiots.
Cheers,
@+
aldweb
I. aldweb
![[de]](img/de.gif)
![[es]](img/es.gif)
![[it]](img/it.gif)
![[pt]](img/pt.gif)
Top 
© 2004-2013 
