Jean Parrot wrote to Alan Ianson:

JP>         Thanks for the moral support, Alan. It really frustrated me to
JP>    not be able to use this Lexmark printer on U'U to the extend that I
JP>    got off U'U. I am not a CLI person.

This is an open source thing. Some computer hardware is designed for
Windows rather than computers in general. Even if the manufacturer
doesn't (and most don't) provide a driver for OS's other than Windows
if they would make the technical specifications available then drivers
could be made available by the open source community. This is happening
more and more now but it can still be a problem, especially with older
hardware.

JP>  AI> There is a database of printers (working and not) at 
JP> linuxprinting.org
JP>  AI> that can be helpful in setting up printers (or not) in linux.
JP> 
JP>         I tried, honestly, to get it going but when I noticed that it
JP>    was seen in U'U, even qualified as the default printer but would not
JP>    print at all, I knew that there was more than one snake in the
JP>    woodpile. I am used to plugging in a device and having Windows tell
JP>    me that it is now "ready to be used". Specially a newer
USB device.
JP>    I then connected an older Canon 4300 and it fired away right then.
JP>    And Jeff says that the Z32 is old ? This 4300 is senile. U'U is
JP>    just not up to date, maybe latter ???

U'u is very up to date. I suspect if that printer doesn't work it
never will. At least not without applying that CLI fix (dunno, never
tried).

Without those tech specs it's hard (if not impossible) to move forward.
A lot of printers without any tech specs do work in linux because they
have been hacked together, but that isn't always possible/worth it.

Anyway, just food for thought.. :)

 Ttyl :-),
         Al

... Software means never having to say you're finished


--- MBSE BBS v0.95.4 (GNU/Linux-x86_64)