testing for corruption

[Jeff Harrison]

--- Kenneth Brody <kenbrody at bestweb.net> wrote:

[snip]
> 
> There aren't too many things guaranteed within the
> key file (assuming that
> there is no "corruption", by whatever definition you
> want to use):
> 
> 1 - The first byte will always be 0, 1, or 2.
> 2 - The second byte will always be 0.
> 3 - Bytes 17 to 20 (assuming 1-relative) will always
> be 0.
> 
> Aside from that, you can't really guarantee much.
> 
> 4a - If the first byte is 0, then you could "sanity
> check" the two 32-bit
>       values representing the freechain pointers.
> 4b - If the first byte is 1, then you could "sanity
> check" the three 16-bit
>       values representing @CD/@UD/@BD.
> 
[snip]

Great.  Thanks, that will save me from having to look
that stuff up.  Checking for this alone will tell me
if the data aligns with the map for the key segment. 
As to which is right and what to do about it - again
that is out of my scope here.  

Jeff Harrison
jeffaharrison at yahoo.com

Author of JHImport and JHExport. The fastest and
easiest ways to import and export with filepro. 


      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs