Re: Finding maps and tables in Universal Patcher
Posted: Tue May 24, 2022 7:07 am
Finding tables can be done in different ways.
For any one of it, there is a need of some basic definition file for an OS, that can be used for template or reference.
There is a fresh new offset tool, than can quickly find offsets between different OS. Limitation here is it needs to be done for each OS.
The other strategy is to find a unique code sequence used for table lookup that works with most of the known OS, and add that to tableseek-*.xml file, and use the tabledata from the definition file.
Index was outside the bounds of the array.
This needs some investigation, It may be due to wrong configuration or something else.
Here is some quick list of different xml files being used.
First is
1.segment config xml
It is usually labelled p01-p59.xml [pcm type.xml]
It contains info for file structure[segments name start-end address and so on], checksum configuration, and some other info read from bin file.
It can be edited from patcher->edit segment config (XML)
2. tuner definition XML
To autoload it upon opening a bin, it needs to be named by OS.xml and placed in the tuner folder
It contains all data needed to tune a bin. The xdf equivalent.
It can be edited and opened in tuner->xml->*tablelist
3. tableseek*.xml
This is a basic definition xml converted to tableseek, and instead of address for table it contains a search string.
accessed from patcher->tableseek
There is more xmls being used and I will write about them later.
For any one of it, there is a need of some basic definition file for an OS, that can be used for template or reference.
There is a fresh new offset tool, than can quickly find offsets between different OS. Limitation here is it needs to be done for each OS.
The other strategy is to find a unique code sequence used for table lookup that works with most of the known OS, and add that to tableseek-*.xml file, and use the tabledata from the definition file.
Index was outside the bounds of the array.
This needs some investigation, It may be due to wrong configuration or something else.
Here is some quick list of different xml files being used.
First is
1.segment config xml
It is usually labelled p01-p59.xml [pcm type.xml]
It contains info for file structure[segments name start-end address and so on], checksum configuration, and some other info read from bin file.
It can be edited from patcher->edit segment config (XML)
2. tuner definition XML
To autoload it upon opening a bin, it needs to be named by OS.xml and placed in the tuner folder
It contains all data needed to tune a bin. The xdf equivalent.
It can be edited and opened in tuner->xml->*tablelist
3. tableseek*.xml
This is a basic definition xml converted to tableseek, and instead of address for table it contains a search string.
accessed from patcher->tableseek
There is more xmls being used and I will write about them later.