I don't want to start a thread of advantages/problems of registration, I
only want to keep honest people honest. I'm looking for a registration
routine that is "fuzzy" so that if a hard drive (ie) is reformatted, my
program won't need a new key --- I also want my customers to be happy!
Thanks for comments,
alan.s.m...@boeing.com (work, where I'm on email all the time)
sul...@gte.net (home, where I do this type of work)
We purchased OnGuard, from Turbopower Software Company, because it comes
with full source-code, and then we adapted it in various ways. It is
certainly worthwhile to be able to see and to control exactly what is
going on - without having to start from ground zero.
Since our product must run interchangeably with 16 and 32-bit versions,
we found that differences between the two implementations were initially
troublesome. License codes, like everything else in our application,
must work exactly the same way, and originally it turns out that they
didn't.