Custom Search

Search My Download Corner

Tuesday, May 1, 2012

Make your 32-bit Windows support more than 4GB of memory

As we all know there are 2 editions of Windows starting from XP which is the 32-bit and 64-bit. Sometimes a Windows 32-bit is referred as x86 and 64-bit as x64. A 64-bit Windows can support more 4GB of ram. If your computer has 4GB of ram and you’re using a 32-bit of Windows, you’ll notice that only about 3.5GB is being recognized and the remaining 500MB of memory is gone. Why can't a 32 bit Windows address  the physical ram fully of more than 3 GB>? The answer is simply Microsoft doesn’t want that and it is all just a licensing matter.
ARussian group called Staforce came up with crack/activator for Windows 7. This patch works on Windows 7 (x86) Build 7600 RTM. Download here
 If it doesn't work your Windows 7 (x86) version, check if there is an update in the activator option.
Yet not, refer to (Gavotte RAMDisk in Windows 7) below
-Windows Vista x86 4Gb RAM Patch-

Making Use Of Non-Addressable Physical Address Extension (PAE) in Eindows XP (32-bit) x86 processors  to full 4GB RAM or more................

For Windows Server 2003, Windows XP, and Windows 2000, use the /nolowmem parameter. The /nolowmem parameter loads the operating system, device drivers, and all applications into addresses above the 4 GB boundary, and directs Windows to allocate all memory pools at addresses above the 4 GB boundary. This parameter is valid only on boot entries for 32-bit versions of Windows on computers with x86 or x64-based processors, and only when Physical Address Extension (PAE) is enabled. Example: (edit c:\boot.ini with notepad.) multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /nolowmem Read More

32 bit versions of Windows XP and Vista cannot use the total 4 gb RAM as it has to manage the other devices of the PC. It is a limitation of the 32 bit OS. ou have to use Physical Address Extension mode. The system memory only uses 3GB in XP because its 32-bit. 

Step 1: Download RAMDisk Package-Gavotte_RAMDisk_1.0.4096 Free virtual hardisk

Step 2: Enable PAE mode in Windows XP- See Annex XP

Step 3: Reboot

Step 4: Configure PAE mode for RAMDisk-Gavotte_RAMDisk
In explorer locate the file "ram4g.reg" within the extracted set of files from the RAMDisk, double click the file to add the registry settings. The content of the REG file should look like this:Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RRamdisk\Parameters]

Step 5: Install RAMDisk  to use the stubbornly inaccessable memory between 3.2GB and 4GB. 


After reboot the RAMDisk should be displayed in Explorer 

Navigate to the folder where the RAMDisk files have been extracted and start "ramdisk.exe"
After you clicked the button there will be a warning displayed by Windows Security to validate of you really would like to install the RAMDisk, click on "Install this driver software anyway".
Now you can set the disk size in Bytes(Try on PC’s  4GB RAM, choose up 1 GB.)
, configure the drive letter for the Ramdisk. You can also specify which media type is the drive – RAM Drive, Fixed Media or Removable Media (for simulating a floppy drive). The default choice, Fixed Media indicates that the Ramdisk is simulating a hard disk drive should work in most case. Click on OK when done with configuration

Step 6: Reboot (again)

After reboot the RAMDisk as to selected drive letter should be displayed in Explorer 


Step 7: Enjoy

