Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] What Happened to Interdata?
Date: Tue, 25 Jul 2023 23:23:01 +0000	[thread overview]
Message-ID: <HVRjf4jkQW1dVYskomfTSIyGSjCdbjfs0ykG_cGfY4xTnXPSkPDIgZt86xk_jyaYHr_ukdE8a9LsjFtfWVwgvF3AbB8br2S5BUDNeyZKnEg=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

So I've been studying the Interdata 32-bit machines a bit more closely lately and I'm wondering if someone who was there at the time has the scoop on what happened to them. The Wikipedia article gives some good info on their history but not really anything about, say, failed follow-ons that tanked their market, significant reasons for avoidance, or anything like that. I also find myself wondering why Bell didn't do anything with the Interdata work after springboarding further portability efforts while several other little streams, even those unreleased like the S/370 and 8086 ports seemed to stick around internally for longer. Were Interdata machines problematic in some sort of way, or was it merely fate, with more popular minis from DEC simply spacing them out of the market? Part of my interest too comes from what influence the legacy of Interdata may have had on Perkin-Elmer, as I've worked with Perkin-Elmer analytical equipment several times in the chemistry-side of my career and am curious if I was ever operating some vague descendent of Interdata designs in the embedded controllers in say one of my mass specs back when.

- Matt G.

P.S. Looking for more general history hence COFF, but towards a more UNIXy end, if there's any sort of missing scoop on the life and times of the Bell Interdata 8/32 port, for instance, whether it ever saw literally any production use in the System or was only ever on the machines being used for the portability work, I'm sure that could benefit from a CC to TUHS if that history winds up in this thread.

[-- Attachment #2: Type: text/html, Size: 1847 bytes --]

             reply	other threads:[~2023-07-25 23:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 23:23 segaloco via COFF [this message]
2023-07-26 14:38 ` [COFF] " Paul Winalski
2023-07-26 17:39   ` segaloco via COFF
2023-07-27  3:43   ` Greg 'groggy' Lehey
2023-07-27 16:30     ` Paul Winalski
2023-08-05  1:17 ` scj
2023-08-05  1:46   ` segaloco via COFF
     [not found]     ` <CANxB0bSVf+wc=Np8B+AbMPJ+myLhJR9m0M+etfEyrviqok0uSg@mail.gmail.com>
2023-08-05 13:57       ` [COFF] Re: [TUHS] " steve jenkin

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='HVRjf4jkQW1dVYskomfTSIyGSjCdbjfs0ykG_cGfY4xTnXPSkPDIgZt86xk_jyaYHr_ukdE8a9LsjFtfWVwgvF3AbB8br2S5BUDNeyZKnEg=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).