Software Deployment

In the media tab in installation expert (WPS), change the compression option.

I already did it, but it doesn't works... when I ran the installation, it appears a msg error "missing cab file"..

I'm guessing (because I am more familiar with InstallShield than WPS) that you are working directly on the MSI in Wise Package Studio rather than using a WSI (?). If you were to convert the MSI to a WSI, I presume you would be able to build a 'release' where you could specify internal CABs. This might be the quickest way, but has the drawback that additional WISE-related tables might be added to the vendor MSI after you have compiled the WSI, which may not be desirable to you.

Another method - (if you have access to the Windows Installer SDK) - is to use the Wistream.vbs script as follows

1) From a command prompt, issue the following

[font="Courier New"]cscript wistream.vbs <Full Path to MSI>

this will allow you to see the streams already embedded in the MSI. Make sure there isnt a stream listed with the same name as the external CAB, and if there is such a stream, rename the external CAB file to something else

2) Now issue the following command

[font="Courier New"] cscript wistream.vbs <Full Path to MSI including file name> <Full Path to CAB file including file name>

3) Issue the command at step 1 again to confirm the CAB has now been streamed in.

4) In your MSI editor, examine the media table and find the value in the Cabinet column. Make sure the value is the same name as your original external CAB file and is prefixed with a #

Regards,

Spartacus

I have to package on a unique msi file (cab inside)Why? Dumb client request? Time for Ian's favourite tool, The Packager's Baseball Bat.

If they *insist* (you left them conscious?!?!), then Graham's suggestion of saving to a WSI and then altering the project to use internal CABs is a good one.

why? They give me a document with "standard packaging rules" and I have to agree whit it.

I did the Graham's suggestion, It was the good one.

Thank you!

i have some scripts floating around to put entire content internally due to customer stupidity that I couldn't rectify.

if you need them drop me a line, but I do not warranty them for any reason as in my opinion its kinda dumb to do just to meet a standard. i would prefer not to publish here due to the fact I disagree with the need for it.

interestingly enough the same customer insists on wrapping all msi's with a self extracting exe which they delete after install. so there is case and point enough to prove the standards are somewhat open to interpretation.