If you acquire the data by manifold oversampling, you can infer the speed
and deviations in it from the acquired data. Fortunately, this can all be
handled in software after the goodies are in captivity. You do have to have
some baseline statistics, though, such as FD size.
Dick
----- Original Message -----
From: Sellam Ismail <foo(a)siconic.com>
To: <classiccmp(a)classiccmp.org>
Sent: Wednesday, May 31, 2000 2:34 PM
Subject: Re: Defining Disk Image Dump Standard
I just considered another bit of data that might be useful to store in the
Archive Header.
If one were to have to read the raw bytes off of a track due to some
non-standard format, it would be helpful to know at what rate the disk
drive that read the disk was spinning so that if and when that archive was
used to re-create the original disk, the writing drive could be adjusted
to match the speed at which it was read. This is pretty imperative.
A quick test can be done before the disk is read to determine the RPM. Of
course, having an optimally tuned drive would be recommended if one is to
be serious about creating software archives for posterity.
Sellam International Man of Intrigue and
Danger
--------------------------------------------------------------------------
-----
Looking for a six in a pile of nines...
Coming soon: VCF 4.0!
VCF East: Planning in Progress
See
http://www.vintage.org for details!