ccw@nvuxr.UUCP (christopher wood) (09/22/88)
Hello, all! I have a little problem here. I have a couple of desk accessories (Unstuffit, sigmaedit) that, when I try to open them, just go beep instead. I'm running system tools 6 (finder 6.2, system 6.0, multifinder 6.0) on a 5 Mbyte Mac II (256 color screen). About the finder reports over a megabyte in free memory. Is there any way to increase the memory for DA handler? I'm stumped. Anyone else have this problem? Chris Wood ...bcr!nvuxr!ccw
ech@poseidon.UUCP (Edward C Horvath) (09/23/88)
From article <771@nvuxr.UUCP>, by ccw@nvuxr.UUCP (christopher wood): > ...I have a couple of desk accessories (Unstuffit, sigmaedit) > that, when I try to open them, just go beep instead... The DA needs more memory. Advice from Apple is to open DAs that you hope to use BEFORE starting any other applications (this presumably allows the DA Handler to expand appropriately, which implies that the DA Handler can expand it's partition, something MY application can't do!). This also defeats the whole idea of a DA, which is to be something close at hand when you encounter a need for it...sigh... The alternative, which works for me *most* of the time, is to hold down option to force the DA into the current application's heap. For some reason, I get a sense of vengeance when I inflict that abuse on the Finder's heap. Naturally, very large DAs are not going to make it under all circumstances: apps aren't required to give DAs lots of room. =Ned Horvath=
goldman@Apple.COM (Phil Goldman) (09/25/88)
In article <513@poseidon.UUCP> ech@poseidon.UUCP (Edward C Horvath) writes: >From article <771@nvuxr.UUCP>, by ccw@nvuxr.UUCP (christopher wood): >> ...I have a couple of desk accessories (Unstuffit, sigmaedit) >> that, when I try to open them, just go beep instead... > >The DA needs more memory. Advice from Apple is to open DAs that you >hope to use BEFORE starting any other applications (this presumably >allows the DA Handler to expand appropriately, which implies that the >DA Handler can expand it's partition, something MY application can't do!). >This also defeats the whole idea of a DA, which is to be something close >at hand when you encounter a need for it...sigh... > DAs go in the system heap, not the DA Handler heap. The DA Handler heap is just large enough to fit its code resources and resource map. It does not expand. The reason it is useful to launch the DA Handler first is that otherwise it will cause fragmentation in the MultiFinder heap, if it hangs around, since like all apps it is locked at a certain location. The advice for DAs holds for apps as well. If you have an app that you will be using for a long time you should launch it first. The advice needs to be more explicit for DAs only because to the casual user there is not (and ideally shouldn't be) any knowledge of the DA Handler. Possibly the reason that the large DAs are not launching is that somehow the system heap is being constrained, either by running many apps, or else by running an app that must run in the first meg of memory. If no DAs are opening then it is possible that the DA Handler is no longer in the system folder. -Phil Goldman Apple Computer