InstallAware

Hi. We are IA18 users, and we have run into a head-scratcher. I have a line of script "Install Files <path>\*.* to $TARGETDIR$\<path>, include subs" which works perfectly, except for about 12 files. The source path contains 1,073 files distributed across 26 folders. The installer builds without any errors. However, when I run the installer (tried on both XP and Win7 with same results), I get a series of "OFFLINE\<path>\foo.bar not found" errors. At first, I thought that only files with particular extensions were affected--this is NOT true. Then I thought that IA didn't like something about the names of the folders with these files--again, NOT true. When I examined the OFFLINE folder of the CD/DVD build, I discovered that the problem files were all placed into different folders from their siblings. For example, imagine a single folder with a file named "readme.txt" and several other files in it also. In the OFFLINE tree, readme.txt will be in one folder, and ALL of the other files that were in the original source folder will appear is a different folder--2 folders containing all of the original source files. Of course, I do not know if this is expected behavior, or a bug. The only other data point that I have is that we have other (older) installers also built w/ IA that include this EXACT SAME source tree that function perfectly. However, those older installers were "native" mode and this new installer is "Windows Installer" mode.

Any thoughts?

Solved. The "Include All Executables Required for Windows 8 Logo" feature is the problem.

1) All files matching *.sys are signed WHETHER OR NOT they are binaries.
2) All files matching *.cnt are affected, but it seems that those with long file names (embedded spaces) get broken.
3) All files matching *.tlb are signed as type libraries even if they are not type libraries.
4) readme.txt gets broken.
5) relnotes.htm gets broken.

In my case, these problem files were authored by another company and are included in my installer (partner agreement). Each of these files has specific content over which I have no control nor can I change them and still expect this product to work.

The only solution appears to be to turn the Windows 8 Logo feature off.

Currently only; ".EXE, .DLL, .OCX, .SYS, .CPL, .DRV and .SRC" files get signed if the the "Automatically sign all ..." option is checked.

BTW, I hope it will also possible to selectively exclude/select a file from the signature process... Maybe with the next IA releases.

Regards

Whats about a property in the "install files" dialog? BTW already 3rd party files like dll's sys gets resigned. This is realy bad.

Wolfgang Gürtl