Path: utzoo!dciem!nrcaer!julie!mcr
From: mcr@julie.UUCP (Michael Richardson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: DTR and serial.device
Message-ID: <0352.AA0352@julie>
Date: 11 Feb 89 18:49:37 GMT
Article-I.D.: julie.0352.AA0352
Followup-To: comp.sys.amiga.tech
Distribution: world
Organization: Sandleman Software Works' Debugging Department, Ottawa, ON
Lines: 33

Marco Papa Doc writes:
>As Bryce suggested, a "better" way is to close the device, wait 1 sec and
>then reopen it (with the SAME parameters).  I tried it and it works just
>fine.  DTR is dropped properly.

  Do I have to close ALL my serial.devices or just one? (In the
case of SERF_SHARED, and opening it once for read and once for write.)
I built my own serial cable, and I don't have DTR wired up, but I'll
get around to doing it sometime.
  One advantage (not from a security point of view) is that I'll sometimes
crash the machine in another window, but when I reboot I'm still connected
to the SUN. Can we have a 'hangupOnClose' flag then? And a standard
way to drop DTR? (What if I use it to dial a dumb modem? Or to indicate
that the next bytes are commands for the modem, or 'out of band' data
in a network?)

>Multi-serial manufacturers should ensure that this technique works on their
>hardware too.

  I'd rather they set a (defacto) standard than conform here. How about
it Perry? Does the sioxbs.device (or whatever) provide this?

>-- Marco Papa 'Doc'



--

  :!mcr!:
  Michael Richardson                     Amiga
                                  v--------+
 UUCP: uunet!attcan!lsuc!nrcaer!julie!mcr  | INTERNET mcr@doe.carleton.ca
 Fido: Michael Richardson @ 1:163/109.10<--+ Alter @ 7:483/109.10