Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!att!cbnews!mjs
From: mjs@cbnews.att.com (martin.j.shannon)
Newsgroups: comp.dcom.modems
Subject: Re: USR 9600 baud dual standard
Summary: I dunno!
Message-ID: <1990Oct11.173521.21961@cbnews.att.com>
Date: 11 Oct 90 17:35:21 GMT
References: <1990Sep30.024433.28717@athena.mit.edu> <2461@van-bc.wimsey.bc.ca> <2502@van-bc.wimsey.bc.ca>
Organization: AT&T Bell Laboratories
Lines: 51

In article <2502@van-bc.wimsey.bc.ca>, sl@van-bc.wimsey.bc.ca (Stuart Lynne) writes:
> In article <1990Oct9.161454.10476@cbnews.att.com> mjs@cbnews.att.com (martin.j.shannon) writes:
> >In article <2461@van-bc.wimsey.bc.ca>, sl@van-bc.wimsey.bc.ca (Stuart Lynne) writes:
> >> In article <1990Oct8.195418.1817@cbnews.att.com> mjs@cbnews.att.com (martin.j.shannon) writes:
> >> 
> >I beg to differ.  'e' protocol does *NO* *ERROR* *CHECKING*.  This is
> 
> Hm. Now if I could just find an off the shelf uucp that offer's 'e' for my
> Xenix system, or my SCO UNIX system. Or any of the standard System V
> platforms.

Hmmm.  Did you try any?  I know that ISC 2.0.2 includes 'e' protocol.
Since ISC has it, it wouldn't surprise me if it was in the porting base
for SVR3.2.  That implies that ESIX and others should have it, too.

> Any idea when AT&T will be offerring 'e' as a standard part of
> their uucico? You're in a better position than I am to know.

See my .signature below and my guess above.  I am not currently
connected with the folks who develop the UNIX System, and even if I
was, it is certainly not my place to disclose policy on such matters.
Sorry.

> I'd love to be
> able to use 'e'. But I'm stuck with all of these inferior type uucico's
> which only have 'g'.

All I can suggest is "try it".  Use the protocol subfield in either the
Systems file, or the protocol subfield of the Devices file (no idea
where it is in either of these files).  The docs have all the info
(except which protocols are actually supported, natch).  I don't want
to rely on some fuzzy recollection of what I did.

> So I guess I just assume that if most uucp's don't
> offer 'e' then the default has to be 'g'. I'd love to hear different though.
> Keep us informed. Thanks.

Yes, the default is 'g'.  Notice that you don't specify that 'g'
protocol is to be used in any of your uucp files.  You have to actively
edit one to get 'e' protocol.  To find out if a remote site supports
it, use Uutry and look for the "Pge" message (that's what ISC 2.0.2
gives); if 'e' appears in that string, your neighbor does have it.
Additionally, to verify that you're requesting to use 'e', make sure
that your machine responds with "Ue".

Remember that you *must* have an error-free link, *including* hardware
flow control, if you want to make this work.  It does for me.
-- 
Marty Shannon; AT&T Bell Labs; Liberty Corner, NJ, USA
(Affiliation is given for identification only:
I don't speak for them; they don't speak for me.)