From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: coff@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [COFF] Re: What Happened to Interdata?
Date: Thu, 27 Jul 2023 15:16:43 -0400 (EDT) [thread overview]
Message-ID: <20230727191643.AE34718C079@mercury.lcs.mit.edu> (raw)
> From: Greg 'groggy' Lehey
> 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.
Bitsavers doesn't have a wealth of Interdata documentation, but there is some:
http://bitsavers.org/pdf/interdata/32bit/
Someone who's familiar with the 360 instruction set should be able to look
at e.g.:
http://bitsavers.org/pdf/interdata/32bit/8-32/8-32_Brochure_1977.pdf
and see how compatible it is.
Noel
next reply other threads:[~2023-07-27 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 19:16 Noel Chiappa [this message]
2023-07-27 20:33 ` Paul Winalski
2023-07-28 3:38 ` Greg 'groggy' Lehey
2023-07-28 16:18 ` Paul Winalski
-- strict thread matches above, loose matches on Subject: below --
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
2023-07-27 16:30 ` Paul Winalski
2023-08-05 1:17 ` scj
2023-08-05 1:46 ` segaloco via COFF
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=20230727191643.AE34718C079@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=coff@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).