I have been trying to use the Intel Parallel Studio from the command line (and avoid MS Visual Studio xxxxx). It requires the execution of a batch file to set up multiple environment variables depending upon the target architecture and which version of VS is installed, etc. All too common. Under cmd.exe it works as the Intel folks intend. They must have used it for their development. But cmd.exe is so friendly I have used JPSoft stuff for a long time. Under TC13 I get a "unknown command amd64" because there is a line which looks like "call %xx% %yy%" where xx is null and yy is amd64 so the error message makes sense for that line. But why is xx null? It seems cmd.exe is able to set xx but TC13 skips that. Aren't things supposed to be compatible? Under TC10 (pain in the you know where to switch back and forth) I get an "invalid argument at" with none of the apparent blanks filed in. Even less useful than TC13. What magic switches are needed to get TC to produce the same execution of the Intel batch files?