🚀 go-pugleaf

A question from one naive about PC's.  We have a PC networked onto an
ethernet-work using NCSA's tcp/ip package.  That is, we can ftp and
telnet to the other machines.

From within MS-Windows, we would like to print directly to our postscript
printer, which is also networked.

Unfortunately, it is an Appletalk printer, networked through a converter
box (Dayna's Etherprint) -- so I do not want to print directly to the printer.

Rather, we would like to do this:

	1) select print in windows
	2) automatically save the postscript to a file.
	3) automatically ftp the file to a unix box.
	4) print the file from the unix box.

We have steps 2-4.  It is a script written in DOS that will take the name
of a postscript file, ftp it to the unix-box, and there, a daemon will 
send it to the printer.  A Kludge, but it works.

Question (finally) is:

	* Can we modify the standard printer drivers in MS-windows,
	so that they will save a postscript file, and then call our
	script?

Alternatively, are there any more sane (yet in$expensive$) alternatives?

Please e-mail any info you have (I don't normally follow the bboard).  If
interest warrants, I'll post a summary.

Thanks!

John.


--
John Lee	Research Scientist
Performance Signal Integrity, Inc.
email: jolly@bmw.ece.cmu.edu
voice: 412.682.7101