>>If I can collect a few from folks who _are_ crashing, and compare them to 
>>a few from folks who aren't, maybe I can find some common denominator.
>>
>>Bill
>>P.S. I assume this is different from the perennial "partial app created" 
>>resource error crash that's been around forever, even pre-OS 8. _That_ 
>>one I've seen, frequently, on my 7.6.1 Mac at work.

I too have had this problem, but only on a PowerMac.  I don't have access 
to a PowerMac for real testing, so I have managed to put together an INIT 
that should help us track down the problem and fix it.  The INIT monitors 
all resources being added to anything.  It will display the resource 
type, ID, and destination file.  It will also report any errors after the 
resource is added.  It will catch and warn you if the resource handle is 
invalid, has not been detached (and allow you to force the detach!) or if 
the destination file has been closed.  It also has the ability to force 
the resource to be written out to disk as soon as its added.

All of these options can be turned on and off on the fly via the Control 
Panel,  so you can leave it running on your machine, then when FB starts 
playing up,  turn on all the reporting features and watch what FB is 
doing!

The messages are displayed via MacsBug, so you need to have that 
installed.  I have tested it under 7.1, 7.5.5 & 8.0, but as I said, only 
on a 68k machine.

If there are any volunteers (with a PowerMac) to help me with this, 
please drop me an email so I can get your MacsBug logs from you, and 
generally co-ordinate the effort so everyone can benefit from what we 
learn.  The INIT is only 25k or so, and is available at:

http://www.ozemail.com.au/~benjamen/


Jamin