I learned some things about the 64-bit version of Windows 7 when I built my new home theater PC. I initially thought about installing the 32-bit version of Windows 7, but it can only access 4 GB of memory.
I installed the 64-bit version of Windows 7, which came in the same Windows 7 retail package, and installed 8 GB of RAM in the computer.
Previously, I would have used the OEM license package for Windows, at a considerable cost savings. However, Microsoft changed the OEM license so that it only applies to system builders who are building the PC for sale to unrelated parties. Since I was building a PC for myself, I did not qualified for the Windows 7 OEM license.
I’ve installed some new software that is Windows 7-aware, and I’ve found that it actually installs to different directories than older software.
In the 32-bit version of Windows 7, just as in earlier Windows versions, the default program installation location is in a subdirectory of C:\Program Files.
In the 64-bit version of Windows, if you’re installing 64-bit software, the default program installation location is still a subdirectory of C:\Program Files.
However, if you’re installing 32-bit software in 64-bit Windows 7, the default program installation location is ^quot;C:\Program Files (x86)". Not only that, but with Windows 7’s protection of the Program Files subdirectories, Windows 7 creates an additional directory C:\ProgramData (no space) to store anything that the 32-bit program wanted to store in its Program Files directory.
How does it find the modified version when the program wants it? I’m not sure, but the easiest way would be for Windows 7 to look in the program’s ProgramData folder first, and then, if it did not find the file, look in the program’s Program Files folder
Windows 7 generally knows how to handle the other software. However, its security may block that software from some of its capabilities.
Fixing the issues may involve setting up individual "rules" in the Windows 7 firewall. Click on the Start button (officially, this is now called the Start Orb). Click in the
The issue may be that Windows 7 protects the Windows Registry and the Program Files directory from being modified by programs that don’t have adequate security.
Sometimes, a driver doesn’t work so I can’t use the hardware — I learned that the hard way with my HP LaserJet 1200.
- It works fine on the Windows XP computer to which it is connected.
- It also works fine for my 32-bit Windows 7 on my notebook, when I print across the network to the LJ1200 shared by the XP computer.
- It’s supposed to work with a 64-bit driver built into Windows 7.
- But, starting from a 64-bit Windows 7, trying to route to the LaserJet 1200 through a Windows XP computer does not work. Windows can find the computer and the printer but can’t load a suitable driver.