guinn@mail.utexas.edu (Tim Guinn) writes: >>Do you have the memory partition set high enough on both? > >"both" meaning MacPerl itself *and* the droplet? Memory allocation on the droplet only affects the number of files you can drop. >The MacPerl partition >on both machines is substantial enough that I can run simple s///-type >droplets on 5+MB text files w/o any problem. Different operation, I know, Indeed. A line like "use Net:SMTP" translates into an enormous amount of memory allocation. >I figured the "Out of Memory!" warning was bogus. He he. It's not as if I had a Leprechaun linked into MacPerl which delights in giving bogus Out of Memory warnings. Out of Memory is *always* serious and sadly not always recoverable. Hmm... maybe I should simply put up a dialog and quit on Out of Memory, given that I don't quite manange to handle recovery correctly? >>It's been my experience that out of memory conditions can cause MacPerl >>to become unstable. > >I'd make reference to Net$cape's low memory behavior, but that comparison >would be an insult to Matthias ;-) Not at all. I'd be delighted to be compared to Netscape if only someone would arrange a $200M IPO for me :-) Matthias ----- Matthias Neeracher <neeri@iis.ee.ethz.ch> http://www.iis.ee.ethz.ch/~neeri "I'm set free to find a new illusion" -- Velvet Underground