Home Page——\/——\/——\/——\/
http://www.furulevi.go.ro/
The kernel of the 32-bit version of Windows 7 has only a lock, which prevents access to more memory. More dramatically is this lock in the 32-bit version of Windows 7 Starter Edition: There the prohibition is much more rigorous and it only allows access to 2 GB of RAM:
In the 32-bit version of Windows 7 from 4 GB usually only 3.25 -3.5 GB of RAM are usable:
In general many people believe this “not usable” RAM
is occupied by the graphic card RAM:
The German computer magazine c’t has made a test
with different graphic cards (c’t 23/2009, page 165):
These results are completely incomprehensible. Why is with no video card (0 MB, connection via Remote Desktop)
512 MB RAM blocked? Why blocked a graphic card with 128 MB also 512 MB
RAM – and not 128 MB? And why blocked a graphic card with 1024 MB “only”
750 MB?
The Russian Programmers Group “staforce” has written a small program witch removes the lock in the kernel of the 32-bit version of Windows 7. “ICE Technologie” has translate this program into English. The program automatically makes a copy of the kernel file “ntkrnlpa.exe” and saves the copy as separate file “ntkrlICE.exe”. Then the program removes the lock in the copied file “ntkrlICE.exe” and integrates the new kernel file as an extra boot menu entry in the Windows 7 boot menu. So then you have the option to start Windows 7 either as usual with the original kernel file “ntkrnlpa.exe” or with the modified kernel file “ntkrlICE.exe”.
With such a patched (modified) kernel the 32 bit version of Windows 7
suddenly can use almost the entire 4 GB of RAM:
For these screen shots a 32 MB onboard graphic card is used. So 32 MB is really “hardware reserved”. The rest of 2 MB is reserved for I/O ports (USB port, serial-, parallel port, etc.).
And even 8 GB of RAM are now no longer a problem.
The original kernel still reports that 4898 MB are “Hardware Reserved” – what hardware?
The patched kernel then reports correct that only 34 MB is “Hardware Reserved”:
The RAM limit of the 32-bit version of Windows 7 is therefore 64 GB – like Microsoft describes for the “Windows Server 2003 Datacenter Edition” (see above). More extensive details – still from Vista-times – see here by Geoff Chappell.
The program makes automatically a copy of the kernel file, then removes the lock and integrates the new kernel file as an extra boot menu entry in the Windows 7 boot menu. So then you have the option to start Windows 7, either as usual with the original kernel file or with the modified kernel file.
The patch program does not need to install – it runs as a “stand-alone” program; e.g. directly from a USB stick. And it installs no background program.
What the patch is doing you can read here in German language or here in machine translation. So you also can do it manually
The patch has two small but treatable side effects:
To remove this “watermark” you can use the button “Remove Watermark”:
Then you should reboot.
To change the boot menu you can start the Windows 7 program “msconfig”:
On the tab “Boot” you can specify:
To remove the patch you only need remove the start Menu entry with “msconfig” (you can start the program “msconfig” when you enter in the search box in the start menu “msconfig”). The boot menu then will no longer appear. Because as long as only one menu item is available, no boot menu appears. The copied, patched kernel file “ntkrlICE.exe” in the folder “C:\Windows\system32” can also be safely deleted.
In a Command Prompt with admin rights you can see with the command
“bcdedit” the new boot menu entry in detail:
The text that appears in the boot menu can be found under “description“.
“testsigning = Yes” allows the patched kernel to start despite modification.
The copied and modified kernel is called “ntkrlICE.exe“.
With “pae = ForceEnable” the address extension for the RAM is activated.
Server 1, Server 2.
http://www.furulevi.go.ro/how_to_do_and_undo_the_32bit_RAM_patch_on_Windows_7.htm
——x——x——x——x——x——x——x——x(OR)x——x——x——x——x——x——x——x——x——
This patch enables to use more than 3 Giga Byte of Memory (RAM) on 32-bit Windows 7. By default Windows 7 32-bit (also called x86) recognizes more than 3 GB RAM installed in a PC, but it will not use all of that.
NOT ALL PROGRAMS CAN SUCCESSFULLY USE THE MEMORY ENABLED BY THE PATCH!!
Program used to patch Windows 7: PatchPae.
Server 2
Tested and working on: Windows Vista SP2; Windows 7 SP1.
Operating system patched in this video: Windows 7 Ultimate SP1.
Initial memory usable: 3.5 GB (only 70%)
Memory usable after patching: 5 GB (100%)
After patching Windows 7 (32bit) the memory limit will be 128GB instead of ~3GB.
-temporarily disable user account control
-temporarily disable windows defender
-make sure all commands are typed correctly (don’t trust copy & paste !!)
-make sure you have administrator rights
2. Open Command Prompt as Administrator
3. cd Windows\system32
4. C:\PatchPae\PatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
this patches kernel to enable max 128GB RAM
5. C:\PatchPae\PatchPae.exe -type loader -o winloadp.exe winload.exe
this patch loader to disable signature verification
6. bcdedit /copy {current} /d “Windows 7 (PAE Patched)”
this creates new boot entry
7. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} kernel ntkrnlpx.exe
this sets new boot entry to load new patched kernel
8. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} path \Windows\system32\winloadp.exe
this sets new loader to be new patched loader
9. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} nointegritychecks 1
this will disable verification of the loader
this will set the patched boot entry to be the default
11. bcdedit /set {bootmgr} timeout 5
this sets timeout to shorter
12. Restart the computer!
http://www.furulevi.go.ro/
The kernel of the 32-bit version of Windows 7 has only a lock, which prevents access to more memory. More dramatically is this lock in the 32-bit version of Windows 7 Starter Edition: There the prohibition is much more rigorous and it only allows access to 2 GB of RAM:
In the 32-bit version of Windows 7 from 4 GB usually only 3.25 -3.5 GB of RAM are usable:
In general many people believe this “not usable” RAM
is occupied by the graphic card RAM:
The German computer magazine c’t has made a test
with different graphic cards (c’t 23/2009, page 165):
| Graphic card RAM | Usable RAM from 4 GB |
| 0 MB | 3.5 GB |
| 128 MB | 3.5 GB |
| 256 MB | 3.25 GB |
| 512 MB | 3.25 GB |
| 1024 MB | 3.25 GB |
The Russian Programmers Group “staforce” has written a small program witch removes the lock in the kernel of the 32-bit version of Windows 7. “ICE Technologie” has translate this program into English. The program automatically makes a copy of the kernel file “ntkrnlpa.exe” and saves the copy as separate file “ntkrlICE.exe”. Then the program removes the lock in the copied file “ntkrlICE.exe” and integrates the new kernel file as an extra boot menu entry in the Windows 7 boot menu. So then you have the option to start Windows 7 either as usual with the original kernel file “ntkrnlpa.exe” or with the modified kernel file “ntkrlICE.exe”.
With such a patched (modified) kernel the 32 bit version of Windows 7
suddenly can use almost the entire 4 GB of RAM:
For these screen shots a 32 MB onboard graphic card is used. So 32 MB is really “hardware reserved”. The rest of 2 MB is reserved for I/O ports (USB port, serial-, parallel port, etc.).
And even 8 GB of RAM are now no longer a problem.
The original kernel still reports that 4898 MB are “Hardware Reserved” – what hardware?
The patched kernel then reports correct that only 34 MB is “Hardware Reserved”:
The RAM limit of the 32-bit version of Windows 7 is therefore 64 GB – like Microsoft describes for the “Windows Server 2003 Datacenter Edition” (see above). More extensive details – still from Vista-times – see here by Geoff Chappell.
The program makes automatically a copy of the kernel file, then removes the lock and integrates the new kernel file as an extra boot menu entry in the Windows 7 boot menu. So then you have the option to start Windows 7, either as usual with the original kernel file or with the modified kernel file.
The patch program does not need to install – it runs as a “stand-alone” program; e.g. directly from a USB stick. And it installs no background program.
What the patch is doing you can read here in German language or here in machine translation. So you also can do it manually
The patch has two small but treatable side effects:
- Because Windows 7 observed the changes the kernel can not boot normally. For the Microsoft programmers who often times work with patched kernel Microsoft has built in a boot parameter – an additional switch: “testsigning = Yes”). So they can test their patched kernels. With this switch the patched kernel can start easily.
- But this switch leads to the fact that on the desktop background, lower right corner (above the clock) a hint (“Watermark”) is displayed:
To remove this “watermark” you can use the button “Remove Watermark”:
Then you should reboot.
To change the boot menu you can start the Windows 7 program “msconfig”:
On the tab “Boot” you can specify:
- Which boot menu entry to be booted by default (if the user does not interact).
- How long should the Start menu appear.
- And you can delete one or the other boot menu entry.
To remove the patch you only need remove the start Menu entry with “msconfig” (you can start the program “msconfig” when you enter in the search box in the start menu “msconfig”). The boot menu then will no longer appear. Because as long as only one menu item is available, no boot menu appears. The copied, patched kernel file “ntkrlICE.exe” in the folder “C:\Windows\system32” can also be safely deleted.
In a Command Prompt with admin rights you can see with the command
“bcdedit” the new boot menu entry in detail:
The text that appears in the boot menu can be found under “description“.
“testsigning = Yes” allows the patched kernel to start despite modification.
The copied and modified kernel is called “ntkrlICE.exe“.
With “pae = ForceEnable” the address extension for the RAM is activated.
Download RamPatch——\/——\/——\/——\/
Download “32bit RamPatch”:Server 1, Server 2.
http://www.furulevi.go.ro/how_to_do_and_undo_the_32bit_RAM_patch_on_Windows_7.htm
——x——x——x——x——x——x——x——x(OR)x——x——x——x——x——x——x——x——x——
Enable more than 3GB RAM on 32-bit Windows 7 (PatchPae):
This patch enables to use more than 3 Giga Byte of Memory (RAM) on 32-bit Windows 7. By default Windows 7 32-bit (also called x86) recognizes more than 3 GB RAM installed in a PC, but it will not use all of that.
NOT ALL PROGRAMS CAN SUCCESSFULLY USE THE MEMORY ENABLED BY THE PATCH!!
Program used to patch Windows 7: PatchPae.
Download PatchPae:
Server 1Server 2
Tested and working on: Windows Vista SP2; Windows 7 SP1.
Operating system patched in this video: Windows 7 Ultimate SP1.
Initial memory usable: 3.5 GB (only 70%)
Memory usable after patching: 5 GB (100%)
After patching Windows 7 (32bit) the memory limit will be 128GB instead of ~3GB.
Before you start patching:
-temporarily disable or uninstall antivirus !!!!!!!!!!!!!!!!-temporarily disable user account control
-temporarily disable windows defender
-make sure all commands are typed correctly (don’t trust copy & paste !!)
-make sure you have administrator rights
How to do it:
1. Copy PatchPae to C:\2. Open Command Prompt as Administrator
3. cd Windows\system32
4. C:\PatchPae\PatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe
this patches kernel to enable max 128GB RAM
5. C:\PatchPae\PatchPae.exe -type loader -o winloadp.exe winload.exe
this patch loader to disable signature verification
6. bcdedit /copy {current} /d “Windows 7 (PAE Patched)”
this creates new boot entry
7. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} kernel ntkrnlpx.exe
this sets new boot entry to load new patched kernel
8. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} path \Windows\system32\winloadp.exe
this sets new loader to be new patched loader
9. bcdedit /set {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} nointegritychecks 1
this will disable verification of the loader
OPTIONAL
10. bcdedit /set {bootmgr} default {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}this will set the patched boot entry to be the default
11. bcdedit /set {bootmgr} timeout 5
this sets timeout to shorter
12. Restart the computer!
See a video about this:
No comments:
Post a Comment
Dear Friend ♥