https://mega.nz/#!wYNWkZwK!4Ir_F4fijEOyr9g9A_3opDJHfWN-swNeGxylGBrInSI
I tried to extract this with the cpk.bms script, but it didn't even extract the files properly. Instead, it stopped there and produced this error:
Okami Zekkeiban (PS3) .cpk
-
- Site Admin
- Posts: 12984
- Joined: Wed Jul 30, 2014 9:32 pm
Re: Okami Zekkeiban (PS3) .cpk
The sample is too small to reach that offset.
I guess it's another case of file reported as "compressed" but not compressed, this is something happened once with another game (Naruto I guess).
If you can provide (after testing it) a bigger first sample I will confirm it.
I guess it's another case of file reported as "compressed" but not compressed, this is something happened once with another game (Naruto I guess).
If you can provide (after testing it) a bigger first sample I will confirm it.
-
- Posts: 1125
- Joined: Tue Feb 02, 2016 2:35 am
Re: Okami Zekkeiban (PS3) .cpk
aluigi wrote:The sample is too small to reach that offset.
I guess it's another case of file reported as "compressed" but not compressed, this is something happened once with another game (Naruto I guess).
If you can provide (after testing it) a bigger first sample I will confirm it.
Well, I'll think of it. I usually upload a full archive file after realizing that the sample file isn't enough so... yeah.
EDIT: This is it, the samples for the archive file:
https://mega.nz/#F!kJ0y0Y5Y!_aLV5wCp9aMN_8PCuV7X7g
It'll be updated frequently as I get to upload more of these, as I saved the file into 4 parts using 010 Editor. Take your time in looking into these files while you can.
-
- Site Admin
- Posts: 12984
- Joined: Wed Jul 30, 2014 9:32 pm
Re: Okami Zekkeiban (PS3) .cpk
The script is correct but the archive doesn't correspond to the table. This is the second time I see this.
Take a look here:
0x006f7000 is correct and you can see the "AFS2" magic
Now 0x006f7000 + 440559742 is 0x1ab1d87e which matches the next aligned offset of 0x1ab1e000.
But at offset 0x1ab20000 there is no AFS2 magic, that magic exists only at offset 0x006f7000 and nowhere else in 1.2Gb of sample provided.
What I can imagine is that there is some encryption with some specific files but I don't know.
Take a look here:
Code: Select all
006f2800 17872 bgm/bgm00.afd
006f7000 440559742 bgm/bgm00.afs2
1ab1e000 6192 bgm/gl00_Reset.afd
1ab20000 379688082 bgm/gl00_Reset.afs2
31539800 121888 dr/dr00.dat
0x006f7000 is correct and you can see the "AFS2" magic
Now 0x006f7000 + 440559742 is 0x1ab1d87e which matches the next aligned offset of 0x1ab1e000.
But at offset 0x1ab20000 there is no AFS2 magic, that magic exists only at offset 0x006f7000 and nowhere else in 1.2Gb of sample provided.
What I can imagine is that there is some encryption with some specific files but I don't know.