I have a prepackaged NSIS installer exe which I want to make fully silent or an unattended installer. I used switches like : /S and /NCRC /S but still when I run it, still windows show up asking to click NEXT ACCEPT ....
Is there any other solution for this?
Please help I'm new and just want to have an unattended installer from that prepackaged software.
Passing the /S switch (CASE sensitive!) is not enough: you need to write the installer to be really silent.
Do you have sources (scripts) for your installer? What you need is to
Detect silent mode (IfSilent)
Update MessageBox with /SD parameter to let installer know what button to 'click' in silent mode
Solve your Sections
Check this example and made appropriate changes: http://nsis.sourceforge.net/Examples/silent.nsi
Related
I am having a 3rd party software in my machine. Let the name be Temp.msi
Now I need to uninstall this software when I am installing my setup (setup.exe).
It should not ask for any prompt, is there any way in installshield to do that?
If you have the msi which was used to install the software, You can create a custom action that performs silent uninstall of that product by using:
msiexec /uninstall <msi file> /quiet
(or, for Windows XP/2003: /x <msi file> /qn)
If you don't have the original msi, you need to know, or figure out, the Product Code of that software and use
msiexec /uninstall <product code> /quiet
Figuring out the product code can be done in several ways, a lot of information about it is available, such as here.
I am writing an Inno setup kit where I need to install various updates like Service Pack 3 for XP, DotNet Framework 4 and etc.
My problem is I want to make a generic kit which will take any exe and run it in silent mode i.e. unattended installation. I am aware of different flags that will do these for e.g. for SP3 /quiet and for DotNet framework /q. I would like to know how can I make my inno setup kit a generic one so that whatever exe I pass, it should install it in silent mode.
I'm trying to install some software packaged using ISMP (InstallShield Multi Platform). I'm trying to do a silent mode install something like ./setup.bin -silent which does the installation completely. But, I want to have an option to install specific features using some properties file or something similar in silent mode. Any help would be appreciated. Thanks.
I need to install vcredist_x86.exe (Microsoft Visual C++ 2010 Redistributable Package) quietly. I entered "vcredist_x86.exe /q" on cmd.exe. However, vcredist_x86 didn't install successfully. I used Task Manager to inspect what happened. I found out that a process named "msiexec.exe" keeps alive until you kill it.
VC++ 2005 is made with older version so arguments /q (/qb) or /passive /norestart will not work (mentioned here: http://blogs.msdn.com/b/astebner/archive/2010/10/20/10078468.aspx).
For quiet mode use /Q switch, to get all parameters run vcredist_86.exe /?
To silently install the VC redist, merge the vc redist MSM into your own App's MSI and avoid the need to run a separate EXE at all.
Martyn
PS: Don't kill msiexec. You'll get your machine into a bad state.
My Windows application runs under Wine, but the installation is a bit of a headache for laymen, and the wrappers I've seen online (PlayOnLinux, Wine Doors) require even more packages to be installed. Is there a way to make a package that will install Wine if the user needs it to be installed, install the application and shortcuts, all with minimal user hassle?
I don't believe there's any pre-made way to do this, but you could probably make a Debian package pretty easily that would depend on Wine, copy an MSI onto the machine, then run Wine's msiexec /i /q as the post-install script
Edit: Make sure to think about the uninstall case too! I.e. in the pre-uninstall script, run msiexec again as well.
You can bundle Wine -- that's what Picasa does -- or you can just make your package list Wine as a dependency; then the user's package manager will automatically install Wine for the user when they install your package.
Ideally your Linux package wouldn't run the Windows installer, but rather have all the files already unpacked.
The trick is to arrange for the files your package installs in /usr to show up in each user's .wine directory. You can look at how Picasa does this, but really the Wine community needs to document how to do this much better.
As always, ask at winehq.org if you need more info.
If you'd like to target the Mac OS, you can use WineBottler:
http://winebottler.kronenberg.org/
This project exists just for bundling Wine into a native Mac .app bundle in a way that's fairly hidden from the user.
Answer is simple:
Create Elf installer.
Pack Elf installer onto Exe installer resources.
Exe installer should unpack Elf installer on startup.
Exe installer must tries to run Elf installer after unpack (system call or some think).
If operation fail, we do normal install.
If operation didn't fail, we close Exe installer.