This is really more of a praise-for-TCC post than a bug report, but there is one small item to be addressed, as follows. I often run .BAT files formatted in UTF-8. In general, my UTF-8 files have a BOM at the top. However, cmd.exe and powershell both balk at such files. Upon encountering the BOM, they throw out the whole first line of the .BAT file as unintelligible (even in cp 65001!). I thus find myself often going back into my editor and manually removing the BOM from these files in order to run them. I was extremely pleased to find that TCC does not balk at these files at all, and does indeed execute all commands within the batch file as intended. However, when running the batch file, TCC does still output a few garbage characters to the screen, corresponding to the characters that comprise the BOM at the start of the file. I believe that this is a bug; the BOM is meant only to indicate the format of the file, and should not be output to the screen as if it containing characters to be processed.