1

On bluemsx, for the machine just labelled MSX, adding a '.' full-stop after SCREEN 2 and typing various different types of rubbish does not generate a syntax error message .

SCREEN 2.11111

Noticed this when trying to see if there were any hidden screen-modes for faster graphics ( I have read about why msx is so slow and about the chip, but thought maybe a completely unknown mode may exist inherited from an earlier version of the chip, a single color monochrome mode.

  • What is a 'bluemsx'? Mind to add information about the environment like macine and MSX version? – Raffzahn Feb 26 at 0:48
  • The single colour monochrome mode is SCREEN 0, though you lose sprites and it’s technically a reprogrammable character map; you can also use SCREEN 2 and just don’t upload new colour attributes — it’s basically a 1bpp mode in which you set the palette at 8x1 precision. So just update the pixels, not the colours. Lots of lazy Spectrum ports do it. – Tommy Feb 26 at 1:28
6

On bluemsx, for the machine just labelled MSX, adding a '.' full-stop after SCREEN 2 and typing various different types of rubbish does not generate a syntax error message .

SCREEN 2.11111

This doesn't look like 'rubbish' but a valid floating point number. A number is a valid parameter to SCREEN, so no reason to raise any 'Syntax Error' - try real rubbish, for example SCREEN 2.abc and you'll get the desired error.

When interpreting BASIC collects all digits and uses the integer part - '2' in this case - which is a legal screen mode, thus no reason to raise an 'Illegal Function Call' error.

Bottom line: Nothing to see here, everything as expected.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.