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 | |
Add to favorites | "RSS" Feed | Next newer thread | Next older thread
User Post
elixirnova

Red Paratroopa
Level: 22

Posts: 55/177
EXP: 56507
For next: 1843

Since: 04-05-04
From: Midgar

Since last post: 1 day
Last activity: 1 day
Posted on 09-19-04 10:16 AM Link | Quote
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
Smallhacker

Green Birdo

SMW Hacking Moderator
Level: 68

Posts: 518/2273
EXP: 2647223
For next: 81577

Since: 03-15-04
From: Söderhamn, Sweden

Since last post: 10 hours
Last activity: 9 hours
Posted on 09-19-04 01:46 PM Link | Quote
The best way is to learn ASM.
MathOnNapkins

Math n' Hacks
Level: 67

Posts: 472/2189
EXP: 2495887
For next: 96985

Since: 03-18-04
From: Base Tourian

Since last post: 1 hour
Last activity: 32 min.
Posted on 09-19-04 02:31 PM Link | Quote
Take Jigglysaint as your God (with uppercase) if you want to learn how to find data.


(edited by MathOnNapkins on 09-19-04 05:31 AM)
Ok Impala!

Buzzy Beetle
Level: 31

Posts: 123/383
EXP: 183070
For next: 2293

Since: 03-16-04
From: The Netherlands

Since last post: 4 days
Last activity: 23 hours
Posted on 09-19-04 04:41 PM Link | Quote
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.
elixirnova

Red Paratroopa
Level: 22

Posts: 56/177
EXP: 56507
For next: 1843

Since: 04-05-04
From: Midgar

Since last post: 1 day
Last activity: 1 day
Posted on 09-19-04 07:05 PM Link | Quote
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


(edited by elixirnova on 09-19-04 10:19 AM)
Imzogelmo

Blue Octorok
Level: 11

Posts: 7/41
EXP: 5292
For next: 693

Since: 09-22-04
From: (Longview) Starkville, MS, USA

Since last post: 15 days
Last activity: 1 day
Posted on 09-22-04 01:29 PM Link | Quote
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.
MathOnNapkins

Math n' Hacks
Level: 67

Posts: 525/2189
EXP: 2495887
For next: 96985

Since: 03-18-04
From: Base Tourian

Since last post: 1 hour
Last activity: 32 min.
Posted on 09-22-04 01:32 PM Link | Quote
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.
Euclid

Cheep-cheep
Level: 23

Posts: 110/193
EXP: 65528
For next: 2195

Since: 03-15-04
From: Australia

Since last post: 24 days
Last activity: 7 days
Posted on 09-22-04 08:12 PM Link | Quote
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.
Heian-794

Red Super Koopa
Level: 44

Posts: 463/896
EXP: 611014
For next: 271

Since: 06-01-04
From: Kyoto, Japan

Since last post: 21 days
Last activity: 10 days
Posted on 09-22-04 09:31 PM Link | Quote
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!
MathOnNapkins

Math n' Hacks
Level: 67

Posts: 526/2189
EXP: 2495887
For next: 96985

Since: 03-18-04
From: Base Tourian

Since last post: 1 hour
Last activity: 32 min.
Posted on 09-22-04 11:36 PM Link | Quote
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.
Geiger

Buster Beetle
Level: 34

Posts: 123/460
EXP: 241080
For next: 12571

Since: 03-15-04
From: Indianapolis, IN, USA

Since last post: 6 hours
Last activity: 6 hours
Posted on 09-25-04 08:30 AM Link | Quote
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

Math n' Hacks
Level: 67

Posts: 561/2189
EXP: 2495887
For next: 96985

Since: 03-18-04
From: Base Tourian

Since last post: 1 hour
Last activity: 32 min.
Posted on 09-25-04 08:51 AM Link | Quote
Oh yeah. I think you told me that and I forgot. Sorry about the mixup.
Add to favorites | "RSS" Feed | Next newer thread | Next older thread
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.015 seconds.