Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!rutgers!elbereth.rutgers.edu!joseph From: joseph@elbereth.rutgers.edu (Seymour Joseph) Newsgroups: comp.sys.mac Subject: Re: Imagewriter trouble & possible replacement Message-ID: Date: 1 Dec 89 23:53:55 GMT References: <5330@internal.Apple.COM> <256CECDD.14888@paris.ics.uci.edu> <5403@internal.Apple.COM> <1989Nov29.231627.21009@oracle.com> <5502@internal.Apple.COM> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 26 I supervise a facility that uses lots of ImageWriter IIs in public labs and I would have to agree that they are far from ideal for this purpose. We had much better luck with the ImageWriter Is and would still be using them if there were an AppleTalk option for them. At home, I use an Imagewriter II networked via Localtalk to both a Mac and my Apple IIGS. I find that for my use there, it is not a bad printer. It has some paper path problems, and we have had to learn to adjust to it, but if you treat it right, it can bang out draft copy VERY fast or produce really decent looking text and graphics in a reasonable amount of time. One trick I learned is to never tear off the page that just printed. Pulling on the paper tends to pre-skew it on the tractors and cause a jam on the next page. If the paper is torn at or before the paper bail, it will also tend to curl too far and jam (especially if it was left curled around the platen for a few days). I find the best thing to do is when something finishes printing, take the printer offline, eject a blank page and put the printer back online. Rip your work off, by pulling putting one hand on the blank page and pulling against it, and not the tractors. Leave the extra page on to help guide the paper for the next printout. This wastes paper, but saves lots of jams. Seymour