/build/static/layout/Breadcrumb_cap_w.png

How do you add external .CAB files when building MSI (from ISM release wizard)

Hello all. Please verify if my initial steps were correct and also how to add external CAB files to an ISM build to MSI. My package is close to 3gb, exceeding the size limits for building an MSI. Releasing Wizard and attempting to build the MSI resulted in a failure. Steps taken as follows:

Using Adminstudio Repackager, I created a capture. In Repackaged Output (within the .IRP), I selected “Create MS Win Install Package” with the drop down option menu set to “.MSI File With External .CAB File”. This resulted in four CAB files created alongside an ISM  file which was under 600K. I opened the ISM file and am now ready to Release Wizard to build the MSI. How and when do I associate/incorporate the CAB files when releasing wizard to build the MSI?

 

I am using AdminStudio 2014 for the Repackager

I am using Installshield 2015 for ISM build to MSI (release wizard)

 

Thank you for any help!


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: rad33k 5 years ago
Fourth Degree Brown Belt
1

Top Answer

I'm not sure if I understand the question too but i will try to answer ;)

When you choose 'Realese wizard' and move to 'Media type' dialog (5 times clicked next) you would need to choose 'Network Image' (if we are talking about MSI without size limit) and on the next screen you can choose how files will be stored in the MSI. You have got 4 options:
1. Compress all files - result is one single MSI with all file(s) compressed (CAB embedded into MSI)
2. Leave files uncompressed... - MSI does not contain any files, all files are placed next to the MSI file. (no CAB file)
3. Custom:
    a) One .cab per Component - MSI does not contain any file(s), every Component from the ISM project creates separate CAB file (external CAB(s) next to the MSI)
    b) One .cab per Feature - MSI does not contain any file(s), every Feaure from the ISM project creates separate CAB file (external CAB(s) next to the MSI)

and below you can admire my M$Paint skills ;) BTW. Nice trick rileyz ;-)



Comments:
  • Thanks very much! This answered my question. Selecting "Custom" and then "One .cab per Feature" resulted in the MSI being created alongside the CAB files created from running the Release Wizard. The install went perfect. Thanks again! - rcooder 5 years ago
  • re: rad33k (; - rileyz 5 years ago
Posted by: rileyz 5 years ago
Red Belt
0

I'm a bit confused, maybe I don't understand.

When you compile your MSI, it should produced the .msi and .cab files. If your build is 3gb, then this build time will take awhile. What happens when you try to compile the build? What are you capturing that is 3gb??? Might be a better method to what you are trying to achieve.

One thing, when you build from InstallShield, you should get a folder structure that looks like the below, the end path will contain the MSI and CABs.
Product Configuration 1\Release 1\DiskImages\DISK1

Good luck!


Comments:

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