Now you can be sure to be able to use the RAMDisk.

 Annex XP:-TO enable PAE for systems w/ >3GB of RAM, edit c:\boot.ini with notepad. Change something like: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /NOEXECUTE=OPTIN /FASTDETECT To: 

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /NOEXECUTE=OPTIN /FASTDETECT /PAE 

 Save and reboot. You should now see 4GB of ram because its now running in a fake 36-bit mode (which let's it address that extra 1GB of ram) You’ll be able to get 4GB (or even more – you can use up to 64 GB in x86) of usable memory ONLY if your motherboard supports memory remapping feature.
[XP Pro] Enable PAE - Microsoft Help | DSLReports Forums

Another workaround for XP SP3 but cannot use any USB devices (you have to use PS2 mouse/keyboard): Unfortunately there will be problems with USB devices (pendrives and external usb hdd).Probably usbstor.sys from server 2003 or so ( as well as other files needed to proper work of hex fixed XP SP3.
1. Look for C:\WINDOWS\SYSTEM32\NTKRNLPA.EXEOriginal : BB 00 00 10 00 33 FF 6A 07 8B F0

Modify To : BB 00 00 40 00 33 FF 6A 07 8B F0.

2. Save the modified kernel as mykernel.exe, put it under C:\WINDOWS\SYSTEM32\

3. Open C:\BOOT.INI     Copy and paste your original boot option, but add
             /PAE/KERNEL=mykernel.exeexample:multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=”Microsoft Windows XP SP3 OVER 4G”/fastdetect /usepmtimer /NoExecute=OptOut /PAE /KERNEL=mykernel.exe4. 

            Reboot, choose “Microsoft Windows XP SP3 OVER 4G” from the boot menu

Hex Editor: I will be using HxD in the example. You can download it here.
You will also need to have some tools that are provided with Visual Studio. Unfortunately, you have to install Visual Studio C++ Express edition in order to get them.  The 2008 version will work, so I would recommend downloading that. You can find it here. Select Visual Studio 2008 Express on the top bar, then Visual C++ 2008 Edition. Its a fairly large download (70MB ish I believe) but its definitely worth it if it means gaining the ability to use another GB of RAM or more. Source

REMOVE Pagefile if you have over one Gigabyte of ram
How to remove Pagefile.sys from Windows 
N.B. We discovered setting Pagefile at 0 with 1 & 2 Gb physical ram CPU caused
"run out of memory"in Wins XP for program like Photoshop & Ashampoo Burning Studio.
Solution: maintain at least 1gb Pagefile and  the rest Gravotte virtual hardisk(See below).
This will give you a balance of less wear and tear on the HDD and with better access speed.

The one drawback to having more memory is, if hibernation if not turned off, you end up with a very huge hibernation sys file. (it always matches the amount of ram you have). So, if you have 4GB of "visible" ram, your .sys file for hibernation that is stored on your HD, will be a 4GB file. Also, the page file also increases the more ram you have. So, if you do not have much HD space to begin with, going 4GB could be a negative thing.

Copy of an issue regarding Microsoft's Windows XP Memory Manager tfor the need to kill the page file.  In addition to this excellent reason, another reason would be that kliling the page file would increase WIndows XP's performance and reduce the wear and tear on your hard drive thus expanding its expecrted life span for you as well.  Here is the quote:
To all concerned, This is Brian Dowding writing to you regarding a Microsoft Windows product design flaw. SRZ041029003929 is my old case number regarding this issue. This email, I believe, is much more clear and concise. The Problem: ------------ The algorhythms designed to assist manage memory resources in Windows Environments based on NT code in 32-bit environments have essentially remained unchanged in the last 11 years and were not likely made with the realistic expectation that an average home user would have more than 1GB of physical RAM in its lifecycle of usage in Windows products. Here-in lies the current problem with memory management in Windows NT/2000 Pro & Advanced Server/XP Home, Pro, Tablet, and Media Center Editions/ as well as any other version of Windows that is 32-bit and based on NT code. In a 32-bit environment, memory addressing is limited to a 4GB space. This applies to the sum of Physical RAM installed PLUS the size of the page file in place. When Windows is set to manage the size of the page file automatically, then the page file is calculated by a simple algorhythm of "Installed RAM Size" multiplied by 1.5 equals the "page file minimum size"; "Installed RAM size" multiplied by 3 equals the "page file maximum size". As a security feature, if one has the page file set manually or turned off AND the settings are drastically different enough from what the automatic management would have set it to, Windows can pay lip service to the users desired settings while managing the page file on its own instead. This can be demonstrated by setting Windows to delete the page file on system shutdown, turning off the page file altogether, rebooting, and using a third party tool like "Space Monger" to analyze the contents of the C:\ or primary partition on which Windows is installed, one will sometimes find a page file has been recreated by Windows anyway, and their settings telling Windows not to use one intact. None of this is a problem IF the user has up to or less than 1GB of RAM. Once you install more than 1GB of RAM, this becomes a serious problem to system stability. The following are examples of the algorhythm at work in a 1GB, 2GB, 3GB, and 4GB installed RAM environments: A) A system with 1GB of RAM installed: installed RAM = 1GB page file minimum = 1.5GB total memory space used with a minimum sized page file = 2.5GB page file maximum = 3GB total memory space used with a maximum sized page file = 4GB does this exceed the 4GB limitation of 32-bit addressing? = No B) A system with 2GB of RAM installed: installed RAM = 2GB page file minimum = 3GB total memory space used with a minimum sized page file = 5GB page file maximum = 6GB total memory space used with a maximum sized page file = 8GB does this exceed the 4GB limitation of 32-bit addressing? = Yes C) A system with 3GB of RAM installed: installed RAM = 3GB page file minimum = 4.5GB total memory space used with a minimum sized page file = 7.5GB page file maximum = 9GB total memory space used with a maximum sized page file = 12GB does this exceed the 4GB limitation of 32-bit addressing? = Yes D) A system with 4GB of RAM installed: installed RAM = 4GB page file minimum = 6GB total memory space used with a minimum sized page file = 10GB page file maximum = 12GB total memory space used with a maximum sized page file = 16GB does this exceed the 4GB limitation of 32-bit addressing? = Yes Now, in theory, of course, turning off the page file should be a solution for those with 4GB of RAM. Also, in theory, manual settings adjusting for the page file size so that the sum of the installed RAM and page file sizes do not exceed 4GB should solve this. However, in practice this is not a reliable remedy as Windows can and has been known to pay lip service to the manual settings while ignoring them and managing a hidden page file under the hood, so to speak, which reintroduces system instability. This is because such manual adjustments would create a significant difference between what the end user sets as a page file versus what Windows automatic settings would have been. Additionally, the larger the installed base of RAM, the larger the gap becomes. The /3GB switch has been suggested in the past. This obviously does not address the issue as it simply extends single application resource allotment to RAM maximums from 2GB to 3GB. Despite this, 4GB remains the total addressable limit in a 32-bit environment. The problem remains the same whether or not one uses the /3GB switch. How Can This Problem Be Solved: ------------------------------- I propose a simple and elegant solution. The existing algorhythm is: --------------------------------------------- Minimum Page File Size = Installed RAM x 1.5 Maximum Page File Size = Installed RAM x 3 --------------------------------------------- It should be replaced by the following algorhythm: --------------------------------------------- Page File Size = 4GB minus Installed RAM Size --------------------------------------------- This would address all issues. I would like to reiterate that this problem only affects 32-bit Windows environments with an installed base of RAM over 1GB. Thus, for example, this affects nearly 95% of the worldwide server base - not just home users with over 1GB of RAM. How Can This Be Exploited: -------------------------- One example would be a someone that managed to distribute a simple single change in the registry that turns the page file on for Windows to manage. Most servers, for example again, have 4GB installed RAM with no page file - and is 32-bit. Having the page file on makes Windows try to manage 16GB of memory space when it can only manage 4GB. Just imagine the widespread system crashes - and who would check for a working page file? Technically this would not even be a virus as just telling Windows to work as designed is the culprit.
----------------------------------------------------- How to use full 4GB RAM in Windows 7 32 Bit (Gavotte RAMDisk in Windows 7) Updated 14:42 06/06/2012
Gavotte Ramdisk is a free software which can actually convert to a virtual hardisk so that it can be accessed faster than a “real”hardisk? Why i said this virtual hardisk is faster than your “real” hardisk? This is because RAM has a faster read/write speed than a hardisk. By converting part of your RAM to a virtual hardisk, you can boost up your system performance. Download here
Before installing Gravotte Ramdisk , utilize PatchPae by wj32 which will patch the kernel to enable
 a maximum of 128GB of RAM. Follow instructions as laid out in the included ReadMe text.
