honold
14th June 2002 16:17 UTC

is this idea hopeless?
i want to use a single binary for both normal and silent installs. my plan was to use cmdline/getparameters to check for the commandline argument '-silent', and if that was set to give the appropriate value to silentinstall and silentuninstall.

due to the limitation of being unable to call the function and pop the variable out in the begninning 'non-section', and the limitation of being unable to set installation flags in the first section, i'm wondering if this is possible at all.

can i test for this flag's setting throughout the would-be interactive parts of my installation and still be able to pull of an interactive as well as a 'double click and it's installed with no prompts' silent install?

Smile2Me
14th June 2002 16:29 UTC

Honold,

I judge this as a crosspost! Let this be a warning!
The answer has already been supplied here.

To summarize: /S is available for all (un)installers. You do not need to program it. Just put it at the command line and the installer will be silent (apart from MessageBoxes).

Use the function GetParameters (functions.htm) or GetNextParm to check if /S has indeed been supplied. Set a user variable to 1 if and 0 otherwise. Use this to test (StrCmp) if you need to display MessageBoxes or not.

-Hendri.

honold
14th June 2002 16:57 UTC

my aplogies

i didn't realize the s was case-sensitive - i tried that using /s instead of /S and it failed

this solution works now, thanks