white spaces in command line

[sergega4]

Hi
I m in trouble with a white space included in the path of an .exe file.
Precisely located in Program Files/...
How to deal with the launching of a command that calls this .exe ?

CreateProcess(NULL, ligne_de_com, NULL, NULL, FALSE,
CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &StartInfo, &Process)

According to the fact that the parser will stop after Program !
Any idea of the usual trick ?
For instance how Windows deals with the launching of the "execute" command
when it includes something in Program Files ?

Thanks for pieces of advice.

Regards

Xavier

[Sebastian Dau]

"se******@yahoo.fr" <se*************@discussions.microsoft.com> wrote in
message news:B8**********************************@microsof t.com...

Hi
I m in trouble with a white space included in the path of an .exe file.
Precisely located in Program Files/...
How to deal with the launching of a command that calls this .exe ?

CreateProcess(NULL, ligne_de_com, NULL, NULL, FALSE,
CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &StartInfo, &Process)

According to the fact that the parser will stop after Program !
Any idea of the usual trick ?
For instance how Windows deals with the launching of the "execute" command
when it includes something in Program Files ?

Thanks for pieces of advice.

Regards

Xavier

Have you tried to quote the path string just like: "c:\program files\...".
You have to put the quote signs the string!

Good Look! Sebastian Dau

[sergega4]

thank you for answering but what you mean by "signs the quote" ?
since that you declare
CString ST="C:\Program Files\..."
or
char T[100];
strcpy(T,"C:\Program Files\...")
the result will still be that a white space WS will remain between Program
and Files, WS missunderstood by the command line parser unable to achieve the
task.
Xavier
"Sebastian Dau" wrote:

"se******@yahoo.fr" <se*************@discussions.microsoft.com> wrote in
message news:B8**********************************@microsof t.com...

Hi
I m in trouble with a white space included in the path of an .exe file.
Precisely located in Program Files/...
How to deal with the launching of a command that calls this .exe ?

CreateProcess(NULL, ligne_de_com, NULL, NULL, FALSE,
CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &StartInfo, &Process)

According to the fact that the parser will stop after Program !
Any idea of the usual trick ?
For instance how Windows deals with the launching of the "execute" command
when it includes something in Program Files ?

Thanks for pieces of advice.

Regards

Xavier

Have you tried to quote the path string just like: "c:\program files\...".
You have to put the quote signs the string!

Good Look! Sebastian Dau

[Tamas Demjen]

se******@yahoo.fr wrote:

CString ST="C:\Program Files\..."

"\"C:\\Program Files\\...\""

Tom

[sergega4]

"Tamas Demjen" wrote:

se******@yahoo.fr wrote:

CString ST="C:\Program Files\..."
"\"C:\\Program Files\\...\""

Thanks it seem to match but why ?
Every ones knows that one should "unspecialize" the \ doubling it, obviously
for not letting the compilator parser considere \Program like \P(followed by
rog..) but why could it fix the trouble induced by the presence of WhiteSpace
? I'd like to know.
X

Tom

[Sebastian Dau]

"se******@yahoo.fr" <se*************@discussions.microsoft.com> wrote in
message news:C3**********************************@microsof t.com...

thank you for answering but what you mean by "signs the quote" ?
since that you declare
CString ST="C:\Program Files\..."
or
char T[100];
strcpy(T,"C:\Program Files\...")
the result will still be that a white space WS will remain between Program
and Files, WS missunderstood by the command line parser unable to achieve the task.
Xavier
"Sebastian Dau" wrote:

"se******@yahoo.fr" <se*************@discussions.microsoft.com> wrote in
message news:B8**********************************@microsof t.com...

Hi
I m in trouble with a white space included in the path of an .exe file. Precisely located in Program Files/...
How to deal with the launching of a command that calls this .exe ?

CreateProcess(NULL, ligne_de_com, NULL, NULL, FALSE,
CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &StartInfo, &Process)

According to the fact that the parser will stop after Program !
Any idea of the usual trick ?
For instance how Windows deals with the launching of the "execute" command when it includes something in Program Files ?

Thanks for pieces of advice.

Regards

Xavier

Have you tried to quote the path string just like: "c:\program files\...". You have to put the quote signs the string!

Good Look! Sebastian Dau

As Tamas wrotes...

"\"text\"" means putting quote signs into a string variable...

Sebastian Dau

[Tamas Demjen]

se******@yahoo.fr wrote:

Thanks it seem to match but why ?

Because the operating system and the CreateProcess function treat
everything delimited by double quotes as a single path. This is one way
to get around the space in filename problem. The other one is using the
GetShortPathName API function, which converts long file names to short
ones (with no spaces).

Tom