Bluemsx debugger problem with JR instruction on konami megaroms.

All konami games u pointed are purely and wholly based on INTERRUPTS
this means that the main is just one line like this:

         ei
loop:   jp loop

so if u want to disassemble the game, look for the interrupt routine

So if i check H.KEYI ($FD9A) and H.TIMI ($FD9F) i find the custom interrupt handler?I did this on #fd9f and found (for metal gear 1) a Jp #41ac.

Is this where the custom interrupt handler of the game is kept?

Yes, those hooks are used to store the interrupt handler routine's address.
You should try to disassemble the source starting at $41AC.

BTW, that is an interesting information that you gave here, Artrag.
Does that mean that ALL events in those Konami games are handled only thru the interrupt routine ?
Can you give us more info ?

I checked there and found the interrupt handler.And found it for most konami games.

The interrupt handler is done 50 times/sec or 60/sec when it is ntsc?

What is the proper way to dissasemble a konami megarom?How can i find stuff such as vdp handling inside the interrupt?

By the way i found a way to bypas that jr #4246 instruction on location 4246,i place a watchpoint there or i pause the emulator there,then i place a watchpoint at &h0038 that's where it goes next,then i remove the watch point from jr 4246 and continue,it goes to &h0038.

Has anyone from here done a dissasembly of konami megaroms?I think i will go and dissasemble a smaller game like frogger where it is only 8kbytes.It is very easy now to find the interrupt handler,i noticed that in smaller roms it is the same way to find the interrupt.

I knew that Konami's game code occurred inside interrupts, but every time think about it my body shivers...

I not only think it is not a good programming style, but also that it is not necessary. But obviously it worked for them 8)

I would like to request a new feature for the debbuger of Bluemsx.

Lately i started to dissasemble small konami roms like the video hustler which is 8kbytes.

In order to comment the debugging source and find out how the game is designed i did this.

I placed hundreds (really!) of consecutive watchpoints.So many and i started to remove them so that the game runs and is waiting for me to press space and hit the balls.

If i do this then watchpoints stop the program everywhere (eg has space been pressed ?is game over?Is there sprite collision ?Is highscore ?Has keyboard been used or joystick?)

So slowly with those literraly hundreds of watchpoints i started to have the debbuging source commented.

Problem is that bluemsx does not save the watchpoints when i exit.If i have 500 watchpoints in memory it is very tedious to have to insert them again.And next time i may have some i dont want from the previous one.

So is it possible that in next releases of bluemsx there can be a selection to save those watchpoints that i inserted so i can resume my work without having to insert all of them when i load them back?