Posts Tagged ‘32-bit’
In my previous post on 64-bit systems I was somewhat dismissive of applications being able to use PAE and other technologies to allow a 32-bit operating system to use more than 4GiB of memory. We’ve since asked:
And the answer is, in truth, yes. Yes, you can. But it’ll cost you and, probably, make your life difficult. It’ll also make people wonder why you wanted to try it in the first place too, what with all these new-fangled 64-bit processors and operating systems flying about using whatever memory they need to do whatever they like.
There are many technologies for achieving this, these include PAE, PSE, PSE-36, AWE (Windows), mmap (Unix/Linux) and they all have one thing in common: they require special support to use properly. In some cases forcing the issue means things can and will break, horribly.
TL;DR Version: All these technologies are there for developers. They provide no immediate solution for end users.
In this post we ask two related questions about downgrading.
Granted these are quite distinctly different intentions of end results, but they do share a lot of similar ramifications regarding what you are allowed to do within the scope of your Windows licence.
Downgrading 64-bit to 32-bit.
This not actually a real downgrade as it is simply changing the bit-ness of your operating system but people think of it as a downgrade as it is almost a step backwards in terms of compatibility. If you have more than 3GB of memory then you should almost never consider this as an option as, for reasons I have already stated, you will be effectively crippling your computer.
I’m going to start again by using the Microsoft End User License Terms search tool and present in all versions of the EULA is the following section:
2. INSTALLATION AND USE RIGHTS.
d. Alternative Versions. The software may include more than one version, such as 32-bit and 64-bit. You may use only one version at one time.