In a previous thread, jrietschel pointed out
That seems to fix it. Of course, to be really correct, you would have to past in copies for 'Com', 'cOm', etc. But for me, 'COM' and 'com' cover everything that I actually encounter.
I'm pretty sure, though, that this will only work if your Mac partition is case-insensitive (which is the default).
After poking around a bit, I've got a work-around: In My Computer->Properties->Advanced->Environment Variables, there is an entry for PATHEXT. This is the set of suffixes that windows will match up to a bare command name. By default, it contained all uppercase suffixes. I just added lowercase copied of each one, so that the final value looks like this:tool "tokenizer.exe" is in the local directory (which is a MAC native path)
trying to execute it from commandline ("tokenizer") does not work - not found
renaming it to 8.3 format ("token.exe") does not work either
renaming it to uppercase letters ("TOKEN.EXE") does still not execute if i type in "token",
but if I enter TOKEN then the file is found and executed.
Code:
.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.w
I'm pretty sure, though, that this will only work if your Mac partition is case-insensitive (which is the default).