Wise installer command switches

Wise package install switches for install path? Hello, I have an application which is packaged with Wise Installation wizard. Software Deployment. Posted by: yarborg 15 years ago. I guess you are creating an exe install right?

Below is a list of common command line options from Wise. This is from their help file. For information on reading variables, see Set Variable. OCX or. DLL as it is registered. On some locked-down machines with restricted privileges, these temporary files might fail to write, resulting in a failed installation.

Use this command line option to specify a directory name for which the end user has write privileges. Posted by: Alvinlie 15 years ago. I'm not building the executable. It is a prebuild. Rating comments in this legacy AppDeploy message board thread won't reorder them, so that the conversation will remain readable. Answer this question. Basic MSI is another story. Just to make things interesting, any of these mechanisms might be combined with PFTW. For example, I eventually figured out that the IBM Update Connector requires these flags for unattended installation:.

Finally, InstallShield has a KnowledgeBase article which is less helpful than you might expect. Are we having fun yet? You can usually identify the installers it produces by running "strings" on the executable and grepping for "Wise".

And in my experience, they generally do. But there is no way to set options, and the exit status is meaningless. Don't let them confuse you. Inno Setup is an open source competitor in this space. You can usually identify the installers it creates by running "strings" on the executable and grepping for "Inno". The switches for Inno Setup are fully documented in the ISetup.

The GnuWin32 project has put a copy on the Web. It was created by the WinAmp authors to distribute that application, but it is now a general-purpose system which anyone might use. 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" These options are case-sensitive, so be sure to type them in upper case.

What effect this has, exactly, depends on the person who wrote the script. According to KB article and KB article , Microsoft is moving towards standardized packaging and naming for hotfixes. But they are not done yet. These installers first extract some stuff to a temporary folder and then run a command from inside that folder. If the application simply has no unattended installation procedure, you can create your own.

I prefer to avoid these approaches if at all possible, since they are relatively unreliable and difficult to maintain. There are several tools around which can take a snapshot of a machine's state before and after a manual installation, compute the differences between the states, and bundle them up as an "installer".

The Wise product line provides good support for this, and Microsoft's free tool recently updated provides bad support for it.

The problem with this approach is that it fundamentally cannot work reliably. So the repackaged installer will almost never do exactly the same thing that a fresh installation would, unless the target machine is completely identical to the original machine. In addition, for every new release of an application, you will need to repackage it again. And there are other disadvantages which even Microsoft recognizes. AutoIt is a free tool which can simulate key presses and mouse clicks, following a script customarily named with a.

Most installers have a sufficiently simple and consistent interface that a very short AutoIt script suffices to automate their installation. The AutoIt distribution includes very good documentation. You can copy the AutoIt. First, you must be careful when upgrading to new releases of an application, since the installer's UI may have changed. More worryingly, AutoIt scripts are theoretically unreliable because they do not let you determine when a sub-process has exited. You can tell when AutoIt itself exits, but that is not the same thing at all.

For example, an installer's last window might disappear while the installer was still working. Your master script, waiting only for the AutoIt executable, would then proceed, starting another installation or rebooting the machine. AutoIt provides Run and RunWait primitives, but it does not provide a way to wait for the termination of an application which was invoked by Run. If it did, this race condition could be avoided. In practice, it does not matter much, because most installers do finish their work before destroying their last window.

Just make sure your. You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy! Already have an account? Sign in here. Application Installs Existing user? MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Applications Switches for Wise, InstallShield etc.

Share More sharing options Followers 0. Recommended Posts. Astalavista Posted November 23,