The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] long lived programs
Date: Fri, 23 Mar 2018 12:32:41 -0400	[thread overview]
Message-ID: <02c401d3c2c4$90fe9ba0$b2fbd2e0$@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2N15kvH0Sad9Xn6Cswjw9AG8Czf6GJVc=LqaFGbyPHscA@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

➢ Although simh is huge step in that direction ;)
 
Yep, sometimes that's the easier solution.    Remember the old Honeywell IMPs.     BBN wanted to move forward, but all the code was in 516 emulators (having been ported over from the PDP-1, they should have realized that portability would be important).   They built the C-30 to emulate the Honeywell.

Of course, this isn't even accounting for the VAX emulating the PDP and the like.

You do find some relics still running stuff.    I remember seing a new computer being installed at some FAA facilities.   It was some Apollo systems long after HP had pulled the plug on the DomainOS and the related hardware. 

I still remember a while when we were in the business of porting/selling MOTIF on a wide variety of platforms.    One day, the reps from Stellar insisted they need their loaner machine back.   This was a trade show unit and had an huge anvil shipping case.    I packed it up and put it on our loading dock.    The next day Stellar announced they were out of business.   I didn't think anything about it for a couple of years when I went out to our loading dock and said "Is this stupid thing still here."   They had never come for it.   I then was called into our sales manager's office.    Some guy needs a MOTIF for a Stellar.    I chuckle.    He goes "Yeah I know they're out of business."   I tell him that today's his lucky day.   I still have one.   I uncrated the thing, wrote him out a tape, and packed it back up.    Last I saw one of the CPU boards was hanging on the wall of our conference room as a decoration and another programmer and ripped out the Wyse PC the thing had in the top of it as a boot-up/maintenance processor to take home.



  parent reply	other threads:[~2018-03-23 16:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 15:51 Ron Natalie
2018-03-23 15:57 ` Clem Cole
2018-03-23 16:25   ` Lars Brinkhoff
2018-03-23 16:59     ` Lawrence Stewart
2018-03-23 17:31       ` Steve Nickolas
2018-03-23 16:32   ` Ron Natalie [this message]
2018-03-23 18:27 [TUHS] long lived programs (was Re: RIP John Backus Bakul Shah
2018-03-23 20:50 ` [TUHS] long lived programs Steve Johnson
2018-03-23 21:07   ` Clem Cole
2018-04-05 21:03 Norman Wilson
2018-04-05 21:23 ` Clem Cole
2018-04-05 21:38   ` Bakul Shah
2018-04-06  2:03     ` Random832
2018-04-06  4:27       ` Warner Losh
2018-04-06  4:31         ` Jon Steinhart
2018-04-06  4:58         ` Steve Nickolas
2018-04-06  5:02           ` Jon Steinhart
2018-04-06  4:29       ` Steve Johnson
2018-04-06  5:57       ` Bakul Shah
2018-04-06 21:52         ` Peter Jeremy
2018-04-05 22:46   ` Arthur Krewat
2018-04-05 23:23   ` Paul Winalski
2018-04-05 23:33     ` Arthur Krewat
2018-04-06  0:05       ` Toby Thain
2018-04-06  4:51 ` Dave Horsfall
2018-04-06 15:00 ` Tony Finch
2018-04-07 20:41 ` Paul Winalski
2018-04-06 22:33 Doug McIlroy
2018-04-07  1:01 ` Paul Winalski
2018-04-07  1:09   ` Larry McVoy

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='02c401d3c2c4$90fe9ba0$b2fbd2e0$@ronnatalie.com' \
    --to=ron@ronnatalie.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).