<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-2022-jp">
<META content="MSHTML 5.50.4922.900" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Ken Ray suggested:</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>> </FONT>Is the alwaysBuffer on for the images as well?
</DIV>
<DIV> </DIV>
<DIV>Thanks, but I tried that, too. Whether alwaysBuffer is set on or off, for
the stack or for individual image-objects, the standalone (not the stack)
crashes -- in fact, crashes also happen sometimes when building the
standalone.</DIV>
<DIV> </DIV>
<DIV>However, on a friend's more up-to-date Mac the standalone works fine.
Hmm....</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>> The only other thing I can think of is that<BR>> the MC application
has a larger memory partition defined for it than the<BR>standalones it creates
(although I'm pretty sure this isn't the case, but<BR>you can check in Get
Info).</DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Checking Get Info, MC doesn't have a larger memory partition
than the standalone. Also, for the standalone Prefered size is set to 6457,
available memory is 19.8Mb, and each jpg image that gets loaded is 78k (78x25k =
1950k). Plus, I double-checked each image for flaws.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>So, again, hmm....</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Suggestions still welcome. Thank you.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Nicolas Cueto</FONT></DIV></BODY></HTML>