Difference between msiexec and a Double Click
We are working with Acrobat Pro 9.x. Since this is a huge app it does take a long time to install. But we have noticed something odd.
If we double click on the AcroPro.Msi file it will look for (and in our case find) Acrobat Pro 8.x. It uninstalls this and then installs v9.x
If we run the following command:
msiexec /i "%path%\AcroPro.msi" /qb! TRNASFORMS="%path%\AcroPro.mst" REBOOT=R
It takes "Twice" as long to run and do the same stuff.
This is all on Windows XP. Is there a difference between launching a MSI by double clicking on it Vs. calling Msiexec to run it? Is the msiexec.exe method doing something like reading more data that causes it to run slower?
We have performed this test on at least 4 differnet XP machines and the resuts are the same each time......calling this MSI from a command line takes twice as long.
If we double click on the AcroPro.Msi file it will look for (and in our case find) Acrobat Pro 8.x. It uninstalls this and then installs v9.x
If we run the following command:
msiexec /i "%path%\AcroPro.msi" /qb! TRNASFORMS="%path%\AcroPro.mst" REBOOT=R
It takes "Twice" as long to run and do the same stuff.
This is all on Windows XP. Is there a difference between launching a MSI by double clicking on it Vs. calling Msiexec to run it? Is the msiexec.exe method doing something like reading more data that causes it to run slower?
We have performed this test on at least 4 differnet XP machines and the resuts are the same each time......calling this MSI from a command line takes twice as long.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
turbokitty
15 years ago
Posted by:
turbokitty
15 years ago
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.