I have Windows 7 64-bit and I have an installer for a program, but I want to have the program install the 32 bit version of itself instead of the 64 bit version. Anybody know how to force an installer to think you're running 32-bit windows?
Windows – Make an installer install in 32 bit
32-bit64-bitinstallerwindowswindows 7
Related Solutions
The Same thing happend here. The Adobe web page indicates in the troubleshooter that does not always work. the ActiveX instant installer does not work right. I tested for Browser security and ActiveX filtration, and that did not solve it, for me.
The links at the troubleshooter for the Manuel install are incorrect (or aged). I am not the only one who discovered this. http://forums.adobe.com/message/3961077#3961077 (Forum: why are the direct links not updated.)
At this link below, is the manuel install for flash, "download and self-install" type. It is for deployers and developers , so I avoided it at first myself. It may require Admin install, or elevated (RunAS admin) I do not know.
http://www.adobe.com/special/products/flashplayer/fp_distribution3.html
More Stuff:
The 64Bit installer installs both the 32Bit and the 64Bit, I used the EXE installer version myself.
The Browser and the flash control items should be closed prior to installing.
If you get a Green screen or a crash at Youtube specifically (does not happen at all flash video sites). Right Click the player, and get into the Settings, and turn off "hardware accelerated video". . . For me and others, it was an ATI/AMD card, but I am not sure if it is ATI specific yet, or is due to Youtube ADDs. No persons that I read about, fixed the hardware acceleration problem, by changing to a different version of video drivers.
ADDED: hmmm, seems that the "green flash of death", is not as hardware related as they suspected. I just achieved a clean flash install that works perfect , when the other install had that bug? strangeness.
Also In the "flash installer troubleshooter" is info about removing the old flash first, that is related here, but not likely the cause of the instant install failure. I was able to lap install a 10 version with the 11 version. Uninstall should be simple though, in the Programs and features uninstall program.
If somehow uninstall does not work, on thier site they have an uninstaller, I did not test that yet.
Short answer: To ensure legacy 32-bit applications continue to work the same way they used to without imposing ugly rules on 64-bit applications that would create a permanent mess.
It is not necessary. It's just more convenient than other possible solutions such as requiring every application to create its own way to separate 32-bit DLLs and executables from 64-bit DLLs and executables.
The main reason is to make 32-bit applications that don't even know 64-bit systems exist "just work", even if 64-bit DLLs are installed in places the applications might look. A 32-bit application won't be able to load a 64-bit DLL, so a method was needed to ensure that a 32-bit application (that might pre-date 64-bit systems and thus have no idea 64-bit files even exist) wouldn't find a 64-bit DLL, try to load it, fail, and then generate an error message.
The simplest solution to this is consistently separate directories. Really the only alternative is to require every 64-bit application to "hide" its executable files somewhere a 32-bit application wouldn't look, such as a bin64 directory inside that application. But that would impose permanent ugliness on 64-bit systems just to support legacy applications.
Best Answer
What program is it? Usually there are separate installers for 32bit and 64bit just bundled into one MSI. If it came on a CD try browsing around the disk to find the 32bit installer. If you downloaded it, check your temp folder when you first open the installer or use the MSIEXEC command line options to extract the files into a temp folder.