I think you'd like that stylus studio better... it color codes everything as well when you open it making it easier to identify different sections of the coding.

 

TextPad will color xml tags if I want, but I never use it because it distracts me. Bottomline though is that I've been using Textpad for six years now (started using it at work), and its always served me well. To each his own though.

 

Feh, all of you and your fancy editors. If I'm stuck on Windows, I'll usually use Notepad++. Does syntax highlighting and a bunch of other stuff, but stays out of your way for the most part. It's what Microsoft should have shipped as Notepad in the first place.

 

I have Notepad and use it to modify the XML files. The ROM file though will not open properly using Notepad. The question is about a ROM file being modified. mrfred, your answer to that is the textpad?

 

i could be wrong but with my windows 7 i had to set it up to allow administrative privileges before it would allow me to modify anything. sorry if this is way off base

 

Wait, what? You want to directly edit the ROM? I think everyone above was assuming you were looking for an XML editor.

ROM manipulation is what EcuFlash does (or a hex editor, which I don't think is quite what you're looking for).

 

I'm confused.

Are you trying to modify the .bin/.hex files in notepad?

Or the .xml?

Notepad will edit the .xml files just fine. .bin/.hex on the other hand will need something very different, but I don't see why you want to write anything into the ROM file that can't be done using ECUFlash?

I'm liking the notepad++ though. VERY NICE

 

I have some roms that are using XXXXX for the "inherits from". I want to change the "inherits from" in the actual ROM file so it will get the information from a different XML.

I can modify the XML file perfectly with notepad and have been doing that when I need to add something, such as the updates in this thread for the throttle hang.

While messing with all of this I noticed some of the roms aren't showing all the tables in them and figured out that if they inherited from the correct xml file they would.

So that is why I want to be able to write something into the rom itself, just to change the "inherits from" part of it.

Isn't that what I'd have to do to make the ROM get it's information from a different XML?

 

I think I figured this one out on my own!!!! It can be done right in the ecuflash can't it?!!!

file, options/rom file directory..........then type in the xml you want it to use? Is that right? Did I actually figure something out on my own!!! Oh glory day!!! maybe.



NOPE. I got prematurely excited, that didn't work...............sad day again. haha

 

The "ECU ID" will control which xml file it loads. (96530006.xml, 94170015.xml, etc.)

To change what get inherited, you have to change it in the xml file and not the ROM.

You want to be careful doing this though as you may inherit incorrect tables if you point it at the wrong file. Some xml files are setup very differently and this is why there are so many evo7base files floating around.

 

The "inherits from" is controlled by the ROM ID embedded in the ROM and some of the first lines in the xml files. I'm not following the example you gave though, so I'm not exactly sure what you're trying to accomplish.

 

Let me give you an example. I'm using 1.42, 88590715-TephraMod is the ROM I have opened right now. It inherits from: 88590015_r3compile_20091010.

Please take a quick look at that if you are using 1.42.

Now if I compare the r3compile XML to the standard Tephra XML for 88590715 the Tephra XML contains more files. So I'd like to have Tephra ROM pull it's information from Tephra XML and not the r3compile XML.

See what I am trying to do now and why? So how do I change where that rom inherits from?

 

You know, I'd love to put together an advanced tuning class and have some of you experts fly in to put it on and pay you for it. I bet we could get quite a large class together and not only advance some knowledge but put some money in some of your pockets for your time and teaching. What do you guys think?

 

For further comparison, ROM 88590715, Tephra XML file is 65kb and from what I can tell by viewing the XML it has everything needed in it to work correctly. It doesn't seem to need to draw from an EVO9 base file or anything else.

BUT, I don't have a single rom that get information from Tephra's 65kb XML. They all pull information from the EVO9 base r3compile and the r3recompile 88590715 file.

 

This is getting a bit off topic but I want to help. If you have a tephra v7 ROM open, it ought to be using the tephra v7 xml unless you inadverently modified the tephra v7 xml to tell it to read the recompile xml. Alternatively, you might have inadvertently modified the tephra ROM ID (or maybe some else did if this is a customer's car). Let's try this:

With the ROM open in ECUFlash, click on the "+" next to the "ROM Info" tag in the definitions list on the left. Read the "Internal ID" from the info and post it here.