Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!uvm-gen!chaffee
From: chaffee@uvm-gen.UUCP (Alex D. Chaffee)
Newsgroups: comp.sys.mac.programmer
Subject: Re: What is OpenRFPerm doing?!?
Summary: What to do about corrupt files?
Keywords: resource corrupt OpenRFPerm
Message-ID: <1152@uvm-gen.UUCP>
Date: 21 Apr 89 21:37:16 GMT
References: <1146@uvm-gen.UUCP> <7017@hoptoad.uucp>
Organization: EMBA Computer Facility, Univ. of Vermont, Burlington.
Lines: 21

Tim, your intuition seems to be correct.  Although I haven't _quite_
finished debugging the whole program, it is obvious that the problem lies
with certain, apparently corrupt, resource files.

(For those of you who've just joined us:  When I opened the resource fork of
 a file with OpenRFPerm directly following an SFGetFile, my resource map
 got trashed, as evidenced by Alerts appearing off-screen and so forth.)

I now have two questions:

1)	ResEdit opens these files (there are two) fine, and the FKEYs within
	them work fine when installed into the system.  What can be special
	about them?

2)	How can I programmatically detect and/or correct this user-nasty
	situation?  Or any similar situation where the Resource Manager gets
	confused...  Is there an error-reporting function or global?  I seem
	to remember catching the end of a related thread on the net a week or
	two ago.

Thanks for any assistance or ideas.