Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!bionet!agate!ucbvax!unisoft!fai!sequent!cseaman
From: cseaman@sequent.UUCP (Chris "The Bartman" Seaman)
Newsgroups: comp.sys.amiga
Subject: Re: Copy protection (was Re: Awesome! No I am Pi**ed!)
Message-ID: <47893@sequent.UUCP>
Date: 5 Dec 90 22:07:10 GMT
References: <BK.90Nov29222757@tadtec.uucp> <JKH.90Dec3092012@bambam.pcs.com> <1990Dec5.041002.453@sbcs.sunysb.edu>
Organization: Sequent Computer Systems, Beaverton, OR
Lines: 25

dtiberio@libws3.ic.sunysb.edu (David Tiberio) writes:
< You mentioned that a code wheel or extensive documentation could stop
< pirates. It doesn't.

< Software pirates will break the source code so that the code wheels aren't
< needed, nor are any references to manuals (don't ask me how I know).

I doubt that anyone meant that code wheels or look-up-the-word-in-the-manual
types of copy protection would defeat piracy (I don't know of ANY method
which would be completely 'pirate-proof').  However, these methods are not
significantly easier to defeat, yet they DO allow legitimate users to
backup their disks, and potentially install their software on a hard disk
(not to mention the likelyhood that the software will run at all on
'enhanced' systems).

Is this really asking so much?

Regards,
Chris

-- 
Chris (Insert phrase here) Seaman |    ___-/^\-___
cseaman@gateway.sequent.com <or>  |  //__--\O/--__\\    nI' yIyIn 'ej yIchep.
...!uunet!sequent!cseaman         | //             \\
The Home of the Killer Smiley     | `\             /'