SvarCOM: a batch file that has character 01AH will be interpreted as a "Bad command or file name"

[igully]

In a batch file, a single line containing character 01AH will be interpreted as a "Bad command or file name" using SvarCOM. On MS-DOS, PC-DOS, etc., it will simply be ignored.

I am attaching an example file that showcases this behavioral difference.

TEST.zip

[mateuszviste]

That's an interesting case. Or rather - an interesting question - how is a shell interpreter expected to process control characters inside a batch file? Does it depend on the control character, or should they all be treated equal? I do not think this is documented, so it definitely needs testing to figure out the rules.

BTW is there any functional signification behind the 0x1A character in the batch file that triggered the issue for you? Is the CTRL+Z character supposed to end the processing of the batch file, or is it just an attempt to hide part of it when users display the batch file with TYPE?

[igully]

I came to this finding by accident: I was testing a very tiny text editor (below 4KB in size), and using it for several text related tasks. It seemed that the editor, appended the 01AH character as the end of file char. So, this went unnoticed until I exchanged batch files to SvarDOS and this abnormality showed up.