From: Ed Bradford <egbegb2@gmail.com>
To: arnold@skeeve.com
Cc: UNIX Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] AT&T 3B1 - Emulation available
Date: Wed, 3 Feb 2021 04:13:09 -0600 [thread overview]
Message-ID: <CAHTagfGOC7vgE2Os+kuP4oGzvot2kG3MERpQdLb2EoEhUoFpyg@mail.gmail.com> (raw)
In-Reply-To: <202102030858.1138wuqd011051@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 3039 bytes --]
Hay, Arnold,
MC 68K was created in 1980 or thereabouts. We talked about 10's
of Megahertz, I think, in those times. I was involved (slightly) with the
Zilog Z80,000 which would have competed with the 68K, NS32K and the Intel
80386. Of the instruction sets (architectures) I was most happy with, the
Zilog 32-bit processor architecture was to me, the most minimalist and
thorough. At the time, I managed software development for the Zilog
company's Z8000 computers. It was a fun era. I bought a z8000 system and
developed a CRAY simulator on it when I left Zilog and went to work for
American Supercomputer Company (another interesting Silicon Valley story).
The 1980's were a very interesting time in Silicon Valley.
One of the saddest stories I recall is when "Eagle Computer" went public.
The CEO died on the IPO day after he had become a very rich person when he
crashed a Ferrari during a test drive. Eagle Computer died with the CEO.
Ed
On Wed, Feb 3, 2021 at 2:59 AM <arnold@skeeve.com> wrote:
> The 3B1 had an MC 68010. I don't truly remember how fast the real
> system ran. The emulated system seems to run more or less the same as
> the hardware did, taking my poor memory into account.
>
> The 5620 used the same processor as the 3B2, IIRC. There are emulators
> for both (maybe done by the same guy, I don't remember). I don't know
> of emulators for the 3B5 or 3B20.
>
> Arnold
>
> Ed Bradford <egbegb2@gmail.com> wrote:
>
> > It seems to me today's 2GHz processors should be able to emulate a 3B
> (*3B
> > or not 3B, that is the question*) at a performance that far exceeds an
> > actual 3B. Is the instruction set definition and architecture of a 3B
> > available anywhere?
> >
> > Just wondering. I did such emulations for 68K machines and Cray machines.
> >
> > Ed Bradford ex-BTL, ex Silcon Valley, and ex IBM retiree.
> >
> >
> > On Wed, Feb 3, 2021 at 2:00 AM <arnold@skeeve.com> wrote:
> >
> > > emanuel stiebler <emu@e-bbes.com> wrote:
> > >
> > > > On 2021-01-29 05:49, Arnold Robbins wrote:
> > > > > Hello All.
> > > > >
> > > > > I have made a pre-installed disk image available with a fair amount
> > > > > of software, see https://www.skeeve.com/3b1/.
> > > >
> > > > Thanks for doing & making the disk images, was an easy start!
> > >
> > > You're welcome. It's a fun side project. I think I finally get the
> > > enjoyment of retrocomputing with emulated versions of systems one
> > > used in one's youth. :-)
> > >
> > > > Do you remember, ho to set up the system to have four disk drives?
> > > >
> > > > Cheers & thanks again!
> > >
> > > I don't think it can support more than 2 drives. Certainly the emulator
> > > cannot. I don't know about real hardware.
> > >
> > > You can split a big drive into partitions when formatting with the
> > > diagnostics disk, but I don't think that's what you're asking.
> > >
> > > Sorry,
> > >
> > > Arnold
> > >
> >
> >
> > --
> > Advice is judged by results, not by intentions.
> > Cicero
>
--
Advice is judged by results, not by intentions.
Cicero
[-- Attachment #2: Type: text/html, Size: 5042 bytes --]
next prev parent reply other threads:[~2021-02-03 10:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 10:49 Arnold Robbins
2021-01-29 13:49 ` Ronald Natalie
2021-01-29 14:37 ` Clem Cole
2021-01-31 7:57 ` arnold
2021-01-31 8:41 ` Rich Morin
2021-02-03 7:53 ` emanuel stiebler
2021-02-03 7:59 ` arnold
2021-02-03 8:53 ` Ed Bradford
2021-02-03 8:58 ` arnold
2021-02-03 10:13 ` Ed Bradford [this message]
2021-02-03 14:58 ` Clem Cole
2021-02-03 15:33 ` Henry Bent
2021-02-03 16:53 ` Clem Cole
2021-02-04 0:41 ` [TUHS] 68k prototypes & microcode John Gilmore
2021-02-04 0:52 ` Al Kossow
2021-02-04 1:10 ` Arthur Krewat
2021-02-04 1:33 ` Larry McVoy
2021-02-04 1:47 ` Al Kossow
2021-02-04 1:57 ` Al Kossow
2021-02-04 7:23 ` Arno Griffioen
2021-02-04 11:28 ` Toby Thain
2021-02-04 15:47 ` Arthur Krewat
2021-02-04 16:03 ` emanuel stiebler
2021-02-04 21:55 ` Dave Horsfall
2021-02-04 22:11 ` Steve Nickolas
2021-02-04 22:39 ` Adam Thornton
2021-02-04 22:47 ` Henry Bent
2021-02-05 14:42 ` Michael Parson
2021-02-04 22:56 ` Richard Salz
2021-02-04 23:14 ` Steve Nickolas
2021-02-04 1:35 ` Clem Cole
2021-02-04 2:18 ` Dave Horsfall
2021-02-04 15:53 ` Arthur Krewat
2021-02-05 2:16 ` Dave Horsfall
2021-02-05 2:53 ` Larry McVoy
2021-02-04 1:14 ` Clem Cole
2021-02-04 1:20 ` Clem Cole
2021-02-04 14:56 ` John Cowan
2021-02-03 15:20 ` [TUHS] AT&T 3B1 - Emulation available emanuel stiebler
2021-02-03 16:48 ` Doug McIntyre
2021-02-03 10:46 ` emanuel stiebler
2021-02-03 11:13 ` arnold
2021-02-05 12:44 ` Sergio Pedraja
2021-02-07 7:32 ` arnold
2021-02-17 16:07 ` emanuel stiebler
2021-02-17 22:00 ` Ed Carp
2021-02-17 22:14 ` Larry McVoy
2021-02-18 1:30 ` Ed Carp
2021-02-18 7:59 ` arnold
2021-02-18 18:07 ` Brad Spencer
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=CAHTagfGOC7vgE2Os+kuP4oGzvot2kG3MERpQdLb2EoEhUoFpyg@mail.gmail.com \
--to=egbegb2@gmail.com \
--cc=arnold@skeeve.com \
--cc=tuhs@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).