You may do it my way. Since most of my applications sell for a large price to a small number of individuals on a per computer basis, I calculate a registration key from a combination of the Hard Drive serial number, ASCII value of the user name, and ASCII value of the company name. The values are written into the registry. Then at important processes within the system, I verify these registration entries. If at anytime the registration entries do not match, they get a registration error, and the program prompts the user to call me, and obtain the necessary registration key information.
The program spells out error codes, giving me clues to the HDD serial number and the ASCII values. I plug these error codes into my validation routine, and tell them their 15 digit registration code.
The validation routine adds the values, multiplies the sum by a specified number, then turns that result into a string, swaps a few characters, and violla, there is the new registration key. Since, every computer HDD has a different serial number, I can control who has access. Even if the EXE file resides on a network server.
As people call for the registration key, I will bill based on varying circumstances. Since most of my users are computer illiterate, they have no idea that the reg key is calculated. And whenever, an error occurs, My first question is, "Did you make any recent changes to your computer?"
HTH,
Dan Neuman
PC Advisors, LLC
>I'm really looking for a simple way of ensuring that only customers that have paid for and registered our applications, can actually use them. Something similar to the way shareware works - an expiry date - an opportunity to enter a unique license number based on the company/user name.
>
>Rgds
>Petras
>
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only