Neoware e140 - Thin Client User Manual page 127

Neolinux thin clients user manual
Hide thumbs Also See for Neoware e140 - Thin Client:
Table of Contents

Advertisement

And a corresponding script file (/tmp/config/<Printer name>) is
generated that contains the contents of the Custom filter field. For
example, the example above for the Epson C40US generates a
file:
#!/bin/sh
/usr/local/bin/gs -q -dSAFER -dNOPAUSE -sDEVICE\=stp
-sModel\escp2-c40us -dDensity\=0.8 -r1440x720 -dImageType\2
-sOutputFile\=- -
Windows printer driver [default: <blank>] – This entry must be
completed when a locally-defined printer is intended for use by
Windows server applications through either ICA or RDP connec-
tions. The value entered here is passed by the thin client software
back to the Windows application server in order to identify which
Windows printer driver should be used to prepare the print job.
Depending upon how the server software is configured, a printer
properly configured using the Windows printer driver can be
made automatically available to end-users when connecting from
the thin client.
The text value
entered in the
Windows printer
driver field must
match exactly
(including spaces
and capitalization
of characters) the
name of the printer
driver on the Win-
dows application
server. In Win-
dows 2000 Server,
this name appears as Driver on the printer properties Advanced
tab.
When not blank, this entry creates the following line for this
printer in the dynamically-generated printcap file:
:wd=<Windows printer driver>:
Using the NeoLinux Print Manager utility
Adding printers using Print Manager
Exactly copy this
driver name into
the Windows
printer driver field.
127

Advertisement

Table of Contents
loading

Table of Contents