Hmm... didn't think of that, but maybe you're right. My main concern in this case, given that the unwanted part preceded a DEL command, was to not affect the delete operation and somehow, in some edge case, ending up deleting more than needed (which would be catastrophic, of course). I guess I could put those commands in a batch file just to be sure there are no undesirable surprises in that regard, it's just that I'd have to use a whole bunch of skin related batch parameters to replicate what is easily done from the RunCommand measure itself...Buffer underrun in the logging display code? Missing zero string terminators?
In other words, if it's just about the RunCommand return, I wouldn't care much since I don't currently use that output. The output implies that the gibberish affects the command process itself though, not to mention that the posted parse error part is not at the end of the complete output but right smack in the middle of it. Luckily, so far, it doesn't make sense to the command interpreter, so no side effects yet.
Statistics: Posted by Yincognito — Today, 1:10 am