/build/static/layout/Breadcrumb_cap_w.png

How to use a 32 bit msi on 64 bit machine

I have a 32 bit msi, is there any way to install files to c:\programfiles instead of c:\program files (x86) on 64 bit machine other than changing the template summary to 64 bit.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: StockTrader 8 years ago
Red Belt
0
I bet there is a trick to achieve that but I do not think that is a good idea.
I found some speculations about why the directory are separated and what could happen here:
 Kind regards,
Marco - StockTrader 

Comments:
  • The short answer is no, not without changing the template summery as you mentioned.

    My 2p: Just leave it alone if it works fine! There's a reason why its shoved into the PFc86 folder, as stated in the link StockTrader shared.

    The only time where you need to shove the files into the PF on a 64bit system is when the app is crap and has hard coded paths, but this doesn't happen very often. - rileyz 8 years ago
    • I totally agree....it may break something as well. - StockTrader 8 years ago
      • The application is developed by our internal team members long back and they hard coded it, which we came to know as the application is launching fine only if it is getting installed in the c:\program files instead of c:\program files (x86).

        We never encountered this problem with the application till now as we are using that application in 32 bit machines only till now.

        Now we need to move it to 64 bit machines.And we don't have the source code also to change it.

        Is there anyway we can achieve it? - ur00361883 8 years ago
      • Lame, sucks that its hard coded.
        1) Get it updated if you can? I doubt the business would be willing to pay.
        2) You could hard code a path to install to C:\PF\YourApp, you need proper Windows Installer authoring tools to do this, you can do it with Orca/Instead - its not easy tho, and I recommend you not try unless you know what you are doing. You be wanting to use the [WindowsVolume]Program Files\YourApp - WindowsVolume being the important bit. Things might blow up when you run the app with registry redirection etc. Test it and see what happens?
        3) you could try using Symbolic Links, I think the term is a hardlink, so you create a symlink (folder) to PFx86\YourApp in PF - when you look at PF, its really looking at PFx86\YourApp. The command is mklink - google that and have a good read. - rileyz 8 years ago
Posted by: apptopack 8 years ago
Red Belt
0

By doing so, wouldn't it break the application functionality at any least cost? Have you tested it manually by moving the files to c:\ProgramFiles?

If it works, then let me know. will give you a solution.


Comments:
  • The application is developed by our internal team members long back and they hard coded it, which we came to know as the application is launching fine only if it is getting installed in the c:\program files instead of c:\program files (x86).

    We never encountered this problem with the application till now as we are using that application in 32 bit machines only till now.

    Now we need to move it to 64 bit machines.And we don't have the source code also to change it.

    Is there anyway we can achieve it? - ur00361883 8 years ago
Posted by: anonymous_9363 8 years ago
Red Belt
0
Any company that allows apps to be deployed with no Configuration Management System behind it deserves everything it gets, frankly.

Find a proper developer and get it re-coded but first, get some CM!
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