At 12:35 PM +0100 2/11/01, Axel M. Roest wrote: >At 20:09 +1030 11-02-2001, Paul McCann wrote: >>Just a guess: maybe it's the memory allocation of the *droplet* and not >>MacPerl itself that's giving you grief? Try bumping that up from the 64K >>default and see if it helps. > >Thanks for the advice Paul, >I upped the memory allocation of the droplet to 10MB and it stil >gives an error (it's a *simple* droplet ;-) The error usually means that the OS can't find a continguous block of memory big enough to run MacPerl in. So increasing the memory partition of either MacPerl or the droplet is counterproductive. Try this: quit *all* running applications but the Finder, and then try starting your droplet. If it works, the problem is simply that you don't have enough memory for all of the things you're running in the order you run them. You may need to start MacPerl first and leave it running. If it doesn't work, there may be an OS problem, or a hardware memory problem. But I've been running 9.1 on both iMac and iBook and haven't seen anything like this with MacPerl that can't be solved by shutting down some running applications. When I was running Mac OS on my Performa 6400 (it now runs Linux most of the time), which has less memory than either the iBook or iMac, I routinely started MacPerl first and left it running. > >Axel > >_____________________________ >Axel M. Roest | AXEL Development & Support >[EMAIL PROTECTED] | Macintosh developer & UNIX sysadmin >http://www.axel.nu | XOIP: 020-8749988 -- -- Paul Schinder [EMAIL PROTECTED]
