Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!camex!circus!kent From: kent@circus.camex.com (Kent Borg) Newsgroups: comp.sys.mac.system Subject: Re: 7.0B1 question Finder memory size & Syquests Keywords: Finder 7.0B1 Syquests Memory Copying Message-ID: <1694@camex.COM> Date: 7 Dec 90 00:45:01 GMT References: <33819@athertn.Atherton.COM> <27586@cs.yale.edu> Sender: news@Camex.COM Reply-To: kent@camex.com (Kent Borg) Organization: Camex Inc., Boston, MA Lines: 35 In article <27586@cs.yale.edu> pharr-matthew@cs.yale.edu (Matthew Pharr) writes: >If i remember correctly, 7.0 dynamically allocates memory to applications >as they need it, so thus the get info doesn't have anything of that sort >to change. Nope. The memory model under 7.0 is not very different from the MultiFinder world of 6.0.x. Applications need to say how much memory they want at launch. After that they cannot get more (mostly) or give any up. BUT, there is one difference: The old MultiFinder temporary memory is closer to being real stuff now. Applications can get hunks of memory from MultiFinder (if they know how to ask for it) and keep those chunks longer than the next WaitNextEvent (the old restriction). This memory should be used in ways where, if needed, the user can do something to free up the temporary memory--like close a document or window. This means (I think) that new 7.0-only applications should be set to get a partition that is only big enough for basic purposes, and when the user does something extraordinary, get the extra from MultiFinder--and be prepared to give that up. P.S. As someone else wrote, you can use ResEdit to edit Finder's "SIZE" resource. I did that recently and things work better now. I then opened literaly hundreds of windows, and though things got slow, they kept working. On reboot, however, only the first 40 were re-opened--boooo. -- Kent Borg internet: kent@camex.com AOL: kent borg H:(617) 776-6899 W:(617) 426-3577 Kent's Invasion Countdown: 43 Days