From: Al Kossow <aek@bitsavers.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] a possible source for 4.1BSD tapes
Date: Mon, 11 Mar 2019 14:47:55 -0700 [thread overview]
Message-ID: <29db723b-91f8-c7fa-591e-5ac383bffab0@bitsavers.org> (raw)
In-Reply-To: <ADFDF14544A65F35.9f917bb9-1555-42a4-a4b7-828cb9d3df0b@mail.outlook.com>
On 3/10/19 10:46 PM, Jason Stevens wrote:
> is there a kyrolux like device for tapes?
The problem is dropouts from either tape surface contamination or oxide loss, tape skew, and tape stretch.
I've been working off and on with Len Shustek on analog digitization and recovery of 7 and 9 track tape
https://github.com/LenShustek/readtape
to try to deal with tape that has signal degradation
He and I use Saleae Pro Logic 16 USB 16-channel USB setups connected to the read amps of a tape drive
I have a Linux box set up with 128gb of memory for data capture.
It is a time-consuming process, and I only resort to that for high-value problem children.
next prev parent reply other threads:[~2019-03-11 21:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 7:31 Mike Haertel
2019-03-09 23:24 ` Nigel Williams
2019-03-10 11:18 ` Lars Brinkhoff
2019-03-10 20:55 ` Warner Losh
2019-03-10 22:53 ` Mike Haertel
2019-03-11 0:25 ` Al Kossow
2019-03-11 1:15 ` Mike Haertel
2019-03-11 5:46 ` Jason Stevens
2019-03-11 17:28 ` Mike Haertel
2019-03-11 17:38 ` Larry McVoy
2019-03-11 18:33 ` Lars Brinkhoff
2019-03-11 18:41 ` Clem Cole
2019-03-12 6:21 ` Nigel Williams
2019-03-12 6:32 ` Jason Stevens
2019-03-12 12:44 ` arnold
2019-03-11 21:47 ` Al Kossow [this message]
2019-03-23 17:50 ` reed
2019-03-24 4:19 ` Lars Brinkhoff
2019-03-10 8:20 ` arnold
2019-03-10 15:50 ` Mike Haertel
2019-03-10 19:54 ` arnold
2019-03-10 20:33 ` Warner Losh
2019-03-25 17:19 Richard Tobin
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=29db723b-91f8-c7fa-591e-5ac383bffab0@bitsavers.org \
--to=aek@bitsavers.org \
--cc=tuhs@minnie.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).