libnx/nx
Selver 34f6c4dc4e
Additional comment for fsFsSetArchiveBit()
Describe why HOS might have done this.  While the below is conjecture, the effect matches the comment added to the file.

FAT32 has a (4GiB-1) byte limit per file, but they had to support that media.
They likely wanted to avoid forcing game makers to partition game files.
If the above is true, then this hack could make sense....

The directory, rather than being a "real" directory, is storing the file in multiple parts.

Example (ignoring actual hash-based file names that HOS uses for simplicity):
* The game ships with a file named "FOO.DAT" that is 6GB in size.
* HOS does not attempt to create a 6GB file on FAT32 media (which would fail)
* HOS creates a directory named "FOO.DAT" instead.
* Inside that directory, HOS stores the first 2GB as "FileChunk01"
* Inside that directory, HOS stores the second 2GB portion as "FileChunk02"
* Inside that directory, HOS stores the final 2GB of the data as "FileChunk03"

Unfortunately, by using the archive bit, it can cause problems, especially when an OS (ahem... MacOS) or other utility changes the archive bit settings on directories....
2018-11-30 13:01:15 -08:00
..
data switch to 16x16 console font 2018-02-25 15:49:25 +01:00
external/bsd/include netinet: fix missing declarations (#187) 2018-10-19 17:15:24 +02:00
include Additional comment for fsFsSetArchiveBit() 2018-11-30 13:01:15 -08:00
source Moved usb code specific to usbds into seperate .c/.h. 2018-11-28 17:34:53 -05:00
.gitignore ignore generated files 2017-09-18 19:40:15 +01:00
default_icon.jpg Changed the default icon (again) 2018-02-25 15:49:50 +01:00
Doxyfile Start doxygen bringup, with some miscellaneous cleanup 2018-02-10 22:40:11 +01:00
Makefile Release v1.6.0 2018-11-28 02:09:20 +01:00
switch_rules Add rules for building .npdm, .nsp and .kip, see details: 2018-05-09 17:55:30 +02:00
switch.ld Add MOD0 header to crt0 2018-08-31 13:05:21 +02:00
switch.specs Embed GNU build ID in compiled binaries for use by creport 2018-06-26 19:19:41 +02:00