Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!uflorida!rex!rouge!lar From: lar@pc.usl.edu (Robert, Lane A.) Newsgroups: comp.sys.amiga Subject: Re: Thought's about AppleTalk. Message-ID: Date: 3 Jul 90 19:07:03 GMT References: <23442@snow-white.udel.EDU> <13832@wpi.wpi.edu> Sender: anon@rouge.usl.edu Reply-To: lar@usl.edu (Robert, Lane A.) Organization: Univ. of Southwestern LA, Lafayette Lines: 19 In-reply-to: jdutka@wpi.wpi.edu's message of 3 Jul 90 12:52:15 GMT In article <13832@wpi.wpi.edu> jdutka@wpi.wpi.edu (John Dutka) writes: In article <23442@snow-white.udel.EDU> GWO110%URIACC.BITNET@brownvm.brown.edu (F. Michael Theilig) writes: > I have *NEVER* seen a Mac take that long to print one page. And > if anyone has a messed up system, it's us. We have 8 Mac SEs hooked > to an Apple lazer printer and it never takes longer than 1 minuete to > print. We have 2 Macs (An SE and a IIx) and it takes about 3 minutes per page to print on our LaserWriter...) On the LocalTalk connected LazyWriter we have here, I've seen it take close to 5 minutes to print a page, and I've also seen it kick out pages at the top speed of the print engine. It seems to me that the print speed is more dependant on the CPU time necessary to interpret the PostScript code than the speed of the communication link. Lane lar@usl.edu