Search found 9 matches

Go to advanced search

by InnovRick
Mon Oct 22, 2018 4:54 pm
Forum: Building Installers
Topic: MSI larger than 2 GB
Replies: 4
Views: 21356
 
Jump to post

Re: MSI larger than 2 GB

So is it impossible to include more than 1 CAB file in a MSI? For example, to include 3 CAB files of 1 GB each in the MSI database therefore allowing to exceed the 2 GB size limit?
by InnovRick
Fri Oct 19, 2018 8:50 pm
Forum: Building Installers
Topic: MSI larger than 2 GB
Replies: 4
Views: 21356
 
Jump to post

MSI larger than 2 GB

We are building a project with your software (12.3.1) which archives files into a single CAB file which is included in the MSI database. So basically, we distribute only one file which is the MSI.

We are on the verge of passing the 2 GB limit for the size of a CAB file and we are looking for a ...
by InnovRick
Mon Sep 21, 2015 5:35 pm
Forum: Common Problems
Topic: Finding install path using UpgradeCode
Replies: 3
Views: 4206
 
Jump to post

Re: Finding install path using UpgradeCode

Hi Dan,

Thanks for your prompt answer.

Both MSI's are built with Advanced Installer, but they are 2 different products. The second one is dependent on the first and can be seen as an add-in. It does have access to the UpgradeCode of the first product.

Your second solution using ...
by InnovRick
Fri Sep 18, 2015 10:55 pm
Forum: Common Problems
Topic: Finding install path using UpgradeCode
Replies: 3
Views: 4206
 
Jump to post

Finding install path using UpgradeCode

Hi,

I am trying to find the installation path of a product so I can install another product in the same directory. We do have a key containing the installation path but the key path varies depending on the version that is installed. The most reliable piece of information which does not change from ...
by InnovRick
Mon Feb 10, 2014 7:41 pm
Forum: Common Problems
Topic: Key could not be opened error
Replies: 3
Views: 6744
 
Jump to post

Re: Key could not be opened error

I'd like to know if this issue was ever resolved, I get the exact same error messages when uninstalling my MSI on Win7 x64.
by InnovRick
Mon Oct 21, 2013 11:56 pm
Forum: Common Problems
Topic: Force explorer to unload a dll during uninstall
Replies: 6
Views: 12783
 
Jump to post

Re: Force explorer to unload a dll during uninstall

Thanks for your reply Bogdan.

After doing some tests, we found that using the reboot method was acceptable since our shell extension kept working even without a reboot since it seems a copy is made and kept in use until we reboot and the new one takes effect. Since our shell extension is forward ...
by InnovRick
Wed Oct 16, 2013 8:15 pm
Forum: Common Problems
Topic: Force explorer to unload a dll during uninstall
Replies: 6
Views: 12783
 
Jump to post

Re: Force explorer to unload a dll during uninstall

It's been more than 6 years since this was posted, and I can't seem to find an answer to this question either.

We have a shell extension (dll) which explorer.exe loads when we preview a file of a certain extension. Our MSI's uninstall old versions of our product and install the new one (upgrade ...
by InnovRick
Thu Jun 27, 2013 6:10 pm
Forum: Common Problems
Topic: Registry keys created under WOW6432Node on x64 Vista
Replies: 9
Views: 14982
 
Jump to post

Re: Registry keys created under WOW6432Node on x64 Vista

Hi,

Our whole MSI creation process is automated which means we cannot use the "Organization" page to mark the components as 64-bit, and even if we could, the sheer number of components we would have to mark would make it inconceivable to mark each individually.

Our registry keys are imported using ...
by InnovRick
Wed May 22, 2013 8:48 pm
Forum: Common Problems
Topic: Problem with command SetPackageType x86
Replies: 4
Views: 5128
 
Jump to post

Problem with command SetPackageType x86

Hi,

I seem to have found a bug with the 'SetPackageType' command. When 'SetPackageType' is called with the value 'x86', the resulting MSI does not install on either a 32-bit or 64-bit system (tested on Win7) and gives the following Windows Installer error : « This installation package is not ...

Go to advanced search