Sure? How you can explain me this? Windows XP (x86) uses max 4GB RAM Windows Server 2003 (x86) uses max 32GB RAM
No change of code, registry change only I do not understand why they patch the kernel file and do not simply modify the memory limits in registry. Doing so does not require any extra boot menu nor change in system code nor removing any warning from resources. Maybe the change in registry can invoke BSOD resuling from tampering of register. The check should occur once an hour. So I will try to observe and let you know if you are interested. So 30 minutes so good.
Does it really work? Enabling the PAE is required but not sufficient to extend the RAM which Windows 7 uses.
It looks like processors' and memory's limitations are stored in system license, for Ultimate in Security-SPP-Component-SKU-Ultimate-ppdlic.xrm-ms, particularly in these lines: <sl: policyInt name="Kernel-RegisteredProcessors" attributes="reboot-required, override-only">2</sl: policyInt> <sl: policyInt name="Kernel-WindowsMaxMemAllowedx86" attributes="reboot-required, override-only">4096</sl: policyInt> <sl: policyInt name="Kernel-WindowsMaxMemAllowedx64" attributes="reboot-required, override-only">196608</sl: policyInt> System licenses are incorporated in tokens.dat while installation and kernel reads parameters from...yeah, registry (but may be they should be synchronized with data in tokens.dat?) while booting, idk how it really works... They patch kernel to make it bypass this check...
configuration Win7/Vistax64 x86 software Memory 4 GB instead of 2 GB Which has already tested? hztztzp://wzwzwz.ntcore.com/4gb_patch.php
i've done thoses mods, and frankly go for the 64 bits of win 7. win 7 32bit had lots of hangs up, ie crashing, etc ... once removed and reverted to before, all was running well. But i reinstalled everything in 64 bits, no problems since ....