Make TriaL?
-
Any help me? I have a problem to make a Trial Program with VS 2005,. Thanks,.
Hellooooooooo,.. May I Join??
any way you like, if there was a standard way, everyone would know how to defeat them. Typically you need to store the date the software was installed somewhere so you can check it, and close down if the trial has passed.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
any way you like, if there was a standard way, everyone would know how to defeat them. Typically you need to store the date the software was installed somewhere so you can check it, and close down if the trial has passed.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
You should perhaps keep a count of the number of executions as well, especially if the app is not date critical. This way, even if you end use resets their clock, then program will expire at some point.
Steve Jowett ------------------------- It is offen dangerous to try and see someone else's point of view, without proper training. Douglas Adams (Mostly Harmless)
-
You should perhaps keep a count of the number of executions as well, especially if the app is not date critical. This way, even if you end use resets their clock, then program will expire at some point.
Steve Jowett ------------------------- It is offen dangerous to try and see someone else's point of view, without proper training. Douglas Adams (Mostly Harmless)
I would just store the date in two places, and store the date of the last time run. If it goes backwards, I'd write something telling me to never work again ( so long as it went back 24 hours, otherwise could be daylight savings or a timezone change )
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
I would just store the date in two places, and store the date of the last time run. If it goes backwards, I'd write something telling me to never work again ( so long as it went back 24 hours, otherwise could be daylight savings or a timezone change )
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
What about when the clock is changed for legitimate reasons and the user forgets to reset the clock before running the trail software again?
Steve Jowett ------------------------- It is offen dangerous to try and see someone else's point of view, without proper training. Douglas Adams (Mostly Harmless)
-
What about when the clock is changed for legitimate reasons and the user forgets to reset the clock before running the trail software again?
Steve Jowett ------------------------- It is offen dangerous to try and see someone else's point of view, without proper training. Douglas Adams (Mostly Harmless)
Rered my post - there's no legitimate reason to move your code > 24 hours, unless it was wrong to start with, this is rare.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
Rered my post - there's no legitimate reason to move your code > 24 hours, unless it was wrong to start with, this is rare.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
Christian Graus wrote:
there's no legitimate reason to move your code > 24 hours, unless it was wrong to start with
I can think of several reasons where the date is changed. Our accounts department often changes the date. I changed the date on my PC serval times today, whilst developing date sensitive software, to test different functions.
Steve Jowett ------------------------- It is offen dangerous to try and see someone else's point of view, without proper training. Douglas Adams (Mostly Harmless)
-
Christian Graus wrote:
there's no legitimate reason to move your code > 24 hours, unless it was wrong to start with
I can think of several reasons where the date is changed. Our accounts department often changes the date. I changed the date on my PC serval times today, whilst developing date sensitive software, to test different functions.
Steve Jowett ------------------------- It is offen dangerous to try and see someone else's point of view, without proper training. Douglas Adams (Mostly Harmless)
Well, I guess if someone is writing software ,that's another ting. For accounting to do it, seems strange to me. However, the average user does not, and if you don't do that check, you have to allow people to run your software as long as they run the date back.
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven()" is a very good choice for a function name" - SpacixOne ( offering help to someone who really needed it ) ( spaces added for the benefit of people running at < 1280x1024 )
-
Any help me? I have a problem to make a Trial Program with VS 2005,. Thanks,.
Hellooooooooo,.. May I Join??
You can enstore an encrypted day counter in the registry that the program checks everytime it runs, as long as you use a relatively difficult key to crack, the majority of people will not be able to break it. This works best if you go off times used as oppose to if the date has been changed, because people can always wind the clock back before it ends. There are some great articles on CP about Registry keys and encryption.
Please check out my articles: The ANZAC's articles