I found what appears to be an undocumented (and apparently disabled) debugger in the Kolibri 32x ROM. I was hoping someone with more 68k knowledge than myself might be able to shed some more light on this.
Here is what I've found so far...
Kolibri 32x
Button sequence: Starts at $B5320 (9 bytes long)
Debugger text: Starts at $957D4
Pointers for debugger text: Starts at $95A1D
Here is the debugger text:
WEAPON SELECT: %d...FIELD: %d %s....SOUND NUMBER: %d...-PARAM(C-RESET)-....lower speed: %d....higher speed: %d....startspeed : %d....vjmp accel. : %d....Camera Xpos : %d....Camera Ypos : %d....Slowgame tim: %d....Shield reptim:%d....trn wh. shot: %d....unlimited l.: %d....easy game : %d....Stage reset C+St
Since Kolibri is based on the Ecco the Dolphin engine, I'm guessing that you need to pause the game while the bird is turning (so that he's facing you) to enter the button sequence (just like in Ecco 2).
I've noticed that there are lots of talented people in this forum, so I was hoping someone might be able to look at the ROM and figure out if it's possible to get the debugger up and running, or supply any info that might help me figure it out.
Thanks.
Tony Hedstrom.
Here is what I've found so far...
Kolibri 32x
Button sequence: Starts at $B5320 (9 bytes long)
Debugger text: Starts at $957D4
Pointers for debugger text: Starts at $95A1D
Here is the debugger text:
WEAPON SELECT: %d...FIELD: %d %s....SOUND NUMBER: %d...-PARAM(C-RESET)-....lower speed: %d....higher speed: %d....startspeed : %d....vjmp accel. : %d....Camera Xpos : %d....Camera Ypos : %d....Slowgame tim: %d....Shield reptim:%d....trn wh. shot: %d....unlimited l.: %d....easy game : %d....Stage reset C+St
Since Kolibri is based on the Ecco the Dolphin engine, I'm guessing that you need to pause the game while the bird is turning (so that he's facing you) to enter the button sequence (just like in Ecco 2).
I've noticed that there are lots of talented people in this forum, so I was hoping someone might be able to look at the ROM and figure out if it's possible to get the debugger up and running, or supply any info that might help me figure it out.
Thanks.
Tony Hedstrom.