UTILITY: compare two maps easly

deLux · **Joined:** Thu May 22, 2008 2:22 pm **Posts:** 80

Here is a little tool I wrote last week. It will compare two ROM files (same size & ECU ID) and tell you which tables have been modified.
If there is a change that doesn't match any table, you can at least get an offset of it.

now supports 160, 190 & 512 kB files
supports command line 1, 2 or 3 params: 1st ROM file, 2nd ROM file, ecu defs file.
if you just include ROM file names and there is ecu_defs.xml in current dir, it will compare right after start - could be added to explorer context menu or used in batch scripts.

Uploaded with ImageShack.us

It is a DOT NET app so you may have to install some libs from M1crosoft

added 1Mb file support
2010-11-16 some xml parsing fixes to accept not only the official RomRaider xml

BigWater · **Joined:** Fri Apr 18, 2008 9:35 pm **Posts:** 54

Exellent work! Very usefull!

Thanks!

deLux · **Joined:** Thu May 22, 2008 2:22 pm **Posts:** 80

thanks, I thought the same

sspeed · **Joined:** Wed Feb 06, 2008 4:09 pm **Posts:** 15

Wow, this is impressive! I emailed deLux last night and asked about some functionality, it was in there by morning. Amazing! Thanks!

yallahyimshi · **Joined:** Thu May 13, 2010 2:34 am **Posts:** 30

great tool from a great guy!

MFB · **Posted:** Sun Oct 31, 2010 1:28 am

great work, thanks!

Guy on the corner · **Posted:** Sun Oct 31, 2010 8:55 am

Really cool! Thanks!

deLux · **Joined:** Thu May 22, 2008 2:22 pm **Posts:** 80

There is reported problem on Win7 64b.
If anyone can confirm or deny this please let me know as I do not have access to 64b win7 right now.
thanks!

sspeed · **Joined:** Wed Feb 06, 2008 4:09 pm **Posts:** 15

I have win7 64bit and didn't notice a problem, what was the specific problem?

deLux · **Joined:** Thu May 22, 2008 2:22 pm **Posts:** 80

sspeed wrote:

I have win7 64bit and didn't notice a problem, what was the specific problem?

couldn't compare maps, I do not have better description now

sspeed · **Joined:** Wed Feb 06, 2008 4:09 pm **Posts:** 15

Weird, works for me, maybe they weren't locating the ecu_defs.xml because it's in a Program Files (x86) directory?

deLux · **Joined:** Thu May 22, 2008 2:22 pm **Posts:** 80

ok so the problem is a bug triggered by different location of ECUID on 09 FXT ROM (and possibly other ROMs)
This is not related to OS at all

I'll let you know when this gets fixed.

--- edit ---
it is fixed now.
4342592006 / A8DG300Z is not supported right now.

MFB · **Posted:** Mon Nov 01, 2010 8:38 pm

Thanks for your time on this, appreciate the help. :-)

This is a good tool for those who dont want to update to the latest ecuflash beta yet.

IanB · **Joined:** Mon Aug 16, 2010 12:03 pm **Posts:** 18

I can't get this to work, gives me the message:

Matching ECU IDs: E2ZJ101B
reading ECU DEFs file: C:\Documents and Settings\Ian\Desktop\Subaru Tuning\2005Legacy25i-E2ZJ101B_v1.xml
ROM ID E2ZJ101B not found
Error reading ECU defs

Any ideas? Thanks.

dschultz · **Posted:** Sun Nov 07, 2010 1:01 pm

In the def file I made. Delete all the stuff before the first <roms> tag.
The compare app may have a bug, doesn't like the XML file type tag and comment stuff.

Delete this stuff:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!-- ROMRAIDER STANDARD UNITS ECU DEFINITION FILE (VERSION E2ZJ101B_v1) 2010-09-11

TERMS, CONDITIONS, AND DISCLAIMERS
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
WARNING: These definition files are created as the result of the extremely complex and time consuming
process of reverse-engineering the factory ECU. Because of this complexity, it is necessary to make certain
assumptions and, therefore, it is impossible to always deal in absolutes in regards to representations made
by these definitions. In addition, due to this complexity and the numerous variations among different ECUs,
it is also impossible to guarantee that the definitions will not contain errors or other bugs. What this all means
is that there is the potential for bugs, errors and misrepresentations which can result in damage to your motor,
your ECU as well the possibility of causing your vehicle to behave unexpectedly on the road, increasing the
risk of death or injury. Modifications to your vehicle's ECU may also be in violation of local, state and federal
laws. By using these definition files, either directly or indirectly, you agree to assume 100% of all risk and
RomRaider's creators and contributors shall not be held responsible for any damages or injuries you receive.
This product is for advanced users only. There are no safeguards in place when tuning with RomRaider. As such,
the potential for serious damage and injury still exists, even if the user does not experience any bugs or errors. 

As always, use at your own risk.

These definitions are created for FREE without any sort of guarantee. The developers cannot be held liable
for any damage or injury incurred as a result of these definitions. USE AT YOUR OWN RISK!-->

RomRaider

Forum rules

UTILITY: compare two maps easly

Who is online