Newsgroups: comp.sys.next
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!pa.dec.com!decuac!grebyn!walters
From: walters@grebyn.com (Chris Walters)
Subject: Re: Cap/Kip (really non-NeXT printing;2.X)
Message-ID: <1991Apr12.033124.11905@grebyn.com>
Summary: Not always
Organization: Grebyn Timesharing
References: <1991Apr10.170759.182@gacvx2.gac.edu> <4!fgxhj@rpi.edu> <xcfgc=l@rpi.edu>
Date: Fri, 12 Apr 1991 03:31:24 GMT

In article <xcfgc=l@rpi.edu> gad@eclipse.its.rpi.edu writes:
>In article <4!fgxhj@rpi.edu> Garance_Drosehn@mts.rpi.edu 
>           (that's me...) writes:
>  ...(first I quote someone else commenting on problems printing
>      to non-NeXT printers, and then I say)...
>
>>It should be noted that the problem with NeXT 2.0 and printing to non-NeXT
>>systems is readily fixable.  Just open a terminal window and enter the
>command:
>>
>>   dwrite System PrinterResolution 1

Not always!  It doesn't work for remote printing to a DEC LPS 20 on
a VAX 6000 running ULTRIX.  We have tried just about everything,
and if anyone has any ideas I'd like to hear them.

 Chris Walters
 walters@grebyn.com