Author
|
Topic: Hex editor and dumper for large files. (Read 1062 times)
|
DaMarsMan
Guest
|
 |
« Reply #15 on: May 30, 2007, 02:51:00 pm » |
|
RTFM! *Points to getting started section.*
|
|
|
|
|
Rai
Guest
|
|
« Reply #16 on: May 30, 2007, 02:56:38 pm » |
|
And... it has ASCII table values so I can just apply an ASCII table. No use to waste your time when you know the values already. If the text editor just shows gibberish Japanese characters though, I guess I'll have to use relative searching.
Don't use a text editor for hacking ROMS. Seriously. It's showing gibberish because it's not made to show data. Do you modify images by opening them in a text editor? No? Right, you use a paint programm, since they are specifically made for that. Use tools for hacking then and forgot your text editor! Did you honestly think I hacked roms with a hex editor? Wow. No I opened the rom in a text editor to see whether or not it has ASCII text or not. Then I search that ASCII text in a Hex Editor and yeah. It's rather elementary my dear Watson. |
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #17 on: May 30, 2007, 03:09:05 pm » |
|
Cut the crap, everyone. Seriously. This includes you, Rai, there's no need for witty retorts.
|
|
|
|
|
Rai
Guest
|
|
« Reply #18 on: May 30, 2007, 03:18:31 pm » |
|
Well, I'll do this later. But I think an 8MB GBA game is much more my level.
|
|
|
|
|
Kajitani-Eizan
Guest
|
|
« Reply #19 on: May 30, 2007, 06:13:27 pm » |
|
i fail to see how the size of the game makes any difference at all. if the file takes longer than a few seconds to open, either a) you have a really crappy computer or b) you're not using the right programs. beyond that, the size would only matter if you were manually scrolling through the whole file, which you shouldn't be doing anyway.
|
|
|
|
|
Spikeman
Guest
|
|
« Reply #20 on: May 30, 2007, 06:25:07 pm » |
|
I usually scroll through the ROM in a hex editor just to check if there's any noticeable text and I can also usually recognize pointer tables, I also scroll through in a graphics editor and note locations of textual graphics, so I don't think it's something you shouldn't be doing. Also I don't see why Translhextion wouldn't be able to open a 32MB ROM, doesn't it just load the whole file into RAM? Just upgrade your computer's RAM or have less programs open.
|
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #21 on: May 30, 2007, 10:58:40 pm » |
|
i fail to see how the size of the game makes any difference at all. if the file takes longer than a few seconds to open, either a) you have a really crappy computer or b) you're not using the right programs. beyond that, the size would only matter if you were manually scrolling through the whole file, which you shouldn't be doing anyway.
Or he's using Translhextion, which loads the entire file to RAM. Try loading a 64 meg file and you'll die of old age. :p |
|
|
|
|
creaothceann
Guest
|
|
« Reply #22 on: May 31, 2007, 10:24:34 am » |
|
Even when loading the file into RAM you can get full speed. Just google for "memory-mapped files".
The only downside is that you can't change the size of the opened file.
|
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #23 on: May 31, 2007, 04:02:00 pm » |
|
Even when loading the file into RAM you can get full speed. Just google for "memory-mapped files".
The only downside is that you can't change the size of the opened file.
You've never used Translhextion, have you?  |
|
|
|
|
Kajitani-Eizan
Guest
|
|
« Reply #24 on: May 31, 2007, 05:04:55 pm » |
|
i fail to see how the size of the game makes any difference at all. if the file takes longer than a few seconds to open, either a) you have a really crappy computer or b) you're not using the right programs. beyond that, the size would only matter if you were manually scrolling through the whole file, which you shouldn't be doing anyway.
Or he's using Translhextion, which loads the entire file to RAM. Try loading a 64 meg file and you'll die of old age. :p see bolded text. though heck, i'm not sure why even loading a 64 meg file into memory would take that long, assuming a) it's not coded like ass, b) you have a half-decent amount of physical memory (say, 512 mb or so), c) your hard drive isn't like, 1000 RPM, and d) your file and/or MFT aren't horrifically fragmented. |
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #25 on: May 31, 2007, 06:28:31 pm » |
|
The author of Translhextion itself said the program was really badly coded. It can handle small files fine, but try loading huge files and you'll have problems. He told me he wanted to rewrite it before vanishing into the internets all those years ago.  |
|
|
|
|
tomaitheous
Guest
|
|
« Reply #26 on: May 31, 2007, 11:26:24 pm » |
|
I mainly use ultraedit and less often, hex works. The largest file I had open was 400+ megs so you shouldn't have a problem there.
|
|
|
|
|
creaothceann
Guest
|
|
« Reply #27 on: June 01, 2007, 07:29:50 am » |
|
Even when loading the file into RAM you can get full speed. Just google for "memory-mapped files".
The only downside is that you can't change the size of the opened file.
You've never used Translhextion, have you? Actually, no. Why? |
|
|
|
|
|
RHDN Forum Archive
