Computer Old Farts Forum
 help / color / mirror / Atom feed
From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] 52-pin D-Sub?
Date: Fri, 28 Feb 2020 15:12:25 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.2002281506420.1121@aneurin.horsfall.org> (raw)
In-Reply-To: <905CE999-5601-4521-847B-B2146C60B564@serissa.com>

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

On Thu, 27 Feb 2020, Lawrence Stewart wrote:

> Huh.  New to me too, but Digikey links to the datasheets, and they 
> really do mean DB.They go up to DD100.  They are called “double 
> density”.

No; the "B" in "DB" means B-sized e.g. the size of a DB-25 connector. 
This is a common mistake e.g. a "DB-9" (sic) would be a 25-pin sized 
connector holding just 9 pins (it's really a "DE-9") with godnoze-what 
spacing.

Believe it or not there is a convention for it:

     http://en.wikipedia.org/wiki/D-subminiature

Yes, it's one of my gripes...

-- Dave


  parent reply	other threads:[~2020-02-28  4:12 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 [this message]
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
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.2002281506420.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).