Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site tolerant.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!sun!idi!oliveb!tolerant!berry
From: berry@tolerant.UUCP (David Berry)
Newsgroups: net.micro.mac
Subject: Re: Re: How do you clear the "File Busy" bit?
Message-ID: <276@tolerant.UUCP>
Date: Wed, 5-Feb-86 18:26:54 EST
Article-I.D.: tolerant.276
Posted: Wed Feb  5 18:26:54 1986
Date-Received: Fri, 7-Feb-86 22:10:31 EST
References: <3157@sdcc3.UUCP> <188@sivax.UUCP> <3158@sdcc3.UUCP>
Organization: Tolerant Systems, Inc.  San Jose, CA
Lines: 20

> It brings up a different question, though, about why ResEd pretended to clear
> the bit in 0.8 (and didn't actually) and wouldn't allow it in 1.0 D4.  Both
> versions pretended to delete the file but didn't actually.  Is the "File
> Busy" bit so sacred that even the hacker's ResEd can't touch it?  While the
> Finder merrily ignores it given the correct keys?  (Where is that documented,
> anyway?)
	Something that I have discovered quite recently is that the
PBSetInfo trap doesn't change the file flags portion of the information
structure.  It only affects the creation date, modification date, and
Finder information structure.  The busy bit is actually a bit in the
file flags word and therefore can't be changed short of actually changing
the actual disk block.
-- 

	David W. Berry
	dwb@well.UUCP
	Delphi: dwb
	{ucbvax,pyramid,idsvax,bene,oliveb}!tolerant!berry

	I'm only here for the beer.