Problem with setting installdir as a windows variable
I have a question guys
I need to create an application package(adobe) which set the installdir to %SYSTEMDRIVE\Apps\Adobe\Acrobat8.0.
I use the Adobe Customasatino wizard tool to create the mst.
After this i open the created mst file in Wise. Creating a custom action to set the installdir to to %SYSTEMDRIVE%\Apps\Adobe\Acrobat 8.0
When i run the cmd line: msiexec /i msi /qb! TRANSFORMS=transformsfile ALLUSERS=2 (The installdir is set correctly but if i add the parameteres /qb! to my installationstring my installdir will be c:\programfiles\adobe....
Why does this happend?
I need to create an application package(adobe) which set the installdir to %SYSTEMDRIVE\Apps\Adobe\Acrobat8.0.
I use the Adobe Customasatino wizard tool to create the mst.
After this i open the created mst file in Wise. Creating a custom action to set the installdir to to %SYSTEMDRIVE%\Apps\Adobe\Acrobat 8.0
When i run the cmd line: msiexec /i msi /qb! TRANSFORMS=transformsfile ALLUSERS=2 (The installdir is set correctly but if i add the parameteres /qb! to my installationstring my installdir will be c:\programfiles\adobe....
Why does this happend?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
AngelD
15 years ago
Because you added the set directory or property custom action in ui sequence (InstallUISequence), try InstallExecuteSequence instead.
However I would do this in InstEd (or ORCA) instead as wise adds more junk then needed.
Why not change the Directory_Parent column value for the Adobe directory to point to "Apps" instead?
You should also set the ALLUSERS property to 1 instead.
However I would do this in InstEd (or ORCA) instead as wise adds more junk then needed.
Why not change the Directory_Parent column value for the Adobe directory to point to "Apps" instead?
You should also set the ALLUSERS property to 1 instead.
Posted by:
Bankeralle
15 years ago
not change the Directory_Parent column value for the Adobe directory to point to "Apps" instead?
Can you please explain some more AngelD. Thx for the help though
You are absoultly right. The custom action is in uisequence instad of Installexecutesequence.
Is this becaues i set the customaction (Set_Installdir) to be type 51?
Figures it out If i set the custom action to Normal Execute Immediate/Deferred instead of normal execute it will be correctly listed under Installexecutesequense.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.