hi all..
when i run Setup.exe /s or /r /f1(path\setup.iss) it seem to run through the normal install process but the actual file is not getting created in the specified folder or within C:\windows.
what im trying to do is create an answer file for the .msi installation
thanks in advance...
fresko
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
missing setup.iss
Started by
FRESKO
, Nov 03 2009 03:47
4 replies to this topic
Posted 03 November 2009 - 09:22
The .iss answer file concept only works for InstallScript setups, not for MSI setups.
Instead, either set the properties on the command line or create a transform for this purpose. If you don't need to adjust the selection but accept the defaults, you can simply run the setup in silent mode:
msiexe.exe /i your.msi /q
If the msi is packaged inside a setup.exe it will depend on that exe how to set silent mode. For InstallShield this would be:
Setup.exe /s /v"/qn"
Instead, either set the properties on the command line or create a transform for this purpose. If you don't need to adjust the selection but accept the defaults, you can simply run the setup in silent mode:
msiexe.exe /i your.msi /q
If the msi is packaged inside a setup.exe it will depend on that exe how to set silent mode. For InstallShield this would be:
Setup.exe /s /v"/qn"
Stefan Krüger
InstallSite.org twitter facebook
Posted 04 November 2009 - 07:35
just to add... i had this problem earlier on and found a cure for this...
if the software is prompting for a reboot after the install.. add this and it should suppress the reboot..
/qn REBOOT=ReallySuppress"
FRESKO
if the software is prompting for a reboot after the install.. add this and it should suppress the reboot..
/qn REBOOT=ReallySuppress"
FRESKO
Posted 04 November 2009 - 09:52
QUOTE (FRESKO @ 2009-11-04 07:35) |
add this and it should suppress the reboot.. /qn REBOOT=ReallySuppress" |
...provided of course the packager relied on the Windows Installer reboot triggers and didn't use a Custom Action. Like Symantec do. And IBM. And Adobe.
It's good general advice, though.
- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.
- Try using http://www.google.com before posting.
- I answer questions only via forums. Please appreciate the time I give here and don't send me personal emails.