One project file - different Installer for 32bit and 64bit

[Rizi]

Hi,

i need some help on how i shoud set up my Advanced Installer project for 32bit and 64bit installations.

My requirements are:

1. One Advanced Installer project file

2. Two Builds (via Media Tab). One Installer for the 32bit installation and the other one for the 64bit installation
for our software.

3. The different (32bit/64bit) binaries for the 32bit installation should be stored in a "...\bin" folder and for the 64bit installation in a "...\bin64" folder.

4. The installer package for the 64bit installation should run as a 64 bit process (especially because of some VBScripts, which are searching for specific installation entries in the Windows registry)

5. The 64bit installer shall not be allowed to run on a 32bit machine.

6. Our Software shall be installed in the proper windows program folder

7. Set up different "prerequistites" files for 32bit and 64bit Installations


I tried several setups in my Advanced Installer project but especially the 64bit Installation fails (the installer runs always as 32bit process).
What is the best solution / approach to fullfill my requirements above?

Thank you very much in advanced.

[Dan]

Hello,

Two Builds (via Media Tab). One Installer for the 32bit installation and the other one for the 64bit installation
for our software.

In order to achieve that, you can create in Builds page two builds (one for 32 bit and another one for the 64 bit). Then, you can go in the Install Parameters page and set the Package type for each build. Please note that you can select the build for whom to apply the related changes as you can see in the below image. Also you can take a look Package type article which may be useful to you.

InstParamPage.png (40.17 KiB) Viewed 6850 times

The different (32bit/64bit) binaries for the 32bit installation should be stored in a "...\bin" folder and for the 64bit installation in a "...\bin64" folder.

You can create this structure in the Application Folder from the Files and Folders page where you can add these regular folders e.g. bin and bin64.
In order to make sure that these will be included in your build based its type, you can go in the Organization page and create two features (e.g. 32bit and 64bit) in order to organize your application into features . Add in these features the component which are specific for the 32 and 64-bit. Then, in the Builds section from the Feature properties you can select the build which will include the related feature.

Set up different "prerequistites" files for 32bit and 64bit Installations

In order to achieve that you can go in the Prerequisites page and add you prerequisite. Also, in the Install Conditions tab you can set the install conditions and also the Supported Windows Versions(64-bit or 32-bit). For the Feature-based and Post-install prerequisite you can also select the build to which is specific the related prerequisite from the Feature properties.

By the way, have you noticed our Mixed 32/64-bit matching the platform mode? Here is an article which may be useful to you: How do I create a package that will be installed like a 64-bit package on 64-bit platforms and as 32-bit package on 32-bit platforms ?. This easy approach is to use the Mixed 32/64-bit matching the platform wizard. The wizard is easier to use, but the advanced package structure settings are configured automatically.

Please let us know if you have other questions.

Best regards,
Dan

[Rizi]

Hi Dan,

thank your very much for your detailed information. I set up / modified my Advanced Installer project regarding your
instructions. I think most of my requirements are fulfilled with this set up.

But my 64bit Installer package don´t run as 64bit application on a 64bit machine!? Is this possible in general? I set up
a test Advanced Installer project; just with a text file to install. I specified also the installer package as "64-bit for x64 processors
(AMD64,EM64T)" within this test project. But also this test installer dont´t run as 64bit application on a 64bit machine!?

The reason for my request is, that i have several VBScripts which are looking into the registry regarding specific installed software. When the installer
runs as a 32bit application the VBScripts are atomatically pointed to the registry "Wow6432Node". Which is fine for my 32bit installation.
But for my 64bit installation the VBScripts shall not be pointed to this "Wow6432Node", because then the software i´m searching for in the registry
are 64bit versions.

Thank you very much for your help!

[Dan]

Hi,

If your application package is created as a .msi file, then this is a normal Windows Installer behavior. Windows Installer handle 64-bit package installation through both versions, 32-bit and 64-bit, of msiexec.exe.

So, you may need that your custom action that search through the registry be marked as a 64bit if applicable.

However, did you noticed our Search support? Use the [ New Search Wizard ] toolbar button, to quickly and easily set up a new search, following step-by-step directions. Here you can also enable the Search the 64-bit portion of the registry option for the Registry Location Properties. Also, you should take a look on our Extended Search Properties article which may be useful to you.

Please let us know if that helped.

Best regards,
Dan