From: tfb@cley.com (Tim Bradshaw)
Subject: [TUHS] Franz Lisp platforms
Date: Thu, 3 Apr 2003 16:39:40 +0100 [thread overview]
Message-ID: <16012.21948.183397.79264@cley.com> (raw)
In-Reply-To: <3E8C2C41.4610.94D49@localhost>
* L J Buitinck wrote:
> I was especially surprised by "lisa_unisys3". is that Unisoft SysIII
> for the Apple Lisa?! and does anyone know what
> {dual,pixel}_unisoft and mc500_2_0 mean?
You might get a better answer by asking on comp.lang.lisp, but my
guesses are that mc500_2_0 is a Masscomp 500 (?) running RTU 2.0.
Dual seem to have been people who made early 68k boards and machines
and (according to
http://www.clock.org/~fair/computers/dual-systems.html) were Unisoft's
first customer. Didn't Sun use unisoft as well, before the BSD ports
(so sometime pre SunOS 1 I guess...).
All of these, look like early 68k Unix machines - there must
have been hundreds of kinds of these, I guess.
--tim
next prev parent reply other threads:[~2003-04-03 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 10:42 L.J. Buitinck
2003-04-03 15:39 ` Tim Bradshaw [this message]
2003-04-03 15:41 ` Tim Bradshaw
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=16012.21948.183397.79264@cley.com \
--to=tfb@cley.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).