From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] 780 System III tape images
Date: Thu, 27 Sep 2007 10:53:15 +1000 [thread overview]
Message-ID: <20070927005315.GA2805@minnie.tuhs.org> (raw)
In-Reply-To: <46FAEE5D.70704@datanet.ab.ca>
> Al Kossow wrote:
> >I've placed two sets of 800bpi 780 System III tape images
> >temporarily under http://bitsavers.org/sysIII
On Wed, Sep 26, 2007 at 05:42:21PM -0600, Andrew Warkentin wrote:
> Why do I get read errors on the second file on the first tapes of both
> sets under SIMH? I didn't think it was even possible for tape I/O errors
> to occur under SIMH unless the image is corrupted.
Hmm, I seem to have lost the tools I used to use to manipulate tap files.
Can someone e-mail in pointers to useful tap tools?
Thanks,
Warren
next prev parent reply other threads:[~2007-09-27 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3368126406-2252@localhost>
2007-09-26 12:22 ` Andrew Warkentin
2007-09-26 23:42 ` Andrew Warkentin
2007-09-26 23:55 ` Al Kossow
2007-09-27 0:53 ` Warren Toomey [this message]
2007-09-25 2:40 Al Kossow
2007-09-27 2:24 ` Warren Toomey
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=20070927005315.GA2805@minnie.tuhs.org \
--to=wkt@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).