Path: utzoo!mnetor!uunet!seismo!lll-tis!ati.tis.llnl.gov!sierra From: sierra@ati.tis.llnl.gov (Frankie Sierra) Newsgroups: comp.sys.mac.programmer Subject: Re: StartUpScreens Eats Memory!? Message-ID: <22193@tis.llnl.gov> Date: 11 May 88 00:01:38 GMT References: <22188@tis.llnl.gov> <9488@apple.Apple.Com> Sender: news@tis.llnl.gov Reply-To: sierra@ati.tis.llnl.gov (Frankie Sierra) Organization: Lawrence Livermore National Laboratory, Livermore CA Lines: 23 In article <9488@apple.Apple.Com> dan@apple.UUCP (Dan Allen) writes: >Most startup screen INITs that I have seen do NOT allocate their memory >on the system heap, but rather put the startup PICT in high memory and >adjust the low memory global BufPtr accordingly. Apple's RAM caching >scheme and MacsBug the Debugger both also use this method. > >Dan Allen >Software Explorer >Apple Computer StartUpScreen INITs are another game here, and yes, they do tend to gobble memory too. What I was referring to, in my original posting, was about standard vanilla files with just a resource fork with a PICT resource of ID = 0. No init, code, or whatever other resources. In other words, this is not the file's problem, but somehow a system problem, that is allocating system heap space for something that doesn't require it. Frankie Sierra Frankie Sierra sierra@ati.tis.llnl.gov