InstallAware

A developer at our site has just installed InstallAware and tried to build the setup using the project I authored. However, it is warning that it cannot find the .NET 2 SP1 and Visual C++ runtimes. The warnings say:

"WARNING! No files matching wildcard pattern C:\\PROGRA~1\\InstallAware\\InstallAware\\runtimes\\vc8bin\\*.*"

and

"WARNING! No files matching wildcard pattern C:\\PROGRA~1\\InstallAware\\InstallAware\\runtimes\\net2sp1bin.7zip"


He has IA installed to "C:\\Program Files\\InstallAware\\InstallAware 8\\." Notice how the warning is missing the " 8" from the path. This is coming from the setupvc8 and setupnet2sp1 scripts that are part of InstallAware. The scripts are getting the path using #IADIR#. Apparently #IADIR# is not evaluating correctly on his system. Why might this be?

Thanks.

Another developer here has just seen this same problem. Has anyone else seen this? Perhaps someone from InstallAware could weigh in here...

Install aware is installed to its default location:

C:\\Program Files\\InstallAware\\InstallAware 8But when he builds the installer, it's looking for the runtimes in:

C:\\Program Files\\InstallAware\\InstallAwareInstallAware is not expanding the pre-defined compiler variable, IADIR, correctly. The error is coming from the setupvc81 script which is part of the default InstallAware program. It's not coming from a custom script.

You should check exactly what path #IADIR# is resolving into. For instance, try to display a MessageBox with #IADIR#.

Also check if short path names are enabled on the affected systems.

Thanks, Michael. Will do and will post back with results...

Michael,

I just realized I forgot to post back to here with what I found. Both developers that saw this problem have the following reg value set to 1:

HKLM\\SYSTEM\\CurrentControlSet\\Control\\FileSystem\\NtfsDisable8dot3NameCreation

The default is 0. Is having this set to 1 known to cause issues with IA?

Ah, that's great to know. Yes, certainly - that would cause problems with InstallAware.

Thanks, Michael. Is this a known issue that's documented for IA? Is it a considered to be a bug that will be fixed in a future release?

It's not considered a bug.

FWIW, that registry setting will cause all sorts of problems with other applications.

Can anyone comment how to fix this issue? I am experiencing the same problem. I set the registry setting back to the default value. However when it tries to get runtimes, it still tries to access C:\PROGRA~2\InstallAware\InstallAware instead of C:\PROGRA~2\InstallAware\InstallAware 15\

I can't seem to find where I can fix this bug myself? I searched the registry for the incorrect value that InstallAware assumed, but cannot locate it. I tried doing a repair install for InstallAware, but that did not seem to fix it. Can anyone help?

Dear User,

could please verify if the following helps you?
http://www.installaware.com/forum/viewtopic.php?f=2&t=9469

Regards.

It helped in letting me understand the bug. I was able to fix my problem due to the bug by doing a full uninstall/reinstall after enabling 8.3 file naming.

I'm happy you solved.

Regards