Carried out all the steps stated.

1)Click on the Ramdisk.exe to start your application. If you never install any Ramdisk before, all options will be disabled except the Install Ramdisk and Cancel button. Let’s click on the Install Ramdisk to start. 2)You can choose the Disk Size and Drive Letter. For the Disk Size, please choose properly and depends on your needs.
For PC with 3GB ram or more, allocate the remaining ram above what the system recognize for the Ramdisk

If your PC’s RAM is more than 1.5GB, you can choose up to 256MB. It is advisable to keep around 1GB for your system if you are using XP and around 1.5GB for Vista & Wins 7. You can choose any Drive Letter. 3)All is done and restart system. After that, you can find your Ramdisk on My Computer. Final words: You can remove the Ramdisk anytime by click the Remove Ramdisk. Ramdisk is very useful for BT users, as BT client always read and write from hardisk, which will shorten the hardisk lifetime. By using Ramdisk, it will prevent this to happen. But, remember to copy downloaded files from Ramdisk before you shutdown your PC, else you will lost everything!

Five reasons to use a RAM disk 1) Higher PC performance. Using a fast in-memory disk for temporary data boosts PC performance up, provided you have got a sufficient amount of RAM. 2) Reduced file system fragmentation. The file system on your disks will be far less fragmented as temporary files are never written to the disk. 3)Reduced wear-and-tear of the physical disk. As temporarily files are not written to the disk, there will be fewer read/write cycles, which is especially important for Solid State Drives (SSD) installed in some laptops. 4)Less junk on the hard disk. Often software applications create temporary files that remain undeleted although no longer needed. 5)Less noise and heat from the hard disk. The system will use the hard disk less intensively as it would storing temporary files on the disk.

