installshield silent/unattended:
installer.exe /r (record your answers into c:\Windows\setup.iss)
[InstallShield Silent] Version=v7.00 File=Response File [File Transfer] OverwrittenReadOnly=NoToAll [{93D43786-ECE3-48BC-937D-8B887EA33476}-DlgOrder] Count=0
For the unattended silent installation:
installer.exe /s /sms (with the setup.iss in the same directory)
(If you use renaming of setup.iss beware it strips non-alphanumerics)
Many packages have "custom dialogs" which are not supported by setup.iss, which means the dialogs will always appear no matter what you do. For such packages, I suggest asking the vendor to fix their installer.
When things go wrong you can look at the setup.log to see what kind of errors:
C:\Documents and Settings\user\Local Settings\Temp{14B42000-AAB1-4BBA-B30B-E54D8B1C56A1}\Disk1
[InstallShield Silent] Version=v7.00 File=Log File [ResponseResult] ResultCode=-5
0 Success -1 General error -2 Invalid mode -3 Required data not found in the Setup.iss file -4 Not enough memory available -5 File does not exist -6 Cannot write to the response file -7 Unable to write to the log file -8 Invalid path to the InstallShield Silent response file -9 Not a valid list type (string or number) -10 Data type is invalid -11 Unknown error during setup -12 Dialogs are out of order -51 Cannot create the specified folder -52 Cannot access the specified file or folder -53 Invalid option selected
this means that setup.exe /s /f1"c:\setup.iss" is better! (couldn't find the file!)
If you have an .exe that wraps/extracts 2 .exe's that you then run one and it extracts an .msi
msiexec /i FILENAME.msi /q
(this will actually work!)