QB / QB64 Discussion Forum      Other Subforums, Links and Downloads
 

 Return to Index  

Hmmmm....

November 19 2003 at 6:13 AM
Jonathan Simpson  (no login)


Response to still unsolved...

 

Well, if we knew what the program was intended for... you could date stamp the output, which would perhaps make it unusable. Alternatively, if its a program they use on a daily basis, it might be worthwhile to track the number of uses as well, and shutdown at 30, 60, 90... whatever. As has been said, there can be no perfect way that uses local system time, and i don't like to force the user to have a current internet connection, especially not knowing what the actual program is for.

I don't think you can get this solved perfectly with just the program, but you could add a little bit of security by letting them know that you will not renew the software again for them if they don't renew it every month. This way they will be a little more reluctant to cheat and skip a renewal.

Final note: if you take the previous method and write the time info directly to exe file, it makes tampering even more difficult... especially with a checksum. Of course, they could remove the protection, but they can do that with anything.
Jonathan Simpson

 
 Respond to this message   
Responses

 Copyright © 1999-2014 Network54. All rights reserved.   Terms of Use   Privacy Statement