I am in the process of repackaging Adobe Reader 7.0.8 for my organization. After gathering the extracted files from the .exe file, it appeared to me that all the files contained for the installation are placed into an external cab file (data1.cab). I extraced all the files from the cab file and was trying to place them into the .msi file using Wise Package Studio but was unable to do it. If anyone has any advice on the correct way to do this I would really appreciate it.

-Dan
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Don't repackage Adobe Reader. Download the Tuner utility from Adobe and create a transform for it. Check the Package Knowledge Database for info:
http://www.appdeploy.com/packages
Answered 08/03/2006 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
I apologize...let me reclarify. By "repackaging" I mean modifying for use within our agency (it's already in .msi format-so there's no need to repackage it). I have created an .mst through the Installshield Tuner. The only reason I opened up the .msi in Wise Package Studio was to find a way to compress the files that were in the external .cab file into the .msi file so I can have just two files (.mst and .msi) instead of three (the .msi, .mst and .cab file).
Answered 08/03/2006 by: danr29
Purple Belt

Please log in to comment
0
Hi Dan,
this is best done with the tools from the installer SDK.
Use WiMakCab.vbs to generate the cab and WiStream.vbs to store the cabfiles in the MSI-package.
Use ORCA to add the necessary rows in the file and component tables.
Don't forget to add the '#' to the cabfile names in the media table.
Regards, Nick
Answered 08/03/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
As an alternative, if you're comfortable with using WSI project files, then you can "convert" the vendor's base MSI to a WSI project file, create a new Release item within the project and specify that the Compression option for the item is set to "Compress files inside .MSI"

Then once you have compiled your release, you should have an MSI complete with internal CAB. The MST you created with the Tuner should still work with the internal CAB MSI.

Sorry I can't be more specific, it's a little while since I used WPS (I use InstallShield AdminStudio these days), but I'm sure some of the WPS "regulars" on this forum can provide step by step details on the above, should you require them. [:)]

Spartacus
Answered 08/04/2006 by: spartacus
Black Belt

Please log in to comment
0
I prefer using ORCA and WiStream.vbs for this kind of stuff but here you go ;)

Start Windows Installer Editor
Open the msi and choose to convert to WSI.
Go to the Release Definition -> Media in Installation Expert
Hit the Details button on the Media and change the Compression Option to "Compress files inside .MSI"
Recompile
Answered 08/04/2006 by: AngelD
Red Belt

Please log in to comment
0
Thank you for the replies. I was originally using Wise Package Studio to do this, but when I placed the external .cab files into the .msi I would get an error when compiling that said all of the files contained in the .cab file lost all of their keypaths. I tried it again and it appeared to work this time. I'll also try it the Orca way since it seems that most of you (the pros[:)]) prefer to do it this way. Thanks again everyone!
Answered 08/04/2006 by: danr29
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share