C
chengbanger
I'm looking for information about exactly how scanpst works internally
- which is probably the same question as, "what do we know, how much
information do we know about the proprietary PST file format?"
I'm hoping to stumble up that one posting that will tell me what is
publically known about it. Is it a well kept secret that the makers of
3rd party PST repair tools only know about?
For example, what does this mean:
Invalid BBT page (bid=81142A4, ib=130393088)
Sig mismatch (read 914C, computed E970)
BID mismatch (read 8113A98, expected 81142A4)
Sure, I can guess a general idea of what's going on. But it might be
worthwhile to know exactly what is inside a "BBT page" - is it a
one-to-one mapping of BBT page to email message (or outlook item -
calendar entry, contact entry, etc) .. or a one-to-many relationship?
Just to reiterate, the issue is not to get a particular instance of PST
to work and to move on. I'm wondering about the core problem - can it
be fixed? Does the log file reveal anything of value?
- which is probably the same question as, "what do we know, how much
information do we know about the proprietary PST file format?"
I'm hoping to stumble up that one posting that will tell me what is
publically known about it. Is it a well kept secret that the makers of
3rd party PST repair tools only know about?
For example, what does this mean:
Invalid BBT page (bid=81142A4, ib=130393088)
Sig mismatch (read 914C, computed E970)
BID mismatch (read 8113A98, expected 81142A4)
Sure, I can guess a general idea of what's going on. But it might be
worthwhile to know exactly what is inside a "BBT page" - is it a
one-to-one mapping of BBT page to email message (or outlook item -
calendar entry, contact entry, etc) .. or a one-to-many relationship?
Just to reiterate, the issue is not to get a particular instance of PST
to work and to move on. I'm wondering about the core problem - can it
be fixed? Does the log file reveal anything of value?