Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: What Happened to Interdata?
Date: Wed, 26 Jul 2023 10:38:04 -0400	[thread overview]
Message-ID: <CABH=_VRu-oCUKKxX1nhO91=99rLhw1zUGEfXQ08uXqSUPC8OyQ@mail.gmail.com> (raw)
In-Reply-To: <HVRjf4jkQW1dVYskomfTSIyGSjCdbjfs0ykG_cGfY4xTnXPSkPDIgZt86xk_jyaYHr_ukdE8a9LsjFtfWVwgvF3AbB8br2S5BUDNeyZKnEg=@protonmail.com>

On 7/25/23, segaloco via COFF <coff@tuhs.org> wrote:
> 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?

I suspect that Interdata had the same problem with their S/360
lookalikes that RCA did with theirs.  If your business model is to
provide a cheaper hardware alternative to IBM, your machine has to run
IBM software, particularly the OS.  When IBM did their pre-release of
the S/370 specifications they deliberately left out key bits of the
privileged architecture, such as the detailed bit layout of the PSW.
Companies such as RCA and Interdata had make guesses while designing
their S/370 lookalikes and in some cases they guessed wrong.  RCA's
Spectra 70 couldn't run IBM OS/VS or DOS/VS and that made it a total
non-starter for most IBM commercial shops.  I suspect Interdata ran
into the same problem.  Yes, they could design their own me-too
operating systems, but they would always lag behind on new IBM OS
features, on which critical IBM applications would depend.  The IBM
customer base knew this and stuck with genuine IBM.  A lower price
point wasn't enough to make up for the incompatibility.

The advent of 32-bit minicomputers at the end of the 1970s brought
down for good the IBM price umbrella under which Interdata and other
lookalikes had been living.  An example of how high that price
umbrella had been:  In 1978 my undergraduate alma mater was a
true-blue IBM shop with a S/370 model 125 running batch, CICS, and a
small BASIC timesharing system for the students.  They'd outgrown the
model 125.  IBM's solution was to upgrade to a model 135.  For the
same price as the IBM processor upgrade, DEC was offering a complete
VAX-11/780 system to run timesharing and other academic computing,
with the S/370-125 devoted exclusively to the business side of things.
The 11/780 was roughly equivalent in computing power to an IBM
S/370-158--two models up from the 125.  Buying the 11/780 was a
complete no-brainer.

IBM was forced to cut prices on the S/370 line, and that fatally
destroyed Interdata's one advantage over true S/360/370.

-Paul W.

  reply	other threads:[~2023-07-26 14:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 23:23 [COFF] " segaloco via COFF
2023-07-26 14:38 ` Paul Winalski [this message]
2023-07-26 17:39   ` [COFF] " 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
2023-07-27 19:16 [COFF] " Noel Chiappa
2023-07-27 20:33 ` Paul Winalski
2023-07-28  3:38   ` Greg 'groggy' Lehey
2023-07-28 16:18     ` Paul Winalski

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='CABH=_VRu-oCUKKxX1nhO91=99rLhw1zUGEfXQ08uXqSUPC8OyQ@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=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).