Solved

What happens when a program is placed in the "program files (x86)" directory?

Posted on 2008-10-01
4
221 Views
Last Modified: 2013-11-29
I was wondering what happens when a program is installed in the "program files (x86)" directory versus the "program files" directory in Windows XP64. I know that one is for x86 programs that are installed and the other is for x64 programs that are installed.. But, does Windows look at each directory differently? or are each programs installed there flagged to run 32-bit or 64-bit?
0
Comment
Question by:jvilla1983
4 Comments
 
LVL 77

Accepted Solution

by:
arnold earned 125 total points
ID: 22615711
The OS does not distinguish based on a parent folder.
The program Files and program files (x86) are mere suggestions by the OS/installer on where to store an application.
The designation is often to simply a software audit to determine which application are 64 bit and which are 32 bit.

There is no functional significance on the windows side to start an application 64 bit or not in any folder.

Windows stores much of the data in the registry i.e. wow6432node will include 32 bit applications, etc.
A 64bit OS will often translate/transform a 32bit application access attempt into the registry to direct the application to the wow6432node hierarchy.
0
 
LVL 47

Assisted Solution

by:rpggamergirl
rpggamergirl earned 125 total points
ID: 22619906

>>> are each programs installed there flagged to run 32-bit or 64-bit?
<<< 
The 64-bit is running in its native environment while the 32-bit which is the "program files (x86)" directory' is running within an emulator(WOW64 emulator).
Windows makes 64-bit and 32-bit programs runs separately because 32-bit and 64-bit don't mix, 64-bit files and 32-bit files are separate.
A 32-bit app can not run natively in a 64-bit environment, they just run side by side without mixing or sharing any files.

When you install a 32-bit program in a 64-bit environment, the WOW64 emulator makes the program thinks that it's running inside a 32-bit environment. So when the program's own installation wizard installs files in the system32 folder, it has no idea that its actually writing/installing files in the Windows\SysWOW64 folder.
And from thereon, whenever a 32-bit program needs to read/write files to or from the system32 folder all requests are redirected to Windows\SysWOW64 folder.
0

Featured Post

Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question