4GB in 32bit - concerns about patching kernel - PatchPAE2

[mt12345]

I use 32bit version of Windows 7 on one of my machines, because some older programs don't work on 64bit.
I use patched kernel (PatchPAE2) to use whole 4GB of RAM, it seems to works fine.
I'm concerned however about security and stability.
In linux world PAE kernel (and patching the kernel in general) is pretty much standard, but in Windows it seems like nasty 'hack'.
I didn't find much info about it, many people strongly advise not to use it but they can't support their opinions by any example. Does anyone here have experience?

 

[Megahertz07]

You have 4G of memory and use internal graphics. The ideal OS for this scenario is Win 7 32.
The Win 7 32 will use 3,2 G and the internal graphics (and other hardware) will use the remaining 0.8G.

I can't see the miracle of patched kernel. 32 bits OS can only deal with 3,2 G. That's not a Windows limitation. It's a memory address limitation (32bits).

I would use the standard kernel.

 

[SIW2]

32-bit Windows Server 2003 running on 64-bit processors supports 128GB. The limit is 64GB on 32-bit x86, but higher on x64 processors.

 

[mt12345]

Im thinking about memory upgrade 6GB or 8GB

 

[mt12345]

the internal graphics (and other hardware) will use the remaining 0.8G.

actually it's 2.96GB not 3.2GB so internal graphics (and other hardware) uses 1.04GB. what for?!

 

[Megahertz07]

If you have now two memory sticks (2+2) G, my suggestion is to buy a match pair (4+4)G.
If you don't want to have memory problems, don't mix different memory types / sizes.
You'll need to do a Win 7 64 clean install.

 

[mt12345]

Two scenarios:

1.PC with 4GB ram windows 7 64 standard kernel - it uses full 4GB ram but some old programs dont work
2.PC with 4GB ram windows 7 32 patched kernel - it uses full 4GB ram and all old programs work

Im asking about any issues I may get in scenario 2.

 

[LMiller7]

Windows RAM limits, particularly in 32 bit versions, are rather complex.

A 32 bit OS has a nominal 4 GB physical address space. But since this address space but be shared with memory mapped hardware devices which must have priority not all of this is available for RAM. Typically about 3.25 GB is available but it can be more than 3.5 GB or less than 3 GB. I have a 32 bit system with 3.46 GB while some older motherboards simply limited it to 2 GB. If system RAM is shared with the video system, very common with laptops, this value will be further reduced.

But 4GB is not an architectural limit in a 32 bit OS. Even prior to 2000 there were many 32 bit processors with a 36 bit physical address bus which supported up to 64 GB RAM. Windows 2000 Enterprise Server officially supported 64 GB RAM. Not that there was much hardware available at the time that could provide that much.

It is the PAE kernel that makes this possible. PAE is not a hack that has a major performance impact and can only be used with special PAE aware applications.The performance impact is minimal and any application, even those that predate PAE, can freely use RAM over 4 GB. The method that PAE uses is essentially the same as used in modern 64 bit systems and is in fact somewhat simpler. Any 32 bit OS that is using DEP, enabled by default on compatible hardware, is already using the PAE kernel.

However, when XP SP2 was in development Microsoft discovered that considerable numbers of third party device drivers behaved very badly when RAM existed over the 4 GB mark. For that reason the kernel in XP SP2 was modified to ignore any RAM above 4 GB. This means that PAE does NOT allow using more than 4 GB RAM. This limit has been maintained in all later 32 bit client versions of Windows, right through to Windows 10. It is also a licensing limit.

Note that this limit does not apply to 32 bit server versions of Windows, some of of which support up to 64 GB RAM with a 32 bit CPU and 128 GB with a 64 bit CPU. The driver problem was most common with video and audio devices. Servers tend to have very basic video that rarely have this problem and many do not have audio capabilities at all.

How serious the driver problem is now in 2017 is difficult to say. It could be argued that such problems would have been fixed long ago and are no longer an issue. That may be. It could also be said that since the kernel does not officially support more than 4 GB RAM developers have no reason to do so either. As of Server 2008 R2 there have been no 32 bit server versions of Windows to support.

And do understand that using any hacked version of a Windows kernel is a violation of the EULA.

 

[Layback Bear]

Because a COA key is usable on a 32 or a 64 bit Windows 7; why not just install Windows 7/64 and install a bunch of ram? Presuming the cpu is 64 bit capable.

Jack

 

[mt12345]

Because a COA key is usable on a 32 or a 64 bit Windows 7; why not just install Windows 7/64 and install a bunch of ram? Presuming the cpu is 64 bit capable.

Jack

see 1st post, 1st line.

 

[Layback Bear]

Which Windows 7 do you use?
If you use Windows 7 Pro or Ultimate you can use 'XP mode' to install many older programs.

Jack

 

[mt12345]

XP mode is simply VM - I run audio production software so I need direct access to audio (low latency drivers).

EDIT: I also need WASAPI (Vista and above)

 

[mitchell65]

Do you really have no anti virus software installed?

 

[mt12345]

Do you really have no anti virus software installed?

yes

I don't browse xxx sites or dodgy download sites.
I don't share files using pendrives.

my friends use antivirus software yet their computers get infected.

 

[RoasterMen]

If you have now two memory sticks (2+2) G, my suggestion is to buy a match pair (4+4)G.
If you don't want to have memory problems, don't mix different memory types / sizes.
You'll need to do a Win 7 64 clean install.

I wouldn't waste much money on a laptop with DDR2 memory support. 6GB is going to be fine for his needs.

At least have another stick that have the same memory clock as the current one.

 

[mt12345]

my laptop has DDR3 2+2 I was thinking about 2+4 (cheap).
my other systems:
Dell miniPC DDR2 2GB 800 + 1GB 667 (win7)
old Asus board DDR1 1GB 400 + 1GB 333 (xp/linux)
old AMD Sempron board it has 3 memory slots occupied by random ddr1 modules (not in use at the moment planned win98se)
Atom 330 board - this one has only 1 slot so no mixing (linux)

I've been building PCs from recycled parts since 2004. Never had any problems with mixed modules.
If it passes mem86+ it's fine.

Actually many Windows 7 laptops were sold with 2+1 configuration.