New game for MSX1 (Transball)

Just a quick guess here: RAM might be faster compared to ROM on turboR, so if your code has active wait-loops it might make a difference in R800 mode ? (Assuming ODO loads in RAM and other ways load in a ROM)

Flashing the rom in a flashrom, stage 5 works ok.

Where do you initialize the stack?

santiontanon: This indeed starts to sound like that ODO does not initialize stack and you don't initialize stack... Stack is very much lower in MSX-DOS (~$E800) than when starting from cartridge ($F380). I would anyway say that what ever the problem is, it is not your problem. ODO needs to be fixed, not your program.

Hi NYYRIKKI. Sorry, I disagree with your statement. ODO can't initialise the stack, because the games using DOS will stop working.
If Transball does not use DOS, should initialise the stack. Remember:

DI
IM 1
LD SP,#F380
[your awesome code here]

Anyway, ODO is able of run game forcing boot. You can hold [CTRL] key, while the game is loading, to force reset. And Transball, magically, works.

This is very simple: ROM games can't ever expect disk system to be present. If they need disk routines, they need to exit and init them self later though hooks when disk system has been initialized. (like ie. Konami Game Master does)

In theory it is nice idea if cartridge checks that it has enough stack space, but usually game cartridges are placed in slot 1 and in case of error there is very little the cartridge can do (except displaying error or defining the whole operating environment again by clearing hooks etc.) -> I find this relatively useless check and I don't expect many cartridges do that. In perfect world all programs would consider all the possible tricks that users can imagine using all kind of external programs, memory managers and such, but turning it to responsibility of developer is a bit overkill as: 1) I think it is reasonable expectation for ROM developer to expect that the ROM is first thing MSX executes after boot & init. 2) it causes extra work, needs extra space and even then MSX does not have mechanisms to protect it self from serious user errors.