Question About C:\Program Files (x86)

[MadMaxData]

Howdy Members,

I have a question concerning running programs in 32-Bit mode. The OS I'm running is Windows 7 Ultimate x64 (Retail version). The current HDD setup on my machine is two internal HDD's. The first HDD is C:\ & the second is D:\.

I run the OS on C:\ drive & have D:\ drive set up as a storage drive [pretty basic setup]. What I need to know is this. I would like to run program applications from D:\ drive in 32-Bit mode, but I'm not certain as to how I should set it up. How does the C:\ Program Files (x86) run applications in 32-Bit mode? In other words, is there some file in the C:\ Program Files (x86) folder that I should copy over to the D:\ drive folder that I want to run 32-Bit applications from, that will tell the OS to run them in 32-Bit mode? I want to make a directory of D:\ Program Files (x86) to run 32-Bit applications from. I'm sure there is a simple way to do this.

All comments are welcome, but please don't post a "guess" as a solution. If you've actually done this procedure successfully, I would really like to know how you did it. And yes, I know I could find the answer online, or find it by simply testing things out, but I thought I would save myself the time, and ask our knowledgeable members first. Any input would be appreciated though.


Thank you,
Max

 

[Jonathan_King]

Well installing programs to the Program Files (x86) folder is not the same as installing them in 32-bit mode.

That directory is just another folder. Chances are you could easily install those programs into your other Program Files folder, or your music folder, or even your desktop.

That folder just makes organization a bit easier.

 

[MadMaxData]

Well installing programs to the Program Files (x86) folder is not the same as installing them in 32-bit mode.

That directory is just another folder. Chances are you could easily install those programs into your other Program Files folder, or your music folder, or even your desktop.

That folder just makes organization a bit easier.

I want to install the 32-Bit programs on D:\ drive, not somewhere else on C:\ drive. I've tried to run 32-Bit applications from a created folder on D:\ drive already, but got error messages, because the OS tries to run them in 64-Bit by default.

I don't think the C:\Program Files (x86) is "just another folder." However, I could be wrong, as I'm not certain about that.

There are a few folders in that directory that are hidden. Like "InstallShield Installation Information." Perhaps there's something in there that tells the OS to run those applications in 32-Bit mode?

 

[Jonathan_King]

I don't of a way to run them in 32-bit mode. In fact, I doubt there is a way.

To test to see if the Program Files (x86) is just another folder, try installing to the other Program Files folder, or even just a folder on your secondary drive.

 

[MadMaxData]

I don't of a way to run them in 32-bit mode. In fact, I doubt there is a way.

To test to see if the Program Files (x86) is just another folder, try installing to the other Program Files folder, or even just a folder on your secondary drive.

Huh? I've already tried running 32-Bit applications from a folder on the secondary drive, I get errors, as I've already stated.

I suppose I could copy the Program Files (x86) folder over to the secondary drive at OS install, then deleting everything in it, but there should be a better way.

 

[Jonathan_King]

Right, those apps are just not compatible with x64.

That's one of the downsides to using 64-bit; there are a handful of programs that just won't run.

 

[MadMaxData]

Right, those apps are just not compatible with x64.

That's one of the downsides to using 64-bit; there are a handful of programs that just won't run.

But they run fine out of C:\Program Files (x86). I think perhaps your missing what I'm driving at here, Bro.

 

[Jonathan_King]

Don't copy the folder you installed to; actually run the installer again and tell it to install on the drive.

When you install the program, not only does it create files and folders, but also registry entries. When you copy the folder to another location, the registry entries are not copied.

That can lead to errors, such as yours now.

 

[MadMaxData]

Don't copy the folder you installed to; actually run the installer again and tell it to install on the drive.

I did.

When you install the program, not only does it create files and folders, but also registry entries. When you copy the folder to another location, the registry entries are not copied.

I'm well aware of that.

That can lead to errors, such as yours now.

That's not why, because I did install the applications on the secondary drive. I still think your missing what I'm driving at here.

 

[Jonathan_King]

I guess I'm not sure as to the problem then.

You have a 64-bit system, and the 32-bit program you are installing works fine if you install it to the default location, but not when you install it to another location.

Is this correct?

I'm sorry for this misunderstanding.

 

[MadMaxData]

You have a 64-bit system, and the 32-bit program you are installing works fine if you install it to the default location, but not when you install it to another location?

Now you got it, Bro. I suppose I could just do some research on it myself. I thought this would be an easy question to answer for our members. That's why I even bothered posting it. No need to go out of your way to find a solution. Unless of course, your bored and need something to do....LOL

To sum it all up...32-Bit applications only work on a 64-Bit OS when they are installed at C:\Program Files (x86). So there has to be something special about that specific folder, one way or another.

 

[MadMaxData]

I'll give you a for instance. I have a game program called Escape Rosecliff Island. It's programed for the x86 architecture. If I install it at C:\Program Files (x86) it works great. If I try to install it anywhere on D:\ drive it won't run at all. So, there has to be something special about the C:\Program Files (x86) directory.

 

[Jonathan_King]

What if you install it to another location on the C drive, like in the normal program files folder?

 

[stormy13]

Or it is just a badly written program that won't run from anywhere other than C:\.

I have all my games installed on a separate drive and have never run into one that won't run from there. As far as that game you mentioned,



Just installed it and it runs just fine. Beginning to think that there is a problem with your Windows install more than a problem with the game than anything.

 

[MadMaxData]

What if you install it to another location on the C drive, like in the normal program files folder?

That's defeating the purpose. I don't want it anywhere on C:\ drive.

 

[MadMaxData]

Just installed it and it runs just fine. Beginning to think that there is a problem with your Windows install more than a problem with the game than anything.

Come to think of it, I only tried that single program, and it was right before that D:\ drive HDD failed (Western Digital...go figure). Perhaps it was just an issue with the garbage HDD? I'll have to check into that.

 

[HammerHead]

X86 vs x64

I'm not sure if I understand the discussion here. But I run programs from my E:\ drive all the time never checking to see if they are 32bit or 64 bit.

View attachment 63224

These progs were installed to E drive. They are not all, if any X64.

 

[CommonTater]

Right, those apps are just not compatible with x64.

That's one of the downsides to using 64-bit; there are a handful of programs that just won't run.

But they run fine out of C:\Program Files (x86). I think perhaps your missing what I'm driving at here, Bro.

Relocating that folder is not as simple as drag and drop to another drive. You also have to tell Windows where it went.... It's actually a shell folder. Under XP there was a registry entry in HKLM\software\windows\currentversion\shell folders for it but I see it's not there in Win7... Hmmmmm....

 

[stormy13]

Perhaps it was just an issue with the garbage HDD? I'll have to check into that.

That could certainly be the problem, even more so if it runs fine from one drive and not the other.

 

[MadMaxData]

I just installed a 32-Bit application on my secondary drive, and it ran perfect. Therefore, it had to be the bad HDD I tried it on at first. So.....nevermind. LOL