tephra

iTrader: (6)

yeah vista sux... its been covered b4..

i think you need to save the file elsewhere and then copy it into the directory and overwrite it that way... rather than trying to save over the file..

kayman

as Dave mentioned above vista wont let you edit files in the program files directory etc.... you need to move the XML file to your desktop or My documents and edit it there then move it back to the previous location.

Dennis F

iTrader: (22)

I am lost here.

I was able to copy the .XML file in the right location and I see the mods in ECUFlash now, but all the values are way over the place. I saw someone up top had the same issue, all he did was check all the boxes or something?

This is exactly where I get lost. I did the 5.10 patch with all the goods but I am doing something wrong. I have not flashed it to my car as I am on my work computer trying to learn this stuff.

I have all the fuel/timing tables carried over but now I think I am just confused. Any idea what I am doing wrong?

I am trying to go from the 0008 rom ID to the 0015 ID. TIA

tephra

iTrader: (6)

ok if the values dont make sense then you have the wrong XML OR you have OLD xml in there...

so check your XML, remove any old stuff (tephramod stuff) and re-copy the xml from the 5.10 zip in...

Dennis F

iTrader: (22)

I got the 0015 ROM from the wiki page today and just installed your mods today as well.

As far as I can tell, there were no mods in that file to begin with. I probably just did something wrong. I am also using ECUFlash v1.34 and I changed the code to "big" where it was stated to.

voidhawk

iTrader: (20)

Back from the dead ... good info here! Question: has anyone thought of making a utility (or maybe a function in ECUFlash) that will copy all settings from rom file to another? Most of my tables are non-stock by now and copying everything by hand is not only tedious, but dangerous since it's easy to make mistakes ... just wondering?

nothere

iTrader: (23)

void, I agree, but, select all,cut and paste works for the whole chart

mx5tc

iTrader: (5)

I've gone thru most of the 50+ page thread on V5.XX and all of this thread but haven't been able to figure out which Evo9base XML file I should be using. I just updated my EcuFlash to Version 1.41 and it has the following Evo9 XML files in the EVO rommetadata directory:

88590015 15k
evo9base 19k
evo9base_20080530 38k
evo9base_20081101 41k

I made the mods to the 88590015 file as detailed in the comments in Tephra's .XML file and can see the Tephra mod variables and tables in EcuFlash when I open the Tephra modded 88590015.bin. However, I have some jumbled looking data in the mod tables.

I then took a harder look at the 88590015.XML file that "came with" Version1.41 and noticed that it has a XML "includes command" for evo9base_20081101. Should I just change this "includes" to evo9base.xml??? Any idea why the new version of EcuFlash is defaulting to a "non stock" base.XML file???

Thanks in advance,

Mitch

fostytou

iTrader: (15)

This is because evo9base_20081101 .xml is a newer version that is updated and consistent for the IX. The standard base file was being used for some VIII models so they did not want to change it and render other definitions incorrect. Make the evo9base modifications to whichever evo9base file is <included>'ed in your rom's XML.

mx5tc

iTrader: (5)

Thanks! I've got it "working" now (had to do the usual Vista BS, editing in another directory and then copying back to the EcuFlash directory), just in the process of copying/verifying all the old tables from my existing 88590014 ROM.

Mitch

tephra

iTrader: (6)

you shouldn't be putting the new defs in the base file. because then it will affect all romid's... which is wrong and wont work...

mx5tc

iTrader: (5)

Yes, I suspected that from a cursory review of both the evo9base and 88590015 files. I was just concerned about which evo9base base file should be "included" in the 88590015 file. At the end of the day, the "real problem" was Windows Vista on my desktop somehow mysteriously retaining an old evo9base.xml file which fudged everything up. I have everything working perfectly on my laptop (XP) so all is good for the short term.

Thanks,

Mitch

silver9mr

iTrader: (8)

great info thanks alot