Installation Manager chooses 64-bit Installation - Not 64-bit Tolerate or Exploit and Prevents 32-bit Package Install
![](http://jazz.net/_images/myphoto/6a1d69bb1e0818a6f6b83f4956307285.jpg)
I know that at some point in the recent past, I was able to install 64-bit packages with IBM Installation Manager and the copy of Installation Manager was placed under Program Files(86) on Windows but would run in either 64-bit Tolerate or 65-bit Exploit depending upon the Windows platform.
However, now I am installing these same products and the Installation Manager is going directly to Program Files (which is all well and good as long as I don't have any 32-bit packages to install later).
If I install the 32-bit package first this is not acceptable, because now I end up with a 32-bit Installation Manager as opposed to the 64-bit tolerate/exploit version (I do not want this).
What do I do? I am not sure why Installation Manager 1.8+ is not working as past releases did.
One answer
![](http://jazz.net/_images/myphoto/6a1d69bb1e0818a6f6b83f4956307285.jpg)
What really matters is the native libraries. If CDA requires 32 bit libraries, it just cannot run within a 64 bit Eclipse. I believe you have to install CDA into a separate 32 bit Eclipse base.
The below post discussed about differences between Eclipse 32 bit and 64 bit but the concept extends to other plugins as well.
http://stackoverflow.com/questions/6331822/difference-between-32-and-64-bit-eclipse