You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a disk where FAT1 and FAT2 are missing. It's a very old drive, so heads 1 and 2 are no longer over the tracks for the first several tracks (I'm using an advanced imaging tool that tells me things like this about the drive). So, the drive cannot read those areas and so my image has 0's in them. It would be nice to be able to start somewhere and initialize a FAT whose chains are all 1 long, based on different parameters I give on the command line. This may also mean the first N sectors of the root directory are zero'd too, I don't know yet. The first entry is weird, so I strongly suspect that's the case:
It's a 10MB file from a non PC-DOS compatible computer (it ran MS-DOS 2.11), so there's also some weird stuff at front for the non-standard partitioning scheme that it uses. It's clearly more damaged than you're used to dealing with in your fatcat program...
The text was updated successfully, but these errors were encountered:
Hi
I guess you could use fatcat with orphan (lost+found) feature
One issue is that you at least need fat headers there, so maybe we can consider rebuilding them
Also, if FAT are missing, it means that files will be read contiguously, which might not be be perfect
I have a disk where FAT1 and FAT2 are missing. It's a very old drive, so heads 1 and 2 are no longer over the tracks for the first several tracks (I'm using an advanced imaging tool that tells me things like this about the drive). So, the drive cannot read those areas and so my image has 0's in them. It would be nice to be able to start somewhere and initialize a FAT whose chains are all 1 long, based on different parameters I give on the command line. This may also mean the first N sectors of the root directory are zero'd too, I don't know yet. The first entry is weird, so I strongly suspect that's the case:
It's a 10MB file from a non PC-DOS compatible computer (it ran MS-DOS 2.11), so there's also some weird stuff at front for the non-standard partitioning scheme that it uses. It's clearly more damaged than you're used to dealing with in your fatcat program...
The text was updated successfully, but these errors were encountered: