Installing Device drivers through MSI
Hi I want to install 2 device driver softwares along with my applcation.So i made an MST for the vanilla MSI and added DPinst.exe and these signed drivers through this MST . And added a custom action to execute the above exe in the action:'Execute Program from Installed files' , location after 'InstallServices' and sequence 'Execute defferred'
While installation of the MSI/MST it throws an error : 1722: Program run as part of setup did not finish as expected....
Eventhough the installation happened finely and the driver got installed :)
Is there any Idea to get rid of this error
or a better way to execute my exe in between the installation of MSI/MST?
Bob
While installation of the MSI/MST it throws an error : 1722: Program run as part of setup did not finish as expected....
Eventhough the installation happened finely and the driver got installed :)
Is there any Idea to get rid of this error
or a better way to execute my exe in between the installation of MSI/MST?
Bob
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
spartacus
16 years ago
Following your installation, take a look in the file %windir%\DPInst.log. You may see in the log file that a reboot is needed to finalise the installation of the drivers. Should this be the case, then your custom action may be returning a status that is interpreted as an "error", so the simplest solution would be to alter the custom action to ignore the return status.
For any other reason then, as is often the case, creating a verbose log file of the MSI installation should reveal some clues.
Regards,
Spartacus
For any other reason then, as is often the case, creating a verbose log file of the MSI installation should reveal some clues.
Regards,
Spartacus
Posted by:
anonymous_9363
16 years ago
In all probability, the install completes because you have set the Custom Action to ignore any error.
Take a verbose log of the install and check the command line being used. It's likely you have a typo in there or are trying to use a property in the CA and have failed to use the special CustomActionData property which you require in deferred CAs.
Take a verbose log of the install and check the command line being used. It's likely you have a typo in there or are trying to use a property in the CA and have failed to use the special CustomActionData property which you require in deferred CAs.
Posted by:
jmcfadyen
16 years ago
Posted by:
AngelD
16 years ago
Posted by:
blogbobb
16 years ago
Posted by:
AngelD
16 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.