Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!uunet!dlogics!kam
From: kam@dlogics.COM (Kevin Mitchell)
Newsgroups: comp.sys.mac.misc
Subject: Re: ToMultiFinder and SuperSpool (Re: Why I can't print under MultiFinder)
Keywords: I DISCOVERED the problem!
Message-ID: <708@dlogics.COM>
Date: 18 Dec 90 15:24:21 GMT
References: <138@atux01.UUCP> <5076@husc6.harvard.edu>
Organization: Datalogics Inc., Chicago
Lines: 15

In article <5076@husc6.harvard.edu>, siegel@endor.uucp (Rich Siegel) writes:
> 	(I also wonder why SuperSpool really cares whether MultiFinder
> is running or not - the gospel is that correctly-written software shouldn't
> have to know...)
> 

The SuperSpool and SuperLaserSpool allocate permanent space for the spool program
and work area under Finder. Under Multifinder, they launch the spool program 
as necessary, so you don't have to commit the memory to it all the time.

-- 
Kevin A. Mitchell                (312) 266-4485
Datalogics, Inc                  Internet: kam@dlogics.UUCP
441 W. Huron                     UUCP: ..!uunet!dlogics!kam
Chicago, IL  60610               FAX: (312) 266-4473