Re: VDU question

[oscarv <vermeul...@gmail.com>]

Hi all,

Turn out it was a matter of parameter tweaking after all.

Instead of (in VDU.ASM)

VDU_INIT6845:
.DB 07Fh, 50h, 60h, 0Ch, 1Eh, 02h, 18h, 1Ch, 78h, 09h, 60h, 09h, 00h, 00h, 00h, 00h

Changing the VSYNC to be generated two rows earlier:

.DB 07Fh, 50h, 60h, 0Ch, 1Eh, 02h, 18h, 1Ah, 78h, 09h, 60h, 09h, 00h, 00h, 00h, 00h

solves the problem. Thanks for all the hints! Hearing that others also had issues with the top line made clear it was not likely to be something specific with my hardware - so the datasheet was the place to look.

BTW, Douglas - the Olympia PEOPLE: I remember that machine... funny that a derivative of its code made its way into my N8VEM :)

Regards,

Oscar.