From: clemc at ccc.com (Clem Cole)
Subject: [COFF] 52-pin D-Sub?
Date: Fri, 28 Feb 2020 17:28:14 -0500 [thread overview]
Message-ID: <CAC20D2P6g43jFkLUwVfARNx8a3vZrhfYXof2O-hTrTrqOAHUsg@mail.gmail.com> (raw)
In-Reply-To: <20200228220532.17F741ADFAF@yagi.h-net.msu.edu>
On Fri, Feb 28, 2020 at 5:12 PM Dennis Boone <drb at msu.edu> wrote:
> > using the secondary pins as well.
>
> Best I could tell, the major intended purpose of the secondary circuits
> was to implement autodialer, especially when those handshaking signals
> on the primary were down because there was no connection, so you
> couldn't do anything through them yet.
>
The autodialer is a separate spec. It's ECMA RS-4xx something IIRC, I
forget the number and I'm not near my books. That was the DN-11 from DEC
which talked to an AT&T 801 dialer. It used RS-232C electrical signals,
but it's actually different than RS-232C (IIRC, Able called them a
'QuadraCall').
The way auto-dialing is spec'ed, is that a single dialer supports N
modems. The Out-Band dialing stuff was an invention of Hayes who clearly
had not read the AT&T (later ECMA) spec.
>
> Was there anything else in mind during the spec process?
>
RJE stations.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200228/826c15f1/attachment-0001.html>
next prev parent reply other threads:[~2020-02-28 22:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 23:37 athornton
2020-02-28 0:04 ` dave
2020-02-28 1:37 ` stewart
2020-02-28 2:12 ` athornton
2020-02-28 4:12 ` dave
2020-02-28 4:18 ` dave
2020-02-28 14:11 ` clemc
2020-02-28 14:34 ` athornton
2020-02-28 21:23 ` dave
2020-02-28 16:35 ` krewat
2020-02-28 21:28 ` dave
2020-02-28 21:44 ` clemc
2020-02-28 21:58 ` dave
2020-02-28 22:20 ` clemc
2020-02-28 23:22 ` pechter
2020-02-29 13:12 ` emu
2020-02-29 15:45 ` krewat
2020-02-29 15:49 ` clemc
2020-02-28 22:38 ` pechter
2020-02-28 22:05 ` drb
2020-02-28 22:28 ` clemc [this message]
2020-02-28 22:26 ` pechter
2020-02-28 22:36 ` clemc
2020-02-28 23:40 ` pechter
2020-02-29 16:52 ` clemc
2020-02-28 23:54 ` pechter
2020-02-29 9:59 rudi.j.blom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC20D2P6g43jFkLUwVfARNx8a3vZrhfYXof2O-hTrTrqOAHUsg@mail.gmail.com \
--to=coff@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).