Hi, guys..
Problem description:
There is third-party EXE-module which associated with feature.
The EXE-module has various exit codes and installs the device driver.
The EXE-module must be on source CD.
How to execute the EXE-module during REINSTALL action from source CD?
Note:
I cannot use CA 2,18,50,34 to launch an executable file because
custom actions that are executable files must return a value of 0 for
success.
The installer interprets any other return value as failure.
I need a solution... Please help...
Thanks in advance...
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
How to execute the EXE-module during REINSTALL act
Started by
ooooo
, Sep 09 2002 19:30
2 replies to this topic
Posted 10 September 2002 - 09:04
Note:
I cannot use CA 2,18,50,34 to launch an executable file because
custom actions that are executable files must return a value of 0 for
success.
The installer interprets any other return value as failure.
Adding 64 or 192 to the CA code instructs the installer to ignore the return code.
See Documentation
Windows Installer
--Custom Actions
----Custom Action Reference
------Custom Action Return Processing Options
I cannot use CA 2,18,50,34 to launch an executable file because
custom actions that are executable files must return a value of 0 for
success.
The installer interprets any other return value as failure.
Adding 64 or 192 to the CA code instructs the installer to ignore the return code.
See Documentation
Windows Installer
--Custom Actions
----Custom Action Reference
------Custom Action Return Processing Options
Ian Blake
(Currently Unemployed)
(Currently Unemployed)
Posted 10 September 2002 - 10:04
I'm sorry.. I have overworked... ;-)
I have forgotten to tell that I need to check exit codes.
Certainly it is possible to ask each time the user a path to EXE-module, but
in my opinion it is the ugly solution.
I have forgotten to tell that I need to check exit codes.
Certainly it is possible to ask each time the user a path to EXE-module, but
in my opinion it is the ugly solution.