Hexecute Search Messing Up Characters

[scarecrow]

Hello, Zophar's Domain, I've been watching you.

Well, more like Lurking for the past few weeks. I didn't want to post without searching extensively first (Plus I like trying to figure it out myself).

I've been trying to HexEdit Mario Kart 64 recently, well, it's the only thing I've actually tried, but more on that later.

Anyways, for some reason, Hexecute has decided to bug out on me. When I'm using search and I search for a string (text or hex) that doesn't appear in the file, all the characters are replaced with incorrect ones. I know it's the wrong characters, because at the beginning of the code are the words "MARIOKART64". When I go back to look at this after searching, not only is the text replaced with "$..Á..ª...." but the hex code has changed as well.
Any ideas?

And on a side note:
I discovered this while trying to search for "318c". I noticed a pattern of it appearing over and over again, so I was trying to catalog when the sequence began, and when it ended, so that I could corrupt that specific area for the string "318c" in an attempt to figure out it's function in Mario Kart's code. Hexecute is supposed to be able to search for up to 16 characters, so I typed "318c" in the search, but then the glitch I described above happened. I can search fine for just "31" and "8c", but how would I search for four characters simultaneously?

I apologize for the double post, I really do, I hate double posters. ><*
The Edit function isn't working on my first post for some reason, so this is all I can do.

I figured out that it also glitches when you search for letters in hex as well, which is odd.
It also glitches just randomly while it's running as well.


----------EDIT--------------

I need to run it in Compatibility mode for Windows XP to fix searching for characters in sets of two, but it still glitches when I search for characters in sets of 4.


---------EDIT---------------

And now it stopped working when I run it in compatibility mode.

---------EDIT---------------

Ok, so now I've figured this out:
-Run in Compatibility Mode for Windows XP (Service Pack 2)
-Run as Admin
-Check the bottom three boxes in settings.

It will search for most letters in hex and not glitch, even in sets of four(except ffff), but when I search for something invalid it still glitches.

--------EDIT----------

Screw it.
I got off my ass and got Hex Workshop.

 

[InVerse]

The edit post problem has existed for awhile, in the future, just go into Advanced Mode and edit it from there and it will save fine. I can't use the Quick Edit feature half the time either.

As for your problem, you've halfway found your solution. You definitely don't want to use Hexecute. If you need ROM hacking specific features, use Windhex. For basic editing, Hex Workshop is excellent. (I've been meaning to write an app to convert ROM hacking style tables into Hex Workshop style character maps but I haven't been ROM hacking and I'm lazy.) If you need robust relative searching features, I would suggest Monkey Moore first but if you really need it in a hex editor, then Translhextion. Hexecute should only be used ironically in this decade.

 

[scarecrow]

Half the programs you've listed I've tried, and don't work with Windows 7. I'll sure as hell look into the other programs. Thanks!

 

[InVerse]

You might want to look in to DOSBox as well. ROM hacking on Windows 7 is about as productive as making phone calls on an iPhone.