Changes between Version 7 and Version 8 of CupsFaq


Ignore:
Timestamp:
Jan 9, 2011, 4:05:38 AM (14 years ago)
Author:
Alex Taylor
Comment:

Various minor corrections

Legend:

Unmodified
Added
Removed
Modified

  • CupsFaq

    v7 v8  
    260260that file along to CUPS.
    261261
    262 <p>It's certainly possible to use the standard OS/2 PostScript driver for this.
    263 However, the eCups team has provided an updated PostScript driver called
    264 ECUPS.DRV; this is actually based on the standard PostScript driver, but with
    265 various fixes and other improvements to make it work with CUPS more smoothly.
     262<p>It's possible (at least theoretically; in practise there are sometimes
     263various problems) to use the standard OS/2 PostScript driver for this. However,
     264the eCups team has provided an updated PostScript driver called ECUPS.DRV; this
     265is actually based on the standard PostScript driver, but with various fixes and
     266other improvements to make it work with CUPS more smoothly.
    266267
    267268<p>The general flow of operation thus looks something like the following (greatly
    … …  
    321322#          v                         v                             v         #
    322323#    +------------------------------------------------------------------+    #
    323 #    | CUPS backend (parallel/serial/USB/IPP/LPD/SMB/AppleTalk/etc. (D) |    #
     324#    | CUPS backend (parallel/serial/USB/IPP/LPD/SMB/AppSocket/etc. (D) |    #
    324325#    +------------------------------------------------------------------+    #
    325326#                                    |                                       #
    … …  
    332333</pre>
    333334
    334 <p>The box labelled "CUPS" indicates components which are part of the cross-
    335 platform CUPS system.  The whole diagram, with the exception of the application
    336 at the top and the printer at the bottom, comprises the eCups framework.
     335<p>The box labelled "CUPS" indicates components which are part of the
     336cross-platform CUPS system.  The whole diagram, with the exception of the
     337application at the top and the printer at the bottom, comprises the eCups
     338framework.
    337339
    338340
    … …  
    360362<ul>
    361363<li>Importing certain (mostly Foomatic) PPD files into ECUPS.DRV can cause the
    362 OS/2 spooler to crash when printing.  This is probably due to both CUPS and
    363 Foomatic using some very convoluted PPD syntax which the OS/2 PostScript driver
    364 cannot handle.  Until a fix can be developed, you should be able to use the Generic
    365 PostScript Printer driver (and configuring all printer-specific settings through
    366 the CUPS administration GUI).<p>
     364OS/2 spooler to crash when printing.  This is due to both CUPS and Foomatic
     365using some very convoluted PPD syntax which the OS/2 PostScript driver (or,
     366more specifically, PIN) cannot handle. 
     367
     368<p>Until a proper fix can be developed, you can usually avoid the problem by
     369"cleaning up" the PPD file before running PIN on it.  The InstPDR utility
     370(available on the eComStation BetaZone) does this automatically; there is also
     371a script called CleanPPD (available separately) which does the same thing.
     372
     373<p>If all else fails, you should be able to use the Generic PostScript Printer
     374driver (and configuring all printer-specific settings through the CUPS
     375administration GUI); see <a href="#2_5">question 2.5</a> for details.<p>
    367376
    368377<li>Printing to printers which use Foomatic plus a built-in GhostScript driver
    … …  
    380389<p>Alternatively, you can bypass CUPS (and Foomatic) entirely, and print using
    381390GhostScript as an inline print processor.  This has the advantage of allowing
    382 basically seamless printing, at a cost of being somewhat awkward to configure
     391basically seamless printing, at a cost of being rather awkward to configure
    383392properly.  There are somewhat generalized instructions
    384393<a href="http://svn.netlabs.org/ecups/wiki/GhostScriptRasterPrinting">here</a>.
    … …  
    490499<dd>IPP or Internet Printing Protocol.  This is a modern TCP/IP protocol for
    491500networking printers which was designed to replace the much older LPD.  It
    492 supports many features which the LPD and AppSocket do not, including encryption,
     501supports many features which LPD and AppSocket do not, including encryption,
    493502authentication, and job control.  Not all print servers may support it, however.<p>
    494503<dt><tt>lpd://</tt>
    … …  
    700709
    701710<p>Specifically, you need to obtain the file <tt>smbspool.exe</tt> from the
    702 OS/2 Samba client port.  Rename this file to <tt>smb.exe</tt> and place it
    703 in the <tt>/cups/lib/cups/backend</tt> directory.  The next time you go into
    704 the "Add printer" page in the CUPS Adminstration GUI, you should see a new
    705 option for "Windows or SAMBA" printer listed.</p>
     711OS/2 <a href="http://svn.netlabs.org/samba">Samba client port</a>.  Rename
     712this file to <tt>smb.exe</tt> and place it in the <tt>/cups/lib/cups/backend</tt>
     713directory.  The next time you go into the "Add printer" page in the CUPS
     714Adminstration GUI, you should see a new option for "Windows or SAMBA" printer
     715listed.</p>
    706716
    707717<p>Enter the URI in the form: