] > With the help of Maarten and Jose Morente I fixed the bug at last.
] > Indeed the MSX-MIDI was generating interrupts every 5ms and my program was
] > expecting it at 16/20 ms.
] >
] > Instead of switching hooks, I fixed the bug with a simple lookup
] > in the vdp status register, to check if the interrupt was indeed a VIRQ:
] >
] > IN A,(99h)
] > AND A
] > RET P
]
] Does that work??? I think the VDP statusregister is being reset upon readout
] in the MSX interrupt routine itself...
]
] Anyways, relocating the hook to #FD9F is a much, much nicer solution I
] think.
Indeed. The solution of reading #99 on #FD9A may work on a freshly rebooted
MSX but as soon as a different routine as hooked-up to #FD9F (e.g. micro
music), that routine will not be called anymore, since the bios only calls
#FD9F if the bios knows that the VDP generated the interrupt.
Kind regards,
Alex Wulms
--
Visit The MSX Plaza (http://www.inter.nl.net/users/A.P.Wulms) for info
on XelaSoft, Merlasoft, Quadrivium, XSA Disk images, the MSX Hardware list,
SD-Snatcher on fMSX, documentation and lots more.
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
