I guess I'll just post here when I have trouble that after researching thoroughly I can't solve on my own (which will be pretty rare). Anyways, the question I pose today that has me kind of puzzled is this...
Is there any efficient way of detecting free space in the OoT Debug ROM? I have the idea that doing a thorough search of all the tables within the ROM and recording/comparing offsets would help tremendously but what if someone places custom code at a certain offset? No file table will have a reference to said code's offset.
Code snippets are appreciated no matter what language they may be in!
EDIT:
Well, you actually could find references to the custom code by disassembling certain parts of the ROM and searching for bits of code that made jumps DMARomToRAM or wrote to the special DMA registers. But the again, that's going above and beyond.
Question
Jason777
I guess I'll just post here when I have trouble that after researching thoroughly I can't solve on my own (which will be pretty rare). Anyways, the question I pose today that has me kind of puzzled is this...
Is there any efficient way of detecting free space in the OoT Debug ROM? I have the idea that doing a thorough search of all the tables within the ROM and recording/comparing offsets would help tremendously but what if someone places custom code at a certain offset? No file table will have a reference to said code's offset.
Code snippets are appreciated no matter what language they may be in!
EDIT:
Well, you actually could find references to the custom code by disassembling certain parts of the ROM and searching for bits of code that made jumps DMARomToRAM or wrote to the special DMA registers. But the again, that's going above and beyond.
Link to comment
Share on other sites
22 answers to this question
Recommended Posts