Incorrect Program Files directory?

[moorelife]

For one of our installers, the 64-bit checkbox has been set.
As the target directory, we specified $PROGRAMFILES$\\Rogan\\View Pro-X.
When executed, this is shown as C:\\Program Files (X86)\\Rogan\\View Pro-X.
(execution on a 64 bit machine with 64-bit XP running)
But we want to install 64-bit executables, to
C:\\Program Files\\Rogan\\View Pro-X.

Are we doing anything wrong, or is this a bug?


Regards,

Dre'

[mikehancock]

I am facing the same issue- is there a resolution for this?

I tried using:
Get Environment Variable %ProgramFiles% into Variable PROGRAMFILES
Get Environment Variable %ProgramFiles(x86)% into Variable PROGRAMFILESX86

however, these both get the value of C:\\Program Files (x86) so there must be a bug in the Get Environment Variable code somewhere.

I tested the value of both these env variables in .Net and they were C:\\Program Files and C:\\Program Files (x86) respectively

[dunion]

Other than hard-coding it?

[dunion]

that is if you know you are installing a 64 bit app on a 64 bit system (there is a flag for that, you can put this in that area) you can just get SYSTEMDRIVE to a variable then construct PROGRAMFILES from SysDriveVariable + Program FilesNote for some reason you don't use the \\ at the beginning like everywhere else, not sure why, or you get two of them, because the 'old' program files variable has one at the end, I put one at the end also.

[dunion]

I did this and it creates all the directories in the c:\\program files\\...
but then it recreates them and installs all the files in the c:\\program files(x86)\\... path.

I'll have to go through the script some more. Is there a standard fix for this???

THanks.

[dunion]

for components. I included some .NET x64 runtimes as requirements. All the related scripts set the mode back to x86 at the end. If you manually change each of these scripts you're back to the correct program files directory.