This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
BMCEngineer
Level 3
‎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
Labels (1)
Labels
0 Kudos
(1) Reply
BMCEngineer
Level 3
‎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
0 Kudos