Maarten ter Huurne wrote:
> > After reading through your source quickly I noticed that you didn't
> >read out s#0 after each line interrupt to clear the interrupt request.
>
> According to the data book, the bit in S#0 is only for the vertical blank
> interrupt. So it shouldn't be necessary to read it on line interrupts.
>
> One thing that struck me about the program is that you only set the
palette
> index once. I'm not sure it wraps around at 16. If it doesn't, it would
> cause your program to fail.
It wraps around. And I relocated that part, the problem persists.
Besides, if this was the problem then it would not result in what I have now
but in a proper screensplitted screen, just with the wrong colors.
> Actually, in which way does your program fail? Crash, wrong display, ...?
Maybe you should run it??? :)
Then you can see it...
It runs, but it gives a wrong display, the screen flickers like crazy.
Eric Boon wrote:
Hi all,
>
>another attempt to resolve the Multisuperscreensplitwithpalette problem:
>
>Shouldn't you be writing the palette data to port #9A instead of #99?
>(MSX Tech. handbook says VDP port #2 (= VDP_Write+2) for the pallete data)
??? I do write the palette to port #9A using an OTIR. Register C is defined
to #9A a few lines earlier.
~Grauw
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
