G
gus
Guest
> On Mar 3, 2016, at 10:06 AM, eswarm wrote: > > Yes I share the same experience, but thought of checking if someone has tried breaking algorithm behind mismatch counters and keys 
doing that will not help. the counters are there for a reason. when a block's counters don't match the counter in the ai note, nearly always the data in the block will not match either. ignoring the mismatched counters when a note that says "replace the 23 bytes at block offset 581 with these other 48 bytes in area 12, block 651" is applied will result in corruption and maybe a crash if the contents of the data block is not in the expected state. other notes could cause knots in linked lists.
Continue reading...
doing that will not help. the counters are there for a reason. when a block's counters don't match the counter in the ai note, nearly always the data in the block will not match either. ignoring the mismatched counters when a note that says "replace the 23 bytes at block offset 581 with these other 48 bytes in area 12, block 651" is applied will result in corruption and maybe a crash if the contents of the data block is not in the expected state. other notes could cause knots in linked lists.Continue reading...