Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: XOFF Deadlock on R.O. Diablo. Help!
Message-ID: <3490@ucbvax.ARPA>
Date: Tue, 27-Nov-84 03:03:29 EST
Article-I.D.: ucbvax.3490
Posted: Tue Nov 27 03:03:29 1984
Date-Received: Wed, 28-Nov-84 02:05:12 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 21

From: <OTHB@SRI-KL.ARPA>

	Is there any way to unjam a receive-only printer that VMS thinks has
sent an XOFF when the printer cannot be coaxed into sending an XON?  A way,
perhaps to poke a character into VMS's input buffer for that device?

	I have a DIABLO 1650 printer as a queued terminal device at 1200 bps,
and it gets itself stuck several times a week.  The simplest way I have found
to clear the deadlock is to yank the Diablo's cable out of the DZ, plug in a
VT-100, set VT-100 to 1200 bps, hit control-Q, and replace the cables.  The
printer people say the Diablo is fine, DEC says the DZ, UNIBUS and VMS are
fine, and I am tired of fiddling with cables.  $STOP/NEXT, STOP/ABORT, and
DELETE/ENTRY= all fail if there is a current print job active and VMS is
waiting for an XON.

	One software solution I have found is to reboot the 780, but that is a
bit extreme.  Any suggestions on a less painful solution?

						advaTHANKSnce,
							Jon Spear
-------