Moreover, you can patch as many executables as you choose within a single session, all you need to do is to browse to their location and select them. All in all, 4GB Patch is a nifty utility that can be of great use when you want to run x86 apps on x64 computers and you also need them to have access to all the available RAM. While this task can also be achieved using other tools as well, it is the intuitive and user-friendly interface of 4GB Patch that makes it accessible even for beginners.
I originally wrote this tool for a friend of mine who needed it. This very little tool patches x86 executables in order to let them have 4GB instead of only 2 of virtual memory on x64 platforms. This tool comes very handy for applications which need a great amount of virtual memory like games, 3D renderization, multimedia etc. It can be used by clicking on it and choosing the file or through command line e.
If you only have 4GB of memory and do not plan to install any additional memory then I would install the 32Bit version as there is nothing to be gained by installing the 64Bit version. However if you plan to upgrade to 6 or more GB of memory sometime in the future then install the 64Bit version.
Does not matter how much memory you have installed 4GB is the max. In addition other hardware also takes away additional amounts of memory usually a small when compared to the video card and the remaining memory address space is available for Windows XP, Vista or Windows 7 OS and your applications. I just reformatted my laptop. What happen to the other 1GB?
Hardware memory always takes priority over system memory and therefor there is not enough addresses left for the full 4GB of RAM. The problem here is that it will limit the kernel memory to only 1GB. Consider this program a useful tool to test with and perhaps not something to use permanently. Follow the steps below to enable a patched system, the core system files ARE NOT overwritten meaning you can revert back without too much fuss. Download the PatchPae2 command line tool and extract the zip file to a folder of your choice.
Then type the following:. This makes a copy of and then patches the Windows kernel file to enable the extra memory of 4GB and above.
Type the following to make a copy of and disable signature verification in the Windows loader file:. Enter this to create an entry in the Window boot menu, you can change the text in quotes to what you want:. Enter the following commands in turn, pressing enter after each. Now reboot your computer and you should get a new entry on the Windows Boot Manager to run the patched operating system. The good thing here is if you have problems, you can simply switch to the unpatched normal system by rebooting because the kernel files were copied and not overwritten.
When you boot the patched system, a quick check should show that your amount of memory is now fully utilized. This next image shows that Windows Resource Monitor confirms there is 6GB of memory installed and ready to be used, with over 5GB still available for use.
If you want to uninstall this patch again from your system, simply boot into the unpatched Windows, press the Win key, type msconfig and press enter. Then select the boot tab and highlight the patched boot entry, click Delete.
If after a Windows update you find the patch no longer works, re-run the command from step 3 to patch the kernel file again. Even though it does not overwrite any system files, that does not stop users from being unable or unwilling to follow the guide correctly, which could stop the system from booting into Windows. It worked for me, just follow the instructions.
Intel Core i5 2. Now i have to install windows again. Only makes copy? Does not affect your current windows? If you have had so much trouble you likely have not followed the guide properly or you tried to cut corners. Had you followed the guide correctly you would have had a separate boot menu entry for the 4GB patch and your original boot entry that can be used to boot normally without the patch.
The whole point of this tool is it does NOT overwrite any system files and instead makes a copy of a couple and then uses them to boot the system.
Whether your files were overwritten or not, it would have been entirely possible to get your system back up and running without too much trouble. The patchpae2. However, Jarek has modified the patcher to work correctly with the new loader: jurasz.
Which may be what the OP was talking about, albeit poorly explained. Rather than do a hard shut down I let it proceed, eventually it said it could not be fixed. After reboot I was able to boot to the unpached version successfully.
I then proceeded to the download jurasz. It is just the executable. I figured being in the system32 directory would still apply so ran step 2, 3 and 4 using the executable from jurasz. I have successfully booted using the patch! Thank you very much for your hard work.
And thank you to those of you with positive comments. As mentioned above some of your comments were key to success! Thanks again! No wait! Truly Awesome! Someone mentioned something about instability.. Cannot comment on that at the moment as posting this comment is one of the first things I have done since the successful boot only about 40 minutes runtime since boot but so far looks great.
It worked for me, but Windows 7 became unstable. My computer rebooted randomly twice before I decided to delete it. I patched mine and the signature override failed, but I completed the patch and made it default boot os in msconfig. I went through the list of commands, at step 4.
Thansk in advance. Element not found. Most probably YES. Generally, there could be eventually some issue with poorly written drivers p. I am using desktop win7 32 bit with 4 GB installed but only 3.
I followed the steps but it failed at Step 4. Could anyone help, please? Thank you in advance. If this tool works with the model, it stands to reason it will also with the dc At present, I installed the 8GB to the unit but only 3. Both machines are 32 bit, and have ATI radeon graphic card, with Pentium 4 for cpu, 3.
For instance, it could crash and burn on the 4GB machine just by the fact it has 4GB. There is no extra RAM to get back because the 0.
Okay, we get access to it without hacks, but.. Also, 32bit software is executed in 64bit enviroment not as native, its emulated. All it does is allow the OS to see the extra memory, nothing is done to the memory itself. How can I overcome this? Hi Greg, You should try 32 bit only driver. It is possible that your 64 driver has a 32 bit driver as well but make sure that it has one. I was able to successfully patch the kernel as per step 3.
When doing step 4 PatchPae2. Just in case I finished up the steps and rebooted to the patched OS and it crashed. I deleted the patched Boot entry in msconfg, and started over rebuilding the patched OS but using the original winload. Still crashes. Any thoughts or suggestions? It seems to me your article is aimed at people who are running 32 bit windows on 64 bit systems.
If however they are using it on a 32 bit system 32 bit processor such as say Pentium IV or so for example , then there is indeed a physical reason why the OS cannot access memory up to and possibly above 4Gb and that has to do with the systems possible inability to actually address that memory at a hardware level, in order to do so the system must support PAE Physical Address Extensions , but even then, PAE is not supported on all 32 bit systems and is typically only present on some of the most recent 32 bit motherboards say within the last years or so roughly.
Of course if they are using a 32 bit version of Windows on a 32 bit system that supports PAE then there is also no real need for software like you mentioned in your article to enable support for PAE in the OS as versions of Windows from Windows XP on up already have support for PAE built in. Though admittedly in the case of Windows XP at least it may not be enabled by default and may need to be enabled through the use of a boot. The details of which can be found easily enough using google.
Additonally there are boot. On another note there are also a few utilities available that can be used to patch 32 bit programs so that they may be able to take advantage of memory above roughly 2Gb making them hence LMA Large Memory Aware , I myself have used one such program to patch the program Bryce 7.
One such utility can be found at ntcore. So if it boots, you can hack windows to use it. I tried the 2 modules in one machine, it worked fine, I tried them in my machine and the machine will boot up but will eventually blue screen and I have to revert to the original boot. The 1st machine worked perfectly, seeing all 4Gig of memory.
Where should I look? Oh, the laptop is an Acer Aspire But, will this modification process open up the computer to malicious exploits? What are the risks? And, how can I mitigate them? All patching is successfully applied but after reboot computer goes to repair mode, peforms some analysis and says that ntkrnlpx.
As I can see this problem persists for years but nobody could find a desision…. Not the tool in the article but the author has a different version out for Win wj Using real double quote in ascii, not some weird variant you got by cutting and pasting from this page.
I think some web publishing blog engines try to pretty up the double quote by turning it into the leading and inverted ones in pairs. Ok Cool.. I tried. I got the same problem as Tim Edwards. However I have not tried disabling my antivirus yet during the patch of the 2nd command line for creation of winloadp.
So if this step fails for you. This also means it may be more advisable to work in a non-networked environment. I will be trying again by turning off antivirus and unplugging my lan later when i get back home tonight to attempt this again. Tim, if you read this. However on startup my screen displayed some fuzzy lines and when trying to login it blue screened. Slack, just go get a 64bit version.
As I said I would look at Rampatch and report back. I have ran the program and received a copy of ntkrlICE which is a patched copy of ntkrlpa which is the original kernel..
The program does NOT at least for me write a boot load change and make it available on a reboot.. The fact is, it wants to review and repair the load just as it does for patchpae. I edited the command structure from patchpae to get the boot loader added. I suspect the issue is in the boot loader. The author of rampatch says the program will edit the boot load file, if that is the case how and where does this happen? Poor documentation is more the norm than quality writing.
Nothing works. Some users report mixed results as well as working versions. I find nothing to work for me. I am through with this moon walk and hope someone else will report a DETAILED writing of how they got a working version for either patchpae or rampatch. Best of luck. Upon several trials it never works. The pathing to the folder used for the installation does not allow at least me to run the file from CMD. The operations at least worked until the above failure.
Everything else seems to be in place and will work. In short it fails all the way around. I am an old DOS guy so I am with in my element.
0コメント