From: Larry McVoy <lm@mcvoy.com>
To: "Aaron J. Grier" <agrier@poofygoof.com>, tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Okistations and OKIX?
Date: Sun, 28 Jun 2020 16:41:01 -0700 [thread overview]
Message-ID: <20200628234101.GU1324@mcvoy.com> (raw)
In-Reply-To: <20200628223955.GH170@ra.poofy.goof.com>
Huh, that's a trip down memory lane. I didn't have that one but the first
PC I ever owned was a CP/M machine made by the same company. Marketed in
this country under the BMC name but it was made by Oki.
2nd one down here:
http://www.classiccmp.org/dunfield/miscpm/index.htm
I took out a $2000 loan and bought it in 1984 or 1985 because the
alternative was a VAX 11/780 that had about 30-40 people trying to
compile their projects at the same time. I believe it had 4M of
ram, definitely not enough for the load.
You'd think a 64K z80 with floppies would be a down grade, it was not,
the performance was predictable, I didn't get swapped out for minutes,
it was always working just for me.
I wrote a _ton_ of code on that machine.
On Sun, Jun 28, 2020 at 03:39:55PM -0700, Aaron J. Grier wrote:
> Anybody on the list know much about the provenance of SVr4 and OKIX for the
> Okistation 7300 model 30?
>
> http://museum.ipsj.or.jp/en/computer/work/0029.html indicates that OKIX
> came later on the model 75, but many years ago as a staff programmer at
> Oregon Graduate Institute, a surplus 7300/30 followed me home, but the
> sysadmins referred to it as OKIX.
>
> if anybody's interested in the hardware to do some spelunking, email me
> off-list.
>
> --
> Aaron J. Grier | "Not your ordinary poofy goof." | agrier@poofygoof.com
> "The price of reliability is the pursuit of the utmost simplicity. It
> is a price which the very rich find most hard to pay." -- Tony Hoare
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2020-06-28 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 22:39 Aaron J. Grier
2020-06-28 23:41 ` Larry McVoy [this message]
2020-06-29 0:35 ` Nemo
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=20200628234101.GU1324@mcvoy.com \
--to=lm@mcvoy.com \
--cc=agrier@poofygoof.com \
--cc=tuhs@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).