The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dennis Boone <drb@msu.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] OT: Need help getting old 9 track tapes read
Date: Sun, 28 Apr 2019 07:12:01 -0400	[thread overview]
Message-ID: <20190428111202.17AEA1C2FC7@yagi.h-net.msu.edu> (raw)
In-Reply-To: (Your message of Sun, 28 Apr 2019 02:45:07 -0600.) <201904280845.x3S8j7GQ008565@freefriends.org>

 > Scott Lee, who worked with me on the Georgia Tech Software Tools
 > Subystem for Pr1me Computers, recently unearthed two tapes with some
 > version of that software.  These may be the only copies extant
 > anywhere.

!!!

 > | I was cleaning out the basement of my house. They're 35 years old,
 > | but they've never been left in the heat or anything. I opened one
 > | of them up and checked the tape and it's not self-sticky or
 > | anything. The odds that they're readable is slim, because old
 > | 9-track bits tended to bleed through each other. You were supposed
 > | to spin through the tape every couple of years to make them last
 > | longer. That's obviously not happened.

I've read stuff that old that was stored in worse conditions.  9-track
is surprisingly robust.  Humidity can be worse on the 80s-era media,
aggravating the "sticky shed" problem.  There are several methods for
dealing with that, including low temp baking, chemical treatments,
stripping coating off the back side of the tape, etc.  I use a low-tech
baking solution at home.  Most methods give you a limited number of
reads over a fairly short time period.

 > Dennis Boone & Bill Gunshannon (are you on this list?) - I may ask
 > you to contribute $$ towards this once I know more.

Let me know.

De

  parent reply	other threads:[~2019-04-28 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28  8:45 arnold
2019-04-28  9:07 ` Bakul Shah
2019-04-28 11:12 ` Dennis Boone [this message]
2019-06-24 20:56 ` Al Kossow
2019-04-28 23:44 Noel Chiappa

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=20190428111202.17AEA1C2FC7@yagi.h-net.msu.edu \
    --to=drb@msu.edu \
    --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).