Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OpenServer Print Filters

Status
Not open for further replies.

MaxKnight

Programmer
May 23, 2003
14
AU
Hi Everyone,

I've found the print filter subsystem in OpenServer to be
quite handy to standardise some filters no matter what
type and how a printer is attached. (eg. make a definition
file, and load it through printer manager as a new filter,
then on the command line you add -T<filtername> to filter).

However, on at least 2 servers so far, after removing and
adding them, it starts to ignore what parameter you put
after -T and it will only use the first filter, even if you
put a non-existent filter name after -T !

So I may have created a text2ps filter, followed by a
unix2dos filter, but if I specify -Tunix2dos it will still
run the test2ps filter, even if I type -Tcrapcrapcrap .

I've tried clearing them all out via the manager, emptying
the filter.table manually, adding them back via the
manager and manually, and doing some thorough system
integrity checks.

Any ideas would be much appreciated, thanks.
 
Are you using local or remote printers? I remember reading somewhere that the remote lp command only allows single command line options, where local allows multiple. As I recall, for remote printers you need to surround multiple options in quotes so they are read as a single item or it won't work. You should review the lp man pages about this.
 
apeasecpc - nope, not related, happens to local or remote, plus I'm not sending any options to the printer, the -T<filtername> parameter is a local spooler option and not sent to a remote printer.

Cheers.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top