I've been reading up recently about the 256GB partition limitation in FATX, if the default of 16KB clusters is used. XBPartitioner will allow for custom sized partitions (not just F gets all or F to 137 G gets rest) and if you create a partition larger than 256GB it will automatically format it using 32KB clusters. Not sure how the math works here, if this increases the max partition size to 512GB or something larger. So XBPartitioner can be used to get around this limitation and take advantage of the 500GB+ drives that are now available. Yahoo.
But... the BIOS needs to support the partitioning. On the X3 BIOS there is an option "Use Saved Partition Table" that instead of storing how the partitions should be set up in the BIOS (stock, f gets all, f to 137 g gets rest) it will read the partition table from the disk and accept what is set up there. While I haven't tried it this should mean that you can do wacky things like set up a 50GB F partition (apps maybe?) and then let G pick up everything else up to the end of the disk (game storage?).
Now, the X2CL README1ST.TXT file states-
-Whoopin'
But... the BIOS needs to support the partitioning. On the X3 BIOS there is an option "Use Saved Partition Table" that instead of storing how the partitions should be set up in the BIOS (stock, f gets all, f to 137 g gets rest) it will read the partition table from the disk and accept what is set up there. While I haven't tried it this should mean that you can do wacky things like set up a 50GB F partition (apps maybe?) and then let G pick up everything else up to the end of the disk (game storage?).
Now, the X2CL README1ST.TXT file states-
In X2CL there is no "Use Saved Partition Table" option, only the 4 LBA48 settings. Does it matter what LBA48 setting is used in order for the BIOS to auto detect the partitions? Has anyone tried this yet? Given that no further info is provided in the readme my assumption would be that the BIOS checks the disk for a partition table first, if not found it resorts back to the table setting stored in offset 0x1b04. Can anyone confirm this?
-Whoopin'