Ask Slashdot: Best 32-Bit Windows System In 2012?
First time accepted submitter justthinkit writes "I have a number of applications that will not run on 64-bit Windows, but I would like to gain the benefits (most better caching) of having more than 4GB of RAM. Am I stuck with these Windows operating systems? And why is Windows Server 2008 Datacenter and Enterprise not included on that page? Should I go with a Linux or Win 7/8 system, and run a VM of Windows XP? Is this a solved problem or a lost cause?"
What's wrong with running Windows 7 x64, and running your 32-bit applications in compatibility mode?
Do you need 3D accelerated graphics? If not, VM is the way to go. Just RDP to the machine and do what you have to do.
Love many, trust a few, do harm to none.
>> I have a number of applications that will not run on 64-bit Windows, but I would like...more than 4GB of RAM
Do you realize that many of your 32-bit applications would freak out in a 4GB memory space?
A VM can have a 32-bit OS installed.
No sig today...
VM's can fake a 32bit cpu.... its almost like there isn't a real CPU and someone is just pretending or something...
- http://www.milkme.co.uk
Think about this critically: you probably want your operating system to be the master of its new hardware, and then you want it to interpret the needs of your older software.
If compatibility mode won't do it, set yourself up a VM and run everything in there. You can share a drive with the host OS and thus be nearly transparent.
It doesn't make sense to me to hobble the OS in order to run older software, when the newer OS is better with the newer hardware.
1. Yes
2. Dunno
3. Yes
4. Yes
5.... errm yes?
- http://www.milkme.co.uk
First and foremost, all consumer 32-bit windows versions are licensed to top out at 4GB. If you want more than 4GB, you will have to buy a (reassuringly expensive) server edition that permits it. Done. End of story.
The only other alternative is to get a 64-bit version of Windows 7 Pro. The Professional (and up) versions of Windows include something called compatibility mode, which is a free copy of Windows XP 32-bit, running inside a virtual machine. That's probably going to be your most cost-effective way of running your legacy apps on top of a 64-bit machine with oodles of RAM.
A 64bit CPU can have a 32bit OS installed. That's not the point. If the 64bit CPU is what causes his applications to fail (and not some software environment problem), then running the OS in a VM won't help because it doesn't change the CPU that the application will see. VMs are not CPU emulators. The code inside the VM runs on the host CPU.
No VM built for resource management convenience in a standard production environment is a CPU emulator, because that's horribly inefficient compared to doing passthrough. If you don't mind incurring substantial overhead, though, something like QEMU can do full emulation of an x86, ARM, MIPS, or SPARC CPU. Not at all fast, compared to passthrough(also supported with KVM or xen); but it can be done.
However you also have to deal with developers who's apps actually check what version you're running and won't even try to install.
It isn't much fun; but the Microsoft Application Compatibility Toolkit provides a mechanism for telling a large number of potentially useful lies to a program about the environment it is living in... Figuring out which ones you need is an exercise for the reader; but if you manage it you can then have the OS automatically furnish those little falsehoods every time the designated program runs.
It's a more powerful and granular version of the 'run in compatibility mode' feature, designed to keep the whiny enterprise customers happy.
This was briefly mentioned earlier, but I wanted to state clearly and concisely:
Windows 7 Professional, Enterprise, and Ultimate all include licensing for Windows XP Mode, a 32-bit virtualized instance of Windows XP SP3. It is an additional download (actually a couple downloads), but it is free. I use it every day at work (on my 64-bit Win7 machine) to run a 16-bit app that was written in 1992, while I wait for that app's replacement to be written. It works perfectly, in fact much better than VirtualBox did for the same use case (there was laggy/odd redrawing issues with VirtualBox, no matter how many resources I allocated to the virtual machine).