Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!cs.umn.edu!uc!noc.MR.NET!gacvx2.gac.edu!dan
From: dan@gacvx2.gac.edu
Newsgroups: comp.sys.next
Subject: Re: Cap/Kip
Message-ID: <1991Apr10.170759.182@gacvx2.gac.edu>
Date: 10 Apr 91 23:07:59 GMT
Article-I.D.: gacvx2.1991Apr10.170759.182
References: <1991Apr8.211736.22881@macc.wisc.edu> <1991Apr9.182022.16485@visix.com>
Organization: Gustavus Adolphus College, St. Peter, Minnesota
Lines: 19

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.  Rumor is saying that the
remote printing support was reworked.  I don't have 2.1 running yet so I can't
say for sure.  Non-NeXT systems using the NeXT as the remote print server works
great under most NeXT OS revisions.  I have a VAX that uses lpr to send print
jobs to a LaserWriter connected via CAP to a NeXT (the VAX sends the print jobs
to the NeXT and the NeXT uses CAP to print them to the LaserWriter.)

-- 
Dan Boehlke                    Internet:  dan@gac.edu
Campus Network Manager         BITNET:    dan@gacvax1.bitnet
Gustavus Adolphus College
St. Peter, MN 56082 USA        Phone:     (507)933-7596