Custom TARGETDIR on 32-bit installer issues

[dmastrop]

I have a 32-bit installer, that I install on 32-bit and 64-bit machines. It has the standard destination directory dialog that comes by default with Installaware. Recently I cam across the issue that if you install on a 64-bit machine, and then change the TARGETDIR from "C:\Program Files (x86)" to "C:\Program Files", and then proceed, the files still only get installed under "C:\Program Files (x86)".

You can choose other directories and it works fine, it's just that if you try to install under "C:\Program Files", it will just create the directory structure there, but all the files will still be installed under "C:\Program Files (x86)". This is not my script changing the destination directory, this is the user, so if they choose this then it should be no problem as I understand it.

Any ideas folks? This is easily reproducible with a new 32-bit installer from template, just change the Destination Directory in the dialog to C:\Program Files and you'll see the issue.

Thanks,
~Daniel

[BobSchaefer]

I'm willing to bet this is being done by the underlying windows installer, and nothing that InstallAware is doing or can control. Regardless, if you're installing 32bit apps on a 64bit machine, they should go in Program Files (x86) and not Program Files. Now, why its creating the directory tree under one directory and then installing under the other, I'm not sure, but again, willing to be its an idiosyncrasy of windows installer and not InstallAware.