Method for providing a trail period on a program

[Larry Bates]

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.

[Ben Finney]

Re: Method for providing a trail period on a program

On Thu, 1 Apr 2004 17:46:12 -0600, Larry Bates wrote:[color=blue]
> 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.[/color]

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/>

[Josiah Carlson]

Re: Method for providing a trail period on a program

> I'm searching for a good way to provide a "trail[color=blue]
> 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?[/color]

Using windows registry pseudo-code

if stoptime_not_in _registry:
stoptime = time.time() + 90*24*3600
store_stoptime_ in_registry(sto ptime)
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

[Dang Griffith]

Re: Method for providing a trail period on a program

On Thu, 1 Apr 2004 17:46:12 -0600, "Larry Bates"
<lbates@swamiso ft.com> wrote:
[color=blue]
>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?[/color]

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