From the desktop shortcuts I:
1. started the shell (i.e. either cmd.exe or TCMD)
2. cd \Users\gordon
3. set > xxx_set.lst for xxx of either cmd or tcmd
4. closed the shell
and then compared the two files.
There were three differences of the sort that seems reasonable.
ComSpec...
The cmd.exe and TCMD runs were done one after the other with no known
changes to anything between them. Both were started from desktop shortcuts
and closed after running a single command pasted in.
Adding the VS2010 argument (Intel seems to suggest it is second!) may
be a workaround. And...
From the manual "Take Command Language - A mature scripting language based on and compatible with CMD, but massively enhanced."
Perhaps there is some other definition of compatible. Matching undocumented
features is sometimes a moving target. I had expected there might be
switches, but...
I have been dealing with the responses that have arrived by email.
What is it that an I supposed to be doing?
The cmd.exe and TCMD are executed one after the other with no attempt
to change the environment. If the two programs think the environment has changed then their dealing with the...
>> You need to figure out why the variable isn't being set.
That is why I posted the fact that the same batch file executed by cmd.exe
and TCMD yield different results. One of the two has an undocumented feature
(aka bug) that goes beyond the TCMD options of duplicating the cmd.exe bugs...
Capturing the output from was straightforward. For TCMD it required recalling
how to capture both output and errors. I removed the TCstart to keep things
simple.
Not much similarity visually as cmd.exe substitutes the values for variables
while TCMD gives the variables. Anyway the two...
Reloaded TC13. The options are under TCC options. Duplicate cmd.exe bugs seems on be default. This on a Windows 7 (64-bit).
With both options off the top ifortvars.bat yields a usage diagnostic so does not get very far.
With either just cmd.exe bugs or both options set the result is the...
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.