From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Brad Spencer <brad@anduin.eldar.org>
Cc: coff@tuhs.org
Subject: [COFF] Re: Microware's OS-9 (was: [TUHS] Clever code)
Date: Fri, 6 Jan 2023 10:38:40 -0600 [thread overview]
Message-ID: <20230106163839.oj7recybz3bk5ozp@illithid> (raw)
In-Reply-To: <xonwn6u5700.fsf@anduin.eldar.org>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
At 2022-12-14T10:39:59-0500, Brad Spencer wrote:
> "G. Branden Robinson" <g.branden.robinson@gmail.com> writes:
> The source to OS-9/6809 would have been released by Microware a long
> time ago had it not been for a particular person in the user
> community. Got mucked up. I fell out of following it after the BSD
> Unixs became available.
They guy's name wasn't Mark Siegel, was it?
(Feel free to reply privately.)
> Level II was nice. It was able to use bank switching and would allow
> a set of random 8k memory blocks out of the 128k or 512k present in
> the CC3 system to be mapped into the 6809 64k address space. The
> Color Computer didn't support memory protection, so no paging or any
> real process protection, but this banking allowed for a lot of
> possibilities. I know that there was other OS-9 systems around that
> ran Level II but I don't really know how they managed memory. I would
> suspect it to be simular to the CC3, but that is just a guess on my
> part.
I ask because I asked around elsewhere, and this guy got very hostile
very fast, and touted the GIME chip as performing "address translation"
as if it were a Motorola 68451 or something. (I'm not sure even _that_
does address translation in the sense we think of it today, but in any
case it was a more powerful, more complex and therefore expensive part
than Tandy was ever going to replicate or put in their Color Computers.)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-01-06 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221214151444.niv5xtnxlmoifbrm@illithid>
2022-12-14 15:39 ` Brad Spencer
2023-01-06 16:38 ` G. Branden Robinson [this message]
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=20230106163839.oj7recybz3bk5ozp@illithid \
--to=g.branden.robinson@gmail.com \
--cc=brad@anduin.eldar.org \
--cc=coff@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).