https://qa.mandrakesoft.com/show_bug.cgi?id=461
------- Additional Comments From [EMAIL PROTECTED] 2002-11-27 05:45 ------- It has never been made clear to me that the "overlap" is real rather than an inconsistency between the two separate representations of partition size for each partition table entry. Apparently MCC is one of many tools that refuse to act upon a partition if those two values for any table entry are inconsistent. OTOH, the operating systems apparently don't care as long as the first of the two entries results in finding a boot sector in the expected location. If the overlap was real, operating systems wouldn't find a good EPBR on the overlapped partition and partitions beyond the overlapping partition would all be inaccessible. It could also be that the overlap is real, but the overlapping sector is virtually always reserved and/or otherwise unallocated and left intact for the EPBR. MCC could probably be fixed to accept them the same as the OS, but that fix I'd guess to be more work that creating or porting a tool designed specifically to fix overlap "problems" in partition table entries. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
