[Bug 10618] dll/kernel32/process. c build_argv returns incorrect argv array for a given command line string

http://bugs.winehq.org/show_bug.cgi?id=10618

Darragh Bailey  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #4 from Darragh Bailey   2008-03-18 18:58:08 ---
It appears this is not a bug really. Ran a test by building the following code
on windows with the command line:
/I C:\DOCUME~1\admin\LOCALS~1\Temp\IXP001.TMP\XLVIEW.MSI CDCACHE="2"
LAUNCHEDFROMSETUP="1"
SETUPEXEPATH="C:\DOCUME~1\admin\LOCALS~1\Temp\IXP001.TMP"
SETUPEXENAME="SETUP.EXE"

#include "stdafx.h"

int _tmain(int argc, _TCHAR* argv[])
{
        int i;
        for(i=0; i<argc; i++) {
                printf("argv[%d] = "", i);
                for(int j=0; argv[i][j] != '\0'; j++) {
                        printf("%c", argv[i][j]);
                }
                printf(""\n");
        }
        return 0;
}

Outputted result was as follows.
argv[0] = "printargs.exe"
argv[1] = "/I"
argv[2] = "C:\DOCUME~1\admin\LOCALS~1\Temp\IXP001.TMP\XLVIEW.MSI"
argv[3] = "CDCACHE=2"
argv[4] = "LAUNCHEDFROMSETUP=1"
argv[5] = "SETUPEXEPATH=C:\DOCUME~1\admin\LOCALS~1\Temp\IXP001.TMP"
SETUPEXENAME=SETUP.EXE"

Basically this proves that wine is building the argv correctly, but msiexec has
custom handling of the command line since when run with the same command line
it has no such problems, and adding the /l*v to see the command line shows that
it reads in the properties correctly.

Sorry for the noise