By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,547 Members | 1,425 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,547 IT Pros & Developers. It's quick & easy.

Method for providing a trail period on a program

P: n/a
I'm searching for a good way to provide a "trail
period" (something like 90 days) for a commercial
application that I'm writing. I'd like something
that can easily stop working 90 days after
installation. Can anyone point me to something
that exists already?

Thanks in advance,
Larry Bates
Syscon, Inc.
Jul 18 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Thu, 1 Apr 2004 17:46:12 -0600, Larry Bates wrote:
I'm searching for a good way to provide a "trail period" (something
like 90 days) for a commercial application that I'm writing. I'd like
something that can easily stop working 90 days after installation.


Why do you want to break your user's programs to gain money? Will they
not pay for your work without their programs breaking? What does that
say about the value of your work?

--
\ "Conscience is the inner voice that warns us somebody is |
`\ looking." -- Henry L. Mencken |
_o__) |
Ben Finney <http://bignose.squidly.org/>
Jul 18 '05 #2

P: n/a
> I'm searching for a good way to provide a "trail
period" (something like 90 days) for a commercial
application that I'm writing. I'd like something
that can easily stop working 90 days after
installation. Can anyone point me to something
that exists already?


Using windows registry pseudo-code

if stoptime_not_in_registry:
stoptime = time.time() + 90*24*3600
store_stoptime_in_registry(stoptime)
if time.time() < stoptime:
continue working
else:
give registration warning and quit
FYI: most (if not all) methods for restricting users to some limited
trial period are flawed in some major way; users can take a snapshot of
their machine before installation and after installation and single run,
and determine what has changed to determine exactly what is necessary to
remove such protections.

- Josiah
Jul 18 '05 #3

P: n/a
On Thu, 1 Apr 2004 17:46:12 -0600, "Larry Bates"
<lb****@swamisoft.com> wrote:
I'm searching for a good way to provide a "trail
period" (something like 90 days) for a commercial
application that I'm writing. I'd like something
that can easily stop working 90 days after
installation. Can anyone point me to something
that exists already?


Look at http://www.macrovision.com/, formerly (or now owner of)
GlobeTrotter Software. It's pretty easy to use, and you can
set it up so users can "activate" their temporary
copy without having to get a new copy of the software.
--dang
Jul 18 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.