Tiny MSI made. - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

stevejones75
Posts: 4
Joined: Fri Jan 30, 2009 5:48 pm

Tiny MSI made.

Hi,
I'm using an old project and, although it was working before, it's suddenly started making MSIs which are 4KB in size rather than 10,000KB. Just in the AppDir we have many megs of files so this is obviously wrong.

It's hard to put my finger on what might be causing this, except that:
i. The project started off as 32-bit and I've just converted it to mixed 32 / 64-bit (no platform-specific stuff: we just want the same features in the same places - relatively - on each of 32 and 64 bit).
ii. This is an AdvancedInstaller 5.x project imported into 6.7.1

The command-line we're using is "AdvancedInstaller.com /build AIPNAME.aip -force", does this still mean the same in 6.7.1 as in 5.x?

I'd love to give you more detail on this, but I'm not sure what detail's relevant other than attaching the whole .aip.
Any thoughts you have would be most welcome...
Thanks,
- Steve.
Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact: Website

Re: Tiny MSI made.

Hi Steve,

Please send the AIP file to support at advancedinstaller dot com in order to investigate this issue. Have you tried reinstalling AI and/or building the project on a clean machine?

Regards,
Ionut
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/
stevejones75
Posts: 4
Joined: Fri Jan 30, 2009 5:48 pm

Re: Tiny MSI made.

Hi,
I've sent you the AIP via email. When you talk about a "clean" machine, what would I need to remove from the machine? Just the previous version of AdvancedInstaller?
Old MSI, CAB files etc, perhaps?

Thanks,
- Steve.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Tiny MSI made.

Hi Steve,
When you talk about a "clean" machine, what would I need to remove from the machine?
By "clean machine" we usually refer to a fresh Windows installation.

I noticed in the project you provided that the "Include CAB file into the MSI database" option is unchecked in the Media tab. This will make Advanced Installer leave the CAB archive outside the MSI. Since the files are not included in the MSI, it will have a small size. If you want to include the installation files in the MSI, you can check the option I mentioned.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
stevejones75
Posts: 4
Joined: Fri Jan 30, 2009 5:48 pm

Re: Tiny MSI made.

OK, so that explains why the MSI is tiny. Thanks.
But, if I check the option, there's an error saying that it's not valid to incorporate the CAB on a mixed 32/64-bit deliverable.
I would normally say that this was fine, but we need to export a merge module - mixed 32/64-bit - so I have no idea how that's going to work.
But that's answered my immediate issue so I'll do some more reading around the documentation before I bother you again.
Thanks for your help,
- Steve.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Tiny MSI made.

Hi Steve,
But, if I check the option, there's an error saying that it's not valid to incorporate the CAB on a mixed 32/64-bit deliverable.
Indeed, a mixed 32/64 installer cannot include the CAB in the MSI. I didn't notice you are using this installation type. However, you can include the install files in the EXE bootstrapper in order to obtain a single EXE setup file. For this, you can use the "Include install files in EXE" option in the Bootstrapper tab of the "Media" page.
I would normally say that this was fine, but we need to export a merge module - mixed 32/64-bit - so I have no idea how that's going to work.
A merge module can be either 32-bit or 64-bit. If it's 32-bit, it can be used by:
- 32-bit packages
- 64-bit packages
- mixed 32/64-bit packages

However, if the merge module is 64-bit it can be used only by 64-bit installers. Therefore, you can try creating a 32-bit merge module.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”