I think I missed your point ("answers ... matter").
It seems there is a third command line issue: the PATHEXT entry. Most installers handle the fourth, the PATH entry. But ".PL;" needs to be included in PATHEXT. And then there are the previously discussed ASSOC and FTYPE settings.
| [reply] |
I think I missed your point
Ok, do you have a question that you need an answer for? A question that is important to answer? Are you still experiencing a problem that needs solving?
This looks not important Does the symbol used in the assoc/ftype values appear anywhere else than these two commands?
This looks not important Specifically, does it matter whether the symbol used is "Perl" or "PerlScript" (or, for that matter, in lc or with caps)?
And now you say It seems there is a third command line is... ... which seems like equal parts vague and non-important
| [reply] |
