>"There is not enought memory to open
>'application' (zero K needed, zero K available).
>Closing windows or quitting desk
>accessories can make more memory
>available"

The "0K" message says that the system is confused. (If it was anything 
else, I'd consider fragmentation, etc...) I've seen this a few times, and 
the only "fix" was to reboot. It then worked fine. Trying to trace this 
in MacsBug led me to the "BowelsOfTheMemoryManager" label, and a clue 
that something was trashing the system heap. I've seen this message on 
_any_ 68K (why 68K? I dunno. PPC apps worked...) application I try to run 
at times - and the only "common" factor I could find is that before I got 
this, I'd been running Navigator or HP OpenMail. Both are notorious for 
memory leaks. If you're getting this frequently, I'd bet that you either 
use Navigator a lot, or you have some "misbehaving" extension out there 
that is causing problems.

If this _does_ happen right after a reboot, that proves the extension 
theory; it's time to buy ConflictCatcher and go through it's debugging 
routine. If it goes away after a reboot, then it's some application 
you're running that's messing up the system...

In any case, it's _unlikely_ to be a problem with the app that's actually 
failing!

Bill