PDA

View Full Version : xenosaga ripped from scratch


groovster
19-03-2003, 18:19
what would be the best way to do this? my idea would be to make the primodvd image, convert the .gi to a mode1/2048 iso image, access the iso, find the movie files, do the math, recompress, remake the iso.

is this logic screwed from the getgo?

BG
20-03-2003, 08:05
I'm working on basically the same principle as you described, except I'm trying it with Gran Turismo Concept 2002 which is dvd-9 also.

I'm not sure if it will work or not, BUT I'm working on it.....

Try it and see......

I already have the .iso (created from my original) and am currently trying to figure out EXACTLY what step to take next....

Will post back on my progress....

groovster
20-03-2003, 17:13
ok, xenosaga has xenosaga.01 through xenosaga.12, many .ovc and .irx files. the .01 to .12 files are mostly very large. i think these must be munge files (game data compressed into an archive with an allocation table). from what i find on ps2 sources, there are utilities that sniff out the ps2 media files, utilities which will then extract these files, and utilities which can reassemble and create a new allocation table....then, hopefully, whall-ah!, you get a new, smaller munge file...and the game won't know the difference. i'm exploring at the moment...and will, too, post results

TylerDurden
21-03-2003, 16:35
Originally posted by BG
I already have the .iso (created from my original) and am currently trying to figure out EXACTLY what step to take next....


You need to know how to code (preferrably in C++) then you make an "extractor/rebuilder". Its not an easy project because of such a large file.

If you do succede in that step then you find out what files can either be downsampled or cut completely out.


Tyler!

groovster
22-03-2003, 11:19
upon using isobuster to explore the global image made from xenosaga....
-there seems to be two mirrored filesystems, one udf and one iso9660, each filesystem having the same amount of bytes, and each almost exactly one half of the total image size. could this maybe be a loophole to make a backup?