May we use winelib-wcmd as $COMSPEC command processor?
Uwe Bonnes
bon at elektron.ikp.physik.tu-darmstadt.de
Sun Sep 8 14:26:46 CDT 2002
>>>>> "Alexandre" == Alexandre Julliard <julliard at winehq.com> writes:
Alexandre> Uwe Bonnes <bon at elektron.ikp.physik.tu-darmstadt.de> writes:
>> > echo $COMSPEC wcmd.exe (I added an echo command to winewrapper)
>> WINEDLLPATH
>> /home/bon/tmp/wine/compile/wine/dlls:/home/bon/tmp/wine/compile/wine/programs
>>
>> 088fccb8:Call kernel32.CreateProcessA(40c8248f "wcmd.exe",40c87f04
>> "wcmd.exe /c I:\\xilinx\\bin\\nt\\ChipView.bat -f magcom
>> .vm6",405c6c3c,405c6c3c,00000001,00000000,00000000,00000000,405c6bf8,405c6be8)
Alexandre> The app is passing COMSPEC as application name to
Alexandre> CreateProcess, so my suggestion won't work, you have to make
Alexandre> COMSPEC a full path. Setting it to
Alexandre> "c:\windows\system\wcmd.exe" should work.
It works with a winelib executable, when COMSPEC points to the real file. As
our present built system creates .exe.so files, comspec must specify this
existing .exe.so file (or the .exe.so file must be renamed to an .exe
file). Just as a reference for others...
Bye
--
Uwe Bonnes bon at elektron.ikp.physik.tu-darmstadt.de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
More information about the wine-devel
mailing list