Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ucbvax!hplabs!qantel!ptsfa!pttesac!vanam
From: vanam@pttesac.UUCP (Marnix van Ammers)
Newsgroups: net.micro.amiga
Subject: Re: Copy protect methods & paranoia
Message-ID: <259@pttesac.UUCP>
Date: Fri, 8-Aug-86 18:00:56 EDT
Article-I.D.: pttesac.259
Posted: Fri Aug  8 18:00:56 1986
Date-Received: Mon, 11-Aug-86 03:10:56 EDT
References: <236@neoucom.UUCP> <169@hao.UUCP> <584@mips.UUCP> <1539@well.UUCP> <257@pttesac.UUCP> <246@neoucom.UUCP>
Reply-To: vanam@pttesac.UUCP (-Root Admin-)
Organization: Pacific Bell ESAC, San Francisco
Lines: 24

In article <246@neoucom.UUCP> wtm@neoucom.UUCP (Bill Mayhew) writes:
>
>	Ture, Maxicomm's solution of compiling your credit card
>number and name into the source code would seems to be a solution.
>It would certainly make one guard a disk as carefully as one's
>credite card.  There is a little hitch in that, though.  Here at
>the University we have Amigas, and we order things with nasty
>purchase orders.  You can darn well bet that I'm not going to
>sacrifice the integrity of my own credit card so that my Lab can
>use a program that may be backed up.  (I suppose I could alwalys
...

It doesn't *have* to be a credit card number, although that
probably works best.  They can also put in there your school's
name, and the name and tel # of whoever is going to be responsible
for the program.  This doesn't mean that they can do anything
about it if that person lets the program get out, but it would
sure put a bad name on the school and that person and I suppose
the software company would never sell to that school/person
again.

It still seems like the best all around solution.

Marnix