Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!unido!mikros!stefan
From: stefan@mikros.systemware.de (Stefan Stapelberg)
Newsgroups: comp.dcom.modems
Subject: Re: Solution to Problems with UUCP/modems.
Keywords: modems ACU driver
Message-ID: <324@mikros.systemware.de>
Date: 21 Sep 88 13:17:41 GMT
References: <1260@moscom.UUCP>
Reply-To: stefan@mikros.UUCP (Stefan Stapelberg)
Organization: MIKROS Systemware, Lohr/W-Germany
Lines: 29

In article <1260@moscom.UUCP> jgp@moscom.UUCP (Jim Prescott) writes:
>
>[driver supporting dialin/dialout on same device]
>
>Anybody know why everyone hasn't picked up on this?  I know that some of
>the PC Unix systems use it.

I would like to implement this scheme, but controlling the
DTR signal from the modem turns out to be a problem: The modem
doesn't answer rings if DTR has not been asserted by the opening
process.  Unfortunately, I have to use DTR to hangup the modem
after dialing out.

So my question is: If getty's open has asserted DTR high and
uucico's last close sets DTR to low, how can I ensure that the
modem still will answer rings?  I cannot use the RI signal.

I didn't want to have the driver to look for a "RING" (in word
responses or as a hardware signal) and initializing the modem
from within driver level seems to be a bad idea also.

Any hints?

Thanx, Stefan

-- 
MIKROS Systemware	stefan@mikros.UUCP, {uunet,mcvax}!unido!mikros!stefan
Stefan Stapelberg	stefan@mikros.systemware.de, stefan@ira.uka.de
Phone +49 9352 5948	^D: These are my employer's opinions - you wonder why?