From
Neness2000:
What usage for this tool ?
Well i've coded this tool because In killzone we have 5 munge files
and the lba of the 5 munge files were mixed together to add a difficulty to rip this game.
As i never found a way to extract the lba CLASSICLY i've decided to code a tool that
could using recursivity extract the whole lba.
There were another difficulty , the lba of one file was also not in order, it need sometimes to
go back in the lba to find the next offsets.
Based on all this, it was clear that if you can know the lba format (for kill zone, START ADRESS,LENGTH, A NAME POINTER)
and the offset of a file, we could retrieve recursivly all the following offset.
It is obvious that the offset to use to detect LBA must be one of the very first (EXCEPT IF FIRST FILE IS 00000000)
To use this tool you have to create a CONFIG.INI file with the definition of the lba
(use same standard as my KIT MAGICIAN INI FILE, see config.ini file i've gave as example)
Give him also the path, the file holding LBA and fill in the parameter section(See lower for an example).
Hit button and the tool will begin to iterate trying to detect the whole LBA.
Tool Stop if
- The last entry it detect + the length is > then GLOBAL SIZE of file you specified
- It has iterate recursivly 100X
Tool will gave you a LBA.TXT file stored in @EXTRACTED (NEVER FORGET TO CREATE THIS DIRECTORY)
If the first file offset you gave is the second entry,
it mean you 'll have to add manually a line in LBA.TXT for first entry !!!!
This tool is not only useful for KILL ZONE ! all game using this protection can be beaten using it
More of this i already seen some game with LBA filled with 0000 (and of course this filling is variable)
Using this tool you can also beat such a protection !
Hope you'll enjoy it
Example for KillZone
--------------------
FIRST FILE OFFSET : For example for file FILE01.DAT 66881536 (3FC8800)
LBA START OFFSET : 199436
LBA END OFFSET : 352232
SIZE OF MUNGE FILE : Give here the global size of one of the munge file.
For FILE01.DAT 990547972