Hi,
FYI snapin client does not expand system variables, so don’t use them they don’t work:
[quote=“Jbob, post: 34657, member: 21733”]Can confirm that the snapin client does [B]not[/B] expand system variables. Adding this feature to my todo list with high priority. The reason is that the snapin client uses:
[code]p.StartInfo.FileName = strRunWith;[/code]
instead of
[code]p.StartInfo.FileName = Environment.ExpandEnvironmentVariables(strRunWith);[/code]
In the mean time you may just set the “Snapin Run With” to msiexec.exe, this will automatically find the file if it has been added to the system path, which windows does by default.[/quote]
[url]http://fogproject.org/forum/threads/fog-snapins-and-windows-system-variables.11288/#post-34657[/url]
cscript is in path you should call cscript msiexec and so on. without any path
To check what’s in PATH open a command prompt and type:
[CODE]echo %path%[/CODE]
That will give you (normally) a list of directorys that are in path, that means every executable file that belongs to a path directly can be run without any path to the binary:
[CODE]C:\Users\Administrator>echo %path%
C:\Program Files\SFX-CreatoR;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Com
mon;C:\Program Files (x86)\Business Objects\Common\3.5\bin\NOTES;C:\Program Fil
es (x86)\Business Objects\Common\3.5\bin\NOTES\DATA;C:\Windows\system32;C:\Wind
ows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Prog
ram Files\Calibre2;C:\Program Files (x86)\H-JTAG V0.4.0;C:\Program Files (x86)
Ford Motor Company\IDS\Runtime;C:\Program Files (x86)\MakeMsi" ;C:\Program Files
(x86)\GNU\GnuPG\pub[/CODE]
Regards X23
