Jeff,
I think this might be an MSI thing. I know that with Visual Studio setup projects you can choose to make the set-up package 32 bit or 64 but there is no equivalent of "Any CPU". If you create a 64 bit package then it simply will not install on a 32 bit machine. So you have to create a 32 bit package which as you say defaults to going in the 32 bit program files directory which is "c:\Progam Files(x86)" on 64 bit machines.
Not sure about advanced installer itself, but maybe instead of letting it use the default target directory you could 'hard code' (create a folder) "c:\Progam Files\..." and do it that way instead. Just guessing though
The fact that it is in the 32 bit program files folder doesn't mean it will run as 32 bit, so it should be fine to run from there. I guess what we really need is "c:\Program Files(Any CPU)" folder !!!
LJ
FOLLOW US
Get the latest news in Application Packaging