Printing to IBM printers, or from IBM computers to anybody's printers, or something like that... ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Newsgroups: alt.folklore.computers Path: cs.utk.edu!emory!gatech!howland.reston.ans.net!vixen.cso.uiuc.edu !ux2.cso.uiuc.edu!shair Message-ID: <2t3m4l$5b4@vixen.cso.uiuc.edu> References: <771056894.AA01033@clone.his.com> Originator: shair@ux2.cso.uiuc.edu Date: 8 Jun 1994 05:49:09 GMT Organization: University of Illinois at Urbana From: shair@uiuc.edu (Bob Shair) Subject: Re: Early laser printers? edward.rice@his.com (Edward Rice) writes: > > EB> From: eric@lfs.loral.com (Eric Burch) > > EB> Typically, early IBM machines had a resolution of 240 dpi, and ran > EB> fanfold paper through about a 10-foot paper path. I liked the > EB> Honeywell (I think) machine that would take an 8.5"-wide white paper > EB> roll and cut a new page every 11 inches. Printed 60-100 > EB> pages/minute. > EB> > EB> Liquid toner! Silicone fuser oil! Bus and tag cables (we don't need > EB> no steenking coaxial cable)! Water cooled CPU's! Third shift block > EB> time reservations! Oh, the good old days. One of the earliest IBM laser printers, before the 3800, was a special machine developed by FSD for the gummint. Don't know the specs on it, but it used roll paper (big rolls, like they print newspapers on), and was REALLY fast. Rumor had it that there was an optional pulp-mill attachment, so you could just back it up to a forest. And of course, it was said that the typical installation ran the output directly into the shredder, for security. -- Bob Shair shair@uiuc.edu Open Systems Specialist SHAIR@UIUCVMD (bitnet) Champaign, Illinois 217/356-2684 ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Newsgroups: comp.sys.hp.hardware,comp.sys.hp.misc,comp.sys.ibm.as400.misc Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!cs.utexas.edu!swrinde !howland.erols.net!newspump.sol.net!spool.mu.edu!munnari.OZ.AU !news.ecn.uoknor.edu!news.ysu.edu!odin.oar.net!malgudi.oar.net!usenet Message-ID: <3325E659.64E3@RESEARCH.BFG.COM> References: <01bc2902$d0461ae0$8dfa13cc@qsad> Organization: BF Goodrich Date: Tue, 11 Mar 1997 15:10:17 -0800 From: "Guy L. Albertelli" Subject: Re: Problems printing from AS/400 to HP Jetdirect over a Wan Denis St-Amand wrote: > > Hi all AS/400 people. > > I'm a little new to AS/400 world and we have a problem. We are printing > using LPR over a wan from an AS/400 to a brand new HP Laserjet 5Si with an > HP JetDirect J2550B Ethernet Adapter (Firmware A.05.05). When we print > little spoolfiles (say less than 30 pages), everything goes right. When we > send bigger spoolfiles, nothing goes out. The AS/400 is configured to > print on a Laserjet 4Si since there are no 5Si drivers. The exact same > problem also appears on another identical 5Si and also on a 4Si printer. > The AS/400 has V3R1 on it. We did some "sniffing" on the local AS/400 > subnet and the result is displayed below. Can someone help ??? > > Thank you very much. > Denis St-Amand (dsa@clic.net) > The basic problem is that the AS/400 is doing EBCDIC to ASCII conversion (an also SCS or AFPDS to PCL conversion) AFTER it starts a conversation with the printer. Therefore large printouts take significant time to convert. 2 possible solutions: 1. Change HP printer timeout interval to more than factory 90 seconds. I usually set to maximum. 2. One of the latest LPR/LPD PTFs has a method of converting once and then if it fails the send (the printer times out), then recycles the converted version back via the LPD. (You have really got to read the cover letter!!!!! See PTF SF38566). Also we have found that the HP JetDirect card microcode works better at the A.05.09 level. FYI ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo One item from the AS/400 FAQ at http://solar.rtd.utk.edu/~mtaylor/as400.faq.html Subject: How can I print Barcodes on an ASCII attached printer without IPDS? **new** Send your ASCII hex codes to the print file on a format that has a TRNSPY CVTDTA command on it. You should be able to emulate your current applications, although you still have the COR and emulation (if via CA) issues to deal with. The TRNSPY CVTDTA command sends the printer into transparent mode and converts the data into ASCII. Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-Mail: ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo