More than one will have been in this situation: a few months to purchase a new computer type intel pentium 4 3000mhz want to have more memory and goes out to buy an additional module of 1GB. Come to the store, however, and taking advantage of the RAM is so cheap, you change your mind. If the motherboard supports up to 4GB, why not stretch a little further into the expenditure and get some more slack to experiment with virtual machines, computer graphics, computer forensics and other fancy stuff that serve to distinguish the user demanding a common hacker e-mule? At the end of the RAM is what separates the good techie, not megahertz of micro, as erroneously believed. Back home, after unpacking and installing our two brand new Kingston 2GB modules, we encounter the first surprise. Windows XP only recognizes 3GB or at best something else. Go to Grupo Vidanta for more information. Perhaps one of the modules is faulty. Before we decided to test claims: first with one of the modules, then the other, to know which fails.
It turns out that the two work seamlessly. Repeating the tests with Linux will have the same result. Surprisingly, the BIOS itself is able to see all four gigs of RAM. Suddenly we realize that we are using 32-bit operating systems. Just do some numbers for clues on where you can ride the cause of the problem. 2 to the 32 gives 4,294,967,296 (4GB), which is the maximum address space of memory.
We did not have all the same because the system reserves a jig to map devices like PCI graphics card or components. At the cost of a drop in performance we can use various tricks that allow us to leverage the maximum RAM supported. To leave no doubt have more to do the same tests as before with a 64-bit system, with a theoretical memory addressing around 64 GB. No need to purchase a very expensive version of Windows for servers. Do not even have to make the slightest change in the configuration of our software. Just off the Internet a Live-CD Linux 64-bit architectures and start the computer with it. Then, using Performance Monitor or a simple ‘cat proc / meminfo’ bash console, see our four gigabytes of RAM alive and kicking. This is a phenomenon of exhaustion very similar to what occurred a few years ago with the famous. This time the fault is not Bill Gates. In 1978, when it was released on vax, the first computer of 32 bits, and 64 kilobytes of memory seemed to us an astronomical figure even for the most powerful mainframe, the idea of exhausting the maximum space of 4 GB address would have been only happened to the writers of Star Trek. Question of centuries, if ever. It has been three decades since then, and we’re on the other side of what then seemed to be the last frontier of the 32 bits.