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
Hachoir (from Debian 3.1.0+dfsg-3) can parse the structure of a FAT image created by mkfs.msdos (showing first 0x200 bytes as Boot, then both FAT copies, and root directory), but on an image created by mtools (specifically mformat -i "test-mtools.img" ::.) it reports a MasterBootRecord partition table followed by only RawBytes, whereas those should be identified as a FAT.
Could this be the presence of a non-empty partition table causing 2 different dissectors to be used?
The text was updated successfully, but these errors were encountered:
I'm unlikely to find the time for this, as going this far proved not necessary to get the cause of the glitch I was after. I'll leave this as an exercise for another potential contributor ;)
Hachoir (from Debian 3.1.0+dfsg-3) can parse the structure of a FAT image created by
mkfs.msdos
(showing first 0x200 bytes asBoot
, then both FAT copies, and root directory), but on an image created by mtools (specificallymformat -i "test-mtools.img" ::.
) it reports aMasterBootRecord
partition table followed by onlyRawBytes
, whereas those should be identified as a FAT.Could this be the presence of a non-empty partition table causing 2 different dissectors to be used?
The text was updated successfully, but these errors were encountered: