This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Getting "InstallShield can not call DLL functions: IsWindow"
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 09, 2009
04:07 PM
Getting "InstallShield can not call DLL functions: IsWindow"
Hi,
I just upgraded our InstallShield version 9 project to InstallShield 2009. I converted the old *.ism project to 2009 with no errors, and the project built with no errors.
However, when I run the installation, I get a "can not call DLL: IsWindow" message for every custom dialog we show. This did not happen before the conversion to 2009.
Has anyone run into this? Any ideas or suggestions?
-Andy
I just upgraded our InstallShield version 9 project to InstallShield 2009. I converted the old *.ism project to 2009 with no errors, and the project built with no errors.
However, when I run the installation, I get a "can not call DLL: IsWindow" message for every custom dialog we show. This did not happen before the conversion to 2009.
Has anyone run into this? Any ideas or suggestions?
-Andy
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 10, 2009
03:54 PM
OK, I found out why. Looks like CmdGetHwndDlg behaves a bit differently in IS 2009 than it did in IS version 9. I am getting a null handle sometimes from this call, and then using that in InstallShield's _WinSubGetWindowRect.
I do not fully understand why I sometimes get a null handle from CmdGetHwndDlg when it worked in version 9. At any rate, I easily fixed this by putting in a check for a null handle before making the WinSubGetWindowRect call.
-Andy
I do not fully understand why I sometimes get a null handle from CmdGetHwndDlg when it worked in version 9. At any rate, I easily fixed this by putting in a check for a null handle before making the WinSubGetWindowRect call.
-Andy
![](/skins/images/CC38E504FC9E1309DC48ACFEB4925670/responsive_peak/images/icon_anonymous_message.png)