Windows 7 Starter 4gb Ram Patch
This preview shows page 1 - 2 out of 3 pages. The Windows 7 Starter edition is only available in a 32-bit version. Starter edition is only available in a 32-bit version. The 32-bit OS is not at fault here, if windows 32-bit was the issue here then it would report around 3-3.3gb of ram. Its most likely an issue with the BIOS while the BIOS has been can read the chip size of 2x 2GB for a total of 4 it is only setup to use up to 2GB you see this a lot with the intel 945-965 chipsets.
I stumbled across a hack to remove the query of ZwQueryLicenseValue from the NT6/7 kernel and tried it out. It took quite a lot of searching because the numerous file hosters were all being ad-ridden annoyances. And it's in Chinese. Or Japanese, I don't know the difference. As most of us know, there's no physical reason why 32 bit Windows can't use a ton of physical RAM other than Microsoft saying 'No', especially when Server 2k3 and Server 2k8 can use a ton of RAM on the same code. The programs you need are here: The main program is 'ReadyFor4GB.exe'. This is a kernel patcher.
It'll copy the kernel and patch the copy, saving it as%windir% system32 ntkr128g.exe. It'll verify that the patch can be applied before applying it. To use this, click 'Check' and see what ActiveAllow comes up with. If it's 4096, then your copy of Windows is limited to the usual 3.2-3.7 GB of physical RAM. It should be.
Then drop down a bit in the window and click 'Apply' to copy the kernel and patch it. However, this is not enough. It's okay having a version of the kernel that doesn't check whether it's banned from using more memory, but the system won't boot an unsigned kernel. To make it use the unsigned kernel we have to remove a bit of security by setting 'testsigning' on in the boot options with bcdedit.
The script 'AddBootMenu.cmd' will do this and set you up a new boot option to use the new kernel. You then reboot, select the new 128GB kernel, and load into Windows. Usually the system will then load the desktop, load startup programs and crash (0x0A or 0x1A usually) because some driver you have really hates large addresses. That's up to you to figure out which driver's being naughty, usually legacy 2k/XP drivers you may be using for older hardware. So then you just reboot into the supported version of Windows, chalk it up to something that doesn't work and be on your merry way, because the hack is adding a kernel, not replacing anything. Have fun poking around but please don't use this on a production system, for obvious reasons. Hey, I didn't say there was a point to this or even a use for it!
I figured out which driver wasn't liking it, an old Highpoint ATA controller, had a quick blast around Fallout 3, and took the obligatory proof of concept screenshot before rebooting back into supported Windows. All 4 GB available to a 32 bit OS. I'll have to say that the extra 650 MB makes all the difference, I really noticed the extra.who the fuck am I kidding, I didn't notice a damned bit of difference other than a small RAID array being missing! There's more irony here than I realized at first. The main compromise made during the hack is driver stability, yet only good reason to run x86 instead of x64 is.driver stability!
(unless you want to do an upgrade instead of a fresh install, I suppose, but who does that?) So for this hack to make practical sense, you'd need to own hardware whose manufacturer is incapable of releasing stable x64 drivers (grr.MOTU firewire soundcards.grr.), but wrote an x86 driver so solid that it handled the 4GB physical addressing barrier correctly on its very first try. (since we can safely assume they aren't developing on hacked kernels themselves; and these bozos never give server OSes a second glance).
Windows 7 Ram Max
Seems like I'm jumping on the bandwagon, but I concur: 'Why bother!?!?' There are 64-bit versions out there to use. That said, I had wanted to roll out Windows 7 64-bit, had a perfect image ready to go, until: no printer drivers! Then I had a Vista 64-bit image, until: imagex barfed!
How To Install 4gb Patch
Then I had a Vista 32-bit image, until: one application barfed! I ended up putting that application into a virtual machine running XP.
Well, enough of that. Anyway, even if you.can. go beyond 4GB with 32-bit Windows, bad idea in a production environment.