Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!OZ.AI.MIT.EDU!GZT.EWW
From: GZT.EWW@OZ.AI.MIT.EDU (Wes Williams)
Newsgroups: comp.sys.apple
Subject: Re: Write protection
Message-ID: <12379906200.78.GZT.EWW@OZ.AI.MIT.EDU>
Date: 5 Mar 88 14:15:50 GMT
References: <343@ga.ecn.purdue.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 25

Brent writes>How else could the original suddenly stop working
            >except to be written to?

Good question! I have not been a cracker as I needed my cpu time working
the systems or doing other things. I do think that a good general
description of the basic types of disk protection is worthwhile.

I would like some indication as to the methods employed for the following
types of copy protection.
        1. How does the " copy all you want until the disk has been booted
one time" work?
        2. How does the "copy from the original but not from a copy" work?
        3. How does the "lotus 123 ((I know, this is a different animal))
remove a hidden file from the disk on copy" work?
        4. I have seen protected software self destruct an original when
a copy program is run to make a backup. As these originals are write
protected, how is the protected software screwing things up?

I don't need the specifics, all those track and sector bits of info
boggle my mind and I mumble for a week. I'd just like to have a feel
for it.

\|/es  \|/illiams
gzt.eww@oz.mit.edu@xx.lcs.mit.edu.arpa

-------