I wrote that you tell me and the acronim of msx2 had a loop with a beep, but the pixels didn't pop up.
I hoped to hear "yeah I see lines!" 
We were doing stuff in parallel.
Now I finished the compiler issues. Older scripts are broken.
pset() of cio.c never works, and that is not compiler issue, but MSX issue. Need to call subrom.
Wait ouch, I missed a point of last posting!
the hex2bin -l doesnt work and the -m is needed.
the -l made bad mirroring things to me.
I got new hex2bin from sourceforge.
ok and now with the newest script and crt0, I dont get troubles with the -l option anymore.
I don't see the line
How can I active the subrom?
I'm not able to active the subrom, hit9918 help me please to do it.
"can't see the line", which line, my line or your line.
I have the feeling that you never really tried my codes but kept modding your own.
one bit wrong in the script and it all explodes. then I got no idea why there is no line.
subrom needs 3 interslot calls for a pset, it crawls like a BASIC.
out() based things are better on so many levels.
e.g. a drawRAMimage() based on otir() (and no additional inline asm needed) with LMMC would be able to reach all 64k RAM, subrom won't. except it does even more slotflip.
"can't see the line", which line, my line or your line.
I have the feeling that you never really tried my codes but kept modding your own.
one bit wrong in the script and it all explodes. then I got no idea why there is no line.
It's not true than i' ve never really tried, indeed I hear continually a beep but I don't see my line in the screen.
Do you see your line in the bluemsx screen ?
yes, I did see it with bluemsx msx2.
and in openmsx, there it also prints "DI HALT detected", so it finished as planned.
yes, I did see it with bluemsx msx2.
and in openmsx, there it also prints "DI HALT detected", so it finished as planned.
I didn't see the line, can you make me understrand why I didn't see the line?
My bluemsx had continually a reset and every reset I hear a beep.
