Gents,
I joined the forum out of desperation, baffled by a problem I have encountered after rebuilding a specialized audio PC. It has Intel DG41CN series board with XP Pro OS and SATA drives set to Legacy mode in the BIOS. The two drives are physically identical WD 160GB hard drives formatted with FAT32. I also use Ghost 2003 as image backup software. The system appears working fine, BUT I have just noticed a problem with the partitions when viewing with Super FDisk. And verified with WD Data Lifeguard that indeed something looks odd....
The 2nd data drive is reporting normal as I would expect with partition type "Win4.1" in the OEM label field and showing CHS as 255/63 (which from what I understand is reflective of default LBA mode). HOWEVER, the boot drive is NOT showing this. Instead it is reflecting OEM label field of "DOS5.0" and CHS as 4/17. This is being flagged in Super FDisk as a potential problem (the 4/17 geometry). I can't say for sure what I used initially to set up the drive - I was using a combination of things like WD Data Lifeguard and other disk tools. But somehow I apparently caused the boot disk to end up configured differently internally. I can see things in Ghost Ok, but am afraid of what may happen if I ever need to restore the partition....will it even work? What other problems might i run into in the future? So...I'd rather get this ironed around now, if it is indeed a problem.
Can any experts explain what is going on here and how I might iron it out so the boot drive is reflecting the proper partition info like the 2nd data drive? I'm not sure if this is an MBR partition entry problem or rather a FAT32 BPB issue or just what exactly is going on.
Help.....
Sonic
I joined the forum out of desperation, baffled by a problem I have encountered after rebuilding a specialized audio PC. It has Intel DG41CN series board with XP Pro OS and SATA drives set to Legacy mode in the BIOS. The two drives are physically identical WD 160GB hard drives formatted with FAT32. I also use Ghost 2003 as image backup software. The system appears working fine, BUT I have just noticed a problem with the partitions when viewing with Super FDisk. And verified with WD Data Lifeguard that indeed something looks odd....
The 2nd data drive is reporting normal as I would expect with partition type "Win4.1" in the OEM label field and showing CHS as 255/63 (which from what I understand is reflective of default LBA mode). HOWEVER, the boot drive is NOT showing this. Instead it is reflecting OEM label field of "DOS5.0" and CHS as 4/17. This is being flagged in Super FDisk as a potential problem (the 4/17 geometry). I can't say for sure what I used initially to set up the drive - I was using a combination of things like WD Data Lifeguard and other disk tools. But somehow I apparently caused the boot disk to end up configured differently internally. I can see things in Ghost Ok, but am afraid of what may happen if I ever need to restore the partition....will it even work? What other problems might i run into in the future? So...I'd rather get this ironed around now, if it is indeed a problem.
Can any experts explain what is going on here and how I might iron it out so the boot drive is reflecting the proper partition info like the 2nd data drive? I'm not sure if this is an MBR partition entry problem or rather a FAT32 BPB issue or just what exactly is going on.
Help.....
Sonic
Facebook
Twitter