Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/17/84; site think.ARPA Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!think!ejb From: ejb@think.ARPA (Erik Bailey) Newsgroups: net.micro.pc Subject: Re: Copy Protection Message-ID: <3624@think.ARPA> Date: Sat, 7-Dec-85 01:49:08 EST Article-I.D.: think.3624 Posted: Sat Dec 7 01:49:08 1985 Date-Received: Sat, 7-Dec-85 21:14:27 EST References: <506@uvaee.UUCP> <456@nicmad.UUCP> Reply-To: ejb@think.UUCP (Erik Bailey) Organization: Thinking Machines, Cambridge, MA Lines: 41 Summary: In article <456@nicmad.UUCP> brown@nicmad.UUCP (Mr. Video) writes: >In article <506@uvaee.UUCP> jaj@uvaee.UUCP (James A. Jokl) writes: >> >>A friend ... >>selling a daTa Base Application Designed To Run on IBM PCs and compatables, >>and wishes that it be copy protected. ... > > . . . > >If I were you, I would tell your friend to forget it. ... Consider the motion seconded. >But, here is the biggest reason of all. Copy protection doesn't really >protect anything. ... Couldn't have said it better myself... :-) >... The cure is then placed upon BBS systems around the country. There are MANY BBSs with entire file sections devoted to unprotects. My favorite is prounlok, which permantly mangles PROLOK protection. But seriously, the lag time from release to hack is not long - maybe a month or so. Then the hack gets distributed and people implement it as if the software wasn't protected at all, and like the unprotect is some sort of dumb setup program. From then on: protection, NO. Pain in the *ss, *YES*. Point made. >End of opinion. [Here come the flames :-(] No flame here... -- _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- -_- Erik Bailey -- 7 Oak Knoll (USENET courtesy of ihnp4!godot!ejb Arlington, MA 02174 Thinking Machines Corp. ejb@think.com.arpa (617) 643-0732 Cambridge, MA) "I was walking in a forest one day and a tree fell in front of me, and I didn't hear it."