Comment 11 for bug 589369

Thanks Idefix, you're absolutely right.

I tried the WinXP test you suggested and it was successful, i.e. Windows recognises Marantz formatting even with the incorrect FSINFO, so Windows is more tolerant than linux in that regard.

Then I hacked the FSINFO back to the standard value using hexeditor. Linux automount started working and the Marantz recorder was not adversely affected, still being able to read and write the card with no problems.

It's tempting to say "WinXP works, linux doesn't, therefore linux has a bug", but why has Marantz introduced this new FSINFO identifier? It's not just Marantz either. Apparently the Edirol R-09HR audio recorder does the same thing. See here:-
http://taperssection.com/index.php?topic=109564.300
In that case the user fixed the broken identifier with `fsck.vfat -a`.

Perhaps there's a bug in the SDK those manufacturers are using, unless
<start evil conspiracy theory music>
it's a plot to thwart linux!
<stop music>

It would also be interesting to know why the Marantz doesn't like the way mkdosfs formats the partition, but I think I'll sign off now, before the music starts again. :)

Cheers.