Extracting Merge Modules from MSI
Hello,
I am editing a vendor MSI (company does not use TRANSFORM ... don't get me started ...) and putting in company properties & standards, but when I go to compile there seems to be two vendor merge modules that are not present, therefore I cannot create this modified MSI. Is there a way to extract those merge modules or a way I can see what is in them so I can re-create? Please help.
Thank you in advance.
I am editing a vendor MSI (company does not use TRANSFORM ... don't get me started ...) and putting in company properties & standards, but when I go to compile there seems to be two vendor merge modules that are not present, therefore I cannot create this modified MSI. Is there a way to extract those merge modules or a way I can see what is in them so I can re-create? Please help.
Thank you in advance.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
AngelD
17 years ago
If you use Wise Package Studio just start Windows Installer Editor and open the MSI. It will ask if you would like to convert the MSI to a project file (wsi), if you convert it will extract the MSMs.
If you get any problem (some have) then use ORCA to edit the MSI and MakeCab for cabinet creation.
The ModuleComponents table will show which components that reside in MSM that have been merged into the MSI. Have in mind that streams
may be included and will not be a component in the ModuleComponents table. You'll have to look in the _Streams table (Binary table should be enuf) and in some how verify if it's part of the MSI or MSM. ModuleSignature table could also be a good place to look in.
Then there can be entries in the Install*Sequence tables and CustomAction table that could be part of the MSM. Find out the guid part of the MSM and search for it in the CustomAction table. That should give you some info in how the CAs have been inserted in the Install*Sequence tables.
If you get any problem (some have) then use ORCA to edit the MSI and MakeCab for cabinet creation.
The ModuleComponents table will show which components that reside in MSM that have been merged into the MSI. Have in mind that streams
may be included and will not be a component in the ModuleComponents table. You'll have to look in the _Streams table (Binary table should be enuf) and in some how verify if it's part of the MSI or MSM. ModuleSignature table could also be a good place to look in.
Then there can be entries in the Install*Sequence tables and CustomAction table that could be part of the MSM. Find out the guid part of the MSM and search for it in the CustomAction table. That should give you some info in how the CAs have been inserted in the Install*Sequence tables.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
