Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!darkstar!ucscb.UCSC.EDU!unknown
From: unknown@ucscb.UCSC.EDU (The Unknown User)
Newsgroups: comp.sys.apple2
Subject: Copy Protection (was:Re: Rastan)
Message-ID: <6306@darkstar.ucsc.edu>
Date: 24 Aug 90 10:50:19 GMT
References: <3945@crash.cts.com> <1753@oucsace.cs.OHIOU.EDU>
Sender: usenet@darkstar.ucsc.edu
Organization: University of California, Santa Cruz; Open Access Computing
Lines: 24


In article <1753@oucsace.cs.OHIOU.EDU> bchurch@oucsace.cs.OHIOU.EDU (Bob Church) writes:
>In article <3945@crash.cts.com>, lbotez@pro-sol.cts.com (Lynda Botez) writes:
>> For those who are curious as to what happened to Rastan (which is finished);
>> apparantly John Brooks' copy protection is causing duplicating problems.
>You mean until the problem is installed. It's hard to believe that people
>are still ruining perfectly good software with copy protection.

	Especially when some cracking group (the F.U.C.K. comes to mind
because of their purposely crude name) is probably going to have the thing
cracked and distributed around the country (in hours), before it even gets
to stores.
	The look-up-a-word-in-the-manual seems like the only decent 
copy protection... If they somehow hide where they check if what you
typed in was right.. [Changing -1 bit- on the disk will remove/solve that
kind of copy protection!]  Plus, it's too much of a pain for people to type
in the manuals/important part of the manual...
	But when we have OCR software for the Apple II.. heh... Some
programs' documentation is already done on Xerox-proof paper.. I wonder if
it's also scanner-proof.

-- 
        /  Apple II(GS) Forever!     unknown@ucscb.ucsc.edu  \
        \    Computer engineering student seeking a job.     /