hal@aya.cs.cornell.edu (Hal Perkins) (01/17/89)
In article <...> MacUserLabs@cup.portal.com (Stephan - Somogyi) writes: >SuperLaserSpool is not a proper init. To the best of my recollection >the installation procedure does the same as a 'Set Startup' on SLS. >SLS then quits to the Finder when it's done. SLS is in fact an >application, therefore it has a CODE 0 that can be messed with. Old versions of SuperLaserSpool and SuperSpool worked this way, but the new versions that came with release 7.0 of the DataFrame utilities are real inits that are installed by just dropping them into the system folder. (I'm sure if I'm wrong many people will feel free to correct me with great enthusiasm.) Hal Perkins hal@cs.cornell.edu Cornell CS
MacUserLabs@cup.portal.com (Stephan - Somogyi) (01/19/89)
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. Regardless of the terminology question, nVIR propagates when TEInit is called; it then patches CODE 0 to point to the virus. After the viral code is done, nVIR executes the jump table entry that was replaced. SLS is succeptible to this. Stephan <- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -> Stephan Somogyi AppleLink: X1058 Software Engineer BIX: mulabs MacUser Labs CIS: 72511,16 950 Tower Lane, 18th Floor GEnie, MacNET: MULABS Foster City, CA 94404 FAX: (415) 378-5675 ...sun!cup.portal.com!MacUserLabs or MacUserLabs@cup.portal.com Any opinions expressed above are mine.
u545731798ea@deneb.ucdavis.edu (Greg DeMichillie) (01/21/89)
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.
newsuser@LTH.Se (LTH network news server) (01/28/89)
In article <3531@ucdavis.ucdavis.edu> lgdemichillie@ucdavis.edu (Greg DeMichillie) writes: >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. I had the same problems when I started to use SuperLaserSpool (2.0) with my ImageWriter II. It was very annoying. However, it was not SLS's fault. When I checked the spool folder (which I had made invisible with ResEdit), there was a document that was not a spool file. Most likely I've put it there myself (don't ask me why). SLS started every 3 seconds or so, checked the document, and decided to ignore it. Repeat forever. When I removed the offending document, everything was OK. SLS runs silent in the background, and you don't notice it until you start to print. Due to some other incompability (with inits/cdevs or system 6) I've stopped using SLS (I think the problem is with some init, not with SLS), but that's another story. When will Apple support background printing for the Image- Writer??? -- Roland Mansson, Lund University Computing Center, Box 783, S220 07 Lund, Sweden Phone: +46-46107436 Fax: +46-46138225 Bitnet: roland_m@seldc52 Internet: roland_m@ldc.lu.se or roland_m%ldc.lu.se@uunet.uu.net UUCP: {uunet,mcvax}!enea!ldc.lu.se!roland_m AppleLink: SW0022
urlichs@smurf.ira.uka.de (Matthias Urlichs) (01/31/89)
In comp.sys.mac roland@DNA.LTH.Se (Roland Mansson) writes:
< Due to some other incompability (with inits/cdevs or system 6) I've stopped
< using SLS (I think the problem is with some init, not with SLS), but that's
< another story.
Problem at my Mac: When one certain DA is installed via Suitcase II,
SLS woill print the first job and then crash the Mac. MascBug doesn't get me
out of that one (except restart with "RS"). Still have to test which DA,
and why.
BTW, I am printing on an AppleTalk ImageWriter. Why does that damn thing pause
after each and every four screeches (read: half lines) in High quality?
--
Matthias Urlichs -- Humboldtstrasse 7 -- 7500 Karlsruhe 1 -- FRG
urlichs@smurf.ira.uka.de -- ++49+721-621127@PTT