win 7 nin belli miktarda ram yemesinin sebebini açıklamıştım. superfetch ismi verilen bir hızlandırma çalışması diyelim. hdd de önyükleme tutmak yerine ramlerde tutma fikri bence gayet güzel, sonuç olarak ramler hdd lerden daha hızlı veri işlemekte. ssd kullanmaya başladığınız zaman göreceksiniz win 7 ramlerinizi daha az kullanmaya başlayacak. çünkü ssd ler hızlı olduğu için bu sefer ram yerine ssd leri otomatik olarak tercih ediyor superfetch derinliğini düşürüyor. %30-40 olan ram kullanımı %20-25 lere düşüyor. ayrıca benchmark testlerinde aynı makinenin 32 bit ve 64 bit işletim sistemlerinde aldığı puanlarıda paylaştım dilerseniz bakabilirsiniz.
http://blog.tune-up.com/windows- ... t-more-performance/2gb ramle her turlu 32bit almis kendi kendine celisiyorsun.32bit dunyanin en saglam ve stabil sistemlerini kullanma sebeb olur.Sorunsuz bir 64bit gormedim.32biti kur 4gb ve uzeri ramin varsa bu yamayi kur sonra bak win7 puanin ve hizin artacak ozaman 64bit kullanmamam gerektigini 32bitin kusursuz oldugunu kavrican.
http://www.pallab.net/2009/12/30 ... in-windows-vista-7/
http://www.unawave.de/windows-7- ... arrier.html?lang=EN
Windows 7 32-bit with full 4 GB or 8 GB RAM support
Do not work - say many people. And it still goes.
In the Internet often haunts the statement a 32-bit operating system can technically only managed a maximum of 4 GB of RAM. This is wrong and Microsoft is even evidence itself, that with the special version of "Windows Server 2003 Datacenter Edition" it worked:http://technet.microsoft.com/en-us/library/cc758523(WS.10).aspx64-GB RAM Maximum
... the 32-bit version of Windows Server 2003, Datacenter Edition supports up to 64 GB of RAM on x86-based computers. ...
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 RAMUsable RAM from 4 GB0 MB3.5 GB128 MB3.5 GB256 MB3.25 GB512 MB3.25 GB1024 MB3.25 GB
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 patch
The small program "4GB-RAMPatch.exe" patches the kernel and removes the kernel lock:
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.
However, you should not remove the boot menu entry for the original kernel. Because there are some very few programs that do not get along with as much RAM as the kernel patch makes available. Then you can always reboot the original kernel.
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.
