2 May
2002
2 May
'02
8:56 a.m.
On Thursday 02 May 2002 14:51, you wrote:
You would rather work the drive to death ?
When I break it, I fix it. I'm good at things like that.
At the
portion of the work where you just want to get the stuff
spooled to a file, you dont care about "block size" yet, you
just need to get it pulled off.
Unix will treat any device as a stream of bytes
And therein lies the problem. You know, any really old tape you are attempting to
recover
you really do not want to be running it thru the tape deck
very much
For tapes that far gone, a digital read won't work. You have
to build your own drive and sample the analog data coming off
the heads using A/D and not using the digital-based discriminator.
For tapes not that far gone (like the ones of mine that spent
days under water and then months with stachybactris growing on
them), I have a wet-read technique that prevents most shoe-
shining.
disks are huge these days, and the content is best
messaged
on a new disk rather than an old tape.
Agreed, *that's why the TAP format exists*, as well as Stan
Seiler's tapedisk/disktape system.
Do you see what im getting at here ? hello ?
No, I don't, because your entire example was disk-centric, Tell you
what... how about an empirical test?
Well since we already know the behavior, we already know
the results dont we ? Go buy a
9-track drive and hang it on your *nix box.
Let me send you a 9-track tape. You read it any way
you want. You send me the tape back.
Then you go get a second tape, and put the data
back on
any way you want. Then send it to me, and I'll tell you
if your technique works or not.
this is very predicatble if you know the raw behavior
of the devices isnt it
the whole idea was to point out some of this raw behavior