In my setup - as usual - the uninstallation is called if a previous version is found. Here is the application flow:
Setup is calling previous version uninstall
Uninstallation started
Apply uninstall returned: COMPLETE
(uninstall)Setup terminates with exit code 0
the calling setup receives a -1073741819
How could this be? Am I missing something, I have no idea how the setup could receive -1073741819 from a process that terminates with exit code 0.
For illustration I have attached the log files and a IA script snippet.
Hope someone can tell me what could be the reason for this.
Uninstallation returns 0 but setup receives -1073741819
Uninstallation returns 0 but setup receives -1073741819
- Attachments
-
- uninstall_returns_0.png (354.21 KiB) Viewed 3677 times
-
FrancescoT
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Uninstallation returns 0 but setup receives -1073741819
Dear Alibaba,
what happens when you run it without SILENT mode?
Regards
what happens when you run it without SILENT mode?
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Re: Uninstallation returns 0 but setup receives -1073741819
This is not a general problem, normally the (un)installation is no problem or more precisely the transfer of the return value is correct. But in this case the setup receives a wrong value.
I have no idea where this value is coming from...maybe from the Windows Api that is used for Run program?
Anyway if you also have no idea and since this is the first occurence of this problem I will not further investigate it and call back if this ecalates into a lets say conflagration
I have no idea where this value is coming from...maybe from the Windows Api that is used for Run program?
Anyway if you also have no idea and since this is the first occurence of this problem I will not further investigate it and call back if this ecalates into a lets say conflagration

