From: William Pechter <pechter@gmail.com>
To: Steve Nickolas <usotsuki@buric.co>,Tuhs <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Unix on Zilog Z8000?
Date: Tue, 21 Jan 2020 13:27:22 -0500 [thread overview]
Message-ID: <455e1c85-8a45-4d20-8653-2274674608ef.maildroid@localhost> (raw)
In-Reply-To: <alpine.BSF.2.02.2001211312550.63702@frieza.hoshinet.org>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
IIRC... Zilog had Zeus (a SYSIII version) running. Exxon Office Systems swallowed and regurgitated Zilog. They were a Vax customer in Princeton in the late '80s. I installed one of the Vax 11/780s with the first RM80 I (and my office) ever saw as a brand new Field Service grunt.
The US Internal Revenue Service was looking at replacing (Z8000 systems) them with AT&T sold Pyramid boxes when I was there. Then they swallowed NCR and it all fell apart. This was around '94 or so.
AT&T and Siemens were both Pyramid OEMs and were about 50% of Pyramid's business (I was told). Anyone have further info? When Exxon pulled the plug on EOS I thing things were up in the air...
Bill
Sent from pechter@gmail.com
-----Original Message-----
From: Steve Nickolas <usotsuki@buric.co>
To: Jon Forrest <nobozo@gmail.com>
Cc: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Sent: Tue, 21 Jan 2020 13:14
Subject: Re: [TUHS] Unix on Zilog Z8000?
On Tue, 21 Jan 2020, Jon Forrest wrote:
> There's been a lot of discussion about early Unix on Intel, National
> Semi, Motorola, and Sparc processors. I don't recall if Unix ran on
> the Z8000, and if not, why not.
>
> As I remember the Z8000 was going to be the great white hope that
> would continue Zilog's success with the Z80 into modern times.
> But, it obviously didn't happen.
>
> Why?
>
> Jon
>
Didn't Coherent run on the Z8K? Though that's not really Unix.
-uso.
[-- Attachment #2: Type: text/html, Size: 1912 bytes --]
next prev parent reply other threads:[~2020-01-21 18:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 17:52 Jon Forrest
2020-01-21 18:13 ` Steve Nickolas
2020-01-21 18:27 ` William Pechter [this message]
2020-01-21 18:15 ` Henry Bent
2020-01-21 18:20 ` Larry McVoy
2020-01-21 21:48 ` Nigel Williams
2020-01-21 22:00 ` Henry Bent
2020-01-21 22:36 ` Derek Fawcus
2020-01-21 22:35 ` Jason Stevens
2020-03-15 18:40 ` Cornelius Keck
2020-03-16 0:28 ` Wesley Parish
2020-03-16 22:02 ` Derek Fawcus
2020-01-21 18:32 ` William Pechter
2020-01-21 21:24 ` Jon Forrest
2020-01-21 18:28 ` Clem Cole
2020-01-21 21:07 ` Heinz Lycklama
2020-01-21 21:32 ` [TUHS] Onyx (was Re: Unix on Zilog Z8000?) Derek Fawcus
2020-01-22 8:18 ` [TUHS] Unix on Zilog Z8000? Arrigo Triulzi
2020-01-22 17:00 ` Mary Ann Horton
2020-01-22 21:04 ` [TUHS] Life at UC Berkeley (was Unix on Zilog Z8000?) Jon Forrest
2020-01-23 2:08 ` [TUHS] Unix on Zilog Z8000? Erik Fair
2020-01-22 19:55 ` Andreas Hein
2020-01-23 12:01 ` Oliver Lehmann
2020-01-25 1:46 ` [TUHS] Dhrystone Benchmark (was: Unix on Zilog Z8000?) Oliver Lehmann
2020-01-25 1:49 ` Oliver Lehmann
2020-01-25 2:29 ` Warner Losh
2020-01-22 10:56 [TUHS] Unix on Zilog Z8000? Paul Ruizendaal
2020-01-22 13:14 Paul Ruizendaal
2020-01-22 15:14 ` Clem Cole
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=455e1c85-8a45-4d20-8653-2274674608ef.maildroid@localhost \
--to=pechter@gmail.com \
--cc=tuhs@minnie.tuhs.org \
--cc=usotsuki@buric.co \
/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).