CODEWITHSUNDEEP
batch-filecommand-linemsp430iar
Rohan Sharma
Rohan Sharma

Reputation: 1566

Command Prompt Error 'C:\Program' is not recognized as an internal or external command, operable program or batch file

I am trying to run the following batch command. The command has been extracted from the IDE so is confirmed working. Getting the error mentioned below.

I have tried a few variations with double quotes but they haven't worked. Even on powershell it has the same message.

C:\Program Files\IAR Systems\Embedded Workbench 7.0\430\bin\icc430.exe F:\CP001\source\Meter\Main.c -D Hardware_P20E -D Calibration_code -D _Optical -D _Configuration_TS0382 -o F:\CP001\Temp\C20EO\Obj\ --no_cse --no_unroll --no_inline --no_code_motion --no_tbaa --debug -D__MSP430F425 -e --double=32 --dlib_config C:\Program Files\IAR Systems\Embedded Workbench 7.0\430\lib\dlib\dl430fn.h -Ol --multiplier=16 --segment __data16=DATA16 --segment __data20=DATA20

Command Prompt

Update:

Trying the solution with quotes confuses the compiler in some way

enter image description here

Upvotes: 74

Views: 303406

Answers (11)

user14730417
user14730417

Reputation: 21

Try putting cd before the file path.

Example:

C:\Users\user>cd C:\Program Files\MongoDB\Server\4.4\bin

Upvotes: 2

Ganesh
Ganesh

Reputation: 1

You can go to folder by doing on first line and next line call exe like below.

cd 'c:\program files\....'
.\abc.exe --install service

Upvotes: 0

emcdee
emcdee

Reputation: 11

If a directory has spaces in, put quotes around it. This includes the program you're calling, not just the arguments

"C:\Program Files\IAR Systems\Embedded Workbench 7.0\430\bin\icc430.exe"

Also - SPACES in your "${workspaceFolder}" (dir to your project) can confuse the compiler!

At least mine was throwing various errors (like that above, but I had fixed the compiler path), I finally noticed it compiled on PC 1 (dir without spaces) and would NOT compile PC 2 (dir with spaces).

Actually don't know where to put quotes ("") to make this work because ${workspaceFolder} or ${fileDirname} are a predefined variable reference in VSC...

Upvotes: 1

user14942174
user14942174

Reputation: 11

Just go to the folder path and type cmd on it. Then press ENTER enter image description here

Upvotes: 0

jaihind
jaihind

Reputation: 1130

Most of the times, the issue is with the paths you have mentioned for 'java home' and 'javac' tags in settings.xml which is present in your .m2 repository and the issue is not with your path variable or Java_Home variable. If you check and correct the same, you should be able to execute your commands successfully. - Jaihind

Upvotes: 0

Soren
Soren

Reputation: 2445

I encountered a similar problem using windows command line for R script, Rscript.exe, which is very sensitive to spaces in the path. The solution was to create a virtual path to the binary folder using the windows subst command.

The following fails: "C:\Program Files\R\R-3.4.0\bin\Rscript.exe"

Doing following succeeds:

subst Z: "C:\Program Files\R\R-3.4.0"
Z:\bin\Rscript.exe

The reason the above-proposed solutions didn't work, evidently, has to do with the Rscript.exe executable's own internal path resolution from its working directory (which has a space in it) rather the windows command line being confused with the space. So using ~ or " to resolve the issue at the command line is moot. The executable must be called within a path lacking spaces.

Upvotes: 0

DheerajS
DheerajS

Reputation: 313

You just need to keep Program Files in double quote & rest of the command don't need any quote. 

C:\"Program Files"\IAR Systems\Embedded Workbench 7.0\430\bin\icc430.exe F:\CP00 .....

Upvotes: 28

n1kkou
n1kkou

Reputation: 3142

Go to Start and search for cmd. Right click on it, properties then set the Target path in quotes. This worked fine for me.

Upvotes: -2

rjzii
rjzii

Reputation: 14563

This seems to happen from time to time with programs that are very sensitive to command lines, but one option is to just use the DOS path instead of the Windows path. This means that C:\Program Files\ would resolve to C:\PROGRA~1\ and generally avoid any issues with spacing.

To get the short path you can create a quick Batch file that echos the short path:

@ECHO OFF
echo %~s1

Which is then called as follows:

C:\>shortPath.bat "C:\Program Files"
C:\PROGRA~1

Upvotes: 24

HelloWorld101
HelloWorld101

Reputation: 4386

I believe James Hunt's answer will solve the problem.

@user3731784: In your new message, the compiler seems to be confused because of the "C:\Program Files\IAR systems\Embedded Workbench 7.0\430\lib\dlib\d1430fn.h" argument. Why are you giving this header file at the middle of other compiler switches? Please correct this and try again. Also, it probably is a good idea to give the source file name after all the compiler switches and not at the beginning.

Upvotes: -1

James Hunt
James Hunt

Reputation: 2528

If a directory has spaces in, put quotes around it. This includes the program you're calling, not just the arguments

"C:\Program Files\IAR Systems\Embedded Workbench 7.0\430\bin\icc430.exe" "F:\CP001\source\Meter\Main.c" -D Hardware_P20E -D Calibration_code -D _Optical -D _Configuration_TS0382 -o "F:\CP001\Temp\C20EO\Obj\" --no_cse --no_unroll --no_inline --no_code_motion --no_tbaa --debug -D__MSP430F425 -e --double=32 --dlib_config "C:\Program Files\IAR Systems\Embedded Workbench 7.0\430\lib\dlib\dl430fn.h" -Ol --multiplier=16 --segment __data16=DATA16 --segment __data20=DATA20

Upvotes: 62

Related Questions