Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!spool.mu.edu!sol.ctr.columbia.edu!emory!gatech!mcnc!duke!physics!kds
From: kds@physics (Kevin Stokes)
Newsgroups: comp.misc
Subject: Re: MOST Shareware is junk
Message-ID: <22247@duke.cs.duke.edu>
Date: 7 May 91 15:56:38 GMT
References: <154598@pyramid.pyramid.com>
Sender: news@duke.cs.duke.edu
Reply-To: kds@physics.phy.duke.edu (Kevin Stokes)
Organization: Duke University Physics Dept.; Durham, N.C.
Lines: 21
Nntp-Posting-Host: physics.phy.duke.edu

In article <154598@pyramid.pyramid.com> lstowell@pyrnova.pyramid.com (Lon Stowell) writes:
...stuff deleted
>   Put any dates in the code, mess with my AUTOEXEC.BAT or
>   CONFIG.SYS files and I will swiftly remove your product from
>   my machine.
>
  I wouldn't want my autoexec.bat or config.sys messed with either,
but why would you object to a program keeping track of the date, by
re-writeing its own .EXE file?
  This is the scheme I use in my shareware product.  I think it works
well, because it doesn't nag the user, and lets them try the full featured
product for a reasonable period.  
  I will also say from experience, that shareware with no protection brings
in almost nothing.  The trick is to put the protection in, but in a way
that doesn't annoy users.


--
	Kevin Stokes
	Duke University Dept. of Physics	kds@phy.duke.edu
	Durham, N.C.      27706