Larry, on Sat Jun 2, 2012 4:39 AM, said:
SA would not copy some EA stuff. Did you try the Bit Writer?
That would be correct for the later
EA protection with too many sectors per track. Michael is talking about the earlier one based on skew align.
Perhaps someone knows what the PDB files actually did?
There are different types of PDBs, with quite different behaviour.
Some PDBs just help the reading/analysis process, in some cases they don't do much more than make it faster. There is precisely one such PDB for the protection we are talking about here, the EA skew align. The PDB just avoids reading the skew align, which is slow and not that accurate. It "forces" the pre known skew align. Btw, this has the effect (don't know if by design, or not) to "fix" a bad skew algn at the source disk. In other words, it just writes with the correct skew align disregarding the one on the source.
Other PDBs are more complicated. And as you know, some, but not all, require a Happy drive to actually run the copy. In these cases, the PDB writes a small bootstrap loader to the destination copy. The bootstrap is a special code to program the Happy drive at runtime to "emulate" the protection. e.g., sectors with weak bits.