JetDirect 170X

Hi,

Does anyone know how to print to a HP LaserJet connected to an HP JetDirect
ethernet adapter from QNX 6.1 ?

Thanks for any help,

Andrea.

“Andrea Borsic” <aborsic@brookes.ac.uk> wrote in message
news:a2rrpt$lg8$1@inn.qnx.com

Hi,

Does anyone know how to print to a HP LaserJet connected to an HP
JetDirect
ethernet adapter from QNX 6.1 ?

Look at the documentation of lpd.

Thanks for any help,

Andrea.

Hi -
Actually, the lpd doc is not quite enough. First you have to make
sure syslogd is running and that the files mentioned in /etc/syslog.conf
actually exist. You will need to look for errors there, because lpd
reports there, although lpr can print them to your console.
Here is my /etc/printcap file, for my HP4Mplus with a JetDirect card
installed - I believe this is almost like the JD 170x:

Simple printcap

lp|txt|default ASCII printer:
:lp=:rm=192.168.13.61:rp=txt:sd=/var/spool/txt:sh:mx#0:if=/usr/local/bin/addcr:

ps|Postscript printer:
:lp=:rm=192.168.13.61:rp=raw:sd=/var/spool/ps:sh:mx#0:

Notice that the remote printer is called txt for straight ascii, and raw
for Postscript (or PCL) printing. Also /var/spool/txt and /var/spool/ps
must exist as directories, and the directory /usr/spool/output is also
required
Oh yes, addcr is a little filter that reads characters from stdin
and writes them to stdout…adding a cr after any newline. I couldn’t
find any way to get the printer to insert cr after nl!
I think that’s all you need; I don’t remember any other gotchas.
Oh ---- start lpd in rc.local - it’s commented out in rc.sysinit…

Phil Olynyk
OBT Software Corp.
YACA - Yet Another Contractor Available


Mario Charest wrote:

“Andrea Borsic” <> aborsic@brookes.ac.uk> > wrote in message
news:a2rrpt$lg8$> 1@inn.qnx.com> …
Hi,

Does anyone know how to print to a HP LaserJet connected to an HP
JetDirect
ethernet adapter from QNX 6.1 ?


Look at the documentation of lpd.

Thanks for any help,

Andrea.

“Phil Olynyk” <pholynyk@home.com> wrote in message
news:3C51BCFE.D2E1E92F@home.com

Hi -
Actually, the lpd doc is not quite enough. First you have to make
sure syslogd is running and that the files mentioned in /etc/syslog.conf
actually exist. You will need to look for errors there, because lpd
reports there, although lpr can print them to your console.
Here is my /etc/printcap file, for my HP4Mplus with a JetDirect card
installed - I believe this is almost like the JD 170x:

Simple printcap

lp|txt|default ASCII printer:\

:lp=:rm=192.168.13.61:rp=txt:sd=/var/spool/txt:sh:mx#0:if=/usr/local/bin/add

cr:

ps|Postscript printer:
:lp=:rm=192.168.13.61:rp=raw:sd=/var/spool/ps:sh:mx#0:

Notice that the remote printer is called txt for straight ascii, and raw
for Postscript (or PCL) printing. Also /var/spool/txt and /var/spool/ps
must exist as directories, and the directory /usr/spool/output is also
required
Oh yes, addcr is a little filter that reads characters from stdin
and writes them to stdout…adding a cr after any newline. I couldn’t
find any way to get the printer to insert cr after nl!
I think that’s all you need; I don’t remember any other gotchas.
Oh ---- start lpd in rc.local - it’s commented out in rc.sysinit…

Phil Olynyk
OBT Software Corp.
YACA - Yet Another Contractor Available

Dear Phil,

Thanks for the suggestions you gave me.

I have tried what you said.

Unfortunately by looking at the syslog file I find that the lpd daemon says:
“unknown printer”.

I went around on the web to find similar /etc/printcap configurations for
JetDirect, for example for Linux, they look as yours and result is
unfortunately again “unknown printer”.

What does it mean this message ? The remote printer is surely accessible to
the neutrino box, I can ping the printer and telnet into it.

Would you suggest any document to read (regarding the daemon config &
errors )?

Thanks again very much,

Andrea.

Andrea Borsic wrote:

“Phil Olynyk” <> pholynyk@home.com> > wrote in message
news:> 3C51BCFE.D2E1E92F@home.com> …
Hi -
Actually, the lpd doc is not quite enough. First you have to make
sure syslogd is running and that the files mentioned in /etc/syslog.conf
actually exist. You will need to look for errors there, because lpd
reports there, although lpr can print them to your console.
Here is my /etc/printcap file, for my HP4Mplus with a JetDirect card
installed - I believe this is almost like the JD 170x:

