From: Arnold Robbins <arnold@skeeve.com>
To: tuhs@tuhs.org
Subject: [TUHS] AT&T 3B1 - Emulation available
Date: Fri, 29 Jan 2021 12:49:17 +0200 [thread overview]
Message-ID: <E1l5RL3-0002iv-Qv@tanda> (raw)
Hello All.
Many of you may remember the AT&T UNIX PC and 3B1. These systems
were built by Convergent Technologies and sold by AT&T. They had an
MC 68010 processor, up to 4 Meg Ram and up to 67 Meg disk. The OS
was System V Release 2 vintage. There was a built-in 1200 baud modem,
and a primitive windowing system with mouse.
I had a 3B1 as my first personal system and spent many happy hours writing
code and documentation on it.
There is an emulator for it that recently became pretty stable. The original
software floppy images are available as well. You can bring up a fairly
functional system without much difficulty.
The emulator is at https://github.com/philpem/freebee. You can install up
to two 175 Meg hard drives - a lot of space for the time.
The emulator's README.md there has links to lots of other interesting
3B1 bits, both installable software and Linux tools for exporting the
file system from disk image so it can be mounted under Linux and
importing it back. Included is an updated 'sysv' Linux kernel module
that can handle the byte-swapped file system.
I have made a pre-installed disk image available with a fair amount
of software, see https://www.skeeve.com/3b1/.
The emulator runs great under Linux; not so sure about MacOS or Windows. :-)
So, anyone wishing to journey back to 1987, have fun!
Arnold
next reply other threads:[~2021-01-29 10:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 10:49 Arnold Robbins [this message]
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
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=E1l5RL3-0002iv-Qv@tanda \
--to=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).