add a 420mb .exe to the project, adds almost 900mb to the size of the installable

[zac_rscom]

We have a custom action set up to install a second .exe that's 420mb. It works fine except that now the project jumped up to a 1gb in size. This makes it a large file that is very slow to install. Any ideas why it seems like InstallShield is including the second .exe file twice? The only other files we have added to the project are less than 2mb in size.

Is there a step by step on how to install a second program with the same installable so I can see where I went wrong?

[Wagaboo]

Is that some sort of merge module or is it totally different?
Maybe it's added twice for this reason, one for per user installation, one for per machine.
Just a guess though

[Wagaboo]

you can build a cdrom, and find where the space come from directly

[zac_rscom]

Turns out there were duplicates in the binary from changing custom actions instead of deleting and making new ones. Had to have support fix it for me but it's all good now.