The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Running v7 in Open-SIMH - update for 2024
Date: Thu, 23 May 2024 16:48:53 -0400	[thread overview]
Message-ID: <CAC20D2PLXvfg79VsoX9yAzN_y_R53uvu-Xb30jWTkvPHHELxEw@mail.gmail.com> (raw)
In-Reply-To: <ac2c9284-f87c-4fda-91e4-e149dc7046c4@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2475 bytes --]

FYI - POR is to push some new tools I have been creating into OpenSIMH
shortly.

In fairness to Will, this is in the class of a "2-minute minor," not a
"4-minute major."  I back into this issue as I was working on Oscar's new
PiDP-10 and moving a very old (v6 syntax) UNIXC program that manipulates
PDP-10 backup and TOPS-20 Dumper images.  PDP-10s do things in 36 bits,
which does not map cleanly to the 8 data bits of a 9-track tape (you don't
want to know what the 10 does unless you have to deal with it).  So, I
wrote some tools to better examine and flexibly manipulate TAP files [the
debug code for tapes in SIMH is a bit of a mess].  Anyway, as I was testing
something, I thought I had made an error in my new tap_decode(1) tool when
I was looking at the v7.tap.gz file that Warren has in the TUHS archives
(that Will supplied/created with his mktape scripts).   When I looked more
carefully, it was missing a record. It turns out SIMH will silently
"attach" a TAP image without a proper 9-track logical end-of-tape (it
should give a warning).  It also turns out Will's directions never looked
for the actual 9-track EOT records - so nobody ever saw this.  I mentioned
it to him quietly - cudo's for coming clean.

FWIW: I always recommend Will's documents for V6 and V7 (in fact, we point
to them in the OpenSIMH archives at my suggestion).  The truth is, I wish
we had had access to a few more that are as good as Will's for some of the
other OSses.

Clem
ᐧ

On Thu, May 23, 2024 at 2:58 PM Will Senn <will.senn@gmail.com> wrote:

> All,
>
> I can't believe it's been 9 years since I wrote up my original notes on
> getting Research Unix v7 running in SIMH. Crazy how time flies. Well, this
> past week Clem found a bug in my scripts that create tape images. It seem
> like they were missing a tape mark at the end. Not a showstopper by any
> means, but we like to keep a clean house. So, I applied his fixes and
> updated the scripts along with the resultant tape image and Warren has
> updated them in the archive:
>
> https://www.tuhs.org/Archive/Distributions/Research/Keith_Bostic_v7/
>
> I've also updated the note to address the fixes, to use the latest version
> of Open-SIMH on Linux Mint 21.3 "Virginia" (my host of choice these days),
> and to bring the transcripts up to date:
>
>
> https://decuser.github.io/unix/research-unix/v7/2024/05/23/research-unix-v7-3.2.html
>
> Later,
>
> Will
>
>
>

[-- Attachment #2: Type: text/html, Size: 4592 bytes --]

      parent reply	other threads:[~2024-05-23 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 18:58 [TUHS] " Will Senn
2024-05-23 19:01 ` [TUHS] " G. Branden Robinson
2024-05-23 20:00   ` Will Senn
2024-05-23 20:48 ` Clem Cole [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=CAC20D2PLXvfg79VsoX9yAzN_y_R53uvu-Xb30jWTkvPHHELxEw@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.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).