/build/static/layout/Breadcrumb_cap_w.png

vendor MSI, can't create a MST, so how?

Hi,

First post here. I enjoy the board and I am junior and would like to get good at packaging. I have a very simple scenario. I am using Wise, and using a third party distribution method to send any MSI packages on workstations.

You have an existing package for Adobe Creative CS3 suite, the whole suite. Not much packaging here, I used their deployment solution. There is a bunch of MSI in this suite. Having a quick look, you can't seem to be able to install any of them separately without installing the setup first. Okay.

So, a package like this, at first, it seems that you can't edit it or creates a Custom MST file. I am using Wise, not used to Orca or other stuff yet.

Here is a simple question: how would you simply just ADD a single file to that package knowing that you need self healing to kick in if this file is broken? What do you do, when you can't create a transform file with WISE for any vendor package and that you want to add some files that needs self-healing?

Your inputs are more than welcome.

0 Comments   [ + ] Show comments

Answers (7)

Posted by: Thegunner 16 years ago
Second Degree Green Belt
0
Why can you not create a Transform with Wise?
Posted by: anonymous_9363 16 years ago
Red Belt
0
Why can you not create a Transform with Wise?With the Adobe apps, that's a really bad idea. You should always, always, always use Adobe's customisation tool, relevant to the actual product (they seem to have one per product).
Posted by: kiptek 16 years ago
Second Degree Green Belt
0
Actually you can customize what you lay down through the setup.xml in the payloads folder... Works like a charm (*considering*).... There should be an entry in the package KB, & I think it was discussed here a couple of months ago...
Posted by: PackagerWannaBe 16 years ago
Orange Senior Belt
0
Hi,

I am still trying to use Adobe Cust Tool for some packages that i need to modify by adding a file to a non standard location and drive. With the adobe tool, i can't create a new destination folder under destination computer like i do with Wise. The only folders that i can drage files too are standard one like, windows, programfiles, etc.

Knowing that i am not used to modify tables directly, does anyone has a clear directive if i want to add file1.txt under a specific folder on a non windows drive with this Adobe Cust Tool? (G:\Folder)

Thanks,
Posted by: kiptek 16 years ago
Second Degree Green Belt
0
drop the files in a folder in the files and folders section, then go to the direct editor and create a set directory custom action.
Posted by: PackagerWannaBe 16 years ago
Orange Senior Belt
0
Hi Kiptek,

If I understand correctly, you are suggesting to include my folder into any existing folder under the destination computer like programfiles. Then i have to create a custom action. When creating the custom action, i need to enter an action name, type and source and target. In the targe i can put anything like G:\folder but what should I put in the Source field to associate this action to the folder i just added in the files tab under program files?

And my next question is where will that file get inserted, does it create a cab file like in Wise Studio?

Thanks for your advice.
Posted by: PackagerWannaBe 16 years ago
Orange Senior Belt
0
Just to give an update.

I succeed by applying my changes on a base MST file with Wise, importing the new MST file to Orca (to easily isolate the modifications) and then exporting the relevant new tables entries into the Adobe MST design tool itself. Pain process but it worked.

Thanks
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