Re: May we use winelib-wcmd as $COMSPEC command processor?

[Alexandre Julliard]

Uwe Bonnes  writes:
> Pointing $COMSPEC to the winelib wcmd processor doesn't work as expected, as
> CreateProcess tries to execute wcmd as windows executable, as CeateProcess
> is called like:
>
> Call kernel32.CreateProcessA(40c8248f\
> "h:/tmp/wine/compile/wine/programs/wcmd/wcmd",40c8ff1c\
> "h:\tmp\wine\compile\wine\programs\wcmd\wcmd /c\
> I:\xilinx\bin\nt\ChipView.bat -f magcom.vm6",...

If you simply set COMSPEC to "wcmd.exe" it should work I think
(assuming wcmd.exe.so is in your WINEDLLPATH of course).