× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Hello group,



I recently posted a message requesting some help regarding printing to a
Pitney Bowes color copier/printer which uses the internal Fiery X3e printer
controller. I was trying to use the remote outq with a dummy device
description approach with limited success. I was able to print to the
printer/copier but my output was including some kind of control character
string at the beginning of the page and at the beginning of every line. For
example, at the beginning of every line I was getting a &a+00216H .



I received a reply offline from Paul Tykodi who is the National Product
Manager for Intermate US, Inc.. Paul not only explained to me what was going
on, but provided an easy solution that I didn't realize was possible. With
his permission, here are portions of his response:



<<Snip>>

<<To date, the typical color copier/printer has only supported the
PostScript

printer language. I checked the Windows print driver that you referenced in

your posting and verified that your Pitney Bowes color copier/printer does

support only the PostScript language. The OS/400 host print transform

function up through OS/400 V5R1 does not offer a driver that outputs

PostScript. The typical laser printer drivers mentioned in the document on

the AS/400 web site you referenced in your posting all output the HP PCL

printer language. The text you are seeing printed at the beginning of every

line is actually an HP PCL command setting the left margin that the Fiery

X3e printer controller doesn't understand which is why the command is being

printed. >>

<<Snip>>

<< If you have Client Access, you could do the following. You could

configure a Client Access PC5250 print session that was not using Host Print

Transform (uncheck the box Transform Print Data to ASCII on AS/400), the

OS/400 EBCDIC data would be transferred natively from the AS/400 to the PC

running Client Access. If you also make sure that you do not select the Use

PDT checkbox, Client Access will convert your EBCDIC data into a Windows

format known as GDI on the PC running Client Access. The GDI format is the

generic input format required by Windows print drivers. You will be able to

use the Fiery X3e 20C-M v1.0 Windows print driver to format the AS/400
data.>>

I have used Client Access printer emulation for years, but my printers were
always physically connected via a parallel cable to each PC. I never
realized that you could use CA printer emulation with a LAN printer!

Paul's Client Access PC5250 print session solution worked perfectly!!

A big Thank You to Paul Tykodi.



Karl Keller

Information Systems
Girling Health Care, Inc.
(512) 458-3090 ext. 5040



Confidentiality Notice:  This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information.  Any unauthorized review, use, disclosure or
distribution is prohibited.  If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

--



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.