Multiple Cab Files...
Hello everyone...
Not a new guy but a newly registered one...Been a lurker on your site for a while but now a query prompts me to register with you guys, a query whose search yielded no results on your site...
I want to start by thanking the forum and site owners for creating this portal through which novices like myself can become more knowledgeable and hone our packaging prowess...Thanks...
I want to begin my entry into this forum with the following query...
OK, so let's say you made your changes to the package, embedded all the files you wanted to e.t.c....WPS creates your MST and your cab file.
Now, a little while later your manager sends you another file to be embedded in your package. You embed it and save it them Voila!, you have two cab files. You save that, add one more file to the package and boom!, now you have 3 .CAB files.
My question is, is there any way to incorporate as many changes as you want yet keep just one .CAB file?
What I mean is, you keep adding subsequent files to your package over time, editing your MSTs yet just end up keeping only one .CAB file, always, regardless of file additions.
Thanks in advance. And I guess you can see, I will be bothering you with many many questions in the days and years to come...
Regards...
Not a new guy but a newly registered one...Been a lurker on your site for a while but now a query prompts me to register with you guys, a query whose search yielded no results on your site...
I want to start by thanking the forum and site owners for creating this portal through which novices like myself can become more knowledgeable and hone our packaging prowess...Thanks...
I want to begin my entry into this forum with the following query...
OK, so let's say you made your changes to the package, embedded all the files you wanted to e.t.c....WPS creates your MST and your cab file.
Now, a little while later your manager sends you another file to be embedded in your package. You embed it and save it them Voila!, you have two cab files. You save that, add one more file to the package and boom!, now you have 3 .CAB files.
My question is, is there any way to incorporate as many changes as you want yet keep just one .CAB file?
What I mean is, you keep adding subsequent files to your package over time, editing your MSTs yet just end up keeping only one .CAB file, always, regardless of file additions.
Thanks in advance. And I guess you can see, I will be bothering you with many many questions in the days and years to come...
Regards...
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
fuz_kitten
14 years ago
Posted by:
MSIPackager
14 years ago
Hello, welcome to the forum :-)
Not sure about AdminStudio but there is an option in Wise Package Studio (under Media) - Cab options. If you are working from a WSI to create an MSI there is a One Cab option to keep it all in one. If you are working with MSIs though you can only use the Quickest (new files and modules get cab file) option - which is were the multiple cabs come from. Obviouslt this doesn't really apply if you are transforming vendor MSIs...
Generally speaking it would be much better for you to get to grips with makecab / cabarc tools to rebuild your own cabs when you add new files - you will also need to get aquainted with the media and file tables (attributes and sequence columns). You'll get your head around it in no time... Couple of points to remember:
1) The filenames in the cab relate to the File column in the file table (e.g. the internal MSI reference) - NOT the actual destination file name!
2) The cab needs to be built in the order of the files in the sequence column of the file table.
See how you get on and let us know if you get stuck...
Cheers,
Rob.
Not sure about AdminStudio but there is an option in Wise Package Studio (under Media) - Cab options. If you are working from a WSI to create an MSI there is a One Cab option to keep it all in one. If you are working with MSIs though you can only use the Quickest (new files and modules get cab file) option - which is were the multiple cabs come from. Obviouslt this doesn't really apply if you are transforming vendor MSIs...
Generally speaking it would be much better for you to get to grips with makecab / cabarc tools to rebuild your own cabs when you add new files - you will also need to get aquainted with the media and file tables (attributes and sequence columns). You'll get your head around it in no time... Couple of points to remember:
1) The filenames in the cab relate to the File column in the file table (e.g. the internal MSI reference) - NOT the actual destination file name!
2) The cab needs to be built in the order of the files in the sequence column of the file table.
See how you get on and let us know if you get stuck...
Cheers,
Rob.
Posted by:
Repackman
14 years ago
Posted by:
cygan
14 years ago
ORIGINAL: Repackman
Hello everyone...
Not a new guy but a newly registered one...Been a lurker on your site for a while but now a query prompts me to register with you guys, a query whose search yielded no results on your site...
I want to start by thanking the forum and site owners for creating this portal through which novices like myself can become more knowledgeable and hone our packaging prowess...Thanks...
got yoursself in a twist here
not a new guy but a novice hmmmmm
anyway welcome to the forum and it is official
where are the cakes to celebrate your membership [:D]
Posted by:
Repackman
14 years ago
Posted by:
anonymous_9363
14 years ago
Convert your MSI...No, no good, since that new MSI will include all the files from the original MSI plus those from the MST and not necessarily (in fact, not very likely) in the same sequence. All that means is that it's easier and quicker to add files to the CAB using MAKECAB and adjusting the File table's sequence numbers accordingly.
The WPS option of selecting to only have one CAB is obviously an even quicker route.
Posted by:
MSIPackager
14 years ago
Posted by:
Repackman
14 years ago
Kitten,
I tried your method...Unfortunately it created a single MSI...No CAB and no MST...I want my MST just like I want my MTV...:)
OK, let me delve a little further...My WPS 7 is a modified standalone version...No SQL backend support and no repository...It's all local...
Now the package I have (an EXE) creates an MSI and an MST as well (I suppose the developers of the program were proactive to the needs of Packagers)...Now, what I am doing is modifying the MST that the EXE spit out...It's all well...I edit the MST with WPS, it creates a CAB file, awesome... Problem is, when I add more stuff to the package through the MST, it creates another CAB file, which I don't want...
What I want is that no matter how many times I add stuff, it keeps going into that one CAB file instead of it making more everytime I add stuff... It's either that or repackage the whole thing from scratch with the new files added so it creates only one CAB, which I know is not right, although proponents say it's fine... Some proponents actually say it's fine to have multiple CAB files for a project...Not for me...I am a one CAB guy...:)
Now I will try MSIPackagers advice and see how that goes...I have never tried the MAKECAB thingie, but a search on your forum will, I am sure, reveal some fertile results...
Regards...
I tried your method...Unfortunately it created a single MSI...No CAB and no MST...I want my MST just like I want my MTV...:)
OK, let me delve a little further...My WPS 7 is a modified standalone version...No SQL backend support and no repository...It's all local...
Now the package I have (an EXE) creates an MSI and an MST as well (I suppose the developers of the program were proactive to the needs of Packagers)...Now, what I am doing is modifying the MST that the EXE spit out...It's all well...I edit the MST with WPS, it creates a CAB file, awesome... Problem is, when I add more stuff to the package through the MST, it creates another CAB file, which I don't want...
What I want is that no matter how many times I add stuff, it keeps going into that one CAB file instead of it making more everytime I add stuff... It's either that or repackage the whole thing from scratch with the new files added so it creates only one CAB, which I know is not right, although proponents say it's fine... Some proponents actually say it's fine to have multiple CAB files for a project...Not for me...I am a one CAB guy...:)
Now I will try MSIPackagers advice and see how that goes...I have never tried the MAKECAB thingie, but a search on your forum will, I am sure, reveal some fertile results...
Regards...
Posted by:
timmsie
14 years ago
It'd be worth you downloading Insted
It's a great free tool which is like a jazzed up ORCA. you could edit your mst with this and it gives you the ability to right click on the cab file in the media table and rebuild the cab.
Thing is though you'll need to understand how to add a file to the msi via the msi tables without the pretty wise front end (I'm not saying you dont!)
Cheers
Rich
It's a great free tool which is like a jazzed up ORCA. you could edit your mst with this and it gives you the ability to right click on the cab file in the media table and rebuild the cab.
Thing is though you'll need to understand how to add a file to the msi via the msi tables without the pretty wise front end (I'm not saying you dont!)
Cheers
Rich
Posted by:
Repackman
14 years ago
The solution was very simple...
All that was needed was for me to edit the MST with the new files embedded...So while WPS is open, embed the new files, then go into the project folder, delete the old CAB file...Turn off 'Quick Compile' and resave the changes...
There would be just one CAB file with your new and old files...
Thanks to everyone for their contributions, especially EdT for this simple yet elusive solution...
All that was needed was for me to edit the MST with the new files embedded...So while WPS is open, embed the new files, then go into the project folder, delete the old CAB file...Turn off 'Quick Compile' and resave the changes...
There would be just one CAB file with your new and old files...
Thanks to everyone for their contributions, especially EdT for this simple yet elusive solution...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.