I confess I don't understand the problem. But I do wonder whether the USB (portable) registration option might work around it.

I don't know what all C#Run does, but I suspect you may be seeing the effects of disk caching there.

... Or if you pass it the name of an existing file.

I like it — an explanation of mojibake, which unintentionally contains further examples of mojibake. Self-referential mojibake.

Note that in the screenshot above, both the selection highlight and the status bar are invisible. I'm pretty sure that SELECT uses SelectStatBarColors for the selection highlight if it's defined, and falls back on reversing the default colors when SelectStatBarColors is not defined.

I'm not clear on how these newfangled "default" foreground and background colors appear to the old-style, 16-color EGA-type calls. As duplicated nybbles, like 0x00 or 0x11? I can see how that would lead to problems in older, non-ConPTY-aware commands like SELECT.

SelectStatBarColors=bri whi on blue It goes in the 4NT section.

Perhaps on the Windows tab. (These two were documented in the (excellent) printed manual, back in the day.)

The selection highlight in SELECT is the same as the status bar color: option //SelectStatBarColors=bri whi on blu select echo ( * )

That actually makes sense to me. ENDLOCAL restores any variables that were changed within the SETLOCAL/ENDLOCAL block, including (potentially) PATH.

It's been a very long time, but.... I think that distinction applied to MS-DOS 8.3 filenames. Not to the long filenames which we've been using since 1995. Or earlier, if you were using Windows NT.

Alternatively: Any change of resurrecting the wiki? Maybe making it invitation-only, at least to start?

The grave accent is the one you call the backquote.

Blue-skying here: If users could attach comments to pages in the web help, and make them publicly viewable, then... you might have even more documentation.

Incompatible platforms are not compatible.