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 16:44:08 -0500	[thread overview]
Message-ID: <CAC20D2OzKhat+Qos7fXOcPm+4d7QKvvXaN9Yg0FxZc7d913bkQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2002290825510.1121@aneurin.horsfall.org>

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

> Hey, don't knock the DZ-11; if you used the right driver they worked just
> fine :-)  The trick was to disable interrupts and empty the silos every so
> often.
>
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?

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...

On my long 'todo' list has been to work with Mark to get SIMH to properly
support the DH in his emulation.   He has some stuff in there, but last
time I checked (about a year ago) it still was not right, which is a sort
of a shame.

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200228/7e93f057/attachment.html>


  reply	other threads:[~2020-02-28 21:44 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 [this message]
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
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=CAC20D2OzKhat+Qos7fXOcPm+4d7QKvvXaN9Yg0FxZc7d913bkQ@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).