Computer Old Farts Forum
 help / color / mirror / Atom feed
From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] 52-pin D-Sub?
Date: Sat, 29 Feb 2020 08:58:40 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.2002290850410.1121@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2OzKhat+Qos7fXOcPm+4d7QKvvXaN9Yg0FxZc7d913bkQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

On Fri, 28 Feb 2020, Clem Cole wrote:

> DZ-11 sucked... for a number of reasons, the SW issue being just part of 
> them, but they were short pinned and really did not do modems well, 
> particularly high-speed ones like the Trailblazer.  As you said, you 
> could make them work, but why bother?

We used ours for local terminals only; 8 DZ-11s on the 11/70 worked fine 
(I don't recall how fast, but probably around 2400/4800).  As I said, it 
came down to the driver.

> Unix folks figure out the best idea was to use the Able DH/DM -  
> cheaper, only one unibus slot for 16 ports (as opposed to 2 for the DZ), 
> fully wired on the DB25 end, hardware flow control and just worked 
> better in that is will DMA.  What was not to love...

Sure, but then DEC Field Circus won't touch the box.

> FWIW:  One of the guys behind DZ (who I will leave nameless) also 
> screwed up the first serial port on the Masscomp MC/500 after he left 
> DEC. I got there too late to fix it in the first version of the CPU 
> board.  So it was not fixed until I tore him a new one and educated him 
> on how RS-232 actually worked (I was the first lead for the data com 
> group as well as 1/2 the OS team).  I never quite understood why HW 
> folks often though of the serial port as '3-wires' -- sigh.

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.

-- Dave


  reply	other threads:[~2020-02-28 21:58 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 [this message]
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
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=alpine.BSF.2.21.9999.2002290850410.1121@aneurin.horsfall.org \
    --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).