Vertical scrolling routine (MSX1)

I think 27 cycles is the recognised minimum spacing of VDP writes on an MSX*; OUTI+JP conditional is 29 but I don't think there's a solution for outputting a block from memory in less than 29 but greater than or equal to 27 cycles, so it's probably the smart choice.

You can actually write a lot more quickly during the vertical border area though, so assuming you're synchronised to end of frame you might consider a loop that uses OTIR for a while, then switches to OTIR+JP. That is, if you really want to get into the complexities on this stuff.

* I'm pretty sure it's 39 VDP cycles on an original TMS9918a, which would ostensibly be 26 Z80 cycles, but only if the VDP were guaranteed to run at exactly 1.5 times the CPU speed and you definitely weren't using a reimplementation with slightly different logic. Neither of which need necessarily be true. So headroom required.

Well I've just realised that my research is flawed; it was based on observed behaviour of ColecoVision titles (and Galaga especially, which has a very tight read loop prior to displaying the title screen), but I failed to spot that the ColecoVision appears to contain the same M1 WAIT delay as the MSX. That's what the 74LS74A is doing in this schematic, I believe. So my present results are questionable.

This is a terrible digression, so ignore all that and keeping it on topic:

• 29 cycles if you can't be certain where you are in the frame, or know yourself to be in the middle of pixel generation; but
• OTIR is an option if you know for certain its entire loop will complete during the vertical border region.

How did you install openMSX? Using the installer?

I saw your question on IRC, but not at all times people are ready to respond. Stay on the channel longer and you'll see someone will respond after a while. But we can't respond if you leave.

I can load my cas file and see my routine go smooth until end, but I have to stay in small window. I can't use console to set fullspeedwhenloading (I can't use console at all, it doesn't open) and I can't copy the code for measuring cpu time...

Nope, cause F12 key works. Except that it make crash the emulator. But when I restart catapult (after crash) then it opens automatically in fullscreen and works fine. But still I can't open console. In the other pc (the one with windows 7), as I said, all works fine.