Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!ucdavis!deneb.ucdavis.edu!u545731798ea From: u545731798ea@deneb.ucdavis.edu (Greg DeMichillie) Newsgroups: comp.sys.mac Subject: Re: SuperLaserSpool (was Re: nVIR ...) Message-ID: <3531@ucdavis.ucdavis.edu> Date: 20 Jan 89 22:00:42 GMT Sender: uucp@ucdavis.ucdavis.edu Reply-To: lgdemichillie@ucdavis.edu (Greg DeMichillie) Followup-To: comp.sys.mac Organization: University of California, Davis Lines: 39 In article <13655@cup.portal.com> MacUserLabs@cup.portal.com (Stephan - Somogyi) writes: >I was immediately corrected by someone at SuperMac that SLS was in >fact an INIT; my apologies, it was my error. > >Nonetheless, SLS contains a jump table and CODE. The guy here at the >office who uses SLS swears that when it becomes active, he gets a >little icon for it in his MultiFinder menu. I guess calling SLS a >hybrid would be more accurate. > I think hybrid is the best term. SLS seems to behave as though a program was being lauched every few seconds, checking to see if there are spooled files waiting print and if not, exiting. If you select "About the Finder" and watch the memory allocation graph you will see a block of memory allocated and de-allocated on a semi- regular basis. The problem is, the Mac locks up for a fraction of a second while this lauch/check/exit process goes on. This annoyed me so much I've gone back to direct ImageWriter printing instead of their spooler. In all fairness, I think PrintMonitor works in a similar fashion, but I don't notice the delay when it works. > >Stephan Somogyi AppleLink: X1058 >Software Engineer BIX: mulabs >MacUser Labs CIS: 72511,16 >...sun!cup.portal.com!MacUserLabs or MacUserLabs@cup.portal.com >Any opinions expressed above are mine. ----- Greg DeMichillie Apple Student Rep - UC Davis lgdemichillie@ucdavis.edu AppleLink: ST0178 Disclaimer: If you've seen one disclaimer, you've seen them all.