dlw@Atherton.COM (David Williams) (12/04/90)
A question about System 7.0B1 concerning memory allocated to the finder... Using the current 6.x series system one may increase the amount of memory allocated to the finder via Get Info. This is nice as I've noticed that without a healthy amount of memory copying many files (ie +300) at a time or one large file to a syquest cartridge will fail. The system gives a disk write (cancel continue) error. From what I've seen of 7.0B1 System the Finder's memory does not seem to be changeable. If you do a get info on it you can't change its allocation as it does not even show one. Is there a preferences somewhere else to allow one to increase the amount of memory the Finder has available to it? Or are the owners of some 600,000 syquest cartridges potentially out of luck in terms of 7.0? It would be highly irrtating to have Finder copies continually fail simply because it can not make use of memory that is physically or virtually available when needed. It looks as if the Finder permanently uses only 330k or so of memory...(this figure is not precise as I am not currently staring at the About the Finder box). As I remember some people also found that running with a larger finder helped them out when running Virtual as well. So whats the scoop? How does one give the Finder more memory under 7.0? David Williams dlw@atherton.com
pharr-matthew@cs.yale.edu (Matthew Pharr) (12/05/90)
In article <33819@athertn.Atherton.COM> dlw@Atherton.COM (David Williams) writes: >A question about System 7.0B1 concerning memory allocated to the finder... > >Using the current 6.x series system one may increase the amount of >memory allocated >to the finder via Get Info. This is nice as I've noticed that without a >healthy amount of memory copying many files (ie +300) at a time or one >large file to a syquest cartridge will fail. The system gives a disk >write (cancel continue) error. > >From what I've seen of 7.0B1 System the Finder's memory does not seem to >be changeable. If you do a get info on it you can't change its allocation as >it does not even show one. >So whats the scoop? How does one give the Finder more memory under 7.0? 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. matt
jmunkki@hila.hut.fi (Juri Munkki) (12/05/90)
In <33819@athertn.Atherton.COM> dlw@Atherton.COM (David Williams) writes: >From what I've seen of 7.0B1 System the Finder's memory does not seem to >be changeable. If you do a get info on it you can't change its allocation as >it does not even show one. Is there a preferences somewhere else to allow one >to increase the amount of memory the Finder has available to it? Or >are the owners of some 600,000 syquest cartridges potentially out of luck in >terms of 7.0? It would be highly irrtating to have Finder copies continually >fail simply because it can not make use of memory that is physically or >virtually available when needed. I don't have a copy of System 7.0, but I'm fairly sure that this good old technique will work. 1) Make a copy of the Finder and put it in a folder. 2) Get Info on that file and change the allocated size. 3) Move the active Finder from the system folder into another folder. 4) Move the copy you modified into the system folder. 5) Reboot. ____________________________________________________________________________ / Juri Munkki / Helsinki University of Technology / Wind / Project / / jmunkki@hut.fi / Computing Center Macintosh Support / Surf / STORM / ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bob@nyssa.uucp (Bob Finch) (12/05/90)
In <33819@athertn.Atherton.COM> dlw@Atherton.COM (David Williams) writes: >So whats the scoop? How does one give the Finder more memory under 7.0? Changing the Finder's SIZE -1 resource with ResEdit works. -- Bob Finch bob%nyssa.uucp@unicorn.cc.wwu.edu bob@nyssa.uucp
ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) (12/06/90)
It seems to me that, if Apple took away the ability to easily change the Finder's memory allocation, it's because they don't think there's a good reason to do it any more. In other words, if you find a situation where increasing the Finder's memory size *does* help, it sounds like a bug, and should be reported as such. Disclaimer: what do I know? I'm still trying to get my copy of System 7.0 beta... Lawrence D'Oliveiro fone: +64-71-562-889 Computer Services Dept fax: +64-71-384-066 University of Waikato electric mail: ldo@waikato.ac.nz Hamilton, New Zealand 37^ 47' 26" S, 175^ 19' 7" E, GMT+13:00
kent@circus.camex.com (Kent Borg) (12/07/90)
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