Helping people with computers... one answer at a time.
Most often the trick to running 32-bit software in Windows 64 is to simply run it. 64-bit Windows has broad 32-bit compatibility built in.
I just purchased a 64-bit PC with Windows 7 Premium. I realized before getting this system that much of my 32-bit software would not work. I have heard of downloadable and free programs that will enable a wider variety of 32-bit software to work on a 64-bit system. Can you make any suggestions where to find such software?
•
Well, it's one heck of a lot easier than I suspect you believe.
I'm running 64-bit Windows and can tell you first hand...
I think you're starting with a very bad assumption.
•
In my experience, most 32-bit software "just works" in 64-bit Windows 7.
Yes, I did say "most", so there are exceptions, but in my experience they're actually not nearly as many as you might think.
I certainly would not get any "free downloadable programs" to somehow get 32-bit software to work, since as I said - most pretty much work already. I'd be very concerned that those downloads are something else - perhaps malware or perhaps trialware that leads you to eventually pay for software that you just don't need.
The processor - the actual CPU itself - actually has the ability to work in either 64-bit mode and 32-bit mode. In fact, believe it or not, for extreme backwards compatibility it also still handles 16-bit mode.
And it can switch between those modes "on the fly".
64-bit Windows manages all this by transparently changing the mode as needed. In fact, there's an interface layer called WOW32 - Windows on Windows - that provides a 32-bit interface to the 64-bit OS for 32-bit applications and handles that translation between 32 and 64 bits. (Once upon a time there was also a WOW16.) Since the Windows itself is 64 bits, that translation needs to happen as activities are handled and passed off between the 64-bit operating system and the 32-bit applications. (64-bit native applications don't need this translation layer. It's not an obvious performance win, though, for reasons beyond the scope of this discussion.)
One thing that this means is that the vast majority of software out there is still 32-bit software, including some of the software that comes with 64-bit Windows itself. Aside from drivers and such, which I'll talk about in a moment, there's not really been a pressing need to convert most applications to 64-bit - unless they were bumping up to some limitation like RAM access that a 64-bit conversion would benefit, or compatibility with some other software that has been converted.
The result? Pretty much everything I had running on my 32-bit Windows XP machine is now running seamlessly on my 64-bit Windows 7 machine without any additional effort. Case in point: I'm typing this article in a 32-bit application (Topstyle) on my laptop running 64-bit Windows 7 - there were no steps I needed to take to make that work, and certainly no software to download.
In fact, after a few additional installs and upgrades I'd be hard pressed to tell you which are 32-bit and which are 64-bit applications without firing up a utility of some sort to examine them and tell me. They all just work and that's what matters.
There are some exceptions, of course - the most obvious being device drivers.
The 64-bit operating system itself is ... well ... 64-bits. Device drivers are part of the operating system and thus need (*) to be converted to 64-bits. That's part of why 64-bit OS's took a while even though the processors were ready and deployed and why some hardware drivers still aren't available for 64-bit OS's and may never be.
(*) There may be hacks for some types of drivers that might side step this requirement, but in general drivers need to be 64-bit native in 64-bit OS's.
Other exceptions typically boil down to updates of existing applications. For example, Windows 7 comes with both 32-bit and 64-bit versions of Internet Explorer. I recently updated to a 64-bit version of Adobe PhotoShop so that it could better take advantage of the available memory on my machine when processing large images.
But these are updates to existing versions. In many - if not most - cases, the prior 32-bit version would also work acceptably well.
In fact, specifically in Internet Explorer's case, the 32-bit version is perhaps the preferred of the two simply because 64-bit support is not yet available for many popular plugins.
And of course there are applications that, by design or by accident, simply make assumptions of one sort or another that are valid in Windows 32-bit but are not in Windows 64-bit, even when running in WOW32. Those are few and far between, in my experience, and probably warrant an upgrade of the application rather than some "free download".
Microsoft did something very interesting with Windows 7 versions "Pro" and better; if your hardware supports it you can get Windows XP "mode" as a free download. XP Mode is a copy of Windows XP that you run within a window inside of Windows 7. Within that copy of Windows XP you can run whatever it was that used to work in Windows XP but for whatever reason fails to run in Windows 7. It's not completely seamless, but it is a solution for many situations where software updates are simply no longer an option.
That's the only "free download" I'd even consider.
Article C4393 - August 12, 2010
We've had quite a dilemma brewing at my company regarding Windows 7 Pro. Our custom program that we use for taking orders, shipping and invoicing was written in 1999 in FoxPro 6.0. We still use it and have been looking for other software that has the same capabilities without implementing a full-blown ERP system. However, most workstations are on XP Pro, with 2 workstations on Windows 7 Pro 64-bit. The program does work on the newer workstations, but is incredibly slow, so much so that we can't use it for invoicing. The original programmer says it is not the program, it is the environment. Our off-site tech people think it's the program, but that just might be because they haven't been able to solve the problem.
So, it has been a major issue with our company and it really putting us in a pickle due to aging workstations and the need to get a different software package that can handle our requirements. Our techs already disregarded the 64-bit vs 32-bit because the program is slow on the Windows 7 32-bit OS also. Hate to think we will have to switch to something that isn't what we need just because we can't find a solution to our problem. And so it goes...
Posted by: Mary Jo High at January 11, 2012 12:32 PMYour article on running 32 bit programs on 64 bit Windows provided an excellent and simple solution. Does this same approach also apply to 16 bit DOS programs that functioned fine on the Windows XP command prompt?
03-Feb-2012
Regarding DOS programs in 64-bit environments: I am able to run Lotus Agenda (1992 DOS program) in DOSbox 0.74 running on a 64-bit Windows 7 computer. Lotus Agenda works easily and well within the DOSbox window. However, I am unable to mark, copy, or paste from or into that DOSbox. I guess this is because the DOSbox program is unable to use the Windows clipboard. This is a severe limitation for me. Does anyone know if Windows XP mode of Windows 7 Professional version (or any other solution) will allow copying and pasting from the DOS window? This was definitely possible with 32-bit Windows Vista and prior versions of Windows. A solution to my question might help others on this string as well. Thanks very much. -dar
Posted by: Dominick at March 30, 2012 12:48 PMRe 32 bit prog on 64 bit Win 7 OS.
I have the opposite problem trying to run 64 bit on win 7 32 bit OS!
I have a new ECG monitor with this problem. It 1/2 works! Any other ideas Leo please?
09-May-2012
@Mal
Posted by: Mark J at May 9, 2012 6:09 AMThe only solution to running a 64 bit device, would be to upgrade to Win 7-64 bit. This would only be possible if your processor is 64 bit. Otherwise you would have to find a 32 bit driver for your ECG monitor, providing such a driver exists.