Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Greg 'groggy' Lehey <grog@lemis.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: What Happened to Interdata?
Date: Thu, 27 Jul 2023 13:43:50 +1000	[thread overview]
Message-ID: <20230727034350.GC92211@eureka.lemis.com> (raw)
In-Reply-To: <CABH=_VRu-oCUKKxX1nhO91=99rLhw1zUGEfXQ08uXqSUPC8OyQ@mail.gmail.com>

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

On Wednesday, 26 July 2023 at 10:38:04 -0400, Paul Winalski wrote:
> 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.

That's not the way I remember it.  RCA (and UNIVAC with them) and
Interdata had instruction sets that were close to the IBM instruction
set, but my recollection was that they were different enough that IBM
software wouldn't run on them.  That's a different situation from
Amdahl, which was almost completely compatible.

But that was a few years ago now, and I have forgotten the details.
Does anybody know for sure whether they could run IBM software?  I
know from my time at UNIVAC that the 9000 series had their own
operating systems.

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

  parent reply	other threads:[~2023-07-27  3:44 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 ` [COFF] " Paul Winalski
2023-07-26 17:39   ` segaloco via COFF
2023-07-27  3:43   ` Greg 'groggy' Lehey [this message]
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=20230727034350.GC92211@eureka.lemis.com \
    --to=grog@lemis.com \
    --cc=coff@tuhs.org \
    --cc=paul.winalski@gmail.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).