I think the binary (fast) mode of UltraCompare shows a better way in this case. You can download it to try from http://www.ultraedit.com/downloads/ultracompare_download.html
I think this feature is very useful to compare firmware files. The firmware files are usually the same size, so the binary ...
Search found 4 matches
- Mon Mar 16, 2009 6:28 pm
- Forum: ExamDiff Pro
- Topic: Binary comparision not correct
- Replies: 10
- Views: 25814
- Mon Mar 16, 2009 1:13 am
- Forum: ExamDiff Pro
- Topic: Binary comparision not correct
- Replies: 10
- Views: 25814
Re: Binary comparision not correct
I think I can understand what your means is.
The binary comparision algorithm of ExamDiff Pro is not wrong but not clear enough.
The different content of these files are from 2000H to 2FFFH and it is not easy to get the result from ExamDiff Pro.
I think ExamDiff Pro is the best of the comparision ...
The binary comparision algorithm of ExamDiff Pro is not wrong but not clear enough.
The different content of these files are from 2000H to 2FFFH and it is not easy to get the result from ExamDiff Pro.
I think ExamDiff Pro is the best of the comparision ...
- Thu Mar 12, 2009 9:47 pm
- Forum: ExamDiff Pro
- Topic: Binary comparision not correct
- Replies: 10
- Views: 25814
Re: Binary comparision not correct
ExamDiff.png is the result of ExamDiff Pro and UltraCompare.png is the result of UltraCompare.
If you open the files with hex editor and jump to the offsets, you will find out the data in those offsets are the same.
If you open the files with hex editor and jump to the offsets, you will find out the data in those offsets are the same.
- Thu Mar 12, 2009 12:34 am
- Forum: ExamDiff Pro
- Topic: Binary comparision not correct
- Replies: 10
- Views: 25814
Binary comparision not correct
I got two binary files. ExamDiff Pro can not compare them correctly.
I tried to compare these file with UltraCompare and it can work correctly.
There are two differences:
1. The content from offset 2000H - 2FFFH is different.
2. Binary1.bin is larger.
I tried to compare these file with UltraCompare and it can work correctly.
There are two differences:
1. The content from offset 2000H - 2FFFH is different.
2. Binary1.bin is larger.