From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] PDP-11 questions
Date: Mon, 25 Jan 2016 11:00:47 -0500 [thread overview]
Message-ID: <20160125160044.GA18971@mercury.ccil.org> (raw)
In-Reply-To: <56A627EC.60509@update.uu.se>
Johnny Billquist scripsit:
> the desktop models are called MS800A, MS800B, MS880A and MS880B.
Good to know.
> Reading through it, it's very clear that this is not OS/8, or any
> derivative of it.
You're right. What it did share, however, was the OS/8 file system,
except that the date epoch was 1972 instead of 1970. I don't know if
COS survived long enough to use extended dates.
> the transfer program
> available to transfer files to/from OS/8.
That didn't actually transfer files, which wasn't necessary; IIRC,
it converted between the COS-310 format for text files (about which
I know nothing) and the OS/8 format (three 8-bit bytes in two 12-bit words,
packed with the first two bytes in the low order bits of the words,
and the third byte split between the four high order bits).
> The EDUsystems were in fact having numbers
> like 10, 20, 25, 30, 40 and 50. No 310 or anything close...
That's what I remember. My first PDP-8 was running EDU30 on top of
OS/8.
> But EDUsystems do not really predate the 8/A. They carried on in the
> PDP-11 systems as well, beyond the 8/A era.
Sure. What I mean is that the EDUsystems began before the 8/A, not that
they ended before it.
--
John Cowan http://www.ccil.org/~cowan cowan at ccil.org
Why are well-meaning Westerners so concerned that the opening of a
Colonel Sanders in Beijing means the end of Chinese culture? [...]
We have had Chinese restaurants in America for over a century,
and it hasn't made us Chinese. On the contrary, we obliged the Chinese
to invent chop suey. --Marshall Sahlins
next prev parent reply other threads:[~2016-01-25 16:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.29.1453684304.15972.tuhs@minnie.tuhs.org>
2016-01-25 3:07 ` Johnny Billquist
2016-01-25 3:09 ` Johnny Billquist
2016-01-25 12:54 ` John Cowan
2016-01-25 13:09 ` Johnny Billquist
2016-01-25 13:49 ` Johnny Billquist
2016-01-25 16:00 ` John Cowan [this message]
2016-01-25 16:17 ` Johnny Billquist
2016-01-25 16:43 ` John Cowan
2016-01-26 20:07 Doug McIlroy
2016-01-26 20:44 ` Clem Cole
-- strict thread matches above, loose matches on Subject: below --
2016-01-26 19:36 Doug McIlroy
2016-01-26 19:59 ` Warren Toomey
2016-01-25 1:11 Noel Chiappa
2016-01-25 1:30 ` Clem cole
2016-01-24 22:40 Norman Wilson
2016-01-25 1:55 ` David Ritchie
2016-01-25 1:59 ` Ronald Natalie
2016-01-25 2:14 ` Clem cole
2016-01-25 11:29 ` Tony Finch
2016-01-25 13:25 ` Ronald Natalie
2016-01-25 16:18 ` Pete Turnbull
2016-01-25 19:37 ` Clem Cole
2016-01-24 22:40 Norman Wilson
2016-01-25 0:23 ` Ronald Natalie
2016-01-24 18:56 Noel Chiappa
[not found] <mailman.25.1453658502.15972.tuhs@minnie.tuhs.org>
2016-01-24 18:34 ` Johnny Billquist
2016-01-24 18:30 Noel Chiappa
2016-01-24 18:36 ` Ronald Natalie
2016-01-24 21:10 ` John Cowan
2016-01-25 0:11 ` scj
2016-01-25 0:36 ` Clem cole
2016-01-24 18:01 Noel Chiappa
2016-01-24 17:37 Mark Longridge
2016-01-24 18:49 ` Clem Cole
2016-01-25 3:16 ` Dave Horsfall
2016-01-25 5:32 ` Warren Toomey
2016-01-25 12:27 ` Clem cole
2016-01-25 13:38 ` Lawrence Stewart
2016-01-25 14:15 ` Clem Cole
2016-01-26 19:52 ` Dave Horsfall
2016-01-26 20:41 ` 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=20160125160044.GA18971@mercury.ccil.org \
--to=cowan@mercury.ccil.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).