Newsgroups: comp.sys.next
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usenet
From: Garance_Drosehn@mts.rpi.edu
Subject: Re: Cap/Kip
Message-ID: <4!fgxhj@rpi.edu>
Nntp-Posting-Host: gilead.its.rpi.edu
Reply-To: gad@eclipse.its.rpi.edu
Organization: Rensselaer Polytechnic Institute
References: <1991Apr8.211736.22881@macc.wisc.edu> <1991Apr9.182022.16485@visix.com> <1991Apr10.170759.182@gacvx2.gac.edu>
Date: 11 Apr 91 16:44:21 GMT
Lines: 32

In article <1991Apr10.170759.182@gacvx2.gac.edu> 
           dan@gacvx2.gac.edu writes:
>In article <1991Apr9.182022.16485@visix.com>, 
            amanda@visix.com (Amanda Walker) writes:
>> Um... doesn't Ultrix support BSD-style remote printing?  Can't you just
>> point your NeXT at your DEC machine?  This would seem to me to be the
>> simplest approach.
>
>NeXT 2.0 has a problem that would prevent a NeXT from remote printing to a
>non-NeXT system.  NeXT knows about the problem and has issued warnings to all
>NeXT support centers.  2.1 may fix the problem.

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

Note: Even after applying this workaround, you won't be able to print to
non-NeXT printers from the PrintManager application.  Also, if you're logged in
as root you won't be able to print to non-NeXT printers from some applications
(for example, Digital Librarian).  There is no workaround for these cases.

If after using this workaround you subsequently print to a non-NeXT printer,
the default resolution is reset and you cannot successfully print to non-NeXT
hosts until you perform the workaround again.

I've done the above workaround on my machine, and then pointed the NeXT box at
our non-NeXT print server machine.  Works great (but then I don't try to print
anything from "root").

Garance_Drosehn@mts.rpi.edu
  = gad@eclipse.its.rpi.edu for Next-Mail