From: Kevin Bowling <kevin.bowling@kev009.com>
To: "Seth J. Morabito" <web@loomcom.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Wanted: AT&T System V Release 3.2.{1,2,3} Source Code
Date: Sat, 19 Jan 2019 07:09:56 -0700 [thread overview]
Message-ID: <CAK7dMtDu16dRGTp_8Q79t3gA9=ATb-NHzREZHY70pwaMsT93AQ@mail.gmail.com> (raw)
In-Reply-To: <87lg3iey47.fsf@loomcom.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
I believe there is a sysvr4 source dump floating around with the 3b2 base
On Fri, Jan 18, 2019 at 9:21 AM Seth J. Morabito <web@loomcom.com> wrote:
>
> [Cross-posted from the 3B2 mailing list]
>
> Hi folks,
>
> I'm in search of source code for AT&T's System V Release 3.2.1, 3.2.2,
> and/or 3.2.3 for the 3B2. Does this exist? Has anyone ever seen it?
>
> Note that I'm not looking for the System V Release 3.2 Source Code
> Provision for the 3B2 /310 and /400 -- I already have that. It was
> absolutely invaluable when I was writing my 3B2/400 emulator.
>
> The reason I'm so keen on getting access is that I have ROM images from
> a 3B2/1000, and I'd like to add support for it to my 3B2 emulator. The
> system board memory map seems a bit different than the /300, /310, and
> /400. These max out at SVR 3.2.
>
> I can't imagine trying to add 3B2/1000 support without the 3.2.x source
> code.
>
> I imagine there's some tape image somewhere that's a delta of files that
> take you from 3.2 to 3.2.1, 3.2.2 or 3.2.3?
>
> -Seth
> --
> Seth Morabito
> Poulsbo, WA, USA
> web@loomcom.com
>
[-- Attachment #2: Type: text/html, Size: 1539 bytes --]
next prev parent reply other threads:[~2019-01-19 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 16:20 Seth J. Morabito
2019-01-19 14:09 ` Kevin Bowling [this message]
2019-01-20 0:08 ` Seth J. Morabito
2019-01-20 9:01 ` Kevin Bowling
2019-01-20 14:35 ` arnold
2019-02-01 17:10 ` Al Kossow
2019-02-03 20:18 ` Al Kossow
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='CAK7dMtDu16dRGTp_8Q79t3gA9=ATb-NHzREZHY70pwaMsT93AQ@mail.gmail.com' \
--to=kevin.bowling@kev009.com \
--cc=tuhs@tuhs.org \
--cc=web@loomcom.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).