🚀 go-pugleaf

"Remy Lebeau \(TeamB\)" wrote:
>"Bob Gonder"  wrote in message
>
>> I believe the docs suggest that you supply a full
>> command line as the second parameter, even if
>> you use the first also.
>> ie:
>> CreateProcess( "Command.exe", "Command.exe Parameters",....)
>
>That would probably do it, but I haven't tested it yet.  Though, I get no
>such impression from reading the docs as to needing to do that.

Quote:
If both lpApplicationName and lpCommandLine are non-NULL,
*lpApplicationName specifies the module to execute, and *lpCommandLine
specifies the command line. The new process can use GetCommandLine to
retrieve the entire command line. C runtime processes can use the argc
and argv arguments. 

To me, that implies lpApp.. is Not passed..only lpCommandline is
passed.  Since by convention, the first parameter on the command line
is the executable....  Also note:

Windows NT: If the executable module is a 16-bit application,
lpApplicationName should be NULL, and the string pointed to by
lpCommandLine should specify the executable module.

This is saying lpCommandLine should be the entire command line (in a
certain case).  It seems reasonable to me that Windows would just pass
lpCommandLine to the command line parser, without any funny business.