On 12/7/05, Feizhou <feizhou@xxxxxxxxxxxx> wrote:
> Er...those drivers are installed on the Windows client, not the samba
> server. Bryan's case is rather special. He is not talking about a raw
> queue but a postscript queue. Since it is postscript, all the Windows
> clients just need to install a postscript print driver (which of course
> will be downloaded from the Samba server) and then they are done. The
> printer settings will have been setup on the Samba server via CUPS as he
> said.
>
> So, no you cannot do that through a Windows client to a Samba raw print
> queue. A raw print queue just sends the data direct to the printer. So
> it can only print ASCII or data in its own printer language. This
> therefore requires that the Windows client has a driver installed
> locally and therefore configured locally.
No.
With a Postscript print queue, you upload Windows printer drivers for
a generic Postscript printer to the Samba server (probably using the
cupsaddsmb script). With a raw print queue, you upload Windows
printer drivers for each printer to the Samba server (probably using
the Add Printer Wizard).
With a Postscript print queue, a Windows client that tries to print to
a Samba printer automatically downloads the appropriate driver. With
a raw print queue, the Windows client does the same. In either case,
the driver is technically installed locally, but no special effort on
the part of the user is required.
With a Postscript print queue, you can configure printer defaults on
the server, using CUPS. With a raw print queue, you can configure
printer defaults under an administrator account on a client, using the
Windows print driver, then it writes those defaults back to the server
for others to use.
Raw print queues really don't have the shortcomings in functionality
that you seem to be saying they do.
Josh Kelley
