The only way to identify this dupes before extraction is by reading the TOC of the psarc for all the files and compare wich position are pointing to.Īs an example the original size of target.psarc is 328mb. This method used at creation time basically works by making several entries of the TOC to point to the same file, this way a single file inside the psarc is indexed several times in the TOC and can be accessed from several different pathsfilenames. This duplication of pathsfilenames inside the.psarc in the practise means when doing a standard extraction 2833 files will be missing, overwrited, or they will give an error at extraction time, the correct way to mess with it is by doing several partiall extractions to different directories, and rebuild it by using a preconfigured.xml where the different paths for each file are specifyed, when rebuilding is also needed to use the -strip option several times to remove part of the paths from all the different working directories, this way the pathsfilenames will be duplicated inside the.psarc archive (but are different files located at different positions and with a different ID number assigned). This is not how the original file was created (but works), the correct way to rebuild it is by defining specific compression levels per file in a predefined.xml. In the creation options suggested above in the table the compression level is not defined and this means all them will use the default compression level 9 (so the.BIK files will have a ridiculous 1 or 2 of compression ratio because is the max they will admit). Is needed to do it this way semi automatized because is usual to find psarc with thousand of files inside. When the purpose of the rebuild is to reduce the size (by removing languages, etc.) the method consists in replacing them by dummies (0kb files), this dummies preserves the positions of all the files.
In step 3 it creates an egg.psarc containing the chicken.psarc made in step 2 (egg.psarc created in step 3 overwrites egg.psarc made in step 1). When using full paths is mandatory to use the -strip option with an explicit path or a regular expression (regex) to remove part of the PC path (e.g: if you strip C:psarctestssource filestest from C:psarctestssource filestestBMPfolder1Image1.bmp the resulting path of the file inside the archive will be BMPfolder1Image1.bmp ). Is posible to generate this kind of filelists automatically by using the output of the -list command and some regular expressions to replace characters.
0 kommentar(er)
