DecodePointer Error when Running Install on Windows 2000

Sheri_Steeves · Postby **Sheri_Steeves** » Tue Oct 29, 2013 12:38 pm

Hello,

Since upgrading to InstallAware 17 my installs will not run on Windows 2000. I get the error message "The procedure entry point DecodePointer could not be located in the dynamic link library KERNEL32.sdll".

Any ideas?

Sheri

Postby **FrancescoT** » Tue Oct 29, 2013 1:06 pm

Dear Sheri,

are you calling any dll with your script?

If you are calling the "KERNEL32.dll" ... please have a look at your code ... this because with your post you wrote "KERNEL32.sdll".

Regards

Sheri_Steeves · Postby **Sheri_Steeves** » Tue Oct 29, 2013 1:21 pm

Franscesco,

Sorry, I did mean KERNEL32.dll.

I am calling dll's to register later on after the program files have been copied to the target system but I never get to that point. I get that error message right after I double-click the install and it has finished verifying the install.
I don't see any of the wizard dialogs, or ever get to my custom actions after the files have been copied.

I tried the /l flag on the setup program but it did not create a log file either.

This same install project, when built with IA15 worked. The install program was the same; no changes made except the version upgrade of the installer, and a product version variable.

Sheri

Postby **FrancescoT** » Wed Oct 30, 2013 11:22 am

Dear Sheri,

did you use the "Unicode Upgrade Tool" to migrate setup projects from older InstallAware versions to Unicode versions of InstallAware?

which IA 17 version are you using?

Regards

Sheri_Steeves · Postby **Sheri_Steeves** » Wed Oct 30, 2013 12:02 pm

Francesco,

No, I did not even know about the Unicode Upgrade Tool; I went from IA15 to IA17 and just opened and re-saved my existing .mpr files.

I am running IA17 (Build 8.20.13). I will look into the tool. I think one of my installs was created directly in IA17 and it still gives me the error message but I will double-check that.

Sheri

Sheri_Steeves · Postby **Sheri_Steeves** » Wed Oct 30, 2013 12:26 pm

Franscesco,

I ran the Unicode migration tool on one of my install project folders. It did not make a difference.

You release notes (blog) said you "rebuilt InstallAware from the ground up" when you moved to the fully UNICODE version. If you moved to the new Visual Studio 2010 compiler when you did this there is a chance that this is what is causing this problem. We ran into this here with our own programs when we moved compilers.

Here's some links if you are interested:
http://qualapps.blogspot.ca/2010/04/visual-c-2010-apps-dont-support-windows.html
http://www.zachburlingame.com/2011/03/targeting-windows-2000xp-rtmxp-sp1-from-visual-studio-2010/

Sheri