06-04-2014, 05:39 AM
None of them are blank on my side.
Is it possible to Decipher file structure from mips?
|
06-04-2014, 05:39 AM
None of them are blank on my side.
06-04-2014, 05:41 AM
I'll try downloading them, and using foxit then. Might just be Firefox's built-in viewer screwing up.
Nevermind then. It was just FF not displaying it properly. Anyway why are you doing this? just for fun, or for a project of some sort? Also, would you mind if I posted this to reddit (r/emulation)? they might be interested in this.
06-04-2014, 08:37 AM
(06-04-2014, 02:56 AM)avok23 Wrote: Thank you very much sir. I dont know why i never thought of IO. You can enable extra logging in Debug menu (might need dev or debug build). Warning it would fill your disk quickly. Debug>logging (there is also an ee debugger). The PS2 got 2 CPU with 2 dedicated OS and 2 dedicated RAM. There is really 2 systems. First one is the EE which run the main game and manage graphics. Seconds one is the IOP which run all the slow things (PAD/SOUND/MEM access...). System uses Remote Procedure Call (RPC seach wikipedia) to communicate. RPC is often use in network system. RPC are based on an hardware dma. The kernel is inside the ROM but some parts can be updated with newer version (file IOPR*.img). You can also loads extra module to the kernel (*.irx file). The interesting module is IOMAN. I'm sorry I will remove the PDF link they are copyrighted material. (06-04-2014, 05:41 AM)Scootaloo Wrote: I'll try downloading them, and using foxit then. Might just be Firefox's built-in viewer screwing up. I dont mind you posting it on reddit. But i dont know what they would gain from it now that the links are gone (Which i dont mind either). I am very beginner to the whole emulation thing. I really only wanted away to decipher ps2 game file formats but i ended up taking a whole Berkeley course (newer) I have also wondered how this guys do what they do.
06-04-2014, 08:59 AM
By the way, what do you seach exactly? The .bin is probably a pack of texture.
(06-04-2014, 08:59 AM)gregory Wrote: By the way, what do you seach exactly? The .bin is probably a pack of texture. The FID.bin file. Code: struct FileEntry The problem is the files are un-named so i actually have to go through each one to decipher what the are. But in the slus file i can actually see the Initialization function and i had hoped it would lead me to what i wanted but there was no loading done in that function it seemed. What i really want are the story texts and possibly the models
06-04-2014, 09:04 PM
I miss somethings. When I mount the iso I get a massive .bin for a games. As far as understand you manage to split into severals files. Can you explain it to me (more than 2 structs)?
(06-04-2014, 09:04 PM)gregory Wrote: I miss somethings. When I mount the iso I get a massive .bin for a games. As far as understand you manage to split into severals files. Can you explain it to me (more than 2 structs)? What version of the game are you looking at and what is the name of the bin? The game i used was Kengo 3. Kengo 2 and 1 use a "JOINT" file format I dont understand. Code: //The main FID.Bin file has a header loop through files and save the data at their offset. But since all the files are unnamed I have to go through each file in an hex editor to figure out what is inside each (over 7000 files). Then writes code that identifies their headers if they have header or magic numbers etc. I have also gotten a debug version of pcsx2. I am guessing i do not have to use Interpreter mode in any of the settings. i enabled IOP logs: Bios, CDVD as well ass SIF (EE <-> IOP) I guess this is all i need
06-04-2014, 09:32 PM
Thanks for the explanation, initial wasn't clear for me.
I just took a random games. That interestings
From logging the IOP->BIOS this is all i get
Code: Possible old value used in COP2 code I can assume this is not what the devs use when debugging And the scroll bar doesnt work either |
« Next Oldest | Next Newest »
|