Richard A Downing wrote:
Alexander E. Patrakov wrote:
Alexander E. Patrakov wrote:
Alternatively, you may want to use the stock Adobe PostScript driver
(although I don't know any reason for such preference). In such case,
...
Hey, now that (all your post) MUST become a hint, at the very least!
Ideally a page in the BLFS book - it's vital information.
I thought I understood it, but clearly I didn't, since I didn't know
that it was possible to offer printer services to Windows without samba!
Sorry, I am not sure that it fits nicely on
http://www.linuxfromscratch.org/ because it is not a Linux hint. It
mainly discusses Windows configuration. If others think that it is not a
problem, I will turn this into a hint. There is also a possible
licensing problem. The inf files are:
cups.inf: modified MSDN sample, looks OK to redistribute
adobe.inf: this is basically pscript.inf from Windows 2000 with
irrelevant parts removed. OK to redistribute (as non-copyrightable
according to local law) because this can't be written in any
substantially different way.
As for winprinters, the untested sequence of actions is:
1) Install winprinter driver on the client (fixme: do all CDs allow to
install a driver without a printer being actually connected?)
2) Add a "raw" printer using CUPS webinterface, configure CUPS to accept
raw jobs from the client
3) Install Internet printer on Windows with the URL
http://www.example.com:631/printers/relevant-printer, try to pick the
proper driver when asked.
This will certainly fail for the printers that require talkback to the
computer, e.g. in order to get ink levels before actually printing
anything (but that's true also for SAMBA and even for Windows
implementation of printer sharing). That's why I always configure
printers shared via CUPS as pseudo-PostScript ones.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
