Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!batcomputer!pyramid!voder!apple!lsr
From: lsr@apple.UUCP (Larry Rosenstein)
Newsgroups: comp.sys.mac
Subject: Re: Excel Meg Limit
Message-ID: <6456@apple.UUCP>
Date: Mon, 12-Oct-87 13:36:59 EDT
Article-I.D.: apple.6456
Posted: Mon Oct 12 13:36:59 1987
Date-Received: Wed, 14-Oct-87 00:46:59 EDT
References: <7272@dartvax.UUCP> <341@intvax.UUCP>
Reply-To: lsr@apple.UUCP (Larry Rosenstein)
Organization: Advanced Technology Group, Apple Computer
Lines: 30

In article <341@intvax.UUCP> loucks@intvax.UUCP (Cliff Loucks) writes:
>in article <7272@dartvax.UUCP>, erics@dartvax.UUCP (Eric Schlegel) says:
>
>> The latest issue of MacWEEK states that Excel will only work under
>> MF if it is loaded first, presumably so that the code will fall in
>> the first meg.
>
>I just loaded and ran Excel in Juggler with Versaterm and Moire
>loaded first.  I don't have any huge files, but it runs fine
>for me.

The reason it works is that Multifinder allocates memory for applications
starting with the top of memory and working its way down.  This makes it
possible for the system heap (which is at the low end of memory) to expand
as needed.  

I believe that Excel requires that it be loaded low in memory, and that
Multifinder contains code to accommodate this need.  Since most application
are loaded high, the low end of memory will usually be free, regardless
of the order in which application are run.

-- 
Larry Rosenstein

Object Specialist
Apple Computer

AppleLink: Rosenstein1
UUCP:  {sun, voder, nsc, mtxinu, dual}!apple!lsr
CSNET: lsr@Apple.com