Just a newb here trying to get my learn on....

In the Task Info field, for IX maps (both the ROM I took from my actual EVO IX, to any map I mod or receive from a friend), I repeatedly see:

Then for an EVO VIII map, I see:

-Why does my map inherent these?

-What would happen if I were to erase 'evo9base_20081101" from my C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo directory?

-Why doesn't my downloaded, oem ROM I took from the car inherit '88590015.xml' if anything as this is 'Internal ID' as displayed by EVOSCAN?

 

Ok, doing some more reading and watching the video tutorials, I see EVOSCAN is a graphical interface to tie together all the difference XML files. The ROM or .hex file is just a gathering if the difference XML files.

But when u change a table in EVOSCAN, just as a timing map to add more timing, or you turn off lean spool...what XML file is that written to? (U're only saving the ROM or .hex, when u select save in EVOSCAN, right?) I know you can modify given XML files to add 'features' into EVOSCAN as the developers discover more and more, but where are ~my~ changes written if the ROM or .hex file is just a gathering of the XML files in my directory?

 

The inheritance of the two files are common entries in all Evo 7-8 and Evo 9 Roms. The individual files hold the differences between the roms and/or the address locations of the common map points.

The XML is NOT written to when you change a point in your rom the hex file you load is. The XML just defines what part of the binary you're looking at.

Try this analogy on for size:

The Rom hex/bin file is like a library, the XML files are like index cards telling you where a book is in the library. So you go to the index cards find the book you want to change or write in then grab it off the shelf in the library and write changes in the book putting it back in the library.

 

88590015.xml = functions on the left that show up as u mod the XML for 88590015.xml, cool. 'evo9base_20081101.xml' = base functions u'd never mess with?

 

the base defines maps that "should" be in the evo 9 file the 88590015 file defines where the map is.

 

Thank you for the analogy RoadSpike and the quick reply. I'll chew on this a bit and read up a bit more. :0

 

Not base functions you'd never mess with. Base locations for maps that are consistent on any rom that inherits that rom. It saves from having to copy the same map locations to 10 different rom ID XML files, by just inheriting from 1 main file.

Then each of the specific rom ID XML files has maps specific to that rom ID.

 

ok that makes sense, thank u.