Autodesk Dwfcomposer2/Installshield packages
Hello..! Sorry for this rookie question.. [&:]
I was having a look at the Autodesk Dwfcomposer2 suite. Especially the Dwgviewer component of the suite. It's a MSI with a separate setup.exe, and a setup.ini, so I guess it's Installshield MSI, right? (correct me if i'm wrong here.. :P)
Anyways, i was able to deploy the package with SMS using some nifty vb scripting, but encountered, what i've seen a lot lately, some issues when editing it with Wfwi :unable to add registry keys etc. to the original MSI and then compile it. I'm using Wfwi, which is unable to create a transform from the original file (MSI).
It's not a real problem, i mean, i can create/remove registry keys using a vb script, copy/move delete files etc. using the vbs, but it's a tad nicer achieving this via a transform file. Using Orca is another option, but is guess orca isn't able to create transforms, right..? So i'm stuck with a transformed MSI, i don't think is is good practise either..
Whilst compiling in Wfwi, i see a lot of sourcepaths, referring to non-existent paths. Probably set by Installshield adminstudio, whilst compiling. That's probably why Wfwi can't compile the MSI's. Maybe something to do with merge modules, i don't know. I can always change the source paths of ALL files (100+), but i can't get past the idea that there probably is another, easier way to do this. Anyone have some good ideas on how to go about this? Thanks in advance..!
I was having a look at the Autodesk Dwfcomposer2 suite. Especially the Dwgviewer component of the suite. It's a MSI with a separate setup.exe, and a setup.ini, so I guess it's Installshield MSI, right? (correct me if i'm wrong here.. :P)
Anyways, i was able to deploy the package with SMS using some nifty vb scripting, but encountered, what i've seen a lot lately, some issues when editing it with Wfwi :unable to add registry keys etc. to the original MSI and then compile it. I'm using Wfwi, which is unable to create a transform from the original file (MSI).
It's not a real problem, i mean, i can create/remove registry keys using a vb script, copy/move delete files etc. using the vbs, but it's a tad nicer achieving this via a transform file. Using Orca is another option, but is guess orca isn't able to create transforms, right..? So i'm stuck with a transformed MSI, i don't think is is good practise either..
Whilst compiling in Wfwi, i see a lot of sourcepaths, referring to non-existent paths. Probably set by Installshield adminstudio, whilst compiling. That's probably why Wfwi can't compile the MSI's. Maybe something to do with merge modules, i don't know. I can always change the source paths of ALL files (100+), but i can't get past the idea that there probably is another, easier way to do this. Anyone have some good ideas on how to go about this? Thanks in advance..!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
AngelD
17 years ago
If it's not that to many registry entries to add then
Open the MSI using ORCA.
Select the "New Transform" option from the Transform menu.
Add the registry in the Registry table; make sure to add new component(s) (Component table) for the added registry and add the component to a existing feature (FeatureComponents table).
When done save the transform by selecting the "Generate Transform" from the Transform menu.
Open the MSI using ORCA.
Select the "New Transform" option from the Transform menu.
Add the registry in the Registry table; make sure to add new component(s) (Component table) for the added registry and add the component to a existing feature (FeatureComponents table).
When done save the transform by selecting the "Generate Transform" from the Transform menu.
Posted by:
Les
16 years ago
Does anyone know how to silently remove DWFComposer or Viewer? I can get it to uninstall with "MsiExec.exe /x{GUID}" but it would bring up the "Windows Installer" pop-up asking "Are you sure you want to uninstall this product?" Loaded each application from MSI.
Thanks in advance for your input.
Les
Thanks in advance for your input.
Les
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
