Josh Kelley wrote:
> On 12/7/05, Feizhou <feizhou@xxxxxxxxxxxx> wrote:
>
>>>>Can't you do the same thing using raw printing, by configuring the
>>>>printer in Windows?
>>
>>
>>Hmm...you meant on a Windows server didn't you?
>>
>>>
>>>He means when you add a network printer, you don't need to carry the
>>>driver cd/disk with you to each Windows PC. Just browse for the printer
>>>and the Windows OS on the PC will automatically download the driver
>>>files and settings and then you are done.
>
>
> No, I meant on a Windows client. You can use a Windows client to
> install Windows drivers to a Samba print server that's operating in
> raw mode. Then you can configure the printer driver from the Windows
> client, and I'm pretty sure that saves the default settings on the
> Samba server. Then you can point-and-print from Windows (no manual
> driver installation needed), just as you could if you were using full
> (non-raw) Samba-CUPS integration.
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.
