Computer Old Farts Forum
 help / color / mirror / Atom feed
From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] In Memoriam: Jay W. Forrester, happy birthday Gene Amdahl, and LSD
Date: Sun, 17 Nov 2019 16:14:10 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.1911171602000.408@aneurin.horsfall.org> (raw)
In-Reply-To: <20191116072354.GA74610@server.rulingia.com>

On Sat, 16 Nov 2019, Peter Jeremy wrote:

> More than just the instruction set - IBM published a formal description 
> of the S/360 (in APL in the IBM Systems Journal issue that announced the 
> S/360).  The S/360 was (I believe) the first case where a company 
> announced a computer architecture (rather than an implementation) and 
> implementations were expected to precisely comply with the architecture 
> (no more finding undocumented instructions and side-effects and writing 
> code that depended on them).  This meant that clone makers could build a 
> clone that accurately emulated a S/360.

Ah, I'd forgotten about the APL documentation; thanks!  Talk about giving 
away the keys to the kingdom: Amdahl, Fujitsu, Hitachi...

> AFAIR, the only "implementation defined" instruction was DIAGNOSE, 
> OS/360 could presumably tell what it was running on by checking 
> particular DIAGNOSE function.  (VM/370 was paravirtualised and used 
> DIAGNOSE to communicate with the hypervisor - CP).

Another point I had forgotten :-(  Yep, the DIAG instruction was utterly 
implementation-dependent, and thus OS/360 could tell whether it was 
running on a clone or not.

Cut me some slack; I turned 67 last month :-(

> In the early PC era, it was not uncommon for applications to verify they 
> were running on a genuine IBM PC by looking for the copyright notice in 
> the BIOS - which clone makers countered by placing a "not" before an 
> equivalent copyright notice.

I remember the days of the "grey imports" (or "gray" for the Americans); 
if it ran Flight Simulator and not labelled "IBM" then it was technically 
illegal; shortly afterwards if it did *not* run FS then nobody would buy 
it :-)

How things change...

-- Dave


  parent reply	other threads:[~2019-11-17  5:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 21:54 dave
2019-11-15 22:26 ` krewat
2019-11-15 22:42   ` dave
2019-11-16  7:23     ` peter
2019-11-16 16:25       ` clemc
2019-11-17  5:14       ` dave [this message]
2019-11-18 16:42         ` clemc
2019-11-18 18:45           ` bakul
2019-11-18 19:19             ` clemc
2019-11-19 20:21             ` peter
2019-11-19 23:17               ` cym224
2019-11-21 19:48           ` dave
2019-11-15 23:19   ` clemc
2019-11-15 23:47     ` krewat
  -- strict thread matches above, loose matches on Subject: below --
2018-11-15 22:33 dave

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.1911171602000.408@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).