RE: Receipt Printer Question

Jon,

Make a copy of the .ws file for the session that prints correctly. You can
open the file with notepad, change the device name, and then save it with a
name for one of the printers that is acting funny. Install that .ws file
onto the appropriate PC, delete the device description from the System i,
and then launch the new printer session. It should reconfigure correctly if
your system is set to auto config.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Al Mac Wheel
Sent: Thursday, December 06, 2007 1:05 PM
To: Midrange Systems Technical Discussion
Subject: Re: Receipt Printer Question

Years ago I had something similar happen.

There's some IBM printer emulation web site that Rob or someone can supply.
It lists the drivers needed based on printer combination.

Suppose you have brand name X printer model Y emulating IBM printer Z
then you need a particular driver for that combination

Not only does the driver have to be downloaded, it has to be configured

The explanation was that there's logic in the printer that competes with
the host setting the rules & the printer logic is hostile to accepting a
report whose page dimensions bigger than some # ... we solved this by
redesigning the PRTF page, so that the width of the report was that printer
friendly.

The reason why this happens on one printer but not another was that some of
the newer printers have undocumented hardware upgrades to make them
smarter, that were designed by brain dead humans. We find that the older
the printer is, the less printing hassles, and the faster it runs, because,
like Windows, the newer versions have more baggage.

I have a remote customer that has about 6 Epson TM U220D Receipt printers
that are configured as AS/400 printers via Client Access. One printer
prints correctly, the rest print correctly the first spool file and then
the printing gets very small and stays that way. I have verified that the
Client Access configuration and the device descriptions are exactly the
same. The network person on the other end claims that the windows drivers
were all installed the same. I've never came across anything like this.
Does anyone have any ideas?

Thanks, Jon
_________________________________________________________________
Connect and share in new ways with Windows Live.
http://www.windowslive.com/connect.html?ocid=TXT_TAGLM_Wave2_newways_112007
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.