Force install path?
Running in a 64bit environment but the application is 32-bit. I need to force it to install to C:\program files\ and not c:\program files (x86). Used the Wise Package Studio to package an application and during the install I specified the path I wanted. When I install the msi on a server it changes the path to the (x86) path. I've tried running msiexec and specifying INSTALLDIR=c:\sybase\ but after the install completes I see that it still has installed in c:\program files (x86)
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
misterd
14 years ago
Don't do it.
In 64bit land:
c:\program files (x86) is for 32-bit apps
C:\program files\ is for 64-bit apps
Now the REALLY hard to believe stuff:
c:\Windows\System32 is for 64-bit apps (I kid you NOT!)
c:\Windows\SysWOW64 is for 32-bit apps (I kid you NOT!)
Don't believe me?
Right-click on wowreg32.exe in both folders, go to properties and check out the Details tab.
Yes, it's stupid
In 64bit land:
c:\program files (x86) is for 32-bit apps
C:\program files\ is for 64-bit apps
Now the REALLY hard to believe stuff:
c:\Windows\System32 is for 64-bit apps (I kid you NOT!)
c:\Windows\SysWOW64 is for 32-bit apps (I kid you NOT!)
Don't believe me?
Right-click on wowreg32.exe in both folders, go to properties and check out the Details tab.
Yes, it's stupid
Posted by:
squintr
14 years ago
I appreciate your response however the alternative is a manual install of the application where I change the install directory during the install sequence. There is something in the application that is hard-coded to look in c:\program files (I know its dumb but I can't change it). So for my 70 or so Citrix server farm that I need to install this app on I can't install it via a package because I can't figure out how to force the install path.
Posted by:
misterd
14 years ago
There are 2 ways to solve your situation:
1-Make your poorly coded app "Think" it's running in C:\Program files using Application Compatibility Shims
(Can't help you here since I just touched this once and only *heard* that this was possible)
2-Make your MSI install "Think" you are installing a 64-bit Application
When you create a blank MSI you can choose between 32 bit and 64 bit templates.
What changes is how Windows installer will treat \Program files\ and \system32\ folders and the registry.
It does this by reading the Template Summary field in the Summary table
You can see this in WPS 7.03, Setup Editor -> Product tab -> Summary
In a 32-bit MSI, the Template Summary field will say:
Intel;1033
The key hear is theIntel part. (1033 means English, BTW)
In a 64-bit MSI, the Template Summary field will say:
x64;1033
or
Intel64;1033
x64 is what you want unless your Citrix server happen to be using Itanium CPUs then you'll have to use Intel64
By editing this "Template Summary" text field you can fool MSI to do your "bidding" and make your 32-bit app install in folders meant for 64-bit apps[;)].
1-Make your poorly coded app "Think" it's running in C:\Program files using Application Compatibility Shims
(Can't help you here since I just touched this once and only *heard* that this was possible)
2-Make your MSI install "Think" you are installing a 64-bit Application
When you create a blank MSI you can choose between 32 bit and 64 bit templates.
What changes is how Windows installer will treat \Program files\ and \system32\ folders and the registry.
It does this by reading the Template Summary field in the Summary table
You can see this in WPS 7.03, Setup Editor -> Product tab -> Summary
In a 32-bit MSI, the Template Summary field will say:
The key hear is the
In a 64-bit MSI, the Template Summary field will say:
or
By editing this "Template Summary" text field you can fool MSI to do your "bidding" and make your 32-bit app install in folders meant for 64-bit apps[;)].
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.