Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!bgsuvax!denbeste
From: denbeste@bgsuvax.UUCP (William C. DenBesten)
Newsgroups: comp.sys.mac
Subject: Re: Morality of Self-Destructing HyperCard Stack
Message-ID: <5471@bgsuvax.UUCP>
Date: 27 Feb 90 19:38:31 GMT
References: <4286@helios.TAMU.EDU>
Distribution: comp.sys.mac,comp.sys.mac.programmer
Organization: Bowling Green State University B.G., Oh.
Lines: 30

In <4286@helios.TAMU.EDU>, t1f4387@helios.TAMU.EDU (Mike Farlow) writes:

> information).  As a result, the DEMO would automatically cripple itself
> after a preset amount of time.
> 
> Michael Farlow,                    X098MF@TAMVM1.BITNET


I have been writing a program for which fresh versions will be needed
periodically.  I was, like you are, contemplating crippling the
program after a preset date.  This really bothers me because someone
could very easily get a program that was unusable and have to wait
while they were getting a new version.

I have come up with what I consider to be a much superior method.
When you start the program, it checks to see if it is too old.  If it
is, it puts up a message that says "This is an old version.  To get a
current version, send me $5.00 (to cover the disk/copying/shipping) or
find it on a local bbs."  The user can then click OK and continue with
their work.

The danger is, of course, that I have to guess at the date of
obsolesence.  I figure that letting users know that it is time to
upgrade and where to upgrade will be something that they find useful.

I anticipate new versions every six months and a timeout about a year
after release.

-- 
William C. DenBesten   is   denbeste@bgsu.edu  or   denbesten@bgsuopie.bitnet