Originally posted by: ninjistar
Originally posted by: Bea_Iank
I will have some two weeks off at the end of April to recover from a surgery.
Pester me about this then and I will take a look at it. I need to figure out how the map is stored in memory and work from there.
I know enough of 6502 Assembly to figure a thing or two how it works as well. It will be a matter of finding out the offset where the PRG is stored in this rom.
I too want to see a 180K+ plus score in this.
You may or may not be in my area of expertise now (IT/programming/data streams and file formats)...
In Linux, use the 'file' command. 'file' will give you basic information on the ROM by using a local database of known formats.
I'm not exactly following what you're wanting to do based on what you said above. I've worked with the 6502 debugging maybe once, but I've done my share of x86 debugging. One would probably want to load it into the debugger and set breakpoints during specific behavior to observe the changes to system state. I imagine there will be a default offset to load the program into memory. For some reason, 0x4000 comes to mind, but don't quote me on that (it may be 0x0400, or something else entirely
).
I'm happy to help, contribute, or sit back and have drinks and make funny comments. 8)
Well, the way I will start is by setting up a memory sniffer on the emulator that allows me to dump the memory to file with a single key stroke.
Then take several memory dumps, tick by tick, first of the wand appearing.
After that, I will add a direction key input as entropy and save the same amount of memory dumps so I can compare.
After I have a direction, I will start looking for the PRG to disassembly and study what is affecting the memory to study and determine what is happening.
Then no one knows. But in the end, we will know what conditions cause the wands to spawn.
