[dangreen]

Why

A player pointed out that the note before the build has the limit wrong. For an archive over 4 GiB it said that a single file over 4 GB does not fit on an exFAT card formatted with the default settings, but the 4 GiB limit on a file is FAT32's: exFAT was made to lift it. The limit itself was a byte off as well, so an archive of exactly 4 GiB went without the note.

What

• The note now says that the installer is too big for a FAT32 drive, as USB sticks and memory cards up to 32 GB usually are, and points to exFAT or the network: "The archive is 6.5 GB, so the installer will be a little bigger: too big for a drive formatted as FAT32, as USB sticks and memory cards up to 32 GB usually are. Use one formatted as exFAT, or copy the file over the network."
• It names no size beside the archive's. The site counts in decimal GB, and the limit, a byte short of 4 GiB, is about 4.29 GB: "over 4 GB" would read as a warning about an archive of 4.1 GB, which FAT32 holds.
• The limit is the largest file FAT32 holds, 4294967295 bytes, instead of 4294967296.
• SPEC 6.3 says the same.

Notes

• Tests cover both sides of the limit: the note appears for an archive of 4 GiB and not for one of 4 GB in decimal units. Moving the limit either way fails one of them.
• The check goes by the archive, and the installer is bigger by its header and meta, tens of KB plus the artwork. An archive that close under the limit gets no note though its installer will not fit; the comment on the constant says so.