Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!lll-lcc!well!ptsfa!pttesac!vanam
From: vanam@pttesac.UUCP (Marnix van Ammers)
Newsgroups: net.micro.amiga
Subject: Re: Bug in 1.1 Protect Command
Message-ID: <268@pttesac.UUCP>
Date: Wed, 27-Aug-86 11:33:51 EDT
Article-I.D.: pttesac.268
Posted: Wed Aug 27 11:33:51 1986
Date-Received: Thu, 28-Aug-86 21:33:30 EDT
References: <897@tekig4.UUCP>
Reply-To: vanam@pttesac.UUCP (-Root Admin-)
Organization: Pacific Bell ESAC, San Francisco
Lines: 14

In article <897@tekig4.UUCP> billh@tekig4.UUCP (William Hansen) writes:
...
>or some such message. It appears that protect has protected the file from
>itself! Not only can't I access the file, but the disk now has an unusable
>spot since the file can't be deleted either. (This could be a real pain on a
>hard disk.) Has anyone else encountered this in 1.1, and does it still exist

Gee, someone could use this bug to advantage by writing a
disk error checking program that would (optionally) lock out
bad sectors.

On second thought,  that would be a bad idea.  Bugs should get
fixed, not used.  Otherwise people would complain of a bug when
the original bug got fixed. -- oh well ...