Re: Multisuperscreensplitwithpalette problems...

1999-06-24 Thread Anonymous
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

Re[2]: Multisuperscreensplitwithpalette problems...

1999-06-24 Thread Anonymous
??? I do write the palette to port #9A using an OTIR. Register C is defined to #9A a few lines earlier. Oops - two mistakes after another, I'll better keep my mouth shut now :-O Eric MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put in the body (not

Re: Multisuperscreensplitwithpalette problems...

1999-06-23 Thread Anonymous
(3rd time I try to sent this msg to the list - still havent seen anything :-/) 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

Re: Multisuperscreensplitwithpalette problems...

1999-06-21 Thread Anonymous
Hi Laurens, I was trying to make... 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. Although I am not sure, this is most likely the reason why your proggy doesn't work. You should try something like

Re: Multisuperscreensplitwithpalette problems...

1999-06-21 Thread Anonymous
I was trying to make... 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. Although I am not sure, this is most likely the reason why your proggy doesn't work. Doesn't reading s#1 clear the

Re: Multisuperscreensplitwithpalette problems...

1999-06-21 Thread Anonymous
At 09:22 AM 6/21/99 +0200, Mark 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

Re: Multisuperscreensplitwithpalette problems...

1999-06-21 Thread Anonymous
ARGH! Eric hitting himself and saying: Lesson one in using a mailing list: think first, replay later. Grauw, you did not make a mistake (at that point ;-)) in the code :-) Eric (crawling back in his corner) MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and

Re: Multisuperscreensplitwithpalette problems...

1999-06-21 Thread Anonymous
I think you made a slight mistake in the filling of the pallette. (10th line after InitPalLop:) : ld a,d rra ld a,e rla : shouldn't that be: : ld a,e rra ld a,d rla : ?? Eric MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put

Re[: Multisuperscreensplitwithpalette problems...

1999-06-21 Thread Anonymous
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) Eric MSX Mailinglist. To unsubscribe, send an email to

Multisuperscreensplitwithpalette problems...

1999-06-20 Thread Anonymous
I was trying to make sum' nice program which puts all 512 colors on the screen. It is attached, but there still is one problem: it doesn't work!!! I also attached the source so maybe some of you can hel me? It's probably just a little bug... The problem isn't the speed of the screensplit because