Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site bradley.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!bradley!root
From: root@bradley.UUCP
Newsgroups: net.bugs.2bsd
Subject: 2.9,PDP 11/73, Emulex CS01 troubles
Message-ID: <1900007@bradley.UUCP>
Date: Tue, 15-Jan-85 11:12:00 EST
Article-I.D.: bradley.1900007
Posted: Tue Jan 15 11:12:00 1985
Date-Received: Wed, 16-Jan-85 16:08:24 EST
Lines: 24
Nf-ID: #N:bradley:1900007:000:980
Nf-From: bradley!root    Jan 15 10:12:00 1985

From: brad (Bradley E. Smith)
Subject: 2.9,PDP 11/73, Emulex CS01 troubles

I am still looking for any help that people can shead on this problem.

Where I stand now is that I in the dhstart routine it has code that checks if
the line is (TIMEOUT|BUSY|TTSTOP) and goes to the end if it is. What I did is
to check if tp->t_state &BUSY), if so then I had it 'dhstop(tp,0)' and also set
the tp->t_state |= TTSTOP.  What this does is unscrew up the output.

Also when i run the job from another terminal and suspend it when it starts
messing up, it continues to still print data for quite a while, usually
terminal goes off in never never land before it stops.

I also can't seem to get the console to mess up which points me in the
direction of the 'dh.c' or the dh itself.

as always, thanks indavance

Bradley Smith			UUCP: {cepu,ihnp4,noao,uiucdcs}!bradley!brad
Text Processing			ARPA: cepu!bradley!brad@UCLA-LOCUS
Bradley University		PH: (309) 676-7611 Ext. 446
Peoria, IL 61625