On 11/1/05, Richard Reynolds <[EMAIL PROTECTED]> wrote:
>
> I dont post often but ive been a moderate linux user/admin/programmer for
> a while now, both professionally and just for fun. Ive seen this topic
> come up before, it just interests me.

> Though i Guess I could have listed the printers by models, however as I
> wasnt really trying to solicit help, and the point was more that
> there are still technical reasons linux is not as reay as it could be
> for the desktop. Linux didn't exist when 2 of my un-supported printers
> were designed ... so NOPE didnt ask about  those, however in plain old
> DOS(no fancy drivers or anything) I can make them  print. linux they
> print garbage, or in the wrong mode.  the canon printers I knew when I
> bought them they were unsupported, im OK ish with that as one is hooked
> up to a  linux box and CUPS prints thru the windows driver to the printer
> (acting  as a mini server and print spooler for the slower printer), when
> it comes to large inkjet printers, HP was it, so as far as I am concerned
> they made the standard and we linux users have not Jumped in line.

Just to talk to the point of "large inkjet printers" from HP.  It has
been a few years since I last used an HP DesignJet printer (36"wide)
which I think is in the large category.  At that time I was sending
data to it both from a Sun Solaris system and a Dec Alpha Linux
system.  No particular dificulties with either.  The most
time-efficient use of the hardware was to produce the large PostScript
files on the Solaris system, render them to HPGL on the Linux system
with Ghostscript, and send the HPGL to the printer via its Ethernet
connection.  As I said just a couple of sentences ago, this was all
very straightforward on the Linux system (Debian).  What line is there
to jump into?

    carl
--
    carl lowenstein         marine physical lab     u.c. san diego
                                                 [EMAIL PROTECTED]


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to