[YEIH]

Hi,

I have created an exe that contains msi and some configuration files using 7 zip.
This works fine on most OS as far as I can tell but when we brought this to our customer site, it failed to launch our msi file.
I ran procmon and noticed that msiexec was looking for msi file in C:\ instead of temp folder that 7 zip created to extract msi and configuration files.
FYI, I tried to run 7 zip program to extract installer exe and I was able to extract them without any issue.

I tried to figure out why this happened but I could not and the issue is that I cannot reproduce this strange behavior locally.

Has anyone seen this behavior before? If you have any insight/suggestion, please let me know. Thanks.

FYI, here is my 7 zip conf file.

;!@Install@!UTF-8!
Title="XXProgram Setup Installation"
BeginPrompt="Do you want to install XXProgram on your computer?"
Directory="C:\\Windows\\System32\\"
RunProgram="cmd.exe /c copy /v configuration.conf C:\\Windows\\temp\\ & msiexec.exe /i setup.msi"
GUIMode="2"
;!@InstallEnd@!



YEIH

This post has been edited by YEIH: 03 November 2009 - 11:18 AM

[ricktendo64]

You dont need to use msiexec or msistub anymore to launch msi installers its built in and you dont have to use & to launch a seperate install process you can use as many RunProgram lines as you like...try

;!@Install@!UTF-8!
Title="XXProgram Setup Installation"
BeginPrompt="Do you want to install XXProgram on your computer?"
Directory="C:\\Windows\\System32\\"
RunProgram="cmd.exe /c copy /v configuration.conf %windir%\\temp\\"
RunProgram="setup.msi"
GUIMode="2"
;!@InstallEnd@!

[YEIH]

Thank you very much for your reply.
I tried your suggestion but setup.msi was not launched at all. Basically exe quitted after copy was done.
FYI, I create exe in linux box and I am just wondering if that caused the issue. Thank you again for your input.

YEIH

[strel]

I think ricktendo is referring to 7-zip sfx modified module. Switch to russian to access to the latests version links.