03white, well if the guys doing all work simply only work on one ROM it will take care of what others want! haha It makes perfect sense to have 1 EVO8 ROM, 1 EVO9 and an EVOX.

Could you, for example use the 96533706 rom in a car that still had a MAF sensor on it? I realize it's modified for speed density and live tuning but can it still be used directly with a MAF? Looking at those files each one gets progressively larger in size, so I'm assuming the 706 file has everything the others do plus the speed density and live map?

I've been messing with this stuff for hours trying to figure some of it out on my own. In 1.42 there is an XML file 88590715, when I open the rom I see it inherits from 88590015_r3compile_20091010. Looking at the XML files in 1.42 Tephra has his own XML file in there and it is much larger and more complete than the r3compile XML. How do you make the 88590715 ROM read from Tephra XML? I hope that's not too confusing. I tried to open the ROM file in Notepad and change the "inherits from" just to see if it would work but it is scambled. I'm assuming I need a different program. IF that rom used the Tephra XML it appears to me as though it would function properly and have more features.

 

David....that exact issue is what I am working to resolve. There is far too man "inherits" in 8859. My goal is to get only a evo9base, a 88590015, and a 88590715-v7 xmls and that is it. This will make tuning much easier and eliminate all of the inherits.

 

Use Microsoft Frontpage.

 

That's actually a step in the wrong direction though. You want to minimize the number of repeat tables loaded in different xml files so things can be found in a single place to make it more easy to update things. Different topic for a different thread.

David, I believe 96532706 is liveMAP + TephraV7 + MAF.

It should be very similar to 96533706 but will not have the speed density tables.

You can probably use the 96533706.xml and not have an issue. Just need to change the ROM ID.

 

03white, or anyone else who knows the correct answer:

My question was probably confusing. The maps with speed density and live mapping for example, can it also be used on a MAF equipped car?

 

No, not if the ROM is patched with SD.

You can use the XML entries...they just show you tables in ECUFlash. But, if the ROM is actually patched for SD (the SD programming and tuning tables are set for SD) then you can't use it in a MAF based car.

 

I just finished sending you a PM actually..........thank you for the simple straight answer.

You guys have to be border line genius's. This stuff confuses the hell out of me.

l2r99gst, the SD programming/tuning tables, can they be set back to MAF settings or turned off if the ROM is already patched for SD?

 

Yes, the tables can be set back to MAF settings. You just have to compare and copy the data from a stock or non-patched SD ROM.

 

Great, that's kind of what I thought. It would just be time consuming to go through each setting in the ROM to set it back up for MAF instead of SD, right?

 

Correct. That's why phenem made separate downloads for the same ROM. This way, each copy of the ROM is already setup for whatever you want...MAF, SD, LiveMap, etc, and you don't have to worry about patching or unpatching them.

I sent you a PM expaining in a little more detail.

 

Never mind, l2r99gst has gotten you taken care of.

 

I understand, hooray! Thanks for the PM!

 

Is there any other program other than Front Page that can be used to edit the Rom's? I don't have front page.

Thanks.

 

Dave,

I jumped on mininova or pirate bay and downloaded a torrent for a program called Stylus Studio. It seems to be pretty easy to use and makes reading and editing the XML files pretty easy.

 

I use TextPad (http://www.textpad.com/). Its a great text editor (xml files are just text files) that costs only about $25.