Re: Remote printing OS to Windows interface
From: Rob S (robatworkDeleteTheseFourWords_at_mail.com.INVALID)
Date: 06/27/05
- Next message: Rob S: "Re: Remote printing OS to Windows interface"
- Previous message: carmelo: "HELP with Simba ODBC Driver for Unify DBMS on Unix"
- In reply to: Tony Lawrence: "Re: Remote printing OS to Windows interface"
- Next in thread: Rob S: "Re: Remote printing OS to Windows interface"
- Reply: Rob S: "Re: Remote printing OS to Windows interface"
- Reply: Brian K. White: "Re: Remote printing OS to Windows interface"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 27 Jun 2005 13:40:54 +0100
Following the advice in this thread and in
http://www.aplawrence.com/Unixart/ldsprintwindows.html
I've got an hp printer working fine from a Unix lp command to a windows 2000
attached printer, with printcap entry
2550:\
:lp=:rm=rob-pc:rp=2550:sd=/usr/spool/lpd/2550:\
:mx#0:
If I add the of entry to this so that it reads:
2550:\
:lp=:rm=rob-pc:rp=2550:sd=/usr/spool/lpd/2550:\
:mx#0:of=/filters/hpt:
then it won't print, regardless of what is in /filters/hpt. For example even
with just
#!/bin/sh
in /filters/hpt the job sits in the unix queue, and windows gives an event log
id 4007 Illegal format used for commands received from 192.168.0.111 : service
refused. I've tried several filter entries all with the same result.
Any ideas?
thanks
-Rob
cc by email to Lytle David Smith
- Next message: Rob S: "Re: Remote printing OS to Windows interface"
- Previous message: carmelo: "HELP with Simba ODBC Driver for Unify DBMS on Unix"
- In reply to: Tony Lawrence: "Re: Remote printing OS to Windows interface"
- Next in thread: Rob S: "Re: Remote printing OS to Windows interface"
- Reply: Rob S: "Re: Remote printing OS to Windows interface"
- Reply: Brian K. White: "Re: Remote printing OS to Windows interface"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|