64 bit os means reading more than 3.2 gig ram?

Actually i have been testing X86 Kernel systems the last 3 days and heres the thing:
-Windows XP SP2 32Bits Kernel only can work until 3.2 - 3.5 GB RAM (no point using PAE switch because the only thing that he gonna change is displaying 4GB of RAM (is a fake).
So if we gonna see any patchs for XP in the future,the Cracker got to know how to reverse engenering
Kernels and add more programming in the kernel because the kernel it self have an limitation of 3.2 or 3.5 of RAM.
Evn although, the XP SP1 add the PAE switch enabled so the system could "see 4GB of RAM", it couldnt go any forward than that (Its all Software limitations)
-Window Vista X86 32 Bits Kernel can go until 64/128GB of RAM with an patched kernel
saying to kernel to not limite the system of the 4GB of RAM and actually work with all physicall RAM installed.
And VISTA can manage more memory because the Kernel it self was programed so he could manage with 36 Bits extensions along with the CPU.(on this days is all file paging before it can go to RAM..thats why.. and the kernel from this OS can manage 36Bits for it..)
Windows 7 X86 32Bits Kernell can also go until 128GB of RAM but with an patched Kernell too.
And Windows 7 also can manage more memory because the Kernel it self was programed so he could manage with 36 Bits extensions along with the CPU.(on this days is all file paging before it can go to RAM..thats why.. and the kernel from this OS can manage 36Bits for it..)
The last 3 days i have been trying to create an windows XP SP2 and SP3 32Bits but
with an Kernel and is dependencies of an Windows Server 2003 Enterprise 32Bits (It loads a few files to memory and then he stops)
So, all the ideas of putting an XP 32Bits running and managing more than 3.2 or 3.5GB of RAM are desmissed (for now..).
Hope that helps
 
Last edited:
Back
Top