All,
I stumbled upon a tool that may prove very useful for people who actually know what they are doing here. Someone wrote a utility that generates XML code for every map within a ROM. I'll just quote what was written on the other forum (this is from like 2007):
Quote:
Here is a utility that will generate Enginuity format map definitions in xml from the raw bin file. It uses the map lookup table located at the start of the map section of ECU memory (usually h'28000)
bin2xml.zip
I've tried it on the new ZX-6, and PetriK K5 busa bin. It worked on both.
You will still need to enter the romid tags that id the make, year, model, etc. by hand at the top of the xml.
This utility is very old school. You can't use long windows filenames, it has to be in the same directory as your files, doesn't support paths in the filename etc. But it gets the job done.
All the maps are named using their address such as "Map 0x00028F8C"
They are group category wise by their dimensions. I figure maps with similar dimensions will have similar function. 2D map categories are like "x17" while 3D categories are "x30y50 for example.
The rest of the definition is very generic. A lot of unknown etc.
Here is an example of an autogenerated file of the ZX-6. It has 229 maps, 151 2D, and 78 3D. I'm pretty sure it took me less time to write the converter than it would have to type in all the maps.
zx6_001.xml
BTW you should check the very last entry of the generated file. The program runs till it encounters a non standard type code. It worked fine on the ZX-6 but on the busa it added one additional map with bogus data. Just delete it before posting the output into your xml file.
Here is the source code for anyone who wants to improve on it.
bin2xml.txt
The links are all dead, but I managed to save a copy of the generator before the website went down.
Let me know if this is useful or not!
https://www.dropbox.com/s/70keiglwylfad2o/BIN2XML.zip?dl=0Updated:
https://www.dropbox.com/s/s2tq2dbim5xzkry/BIN2XML.zip?dl=0
