Xref: utzoo comp.sys.mac:14351 comp.sys.mac.programmer:304
Path: utzoo!mnetor!uunet!husc6!mailrus!nrl-cmf!ames!claris!apple!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer
Subject: Re: AAAAAAARRRRRRRRRGGGGGGGGHHHHHHH!  HELP! ETC!
Message-ID: <7768@apple.Apple.Com>
Date: 23 Mar 88 22:53:37 GMT
References: <1315@ut-emx.UUCP>
Reply-To: lsr@apple.UUCP (Larry Rosenstein)
Followup-To: comp.sys.mac.programmer
Organization: Advanced Technology Group, Apple Computer
Lines: 30
Keywords: SFScrollinit

In article <1315@ut-emx.UUCP> cgeiger@ut-emx.UUCP (charles s. geiger, esq.) writes:
>Today I downloaded the new SFScrollinit which was posted here a
>couple of days ago.  I went to take the old one out of my system
>folder (to save it in case the new one didn't work right), and IT
>WASN'T THERE!  I'm totally confused, because my machine still works

What program did you use for the downloading?  It is possible that it has a
bug.  The problem is that for certain file system calls, the File Manager
will look in the System Folder if a given file can't be found.

So if a downloading program deletes the file being downloaded first (in case
it already exists), then it is possible that it will delete a file with the
same name from the System folder by mistake.

The INIT would still be active, because that code gets installed at boot
time, and does not depend on having the actual file around once installed.
(This is true of most, but not all, INIT files.)

For programmers, the way to bypass this feature is to always specify a dirID
on file system calls.  You need to call PBGetWDInfo to determine the dirID,
given a working directory refnum.

[I directed followups to comp.sys.mac.programmer, since this is relevant
only to programmers.]

-- 
		 Larry Rosenstein,  Object Specialist
 Apple Computer, Inc.  20525 Mariani Ave, MS 32E  Cupertino, CA 95014
	    AppleLink:Rosenstein1    domain:lsr@Apple.COM
		UUCP:{sun,voder,nsc,decwrl}!apple!lsr