problems wrapping .exe using batch or conversion - Advanced Installer Community
dlusk
Posts: 1
Joined: Thu Oct 08, 2015 2:20 am

problems wrapping .exe using batch or conversion

Greetings,

I am a new to MSI files.

I am trying to wrap a .exe file.

I also need to copy a configuration file into the applications folder after it's installed.

I am using the Demo version 12.4.2.

My goal is to create an MSI that can be installed by Active Directory. So far I have been able to build an MSI that works but it only has the .exe's full UI. I need a silent install.

The .exe can be installed using the command line switch /verysilent. I created a batch file Setup.exe /verysilent and it worked as expected, silent install.

When I try and use the same batch file in a LaunchFile custom action I get the full user UI. For some reason Advanced Installer will not process the command line switches for the .exe. The .exe in question was created using Inno Setup Installer www.jrsoftware.com

I also tried importing it using the EXE to MSI feature and adding \verysilent to prerequisites\packages\post-install\install command lines\Full UI ; Basic UI and Silent no matter how I tried to run the MSI I got the full user UI.

I am able to wrap the .exe using the \verysilent switch using Exe to MSI converter Pro 3.8 and it works as required. I would prefer to use Advanced Installer because I think it's a much more flexible application. I am under a lot of pressure to figure this out.

I have not been able to find others posts with this problem but I have only been searching for an hour. I am sure it's something simple I am missing.

As far as the file copy goes I just need to be pointed in the right direction.

Does Advanced Installer take a PO?

Than you for your help

Don
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: problems wrapping .exe using batch or conversion

Hi Don and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

First of all, we apologize for our delay reply. We are quite busy these days.
My goal is to create an MSI that can be installed by Active Directory. So far I have been able to build an MSI that works but it only has the .exe's full UI. I need a silent install.
I assume that you follow the Convert EXE(s) to MSI tutorial in order to get the .MSI installation package from an .EXE package. If not, please use the MSI from EXE(s) template from the Start page -> Convert Project Types. This tutorial will guide you in creating an .MSI installation package which installs existing .EXE packages.

When getting to the 4.1 Include an .EXE package step, please add the /verysilent command line parameter in each field of the Install Command Lines section. Each command is used by your prerequisite based on the UI level of the main package, i.e. if the main package runs with full UI the command from the "Full UI" field will be used to call the prerequisite, if the main package runs with basic UI them the command from the "Basic UI" field will be used to call the prerequisite, the same for the rest.

This way you can have different command lines for each UI level:
  • Full UI - command line parameters used for an installation with full user interface
    Basic UI - command line parameters used for an installation which shows only a progress bar
    Silent (no UI) - command line parameters for an installation with no user interface
I also need to copy a configuration file into the applications folder after it's installed.
In order to achieve this, you can add the configuration file in the Application Folder from the Files and Folders page. Then, in the Custom Actions page you can add the Set installer property as a custom action with sequence.
Set the APPDIR property with the value where you want to copy the related file, the default installation path of the .EXE.

Should there be any difficulty you encounter implementing something, please do not hesitate to contact me and I will gladly assist.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”