From: <ron@ronnatalie.com>
To: "'The Eunuchs Hysterical Society'" <tuhs@tuhs.org>
Subject: Re: [TUHS] Interactive Systems (was Pcc for 386)
Date: Thu, 11 Jul 2019 18:02:21 -0400 [thread overview]
Message-ID: <27f401d53834$51101140$f33033c0$@ronnatalie.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Interactive Systems. Now there’s a name I’ve not heard in many a year. Heinz Lycklama went there.
The did a couple of things, a straight UNIX port to various things (PDP-11, 386) and also there “UNIX running under VMS” product.
They also had their own version of the Rand Editor called “INed” that was happiest on this hacked version of a Perkin Elmer terminal.
Early versions were PWB UNIX based if I recall.
My first job out of college was working with IS Unix on an 11/70 playing configuration management (essentially all the PWB stuff). I also hacked the line printer spooler and the .mm macro package to do classification markings (this was a part of a government contract).
A few years later I was given the job of porting Interactive Systems UNIX that was already running on an i386 (an Intel 310 system which had a Multibus I) to an Intel Multibus II box. Intel had already ported it once, but nobody seemed to be able to find the source code. So with a fresh set of the source code for the old system from IS, I proceeded to reverse engineer/port the code to the Message Passing Coprocessor. (Intel was not real forthcoming for documentation for that either). Eventually, I got it to work (the Multibus II really was a pleasant bus and worked well with UNIX). I went on to write drivers for a 9-track tape drive (which sat in my living room for a long time), a Matrox multibus II framebuffer (OK, that had problems), and a SCSI host adapter that was talking to this kludge device that captured digital data from a FLIR on uMatic cassettes (but that’s a different story).
[-- Attachment #2: Type: text/html, Size: 3757 bytes --]
next reply other threads:[~2019-07-11 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 22:02 ron [this message]
2019-07-11 22:31 ` Dave Horsfall
2019-07-12 2:52 ` Warner Losh
2019-07-12 3:55 ` Nigel Williams
2019-07-12 17:00 ` Clem Cole
2019-07-12 20:12 ` Deborah Scherrer
2019-07-12 20:45 ` Paul Winalski
2019-07-12 21:43 ` Deborah Scherrer
2019-07-12 22:45 ` Clem Cole
2019-07-12 23:18 ` Deborah Scherrer
2019-07-13 0:24 ` Dave Horsfall
2019-07-13 0:36 ` Dave Horsfall
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='27f401d53834$51101140$f33033c0$@ronnatalie.com' \
--to=ron@ronnatalie.com \
--cc=tuhs@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).