Register | Login
Views: 19364387
Main | Memberlist | Active users | ACS | Commons | Calendar | Online users
Ranks | FAQ | Color Chart | Photo album | IRC Chat
11-02-05 12:59 PM
1 user currently in Rom Hacking: hukka | 2 guests
Acmlm's Board - I2 Archive - Rom Hacking - data finding techniques
  
User name:
Password:
Reply:
 

UserPost
MathOnNapkins
Posts: 561/2189
Oh yeah. I think you told me that and I forgot. Sorry about the mixup.
Geiger
Posts: 123/460
Originally posted by MathOnNapkins
His build used to produce a file called output.txt. Hell it still might but I haven't looked recently. In fact all that was was a log of when tracing started and stopped and a few other things unimportant to someone who's tracing a rom. Though, something like output.txt is terribly misleading on a tracer program, you have to admit.


That was actually produced by the original code that I hooked into (IOW, I did not write that part). It was basically a log of the stuff printed to screen (the screen output if you will). It should be eliminated in the current version though.

---Evil Peer
MathOnNapkins
Posts: 526/2189
Originally posted by Euclid

As for how to use the tracer, i think anyone could've figured it out in a few minutes.


Well um, I couldn't figure out how it worked initially because I was looking at the wrong file. His build used to produce a file called output.txt. Hell it still might but I haven't looked recently. In fact all that was was a log of when tracing started and stopped and a few other things unimportant to someone who's tracing a rom. I PMed him and he told me to look in the folder where the rom was. I felt pretty stupid then. Though, something like output.txt is terribly misleading on a tracer program, you have to admit.
Heian-794
Posts: 463/896
I dunno, Euclid; I couldn't make head or tail of what came out of Evil Peer's tracer, and still don't know how to translate ASM codes into stuff that you'll see in a hex editor. And I've already hacked two games successfully!

Elixir, one tip I can give you is to open your ROM with both a hex editor and a graphics editor. This way, if you're looking for certain hex values (suppose you're editing a baseball game and want to find player data, and so you start by trying to find some of their numbers in hex) you'll be able to see which sections of the ROM correspond to graphics and whose hex values can thus be eliminated, since they're not "really" numbers.

Corrupting is inefficient when you're looking for what might be contained in a single row of numbers -- it's like finding a needle in a haystack!
Euclid
Posts: 110/193
knowing those opcodes/address modes will help a lot.

Think Tracer = execution path of a program (a rom assembly in this case)

As for how to use the tracer, i think anyone could've figured it out in a few minutes.
MathOnNapkins
Posts: 525/2189
Originally posted by elixirnova
well so far i know most of the commands.. (lda, sta, stx, and, or...) all that but i dont really know how to trace asm? to find what i want.. should i find a disassembler?

*edit i just dl'ded snes9x w/tracer i dunno how to use it?! but im gonna fool around with it* any help would be nice though


I understand that you're learning and that questions come up from time to time, but please devote more time to thinking your problems through and researching them before asking people for help here. That's my take on it anyways. It looks bad when you don't appear to have the initiative to solve your own problems most of the time. Not that you shouldn't ask questions here, just please use more discretion.
Imzogelmo
Posts: 7/41
Originally posted by elixirnova
well so far i know most of the commands.. (lda, sta, stx, and, or...) all that but i dont really know how to trace asm? to find what i want.. should i find a disassembler?

*edit i just dl'ded snes9x w/tracer i dunno how to use it?! but im gonna fool around with it* any help would be nice though


Now you have the perfect tool, and there are plenty of docs on the subject at Zophar's, so you should be able to figure it out pretty easily. All you need to know is where the data is and what the data is that you're looking at.
elixirnova
Posts: 56/177
well so far i know most of the commands.. (lda, sta, stx, and, or...) all that but i dont really know how to trace asm? to find what i want.. should i find a disassembler?

*edit i just dl'ded snes9x w/tracer i dunno how to use it?! but im gonna fool around with it* any help would be nice though
Ok Impala!
Posts: 123/383
Ok!

I have this same problem while making my Mario Kart hack. Some directions on how to find compression offsets for example using ASM (I know how to do it with Sniff for example) would be really helpful.
MathOnNapkins
Posts: 472/2189
Take Jigglysaint as your God (with uppercase) if you want to learn how to find data.
Smallhacker
Posts: 518/2273
The best way is to learn ASM.
elixirnova
Posts: 55/177
hey im trying to map out a rom and corrupting just isnt doing it all for me its an snes rom and i do know how to find ram adresses and find out where they are used in the rom but just wonderin if there was anyone who could give me some tips on finding data
Acmlm's Board - I2 Archive - Rom Hacking - data finding techniques


ABII


AcmlmBoard vl.ol (11-01-05)
© 2000-2005 Acmlm, Emuz, et al



Page rendered in 0.007 seconds.