Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!ni.umd.edu!ni.umd.edu!zben
From: zben@ni.umd.edu (Ben Cranston)
Newsgroups: comp.protocols.appletalk
Subject: Re: Ethernet-based Color PostScript printer
Summary: Describes Macintosh TCP/IP printing solutions
Message-ID: <1991Mar15.182256.20324@ni.umd.edu>
Date: 15 Mar 91 18:22:56 GMT
References: <1991Mar3.000023.15970@aero.org> <1991Mar4.233654.16274@monu6.cc.monash.edu.au>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland at College Park
Lines: 33
Nntp-Posting-Host: ni.umd.edu

In article <1991Mar3.000023.15970@aero.org> louis@aerospace.aero.org
(Louis M.McDonald) writes:

> Is there a way for my Mac II to see an ethernet based PS printer that
> only accepts jobs via FTP? I have an ethernet card on the Mac II,
> and want to see the printer in the Chooser.

In article <1991Mar4.233654.16274@monu6.cc.monash.edu.au>
john@publications.ccc.monash.edu.au (John Wilkins) writes:

> If you get a solution to this, especially if it allows the hiding of
> the printer from unauthorised users and will work with a Linotronic
> RIP, please post the details here.

I've developed a set of code and patches to the LaserWriter 6.0 file
that cause printing to be diverted to a TCP/IP connection, unfortunately
using a locally-developed printer drive protocol that has at various
times been called NDQS, MDQS(2), and NPP.  The implementation is similar
to the "Asynchronous LaserWriter" stuff except that instead of the ".SerA"
driver a custom ".NetPrint" driver is used.  This driver uses MacTCP to
open a TCP connection to a server host, and then passes it the print data.
It is roughly equivalent to doing a command-f print then FTPing the data.

I've also developed a print server INIT.  This passively listens on a
well-known TCP port.  When a client connects and opens a print file with
the protocol described above, the server opens a PAP connection to the
printer and passes the data on to the printer.

Both pieces are written in assembly code.  The first piece is somewhat
better debugged than the second at this point.

This is not likely to be a drop-in solution anywhere else but it could
serve as the starting point for further development.