Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ll-xn!mit-eddie!bbn!uwmcsd1!csd4.milw.wisc.edu!neighbor
From: neighbor@csd4.milw.wisc.edu (Jeffrey Alan Ding)
Newsgroups: comp.sys.apple
Subject: Re: Write protection
Message-ID: <4995@uwmcsd1.UUCP>
Date: 2 Mar 88 04:19:52 GMT
References: <8802280319.aa05119@SMOKE.BRL.ARPA>
Sender: daemon@uwmcsd1.UUCP
Reply-To: neighbor@csd4.milw.wisc.edu (Jeffrey Alan Ding)
Organization: University of Wisconsin-Milwaukee
Lines: 15

In article <8802280319.aa05119@SMOKE.BRL.ARPA> D7314@uwavm (Patrick Ryan) writes:
>Write protection can be gotten around by pure software.  Copy 2+ (bit copy)
>version 3.xx would write to a copy-protected disk, but I don't know how they
>managed it...  I'll check into it and see what I can see.

You are ABSOLUTELY WRONG when you say that!  The hardware in the disk
drive will not write to a disk when the write protect switch senses
write protection.  If your program does not bother to check write
protection, the program will go through all the moves and it will appear
that you wrote to the disk.  But if you look at the disk, nothing will
have changed.

Write protection is hardware (at least on the Apple computer), not software.


neighbor@csd4.milw.wisc.edu