From: lm@bitmover.com (Larry McVoy)
Subject: [TUHS] DG/UX Machine. $$ reward
Date: Sat, 10 Jul 2010 19:44:50 -0700 [thread overview]
Message-ID: <20100711024450.GB5588@bitmover.com> (raw)
In-Reply-To: <4C390FBE.1070209@bitsavers.org>
On Sat, Jul 10, 2010 at 05:26:38PM -0700, Al Kossow wrote:
> On 7/10/10 2:32 AM, asbesto wrote:
>> using a motorila 68020 processor (if I
>> remember well, maybe I'm wrong)
>>
>
> 88100 or 88110, depending on model.
Wow. Been a long time since I've thought about that CPU. Never wrote
any assembler for it but paged through the manuals. My memories are
vague but what I remember was sort of feeling like "what's the point?".
Quite a different feeling from when I hit the National 32016 and 32032
manuals. That was a chip I so wanted to love (and did, until I used
one, pretty buggy). But a really sweet chip.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2010-07-11 2:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 13:51 DG UX
2010-07-10 9:32 ` asbesto
2010-07-11 0:26 ` Al Kossow
2010-07-11 2:44 ` Larry McVoy [this message]
2010-07-11 4:43 ` Jason Stevens
2010-07-11 13:50 Norman Wilson
2010-07-12 14:51 ` asbesto
2010-07-13 3:37 John Finigan
2010-07-13 3:51 ` Larry McVoy
2010-07-13 6:52 ` Benjamin Huntsman
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=20100711024450.GB5588@bitmover.com \
--to=lm@bitmover.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).