HP3000-L Archives

June 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Burke <[log in to unmask]>
Reply To:
John Burke <[log in to unmask]>
Date:
Thu, 22 Jun 2000 10:44:45 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
Periodically, questions are posted to the list about using HP's network
printing functionality in "unsupported" ways, where "supported" means HP
printer and HP JetDirect network interface.

The situation is, as I understand it from experience, and as I have
counseled previous posters:

- You may be able to use a non-HP network interface (e.g. I've used the
Intel NetXport) by using the undocumented "snmp_enabled=false" directive in
npconfig.pub.sys. This is particularly useful if your printer has a serial
interface since HP does not make a JetDirect with a serial interface.

- You can use any printer as long as it understands some very basic PCL
(most non-HP laser printers fall into this category, but non-HP impact
printers do not fall into this category). Virtually every HP printer I've
ever had the opportunity to try works, including the HP2932 and HP2934 dot
matrix printers and even an ancient HP ThinkJet. I have never had success
with any non-HP impact printer (Epson, Okidata, Digital, IBM, Printek, etc.)
because they do not respond to PCL.

I've decided to re-visit this issue since I now have several dozen DTC's
deployed across a bridged WAN solely to drive serial impact printers from a
variety of manufacturers (the terminals that once hung off these DTCs have
been replaced by PCs). I would dearly like to get rid of them and turn
bridging off. And yes, I know full well there are third party solutions that
will handle this (we even own one) and I will take that route if necessary.
It is just that HP's network printing solution is so convenient ... when it
works.

Anyway, I am not aware of anyone having success with a non-HP printer unless
it supports PCL. There have been many questions posted about using such
printers and many suggestions given about what "might" work, but no actual
reports of success that I know of.

So, the question to the world is, has anyone had success using a non-HP
impact printer (one that does not explicitly support PCL) with HP's network
printing? If so, what is the printer and what did you do to get it to work?

Reply privately and I'll summarize the results on the list in a few days.

John Burke
[log in to unmask]

ATOM RSS1 RSS2