Software Deployment

Does it need some input in the UI mode?? if so you need to pass those parameters also while installing silently.....check by installing in normal UI mode .

ORIGINAL: Bankeralle

im trying to install a NSIS package silent.

[:@]I have tried adding the parameter /S. This starts the setup silent, but quits almost immidiatley.

Any tips would be appriciated:-)


Perhaps you need to specifiy the target installation directory explicity using the /D qualifier ? For example

installer.exe /S /D=C:\Program Files\<Folder to install to>

Regards,

Spartacus

i have tried setup.exe /S /D=... NO LUCK

I i install the application in ui mode the application will extract some files to the profile, i have to click next here after the extraction is succesful so yes that might be the problem.
Is it possible to make a response/answer file for NSIS files?

Thx for all the help

Response file may not be possible in NSIS. Try to display the error status at the end. Another way, write the phases of execution to a text file.

Copy paste for you:

The Nullsoft Scriptable Install System (NSIS) is another open source installation system. It was created by the WinAmp authors to distribute that application, but it is now a general-purpose system which anyone might use.

When an NSIS installer runs, it creates a little window which says verifying installer: N%, where N counts from 0 to 100. So you can recognize these installers by this behavior. (Actually the verification procedure is optional, but most installers have it enabled. As an alternative, you can run "strings" and grep for "NSIS").

NSIS installers recognize /S for silent installation, /NCRC to suppress the CRC (verification) step, and /D=dir to specify the "output directory", which is where the program will be installed. These options are case-sensitive, so be sure to type them in upper case.

Incidentally, all /S does is change the installer script's SilentInstall attribute from "normal" to "silent". What effect this has, exactly, depends on the person who wrote the script. If /S does not perform a silent install, consider submitting a bug report to the installer's creator.



In the past I also encountered a NSIS installer which couldn't be deployed silent. I asked the vendor: "How in %$#^# is it possible to deploy it for 100 users?"

I ended up in repackaging...

As a general note concerning the running of vendor-supplied installs unadulterated, I'd need to be absolutely sure I knew exactly what it will do to my workstations before letting it loose on my estate. This is the single-most important reason for re-packaging this type of install - at the end of that process, you know (and can control!) what gets installed.

What if this package overwrites your painstakingly researched "one size fits nearly all" Visual C++ runtimes?