Tim<br><br><div class="gmail_quote">On Mon, Oct 3, 2011 at 4:27 PM, Tim Waugh <span dir="ltr"><<a href="mailto:twaugh@redhat.com">twaugh@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">First of all, what are you using to set up the printer? "Printers GUI"</div>
could refer to several different things...<br>
<br></blockquote><div>I am using system-config-printer....Selected Windows Printer via SAMBA, keyed in the widows samba printer uri, keyed in authentication details & clicked verify....the printer verified as accessible.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The way to do what you want is to use the system-config-printer<br>
application. Set up the SMB queue, and for the driver choose "Generic"<br>
as the manufacturer and "Raw Queue" as the model.<br><br></blockquote><div><br></div><div>Upon selection of Printer Driver as Epson 24 pin Generic AND upon selection of Manufaturer as Generic & Raw Queue as model, the printer gets installed and does print a test page. It is getting Enabled now...Thanks!</div>
<div><br></div><div>But it still does not print from CLI applications printing to the printer port (In my case, from ls -lha >prn or Harbour compiled legacy dbase applications). The output of ls -lha > prn does not land in the print queue, even if this printer is the default printer, nor does the output of the legacy DOS based programs recompiled on Linux (Harbour project...in my case for recompiling old dbase programs).</div>
<div><br></div><div>Hope you can help me troubleshoot further.</div><div><br></div><div>With best regards & thanks.</div><div>Sanjay.</div><div><br></div></div>