Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!uakari.primate.wisc.edu!ginosko!uunet!ncrlnk!ncr-sd!hp-sdd!ucsdhub!sdcsvax!network.ucsd.edu!HP-UX!dpaight
From: dpaight@HP-UX.ucsd.edu (Dan Paight)
Newsgroups: comp.sys.mac
Subject: Re: Boomerang 2.0B8 problem ...
Keywords: Boomerang, Macintosh
Message-ID: <2009@network.ucsd.edu>
Date: 16 Oct 89 05:14:41 GMT
References: <2472@jarthur.Claremont.EDU>
Sender: nobody@network.ucsd.edu
Reply-To: dpaight@weber.UUCP (Dan Paight)
Distribution: na
Organization: SSCF, UCSD
Lines: 21

In article <2472@jarthur.Claremont.EDU> mberline@jarthur.UUCP (Marty Berliner) writes:
>Hello there ...
>
>   Among all the nice enhancements in Boomerang 2.0B8, the one which pleased
>me the most was the option of keeping the CODE resource in memory at all
>times (so that any SF dialog box would appear quickly, without all the
>time spent in Boomerang loading all its code).
>   The problem is that it seems that this feature does not work with my
>system setup (Plus, 6.0.4, 2.5M, various inits & cdev's).  Anyone else
>experience this problem?  
>
>Marty

I'm using Boomerang 2.0b8 also. I also am running  it on a Plus,
6.0.3, 2.5M, etc. The 'keep code in system heap' feature seems to
work fine on my system (and I've checked).

dp

p.s., Don't you just love Boomerang?  Don't know what I'd do without
it.