Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!columbia!rutgers!caip!clyde!cbatt!ihnp4!inuxc!pur-ee!uiucdcs!uiucuxc!hamilton From: hamilton@uiucuxc.CSO.UIUC.EDU Newsgroups: net.micro.amiga Subject: Re: More VT100 Problems Message-ID: <148600164@uiucuxc> Date: Thu, 16-Oct-86 16:26:00 EDT Article-I.D.: uiucuxc.148600164 Posted: Thu Oct 16 16:26:00 1986 Date-Received: Sat, 18-Oct-86 00:35:25 EDT References: <93500049@convex> Lines: 27 Nf-ID: #R:convex:93500049:uiucuxc:148600164:000:1482 Nf-From: uiucuxc.CSO.UIUC.EDU!hamilton Oct 16 15:26:00 1986 > One more thing. I mentioned a while ago that *my* version ov VT100 > leaves DTR on even after I click the go-away gadget. I thought this > was a real neat feature. But according to Wecker, the program does > *not* leave DTR on. So now I've found that this thing that I thought > was a feature, actually only happens under certain circumstances. I'm > trying to isolate just when I get this feature. For some reason I > could not get the feature to work at all last night (DTR kept going off > when I quit the program) but I swear, the night before it was working > just as I've said: DTR remained on. I will post the details when I > figure it all out. are you switching back and forth between terminal emulators? or are you using a midi interface on the serial port? i think that if DTR happens to be high when vt100 (or anything else that uses the Exec serial.device interface) opens the serial device, it will be restored to that state when the device is closed. thus, if you want DTR on all the time, you could write a short hack that would poke the 8520 port that controls DTR. this would "break" the hangup() code in vt100 v2.2, but you could use +++/ATH0 to hangup manually. wayne hamilton U of Il and US Army Corps of Engineers CERL UUCP: {ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!hamilton ARPA: hamilton%uiucuxc@a.cs.uiuc.edu USMail: Box 476, Urbana, IL 61801 CSNET: hamilton%uiucuxc@uiuc.csnet Phone: (217)333-8703 CIS: [73047,544] PLink: w hamilton