First of all, make sure that you have the latest version of the
package : it now contains more user friendly tools from Jackass
that you may prefer to mines.
> 1. An hex search in xiii_cd2.img and in the 4 files tells
> us that the files we are interested in…
> is there an article where we can find how to do that, or can
> someone explain it to us. Or can we (always) use the 2 files
> spath uses.
You can’t be sure and have to check it yourself. For instance to
check sector 281203 with Ultraedit, load the img, then Ctrl+F and
search for 00 FF FF FF FF FF FF FF FF FF FF 00 62 31 28. Note down
the next bytes, then do the same for the two bin files. The bin
file to select is the one which has different bytes from the img.
Note also that the sector numbers I mentioned are to use with the
european version of XIII, other countries use different twin sectors.
> 2. We followed all the instructions but when we run imganalyzer
> the final.img shows this : IMG:
> 000000 -> 281214
> 281165 -> 281248
> 281299 -> 281421
> 281372 -> 311857
> the SUB shows a whole lot more lines not the 4 spath has.
> What did we do wrong?.
This has been also reported by some users : the problem is that the
drive you use to make the first image is not able to extract correctly
some ranges. You can check this by running imganalyzer on xiii_cd2,
and you should see a single range for IMG but lots of them for SUB.
I would therefore suggest to try other drives to extract xiii_cd2
and choose the one which gives you the fewer SUB ranges ; I used
Plextor, and LiteOn was reported to work too. Please read the
end of this thread for the latest results on this :