Re: IPDS printing

[Pat Barber <mboceanside@xxxxxxxxxxxxxxxx>]

It is not likely you will get the "exact" same results with a tcp/ip
connected printer vs a native attached printer. The one thing you didn't
mention was, do BOTH printers have a IPDS feature code ??? I assume that
the NP-17 has the IPDS feature and the other printer does NOT.

 This remains one area of weakness in TCP/IP and I don't see IBM
really performing any fix to the problem.

They are attempting to keep tcp/ip "standard" and IPDS is not
industry standard.

Some folks have had fairly good luck getting the more advanced
data streams to work using tcp/ip but most have results similar
to yours...

This is the "other side" of dumbing down the output data for cheaper
data networks. When you start seeing a lot "font substitution"
messages, this tells me that the printer doesn't care for some of
the fonts you are attempting to use and this will slow the process
down even more. IPDS under HPT is a poor substitute for native
attached in my opinion.









Ed Chabot wrote:
>
> Hi,
> We are tip-toeing into the area of IPDS printing and overlays and are
> running into a problem.  We were able to create and print a document with an
> overlay on our twinax-attached IBM Network Printer 17 with 34MB of memory
> but when we try to print the same document on our ethernet-attached IBM
> Network Printer 21 with 64 MB of memory, we get the following messages.
>
> Font substitution was performed.
> Font substitution was performed.
> Font substitution was performed.
> Font substitution was performed.
> Device SHIPPRT returned negative acknowledgment with sense data.
> Device storage is not sufficient for resources and data for this sheet.
>
> We do get the font substitution messages on the NP17 but they don't stop the
> print process from completing.  Any ideas or resources?  Thanks in advance.