i was just thinking about this the other day... (i must be feeling that i'm getting near the end of my sub thing :) )... and i decided on something a lil different from the example linked to above...
for registration via online registration, the user runs the registration app on the machine that he/she plans to use the app on... it gets the MAC ID, mangles it some way, then prompts the user to send it up when ordering...
a pre set algorithm, already coded into the app will check the reg code the user receives upon registration, and enters, and it will be saved in the app directory so it can be checked whenever the app is run...
it will be valid only for the machine (or more correctly, for the network card in that machine)... this should at least provide a layer of protection against unauthorized use...
the hardest part was figuring out how to read the MAC ID in Blitz3D...
--Mike
for registration via online registration, the user runs the registration app on the machine that he/she plans to use the app on... it gets the MAC ID, mangles it some way, then prompts the user to send it up when ordering...
a pre set algorithm, already coded into the app will check the reg code the user receives upon registration, and enters, and it will be saved in the app directory so it can be checked whenever the app is run...
it will be valid only for the machine (or more correctly, for the network card in that machine)... this should at least provide a layer of protection against unauthorized use...
the hardest part was figuring out how to read the MAC ID in Blitz3D...
--Mike