On 07/06/2020 11:33, Tauno Voipio wrote:
> On 6.6.20 22:24, druck wrote:
>> On 06/06/2020 13:16, Tauno Voipio wrote:
>>> Another oddity: The /boot partition is in FAT32,
>>> but the Windowses do not like FAT32 smaller than
>>> 500 Mib, so the partition has to be deleted and
>>> re-created in the desired size, of course saving
>>> and restoring the contents separately.
>>
>> Who cares what Windows thinks! :)
>
> FATxx are Windows specifications. The tools available on Linux
> and OS X do respect the Windows desires, so there's a problem.
> Another thing that does not conform to Windows usage is the use
> of lower case letters in the partition label. If the Windows
> partition type must be used, it should be used correctly.

The trouble is Microsoft keeps changing the rules after everyone else
followed the specs.

I remember having problems with FAT16 disks, where Windows wouldn't see
the files a non Windows machine wrote, and the non Windows machine
wouldn't see the files that Windows had written. Both sets of files were
there though.

The reason being is that FAT16 was originally specified with a fixed
size root directory following on from the FAT, but at some point
Microsoft started using FAT32's variable sized root directory on FAT16.
Therefor non Windows machines used the old fixed sized directory as the
format specified, but Windows used a different root directory - which is
right and which is wrong?

So at some point Windows will break FAT32 so Pi's can't boot, so you are
safer using a Linux tool which will produce partitions which follow the
spec at the time the Pi was created, and ignoring any spurious warnings
from Windows.

---druck

--- SoupGate-Win32 v1.05