I installed Win2K in Parallels - everything great so far. Now i moved several projects (containing some older commandline tools) into a mapped drive which happens to be a native Mac OS folder - that's the idea, after all, to have the files available in MAC OS and also windows. Now I encounter a strange problem - example: 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. Any ideas what I am doing wrong here ? Or is this a bug in Parallels filename translations functions ? Johannes
If you Mac is using a case-sensitive filesystem (which is the default) then you must match the case exactly when using files over shared folders. Parallels had mentioned fixing this a while back, but I have not heard anything about it since.
FWIW, my MBP file system isn't case sensitive, and it came that way. Case sensitive is a format option though, and I don't know what the default is in other countries.
I'm having the same problem, and on a case-insensitive Mac partition. The funny thing is, it's clear that for most uses, the file name matching really is case-insensitive. If I cave a file called 'foo' on the mac partition, I can access it as 'FOO', 'fOO', 'Foo', etc. from the windows side. The only part that appears to have a problem is the executable search. Very strange....