Two questions. If I do not get a good answer to the first the second is not important. Are there drivers for a Conon i550 ink jet printer for SuSE? A google on "Cannon i550 SuSE" gave nada. Can SuSE serve a printer to Mac OS X 10.1.3 Panther on a local LAN? The core of OS X system is BSD Unix but I don't know if I just believe it is BSD and edit the /etc/printcap file or if I have to go through one of the old NeXTStep NetInfo tools. What do I have to do on the SuSE end to have the printer networked? SuSE will be the printer server. john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
Hi John, I use the driver for the Canon BJC 6000. I googled a while ago for the driver problem too. There seems to be a commercial software available that has a dedicated driver for the i550. I have to say, I haven't tried color printing yet. Don't have the need at the moment and no color ink either. Also have look at this link: http://www.linuxprinting.org/pipermail/canon-list/2002q4/000669.html Guenter listhub@libros.andante.mn.org wrote:
Two questions. If I do not get a good answer to the first the second is not important.
Are there drivers for a Conon i550 ink jet printer for SuSE? A google on "Cannon i550 SuSE" gave nada.
Can SuSE serve a printer to Mac OS X 10.1.3 Panther on a local LAN? The core of OS X system is BSD Unix but I don't know if I just believe it is BSD and edit the /etc/printcap file or if I have to go through one of the old NeXTStep NetInfo tools. What do I have to do on the SuSE end to have the printer networked? SuSE will be the printer server.
john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
-----Message d'origine----- De : dannoritzer@web.de [mailto:dannoritzer@web.de] Envoye : samedi 17 avril 2004 18:00 A : listhub@libros.andante.mn.org Cc : SuSE SLE Mailing List Objet : Re: [SLE] Serving Printers from SuSE? Hi John, I use the driver for the Canon BJC 6000. I googled a while ago for the driver problem too. There seems to be a commercial software available that has a dedicated driver for the i550. I have to say, I haven't tried color printing yet. Don't have the need at the moment and no color ink either. Also have look at this link: http://www.linuxprinting.org/pipermail/canon-list/2002q4/000669.html Guenter I use the driver for the Canon S800 with very good results with the i550 and i965 use the filter options : density : 2.0 cyan, magenta and yellow level : 2 printing mode : high quality quality 600x600 Michel. listhub@libros.andante.mn.org wrote:
Two questions. If I do not get a good answer to the first the second is not important.
Are there drivers for a Conon i550 ink jet printer for SuSE? A google on "Cannon i550 SuSE" gave nada.
Can SuSE serve a printer to Mac OS X 10.1.3 Panther on a local LAN? The core of OS X system is BSD Unix but I don't know if I just believe it is BSD and edit the /etc/printcap file or if I have to go through one of the old NeXTStep NetInfo tools. What do I have to do on the SuSE end to have the printer networked? SuSE will be the printer server.
john ------------------------------------ John N. Alegre o Andante Systems o eCommerce Consulting o Custom Web Development <*{{{{}>< ------------------------------------
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hello, On Apr 17 09:42 listhub@libros.andante.mn.org wrote (shortened):
Can SuSE serve a printer to Mac OS X 10.1.3 Panther on a local LAN?
Use Google and find for example: http://librenix.com/?inode=3899 --------------------------------------------------------------------- In Panther, it can be difficult to print to a remote CUPS server. This is because Panther runs CUPS as its own print engine, and will attempt to render the PostScript for you once you select your correct printer driver. It will then send the rendered file to the remote CUPS server. The remote CUPS server will then try to render the already rendered file and will give a no_file error. The work-around is to make one end of the chain a 'raw' printer. --------------------------------------------------------------------- It is not a work-around but the correct solution to user a "raw" queue on the server (or something like the option "-o raw" on the client) when the client sends printer specific data to the server. Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Mon, 19 Apr 2004 18:48, Johannes Meixner wrote:
Hello,
On Apr 17 09:42 listhub@libros.andante.mn.org wrote (shortened):
Can SuSE serve a printer to Mac OS X 10.1.3 Panther on a local LAN?
Use Google and find for example: http://librenix.com/?inode=3899
It is not a work-around but the correct solution to user a "raw" queue on the server (or something like the option "-o raw" on the client) when the client sends printer specific data to the server.
Regards Johannes Meixner
Just a note if using the raw option you may have to alter the two mime files in /etc/cups as per the notes appearing therein. see /etc/cups/mime.types and /etc/cups/mime.convs for details -- Regards, Graham Smith ---------------------------------------------------------
Hello, On Apr 20 04:53 Graham Smith wrote (shortened):
Just a note if using the raw option you may have to alter the two mime files in /etc/cups as per the notes appearing therein. see /etc/cups/mime.types and /etc/cups/mime.convs for details
Do you really need it on your machine? Which CUPS version? Which case of printing (e.g. printing from Windows via Samba)? For me it works as described in the /etc/cups/mime.types and /etc/cups/mime.convs comments: ---------------------------------------------------------------------- # Uncomment the following type and the application/octet-stream # filter line in mime.convs to allow raw file printing without the # -oraw option. ---------------------------------------------------------------------- # Uncomment the following filter and the application/octet-stream type # in mime.types to allow printing of arbitrary files without the -oraw # option. ---------------------------------------------------------------------- I.e. with an explicite "-o raw" option you can always force raw printing but without an explicite "-o raw" option the CUPS filtering system would reject a unknown MIME type with the "client-error-document-format-not-supported" IPP message. This is perfectly what you normally want to avoid that a user prints unsupported data types directly on the printer which would result that most printers print tons of sheets with meaningless characters because most printers fall back to ASCII printing when the data type is unknown for the printer. But if the user knows that it is already printer specific data then it is always possible to skip any CUPS filtering by printing it with the "-o raw" option. In contrast when the "application/octet-stream" lines are activated in /etc/cups/mime.types and /etc/cups/mime.convs then the CUPS filtering system would fall back to raw printing in case of any unknown MIME type. A user can now accidentally "print" tons of sheets with meaningless characters because the user cannot know which data types are not supported by the CUPS filtering system. For example one CUPS filtering system may support printing of DVI files and another CUPS filtering system may not support it - see http://portal.suse.com/sdb/en/2004/01/pohletz_print_dvi_90.html In particular on network printers this can be really annoying because normally there is nobody watching the network printer and therefore the printer normally prints continuous until it runs out of paper. Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Monday 19 April 2004 23:05, Johannes Meixner wrote:
But if the user knows that it is already printer specific data then it is always possible to skip any CUPS filtering by printing it with the "-o raw" option.
You VASTLY understate the problem of educating an office full of clerks on the decision makeing necessary to print the boss's memo. By far the easiest solution is to create two cups printers, one named (and set up for) windows/samba and the other for the (much smaller user base) linux users. And yes, having set up 6 or 8 commercial offices, I ALWAYS uncomment the mime types for cups so that raw means raw, and not "raw if you tell me on every single print job that you really do want it raw." Its absolutely infuriating to set up a printer believing that what the screens and the manual say only to find out that raw does not mean raw. That costs the userbase WAY more in hours than 10 sheets of paper now and then. -- _____________________________________ John Andersen
Hello, On Apr 19 23:56 John Andersen wrote (shortened):
You VASTLY understate the problem of educating an office full of clerks on the decision makeing necessary to print the boss's memo.
You are not greeting but shouting about printing via Samba? I think you mix up what should be configured for CUPS and what should be configured for Samba. Regards Johannes Meixner -- SUSE LINUX AG, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/
On Tuesday 20 April 2004 00:16, Johannes Meixner wrote:
Hello,
On Apr 19 23:56 John Andersen wrote (shortened):
You VASTLY understate the problem of educating an office full of clerks on the decision makeing necessary to print the boss's memo.
You are not greeting but shouting about printing via Samba? I think you mix up what should be configured for CUPS and what should be configured for Samba.
I configure nothing for samba, as samba just passes the queue to cups. Anything connected to samba already has (windows) drivers and will deliver print streams to samba (and then to cups) which need no further processing. Any gratuitous processing by cups will only server to wast resources at best, and often (very often in my expirence) screw up an othewise properly prepared print stream. Similarly, and cups (ipp) submissions directly from a windows machine will (not via samba shares) be properly prepared, and needs no further processing. So now there are not only the samba shares to set up with the raw option but also the direct ipp shares (which are frequently from off-site and do not come thru samba). These latter ones must be tracked down individually. FAR easier to uncomment the mime types so that raw really means raw. -- _____________________________________ John Andersen
participants (6)
-
Catimimi -
Graham Smith -
Günter Dannoritzer -
Johannes Meixner -
John Andersen -
listhub＠libros.andante.mn.org