Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] 52-pin D-Sub?
Date: Fri, 28 Feb 2020 17:20:36 -0500	[thread overview]
Message-ID: <CAC20D2NTD-x1gJB6uxqfk6qwXzGGO+V1AAgGmXPaSikVWWokNg@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2002290850410.1121@aneurin.horsfall.org>

On Fri, Feb 28, 2020 at 4:58 PM Dave Horsfall <dave at horsfall.org> wrote:

>
> Sure, but then DEC Field Circus won't touch the box.
>
That's not true.  All our UNIX systems at UCB and CMU had DEC field service
on them and we had lots of non-DEC HW, including memory, disk and disk
controllers.   Funny, the DEC knew we could swap memory chips on the
National Semiconductor memory board for the Vax.  Which we could not do
with the DEC boards, they had to be swapped.

The same was true at BTL, in fact and at Bell, there were DEC folks
on-site.  They might occasionally gripe, but we used to joke about it.  It
probably helped in all these places we had more than multiple systems and
the field offices knew better.  If we called, it was busted.



>
> Heh heh :-)  I don't think I've ever seen RS-232 used "properly" i.e.
> implementing DSR/DTR or RTS/CTS for other than flow control etc, and using
> the secondary pins as well.

Maybe you never saw a serial RJE station or I suspect a  serial line that
was fully synchronous running one of the IBM protocols.  That was sort of
where I started to learn in the late 1960s.  I saw IBM systems before I saw
the DEC ones and IBM used all the wires.  Eventually, I got a copy of the
wonderful DEC press book from John McNamara, called "Technical Aspects of
Data Communications."

Then I learned about UNIX, which came from AT&T which used all that stuff
in their modems and data communications gear.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200228/2c79f9a5/attachment.html>


  reply	other threads:[~2020-02-28 22:20 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 [this message]
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
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=CAC20D2NTD-x1gJB6uxqfk6qwXzGGO+V1AAgGmXPaSikVWWokNg@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).