> Thanks Al,
> 
> > First, it sounds like the memory settings for your application are too low. FB
> > apps seem to store the contents of the clipboard in it's own memory so if the
> > user has a 400K PICT on the clipboard, the app will use an extra 400K of
> > memory just to launch. You should be aware of this especially if your program
> > does any copying and pasting of PICTs. Try copying a very large PICT to the
> > clipboard and then see if you can launch. If not, set the memory requirements
> > a bit higher.
> 
> Yes, this does indeed seem to be the problem. My memory allocations are
> fine for my code and structures, but the problem is with this clipboard
> business. Unless I'm totally missing something here, isn't the clipboard
> a dynamic structure? How can I possiblly predetermine an unknown value?
> And how am I supposed to sell/promote a simple FB-built appl that
> requires an excessive amount of RAM -- just in case I encounter a large
> clipboard?
 
It appears (even though it's not documented anywhere) that the clipboard
overhead is not allocated using the mini-application shell. A solution,
but not really a practical one for me at this point.

Chris, I think it would be in everyone's best interest for you to remove
this happenstance from the FB code and and post an update. Unless
there's another work-around, the alternative to you changing a few lines
of code is that I have to recode everything I've ever created in FB. And
not only do I have to recode, but I can't ship any product  in the mean
time. Then I'll have to break down inventory and repackage, replace
inventory with distributors, send updates to my user-base, etc. <sigh>

Please advise.

DL