Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!ut-emx!ccwf.cc.utexas.edu From: daveh@ccwf.cc.utexas.edu (David H. Huang) Newsgroups: comp.sys.apple2 Subject: Re: Imagewriter II Message-ID: <45990@ut-emx.uucp> Date: 22 Mar 91 03:55:01 GMT References: <1991Mar21.190035.9087@ux1.cso.uiuc.edu> Sender: news@ut-emx.uucp Reply-To: daveh@ccwf.cc.utexas.edu (David H. Huang) Organization: The University of Texas at Austin Lines: 56 In article <1991Mar21.190035.9087@ux1.cso.uiuc.edu> rimovsky@ux1.cso.uiuc.edu (Tony Rimovsky) writes: |I have a problem. My imagewriter II has been acting flakey the past |couple of days. For a while it ust wouldn't print. (Yes, everything |was set correctly, eg The SELECT button was on as well as power) I didnt |do a thing to the printer. I just kept sending print commands. On about the |fifth try, it actually printed. Then, for a while I was getting no line Although this is extremely unlikely, you _might_ have a bad cable (btw, this doesn't have anything to do with the following error message). |feeds when I tried to print. I was using ProTerm 2.2 with the printer set |to on. I have done this many times in the past with no problems. |Finally, I decided to run the self test. Being lazy and not wanting to |go get the book, I tried to hold the PRINT QUALITY button down instead |of the FORM FEED button when starting. I got this message printed: | LOOP TEST | | ROMREV(05) | | DIPSW1 (00000100) DIPSW2 (1100), '1=ON,0=OFF' | | RAM= 0 KB AT=OFF | |LOOP BACK TEST FAILS You need a loopback cable hooked up for this test to work (I guess that's a cable with it's receive hooked up to it's transmit, but I'm no hardware guy). So... this is always going to happen, no matter what you do. |I looked in the manual for the printer and it does not mention this |feature. I did, incidently, run the real test and it came out fine. |Oh Yea! I almost forgot this: the error light started blinking |in a pattern after I got the above print out. 2 blinks, pause, |1 blink over and over again. Any ideas? I dont want to take this |to a *chuckle* Apple dealer (HaHaHaHa!!! Right. Id say Apple IIgs |and they'd say that was my problem!). Anyway, thanks in advance! I've looked in the ImageWrite II Technical Reference, and I didn't find anything about this test (although I might not have looked too hard). The same blinking pattern happens on my IW II, so I think it's safe to say that this error means absolutely nothing. BTW, the 'monitor mode' was documented in the IW II Reference, if you hold down the Select button while turning it on, it'll print the hex bytes that it's receiving instead of ASCII. |------------------------------------------------------------------------- |Tony Rimovsky rimovsky@ux1.cso.uiuc.edu |CSO - University of Illinois (part time) -- David Huang | "Calzoni Pizza: Internet: daveh@ccwf.cc.utexas.edu | Delivery in six UUCP: ..!ut-emx!ccwf.cc.utexas.edu!daveh | hours, or else your America Online: DrWho29 | pizza is cold."