Richard, You could...
1. If you have a limited number of installations, you could store internally a list of keys, then issue one of them to each user. If it matches one of the internal list, it's good. 2. You could have a separate program with an algorithm that creates keys in a particular pattern. Those are the keys issued to users. When a key is entered by the user, the program decodes the key to see if it matches the algorithm thus a valid sequence. I've used something as simple as a test to see if a letter or number is in a particular position, but it could be much more complex. These don't allow for a user name. And of course, none of these eliminates the reuse of a key by someone else. For that you would need an Internet/server system. Peter Bogdanoff UCLA On Mar 15, 2013, at 6:35 PM, "Dr. Hawkins" <doch...@gmail.com> wrote: > On Fri, Mar 15, 2013 at 5:44 PM, Paul Hibbert <l...@pbh.on-rev.com> wrote: >> I can fully recommend Jacque's Zygodact, its on the RunRev store. It's easy >> to set up and it is >> possible to integrate with PayPal if you have an On-Rev account or use >> revServer. > > It's both more and less than I need :) > > I've pretty much dealt with registration keys, including the one-use > keys, which are keyed to both he user name and his client name. > > What I'm looking to do is hardcode the serial number, and possibly the > user name, into the actual executable I distribute without it taking > ten minutes on a fast machine per copy. > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
