Looking for a Good HEX editor

  • Thread starter Thread starter M.Siler
  • Start date Start date
M

M.Siler

I didn't know what group to post this in... I'm looking for a good hex
editor. One that would permit me to view two files at the same time and as I
move the position in one it would also move it in the other. I'm trying to
compare the position location of two files.
 
I don't know about that, but have you tried the old FC command (filecompare)
from the command window (DOS).

In the command window do

fc /? <cr>

for information on options.
 
M.Siler said:
I didn't know what group to post this in... I'm looking for a good hex
editor. One that would permit me to view two files at the same time and as I
move the position in one it would also move it in the other. I'm trying to
compare the position location of two files.
Click to expand...

I like AraxisMerge. Very easy to use and very functional and not very
expensive. There is a sample version available as well.

Rick Sawtell
MCT, MCSD, MCDBA
 
I know the files aren't the same, but I want to make sure at byte xyz they
both have the same data type.

Right now I have both files open and I have to jump between them to check
that at byte 872 both have the phone number starting in that position.
 
Tom Ogilvy wrote...
FC doesn't do that, but if your using vb or Excel VBA, you can use low level
file io to open each and compare at byte level.

http://support.microsoft.com/default.aspx?scid=kb;en-us;151335
Working with Binary Access Files

It would be a lot easier to automate the check than to use hex editors.
Click to expand...
....

Maybe, but VB[A] isn't as easy to use for low-level file I/O as some
scripting languages. Unless the files are HUGE, it'd be easier to do
this in, say, Perl by loading both files in their entirety into
separate variables, then indexing these 'string' variables by byte or
word position. Easier and faster than using VB[A] binary file I/O with
byte record length.

Then again, there's always the venrable DEBUG.COM program, still
included in Windows XP. One could use separate instances in separate
console windows to display binary dumps between specific byte offsets
within the files. E.g.,

C:\test> debug somefile.bin
-d 326 327
13F8:0320 4B 87 K.
-q

C:\test>

And since DEBUG.COM accomodates I/O redirection, this could be
scripted.
 
The folks who made UltraEdit also make a product called UltraCompare.
It looks pretty cool but I have not tried it.
 
Back
Top