Msg #,# (sys:<filename>)

This occurs when the message number (#,#) is not found in the message file whose name is in the (parentheses.) Usually this is because you updated the A-Shell executable but not the message files, and the new version of A-Shell is trying to use a new message that wasn’t previously there. In that case, just download the latest A-Shell release to get the latest message files. Another possibility is that the message file has become corrupted. To check, just VUE it and then resave it. A third possibility is that your language definition file is not right, and so A-Shell is trying to use a non-existent message file extension. If the <filename> mentioned in the message does not exist, check your LANGUAGE= statement in the miame.ini to make sure that it references a valid language definition file. If it is simply a matter of you using a language file that we don’t provide a set of messages for, copy one of the others (with the same filename and different extension) to the desired extension, and then you will at least have messages (although perhaps not in the desired language.) Feel free then to use VUE to edit the message file and translate the messages.