InstallAware

I've recently been given this job and I've never used InstallAware. I've spent the last couple of hours and I've read in forums and in various places that <setup> /s is the way to run a silent installation. However, no where do I see where exactly I'm suppose to add this command line or how to add it. I'm able to update our existing installer with the wizard and it works fine. Now I need to run a silent installation. I'm assuming the Tab on the bottom of the application called MSIcode is the command line interface (InstallAware6). Could anyone help me add the proper line in the proper location, or point me to a tutorial or existing thread that shows this so I can build the silent installation and finish this project. All help would be appreciated.

Raul

You run your built setup with that command line parameter, of course.

Are you saying that once I build the MSI file i can just run the setup with /s parameter??

Read the help file topic titled setup command line parameters please.

Michael,

Thanks for all the help you are giving me. I have read the help topic. That's where i found out which switch I needed. Where my ignorance is, does this switch need to be within the code of the installer or do I run the setup file from a Windows command line and add the switch?

If the latter is correct, is there a way to deploy without having someone add the switch manually. I'm trying to build an automated installer with no user interaction that can be launch remotely.

Again, thank you for your help. I've posted what i read, let me know if this is not what you intended me to read.

"Setup Command Line Parameters

Every InstallAware setup supports command line parameters for silent and logged installs. In addition, you may also set/override the values of variables used in your installation from the command line.

You may freely combine all of the parameters displayed below. See uninstalling from the command line for an example.

Silent Installs

With the silent install command line parameter set, the entire installation will execute silently, without a user interface, or any user intervention. When input is required on dialog boxes, the default values of dialog controls will be used.

<setup> /sIn the above example, setup.exe denotes the main setup executable. "

I respectfully submit to your consideration that if you are unable to obtain the reply from the help fragment you just posted, you may be under-qualified to build installers.

You are correct, i am under qualified to build installers. However, from the wizard within the program i was able to update several key aspects of our software package that include all the dialog boxes, EULA, dotnet framework, ie7 and change our sql server from 2000 to 2008. I compiled, built it and executed a successful package and people are now using the installer in the field.
My intent was to have someone launch our executable and walk away without any further input and have the installer do all the work. I came here to attain insight into this application as there are no training or tutorials available and the help content is somewhat cryptic. I would like to thank you, I have definitely gained insight.

You've come a long way with the built in tools, which I take as testament to the ease of use of InstallAware, but you definitely need to brush up on your OS skills! When you run setup.exe with the /s command line parameter, it will run silently, can anybody else help me explain this?

As Michael was trying to say the /s command is built into every install built with installaware. This is a command that has to be run from the command line.

To do this you can go to Start -> Run -> Type "cmd" -> click OK
This will bring up the command prompt. Once this is done use the command line window to navigiate to the directory where you installer is (cd <path>) type in <setup> /s this will run the installer silently.

If you would like to automate this you can create a batch file with the same line of code <setup> /s. Double clicking the batch file while it is in the same directory as your installer will start the process.

I did understand what Michael was telling me about the command line. I know I can launch the application from the command line. However, I'm giving this to people in the field and they didn't want to go into the command line everytime. I believe we had a miscommunication, and to Michael, I apologize if I wasn't clear enough.

Rooster, I would like to thank you. The batch idea file should work fine. I'll prepare a package and have them launch the batch script instead of the direct MSI package. Thanks for the help to both you and Michael...

Cheers!
Raul

Yep, that's pretty bad communication I'm afraid.

Use the pre-defined script variables - look them up in the help file. Setting $SILENT$ to TRUE will work for you.