Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site sdcc3.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!sdcsvax!sdcc3!borton
From: borton@sdcc3.UUCP (Chris Borton)
Newsgroups: net.micro.mac
Subject: Re: HFS compatability and Software backup - Simple solutions
Message-ID: <3145@sdcc3.UUCP>
Date: Sun, 19-Jan-86 15:52:48 EST
Article-I.D.: sdcc3.3145
Posted: Sun Jan 19 15:52:48 1986
Date-Received: Wed, 22-Jan-86 05:16:48 EST
References: <1636@Shasta.ARPA> <348@ccivax.UUCP>
Reply-To: borton@sdcc3.UUCP (Chris Borton)
Followup-To: net.micro.mac
Distribution: net
Organization: U.C. San Diego, Academic Computer Center
Lines: 26

In article <348@ccivax.UUCP> guest@ccivax.UUCP (What's in a name ?) writes:
>I was just wondering... An article on the net several months ago hinted that
>write-protecting a disk (with the tab in the upper left corner) didn't REALLY
>protect the disk; that it was up to the software to ask the OS if the disk
>was locked; that if the s/w didn't ask, the disk could be written to whether
>or not it was locked.    DOES ANYONE IN NETLAND KNOW IF THIS IS TRUE?????
>
>
>Sam Mantel -- Roch, NY

I believe this is true since I had a nasty experience with ResEdit (0.5 I
think) last spring.  I had the disk locked, and was trying to Paste a resource
into another file.  ResEdit gave a spurious error, not hinting at disk-lock
being the problem at all, and informed me that it couldn't save the file.
However, every time I tried, it would update the Last Modified: date/time for
that file.  One that 'it couldn't save' and was on a locked disk.  This 
indicates to me that disk-locking doesn't have any hardware protection at all.

Anyone have a more technical explanation?

--Chris
---------------
Chris Borton, UC San Diego Undergraduate CS	
Micro Consultant, UCSD

borton@ucsd.ARPA     or  ...!{ucbvax,decvax,noscvax,ihnp4,bang}!sdcsvax!borton