It's a work around, nothing new and it does not give native 64 bit support or actually make use of all the ram, it will however in most cases tell you how much ram you have but that just gives a warm fuzzy feeling, nothing else.
Old news, doesn't give native x64 support, and not even recommended as it can lead to stability issues in the kernel and apps.
Nopes, its more than a warm fuzzy feeling. It is known than 32 bit server versions of Microsoft can access more than 4 GB of RAM (though I think there is a 4 GB limit to how much an app can use). Someone just brought it for Win7. Like @genuine555 said, this has been around for a while, and I remember something of the same lines for XP/ Vista too.
Yeah, it does work if you want to access more then 4gb in an x86 system. BUT it can lead to serious issues with both kernel and driver compatibility. It wasn't designed for home environments, and for a good reason. Kernel stability and driver functionality are the two main aspects to be addressed with much caution, as is the fact phoenix already mentioned, being capability of an app to address more then 4gb. For any home environment, it is a much safer and logic solution to just install x64. Why take the risk in compromising anything when x64 runs without the slightest issue ??? If you need x86 for whatever reason, just set up a dualboot between x86 and x64. It's the best of both worlds. And in any other case, just leave x86 behind, it's starting to belong to the past. OS architectures evolve. Evolve with it. gen
This seems to be a hack to force enable PAE, enabling the OS to use more memory, but with each app only addressing about 3.2gb. Hacking PAE by swapping tokens.dat (SPP certificates store) is a bit dangerous and can cause stability issues like gen mentioned. Hope this helps
... everytime I install this on my m15x it always fails to bood and I always have to fixmbr now the patch is somewhere lost within the system I can't seem to reverse the patch..
No thanx. This patch is just too ridiculus. Emulating x64 when you can simply use x64 just the same ? I mean come on...
Like it was described before, some old but still pretty fast processors support PAE but don't x64 OS, so this can be useful anyway. Just a note, i think the license, which stores and defines certain allowed memory values, is this (for Ultimate): Security-SPP-Component-SKU-Ultimate-ppdlic.xrm-ms. As other system licenses, it's included in tokens.dat and isn't modifiable because of digital signature...
But a patched kernel is still genuine. And software installations which do a separate genuine test also fulfils the genuine test (like MSE "Microsoft security essentials"). And the licence agreement says:
rem ** Enable more than 4GB of memory to be semi-used (displayed) bcdedit.exe /set nx Alwaysoff bcdedit.exe /set pae ForceEnable ...is in my FirstLogon.cmd...
" the 32-bit version of Windows Server 2003, Datacenter Edition supports up to 64 GB of RAM on x86-based computers. "
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 ....