Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ukma!sean
From: sean@ms.uky.edu (Sean Casey)
Newsgroups: comp.sys.amiga
Subject: Re: Copy protection (Amiga Bad Image)
Message-ID: <6896@g.ms.uky.edu>
Date: Mon, 13-Jul-87 03:04:24 EDT
Article-I.D.: g.6896
Posted: Mon Jul 13 03:04:24 1987
Date-Received: Tue, 14-Jul-87 00:50:45 EDT
References: <4826@sgi.SGI.COM> <4238@jade.BERKELEY.EDU>
Reply-To: sean@ms.uky.csnet (Sean Casey)
Organization: The Leaning Tower of Patterson Office @ The Univ. of KY
Lines: 21
Keywords: software terrorism, copy protection, South Africa

In article <22939@sun.uucp> cmcmanis@sun.UUCP (Chuck McManis) writes:
>When the copy protection is
>done poorly (as in the case of MicroProse's Silent Service) the program will
>break. What happens next is the sad part, the user BLAMES THE AMIGA! Yes,
>thats right, the user say's "This stupid machine can't even run a program
>three times without corrupting a disk!" Which is TOTALLY UNTRUE.

Good Point!  I've already remarked about my Amiga's reputation for trashing
disks.  I have come to understand recently that it was really stupid
copy protection schemes that were bashing my disks.

I'm no technical expert, but I do have several years of C and Unix systems
programming experience, and years of experience on several micros.  If I
ignorantly blame it on the machine, you can bet the average Amiga buyer will.


Sean
-- 
--- Sean Casey   UUCP:  cbosgd!ukma!sean           CSNET:  sean@ms.uky.csnet
---              ARPA:  ukma!sean@anl-mcs.arpa    BITNET:  sean@UKMA.BITNET
--- We want... a shrubbery!