Generating Serial Numbers

[danjacoby]

So I have this bound solution, complete with License Agreement, About script, etc. And it's ready to distribute on CD.

So is there a simple way to generate serial numbers, so that each CD I burn has a solution with a different serial number (for registration purposes)?

[DykstrL]

John Osborne ( http://www.databasepros.com ) had a solution for FMD that generates serial numbers based on an algorithm that makes it look like unique numbers. I don't remember what the file was called.

[DykstrL]

It sorta worked like that. He had tip file that used some kind of formula. When the solution was opened the first time, an open script sent the user to a layout, asking for the serial number. Then a serial number that was accepted on the algorithm is entered. The set of "serial numbers" could be generated based on that algorithm. John used it to distribute demo files that had limited functionality. Customers would then "Buy" the serial number". Once entered, the file would then be fully operational. Any one of the "serial Numbers" could be entered and be valid.

I've been trying to find the tip file - but so far no luck. If I remember, the serial numbers were a square times ? of some odd number like 5 or 3.

[SteveB]

I've taken a slightly different approach. I wanted my solution to be installed by as many people as possible from the same CD. I set up a 15 day free trial and when it expired the user must purchase it or it dies permanently. When the user purchases, they give me a number that my solution displays...that number is the disk serial number. I then encrypt it and hide it so that only one purchased copy will run on one disk.

The advantage of this is no need to create different binds or different CDs.

[DykstrL]

The file I was talking about is on the Scriptology disc. The technique file is called REGISTER.FP3. It's worth a look.

[danjacoby]

Perhaps I wasn't clear.

I'd like each copy of the solution to have its own serial number, perhaps embedded in the application that is created by the Developer when I bind the solution -- although I'd rather only have to bind it once, then embed (or attach) serial numbers when I burn the CDs.