Constant, There's a clue here. You indicate that after removing the switch box from the circuit, the printer was able to print a few pages correctly before printing garbage again.
Long ago I had a similar problem and it turned out to be the cable. Unlike serial cables, which send a bit stream down a pair of wires, the printer cable is a parallel cable: each bit gets its own wire. If one of the wires is damaged or if one of the pins doesn't quite connect, the effect is that there is a bit missing from *everything* the printer gets. If you send the phrase "\r\nHello world.\r\n" to the printer (the \r is a CR, the \n is LF) the correct binary values are 00001101 00001010 01001000 01100101 01101100 01101100 01101111 00100000 01110111 01101111 01110010 01101100 01100100 00101110 00001101 00001010 ----- Original Message ----- From: "C. Brouerius van Nidek" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 16, 2002 5:58 AM Subject: [SURVPC] Subject: Re: PRINTER PROBLEM > Bob George wrote > > >"C. Brouerius van Nidek" <[EMAIL PROTECTED]> wrote: > > >> Did the selftest and the outprint is flawless. > >> Are now trying to go after my printer cabling. > > >It's only that one file, right? Could you forward > >a copy of that file to me? It sure sounds like the > >classical CRLF-CR mapping problem. If so, > >it's easy to clean up. > > No. Now it is with every file that I want to print > out ;-( > Have already looked into the files which I wanted to > print and no weird characters were sighted. > > I have removed the auto data switch as a possible > cause but after some print outs, the whole thing > started anew. > > Must be my io card or the printer ;-( > -- > > NTReader v0.36w(P)/Beta (Registered) in conjunction with Net-Tamer. To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