Quote:   A hard drive tends to simply die from being turned on and off a lot.
Especially at short intervals.
Same goes for Fluorescent Tube Light Bulbs.

USEFUL LINKS:- Licensed Memory in 32-Bit Windows Vista
 Boot Options: nx
  Boot Options: pae
Gavotte Ramdisk extended


SuperSpeed RamDisk Plus / Server v11.6.795

RamDisk Plus® shares the same features and performance as RamDisk. Its patent-pending technology adds the ability to automatically save the RAM disk’s contents when the server is shutdown, and to load it when the server is started. This feature ensures that service and application data stored on the RAM disk is preserved between restarts. Data persistence: When enabled, RamDisk Plus automatically saves the entire image of the RAM disk to a special image file located on a user-specified disk partition or volume at system shutdown.

During the subsequent system start-up, RamDisk Plus automatically loads the image into the RAM disk. Data on a “Plus” RAM disk is accessible very early in the boot process, and is immediately available to the operating system, services and other applications. Please note this "backup" and "restore" functionality is only performed during the operating system's shutdown and restart cycle. If the system crashes or loses power, any changed or new content will be lost. When the system is rebooted, the contents of the RamDisk will be the same as they were at the previous shutdown. An attached Uninterruptible Power Supply (UPS) can reduce the risk of loss but not eliminate it. For lowest-risk solutions see SuperVolume and SuperCache. SuperSpeed.RamDisk.Plus.Server.v11.6.795 Homepage
RamDisk Plus additional points over Ramdisk Free Compressed image file for faster image loading Reserve image file space required for a "full" RAM disk option Save RAM disk image automatically at system shutdown option Load a RAM disk from an image file Move an existing RAM disk's image file from one volume to another Change an existing RAM disk's drive letter System page file support Dynamic backup and restore of RamDisks Support for Partitionable Ramdisks Support for Virtual and Removable RamDisks Memory above 4 GB RamDisk Support

External related links:-
Maximum PC | The Pros and Cons of 64-bit Windows 7
Why You Should Go 64-Bit With Windows 7

View blog reactions


Post a Comment