Re: [SOLVED]: Explanation Follows
Posted by EmptyEnvelope2 on .
9. ISOs built with makeps3iso are in full ISO-9660 format, and thus do not contain the UDF file system section that PS3 games have.
10. Conclusion: The real name of the tutorialDiff file (at least for the PS3) does not contain a period at the end. So, JB folders run from a FAT-32 device shouldn't have a problem when running the game. However, if you build a Minecraft ISO with makeps3iso with the tutorialDiff file without a dot, the ISO-9660 file system name for tutorialDiff will not contain a period as it does on a real dump, but as I said before it will probably run properly on a PS3. However, this ISO made with makeps3iso will probably fail ird verification in ManaGunZ because the program expects a period at the end of the file name of tutorialDiff. So, for Minecraft ISOs made with makeps3iso, if you want IRD verification to not fail in ManaGunZ, you need to manually add a period to the end of the tutorialDiff file name.
10. Conclusion: The real name of the tutorialDiff file (at least for the PS3) does not contain a period at the end. So, JB folders run from a FAT-32 device shouldn't have a problem when running the game. However, if you build a Minecraft ISO with makeps3iso with the tutorialDiff file without a dot, the ISO-9660 file system name for tutorialDiff will not contain a period as it does on a real dump, but as I said before it will probably run properly on a PS3. However, this ISO made with makeps3iso will probably fail ird verification in ManaGunZ because the program expects a period at the end of the file name of tutorialDiff. So, for Minecraft ISOs made with makeps3iso, if you want IRD verification to not fail in ManaGunZ, you need to manually add a period to the end of the tutorialDiff file name.
1. PS3 games are in a so called "UDF Bridge" format, which means that the header contains both the ISO-9660 and UDF file systems.
2. Specifications for the ISO-9660 format require files names without an extension to still have a period at the end (the format of filenames in ISO 9960 is "[file_name].[ext];"). However, the standard is not always followed, and sometimes files with no extension are listed without a period. It seems all PS3 games followed the same standard since they were built with the same tool, and do include a period for file names with no extension.
3. The PS3 defaults to the UDF file system, which does not enforce the use of a period for files without an extension.
4. Typically, extraction and dumping tools default to the ISO-9660 format, and read the filenames from there. Thus, the name of files with no extension are typically written with a period at the end. However, due to Windows not allowing files to end with a period, and due to FAT-32 not allowing file names ending with a dot, the period is still removed automatically (by the tool itself, or by the OS).
5. A tool like makeps3iso does not enforce the use of a period for file names with no extension, so a file ending with a period will be written differently than a file with the same name with with no period at the end.
6. It seems that the PS3 by default interprets file names ending with a period in the ISO-9660 file system section as files with no period at the end. One can see this when accessing (with a hex editor) the header of Minecraft for PS3: The tutorialDiff file ends with a period in the ISO-9660 section (per standard), and does not have one in the UDF file system section.
7. It also seems that the PS3 does not care if a file with no extension in the ISO-9660 section of the header end with no period (probably done to support all Blu-Ray films properly). This means that ISOs created with makeps3iso could have this file with no extension written with or without a period, and it wouldn't matter.
8. The eboot.bin of games call file names with no extension with no period at the end (probably only matters for FAT-32 JB Folders).
2. Specifications for the ISO-9660 format require files names without an extension to still have a period at the end (the format of filenames in ISO 9960 is "[file_name].[ext];"). However, the standard is not always followed, and sometimes files with no extension are listed without a period. It seems all PS3 games followed the same standard since they were built with the same tool, and do include a period for file names with no extension.
3. The PS3 defaults to the UDF file system, which does not enforce the use of a period for files without an extension.
4. Typically, extraction and dumping tools default to the ISO-9660 format, and read the filenames from there. Thus, the name of files with no extension are typically written with a period at the end. However, due to Windows not allowing files to end with a period, and due to FAT-32 not allowing file names ending with a dot, the period is still removed automatically (by the tool itself, or by the OS).
5. A tool like makeps3iso does not enforce the use of a period for file names with no extension, so a file ending with a period will be written differently than a file with the same name with with no period at the end.
6. It seems that the PS3 by default interprets file names ending with a period in the ISO-9660 file system section as files with no period at the end. One can see this when accessing (with a hex editor) the header of Minecraft for PS3: The tutorialDiff file ends with a period in the ISO-9660 section (per standard), and does not have one in the UDF file system section.
7. It also seems that the PS3 does not care if a file with no extension in the ISO-9660 section of the header end with no period (probably done to support all Blu-Ray films properly). This means that ISOs created with makeps3iso could have this file with no extension written with or without a period, and it wouldn't matter.
8. The eboot.bin of games call file names with no extension with no period at the end (probably only matters for FAT-32 JB Folders).