Yes, and it's a good decription of procedure worth adding to main help. It
would also be nice for the other major method to work though, and I
discovered that one simple change will do it.
C:\WINDOWS\Desktop>F:\TCC\TCC.EXE F:\TCC\EXAMPLES\HELLO_~2.C
F:/TCC/EXAMPLES/HELLO_~2.C:1: unrecognized file type
C:\WINDOWS\Desktop>F:\TCC\TCC.EXE F:\TCC\EXAMPLES\HELLO_~2.c
These show that TCC is only accepting the lower case C in the manually
edited drag/dropped auto-written shortname path. If TCC were edited to
allow both cases for that .c extension, all would be well. It's not that
it needs to understand these paths at all, it just has to not block them
because the second instance worked fine, so clearly that business with the
tilde and the numbers doesn't bother TCC at all. Just needs C as well as c
to be accepted.