Unable to start program c:windows_ system32_ cmd.exe

Unable to start program c:windows_ system32_ cmd.exe

Bild des Benutzers Richard

Hi
My System is installed dualOSVista(C:\ Drive) and XP(D:Drive).
Intel Parallel Studio installed XP System on D: Drive
step-1.Create test C++ Project
step-2.setting to use intel project
step-3 program build=> success
step-4 try to excute program with Menu Debug=>Start without debugging(Ctrl+F5)
I got error messages "Unable to start program c:\windows\system32\cmd.exe"

project set to use visual C++ and program build ==> prgram excute is OK!!

Intel Paralle Studio version is "Intel Parallel Composer (Package ID: composer.061)"

Richard

4 Beiträge / 0 neu
Letzter Beitrag
Nähere Informationen zur Compiler-Optimierung finden Sie in unserem Optimierungshinweis.
Bild des Benutzers Jennifer J. (Intel)

Try this:
1. close VS
2. add "c:windowssystem32" to your PATH env-var - from my Computer-> Advance->Environment Variables....
3. restart VS, load the project, and run again.

Please respond if this solves the problem.

Thanks,
Jennifer

Bild des Benutzers Richard
Quoting - Jennifer Jiang (Intel) Try this:
1. close VS
2. add "c:windowssystem32" to your PATH env-var - from my Computer-> Advance->Environment Variables....
3. restart VS, load the project, and run again.

Please respond if this solves the problem.

Thanks,
Jennifer

Hi Jennifer,
My XP System is installed on D:windows.
cmd.exe location is d:windowssystem32cmd.exe.
I don't understand why composer find to "c:windowssystem32cmd.exe"

when I tested visual c++ project ==> excute OK!!(start without debugging Ctrl+F5)
when I testedintel c++ project ==> excute Error!! (start without debugging Ctrl+F5)
error message is "Unable to start program c:windowssystem32cmd.exe"

Richard

Bild des Benutzers Jennifer J. (Intel)
After checking with our compiler engineers, this is a bug in our IDE integration.

In this case, the IDE integration is able to find "C:windowssystem32cmd.exe", but could not launch it because it's under Vista.
So the work-around is to rename the "C:windowssystem32cmd.exe" to "...cmd_vista.exe".

If there's any better work-around, I'll let you know.
Or if anyone else found a better work-around, please post here.

Thanks!
Jennifer

Melden Sie sich an, um einen Kommentar zu hinterlassen.