jchiu@ccvaxa.UUCP (03/15/88)
/* Written 1:36 pm Mar 11, 1988 by lsr@Apple.COM in ccvaxa:comp.sys.mac */ >> ... Sure it would have been easier and >> smaller to design in MultiTasking from the start, but MultiFinder is not >> large (50K) and it works very well... Off the heated topic of window interface, does anyone care to explain the memory requirement for starting multifinder? Typically, after starting up with plain finder, the About Box says: 220K for the system, 8xxk(the rest) for the finder Then, if I start up multifinder by double click its icon with opt and command keys, the About Box will say: 350K for the system 160K for the finder It does seem to take more than 50K for the system heap when using multifinder, isn't it? Is this memory usage typical (normal) on a 1-Meg SE? Jeff Chiu Gould CSD-Urbana jchiu@gswd_vms ihnp4!uiucuxc!ccvaxa!jchiu
lsr@Apple.COM (Larry Rosenstein) (03/17/88)
In article <62100001@ccvaxa> jchiu@ccvaxa.UUCP writes: > > 350K for the system > 160K for the finder The difference is probably system resource that you don't notice under UniFinder because they are in the application heap. Under MultiFinder, resources that come out of the System file are loaded into the system heap, rather than the application heap. A good example are fonts. Under regular Finders, any fonts used by the Finder would be in the 8xxK of memory assigned to it. Under MultiFinder, this memory would fall into the System category. The advantage of this is that if you run another application that uses the same fonts, the resources will be loaded only once. -- Larry Rosenstein, Object Specialist Apple Computer, Inc. 20525 Mariani Ave, MS 32E Cupertino, CA 95014 AppleLink:Rosenstein1 domain:lsr@Apple.COM UUCP:{sun,voder,nsc,decwrl}!apple!lsr