Simple printcap

lp|txt|default ASCII printer:\

:lp=:rm=192.168.13.61:rp=txt:sd=/var/spool/txt:sh:mx#0:if=/usr/local/bin/add
cr:

ps|Postscript printer:
:lp=:rm=192.168.13.61:rp=raw:sd=/var/spool/ps:sh:mx#0:

Notice that the remote printer is called txt for straight ascii, and raw
for Postscript (or PCL) printing. Also /var/spool/txt and /var/spool/ps
must exist as directories, and the directory /usr/spool/output is also
required
Oh yes, addcr is a little filter that reads characters from stdin
and writes them to stdout…adding a cr after any newline. I couldn’t
find any way to get the printer to insert cr after nl!
I think that’s all you need; I don’t remember any other gotchas.
Oh ---- start lpd in rc.local - it’s commented out in rc.sysinit…

Phil Olynyk
OBT Software Corp.
YACA - Yet Another Contractor Available

Dear Phil,

Thanks for the suggestions you gave me.

I have tried what you said.

Unfortunately by looking at the syslog file I find that the lpd daemon says:
“unknown printer”.

That is curious. I get the “unknown printer” message from if I leave out
“-Ptxt” before the file name,
and it comes in my terminal window. I put
export PRINTER=txt
after my lpd startup line in /etc/rc.d/rc.local and now I can leave out the
“-Ptxt” if I want to print plain text.

I am getting a syslog message “unable to get official name for local machine
devel-61”…I’ll look at Linux
sources for lpd to try and track that down, but it seems to be just a warning

Phil Olynyk

I went around on the web to find similar /etc/printcap configurations for
JetDirect, for example for Linux, they look as yours and result is
unfortunately again “unknown printer”.

What does it mean this message ? The remote printer is surely accessible to
the neutrino box, I can ping the printer and telnet into it.

Would you suggest any document to read (regarding the daemon config &
errors )?

Thanks again very much,

Andrea.

Phil Olynyk wrote:

Andrea Borsic wrote:

“Phil Olynyk” <> pholynyk@home.com> > wrote in message
news:> 3C51BCFE.D2E1E92F@home.com> …
Hi -
Actually, the lpd doc is not quite enough. First you have to make
sure syslogd is running and that the files mentioned in /etc/syslog.conf
actually exist. You will need to look for errors there, because lpd
reports there, although lpr can print them to your console.
Here is my /etc/printcap file, for my HP4Mplus with a JetDirect card
installed - I believe this is almost like the JD 170x:

Simple printcap

lp|txt|default ASCII printer:\

:lp=:rm=192.168.13.61:rp=txt:sd=/var/spool/txt:sh:mx#0:if=/usr/local/bin/add
cr:

ps|Postscript printer:
:lp=:rm=192.168.13.61:rp=raw:sd=/var/spool/ps:sh:mx#0:

Notice that the remote printer is called txt for straight ascii, and raw
for Postscript (or PCL) printing. Also /var/spool/txt and /var/spool/ps
must exist as directories, and the directory /usr/spool/output is also
required
Oh yes, addcr is a little filter that reads characters from stdin
and writes them to stdout…adding a cr after any newline. I couldn’t
find any way to get the printer to insert cr after nl!
I think that’s all you need; I don’t remember any other gotchas.
Oh ---- start lpd in rc.local - it’s commented out in rc.sysinit…

Phil Olynyk
OBT Software Corp.
YACA - Yet Another Contractor Available

Dear Phil,

Thanks for the suggestions you gave me.

I have tried what you said.

Unfortunately by looking at the syslog file I find that the lpd daemon says:
“unknown printer”.

That is curious. I get the “unknown printer” message from if I leave out
“-Ptxt” before the file name,
and it comes in my terminal window. I put
export PRINTER=txt
after my lpd startup line in /etc/rc.d/rc.local and now I can leave out the
“-Ptxt” if I want to print plain text.

I am getting a syslog message “unable to get official name for local machine
devel-61”…I’ll look at Linux
sources for lpd to try and track that down, but it seems to be just a warning

Phil Olynyk

Ahhhh, my dumb mistake! The name in my /etc/hosts file was dev-61! Changed that,
and now all is well for me. In Slackware lpd that’s a fatal error, not just a
warning.

Phil

I went around on the web to find similar /etc/printcap configurations for
JetDirect, for example for Linux, they look as yours and result is
unfortunately again “unknown printer”.

What does it mean this message ? The remote printer is surely accessible to
the neutrino box, I can ping the printer and telnet into it.

Would you suggest any document to read (regarding the daemon config &
errors )?

Thanks again very much,

Andrea.