Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!cs.utexas.edu!samsung!think!bbn!rochester!udel!new
From: new@udel.edu (Darren New)
Newsgroups: comp.misc
Subject: Re: open this package and you're stuck with it
Keywords: returning software you're unhappy with
Message-ID: <11566@nigel.udel.EDU>
Date: 19 Feb 90 21:53:16 GMT
References: <48a44d7c.20b6d@apollo.HP.COM> <10760@saturn.ucsc.edu> <H7S1666xds13@ficc.uu.net> <9427@cbnewsm.ATT.COM>
Sender: usenet@udel.EDU
Reply-To: new@udel.edu (Darren New)
Distribution: usa
Organization: University of Delaware
Lines: 16

In article <9427@cbnewsm.ATT.COM> wg@cbnewsm.ATT.COM (Bill Gieske) writes:
>What prevents me from turning my clock back to withing the 30-day window of
>use anytime I want to use the software, thus "extending" my use indefinitely.

I've seen silicon compilers for mainframes liscenced on a month-to-month
basis. It's a real pain to switch clocks around on a mainframe that
several people are using.

If you've got an accounting application (or anything else, like Nag, that
depends on the dates being correct) then this won't work.  Datestamps
are critical for Make to work, so you probably wouldn't want
to play around like this for compilers.

Of course, thinkgs like paint programs can't be properly protected just
by switching the dates.
				   -- Darren