Path: utzoo!utgpu!attcan!uunet!lll-winken!ames!ncar!mailrus!cornell!uw-beaver!rice!sun-spots-request From: cml@cis.ohio-state.edu (Christopher Lott) Newsgroups: comp.sys.sun Subject: Re: Apple Laserwriter the same as Sun Laserwriter Message-ID: <8812301530.AA03413@brachiosaur.cis.ohio-state.edu> Date: 7 Jan 89 00:38:31 GMT Sender: usenet@rice.edu Organization: U.Va. CS in Charlottesville VA Lines: 36 Approved: Sun-Spots@rice.edu Original-Date: Fri, 30 Dec 88 10:30:57 EST X-Sun-Spots-Digest: Volume 7, Issue 90, message 8 of 9 Hi, About 2 years or so ago, I hooked an Apple LW to a Sun 2/50, using the Adobe Transcript package, and it worked _great_. When I asked Sun Support about it (don't remember why I was calling, hm) they said that their laserWriter was just the Apple laserWriter with a new logo. It's a straight postScript printer, no matter the logo on the outside. Transcript just puts out straight ps code, so it should not be a problem. Some folks have posted instructions for hooking a sun to a lw; here's what I have: [[ The original message is in volume 5 number 60. I have removed all but the essentials. --wnl ]] > From: parns!harker@sun.UUCP (Robert Harker, all around good guy) > Subject: Re: sun laserwriter help > > ...do the install on > the server as if the LaserWriter was locally installed on the server. > Then when the install is complete you copy the printcap file generated for > the server to the client with the LaserWriter attached, deleting any bogus > entries for other printers. On the client you also link the device that > the Laserwriter is attached to to /dev/lw... Make sure that the server > has an entry for the > LaserWriter that is remote printer entry, not a local printer entry, ie: > > lw|ps|postscript|PostScript:\ > :lp=:\ > :rm=client:\ > :rp=lw:\ > :sd=/usr/spool/lw: cml -- cml@tut.cis.ohio-state.edu Computer Science Department, OSU 614-292-6546 or: ...!{att,pyramid,killer}!osu-cis!cml