Xref: utzoo comp.dcom.modems:2889 comp.sys.att:4701
Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!rutgers!iuvax!inuxc!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.dcom.modems,comp.sys.att
Subject: Re: Verbose modems (Re: MORE 6386 UUCP WOES)
Message-ID: <6916@chinet.chi.il.us>
Date: 9 Nov 88 15:33:17 GMT
References: <319@argon.UUCP> <2096@cuuxb.ATT.COM> <727@wsccs.UUCP> <889@vsi.COM> <758@wsccs.UUCP> <83@prapc2.UUCP> <2174@cuuxb.ATT.COM> <5203@cbmvax.UUCP>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 19

In article <5203@cbmvax.UUCP> ditto@cbmvax.UUCP (Michael "Ford" Ditto) writes:

>My point was that Unix has the software support required to handle
>modems the way they were meant to work -- using EIA signals rather
>than ASCII strings sent by a microprocessor in the modem.  There is
>no reason to have a dialin modem in verbose mode in the first place.

Where is the EIA signal to indicate 9600 vs. 4800 vs. 2400 vs. 1200
baud connection?  Where is the software support for it?  The real
point is that modern microprocessor controlled modems have many more
features than those available when the EIA signals were defined (although
it is still reasonable to expect DCD to indicate a connection to a
remote modem).  ASCII strings are the only way to access the new features,
so why hasn't the software support caught up.  Why can't getty be told
to match the speed of a connection?  (I know something like this has been
posted.)  Why doesn't uucp's dialer pay attention to the CONNECT message and
change speeds if necessary? 

Les Mikesell