Add files to Data1.cab ?
I have this Transform package using WPS .. and i want to add a few files to my package, but Wise INSISTS on creating a new .cab file for them and adding the new .cab to the Media table
How do I make it pack the new files into the existing Data1.cab ?
I tried WinCAB but i can't seem to add files to existing .cab there either, only make a new .cab
Bart [8|]
How do I make it pack the new files into the existing Data1.cab ?
I tried WinCAB but i can't seem to add files to existing .cab there either, only make a new .cab
Bart [8|]
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
dwight66
18 years ago
Hi Bartesque,
Try throw away the .CAB files and recompile your MST in WPS.
It worked for me.
Dwight
Try throw away the .CAB files and recompile your MST in WPS.
It worked for me.
Dwight
Posted by:
Bartesque
18 years ago
ehm .. with no source path it will fail .. and if i type in the source path, it will build seperate cabs for each file ..
Posted by:
brenthunter2005
18 years ago
The idea of creating TRANSFORMS is that you DON'T modify the original MSI (and CAB files).
This is what creating a TRANSFORM is; being able to modify the MSI but without actually touching the physical MSI package.
This is what creating a TRANSFORM is; being able to modify the MSI but without actually touching the physical MSI package.
Posted by:
Bartesque
18 years ago
This is what creating a TRANSFORM is; being able to modify the MSI but without actually touching the physical MSI package.
Right! my conclusion also .. didn't really connect NATIVE MSI to NATIVE CAB thou [&:]
Bart [8|]
Posted by:
dwight66
18 years ago
Hi Bartesque,
This might be a setting in WPS. In our environmet WPS creates one new single CAB file with all the extra files included. This mechanism is to ensure the integrity of the Vendor Based MSI.
There will only one single CAB file.
This might be a setting in WPS. In our environmet WPS creates one new single CAB file with all the extra files included. This mechanism is to ensure the integrity of the Vendor Based MSI.
There will only one single CAB file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.