however use at your own cost (Warning: The patches described in this article am mentioning are kernel patches. They may result in unexpected hardware issues and expose your system to malicious exploits.)
That patch still isnt the same as x64 because its a completely different architecture. It basically creates a virtual drive with the extra ram stored on there. I would advise on just getting x64 instead of x86 you will run into less problems and you will have a much higher performance than x86. Think of it like a page file not like actual ram then you will understand that its not as good.
There is no way to address more than 4 gb of ram on 32bit even with a patch. What you might be doing is creating a ram page drive which is definately not the same as accessing a true 4+ gb of ram.
Windows XP and Windows Vista contain the codepaths to enable PAE (Physical Address Extension) which adds a third level to the paging architecture and turns all real addresses into longs if the hardware supports it. The caveat is that there's up to a 10% performance hit due to the extra CPU overhead so XP and Vista have them disabled by default and are only enabled on their Server variants. The codepaths might exist in Window 7 but that's doubtful since there's no 32 bit version of Server 2008 R2.
PAE extends the physical address space from 32 bits to 36 bits, allowing up to 64 GB of memory to be addressed, however virtual memory spaces are still limited to 4 GB.
However, as another posted mentioned, there's absolutely zero reason not to be running a 64 bit OS. The extra GPRs and other architectural improvements are well worth it and the faster 32 bit dies, the better.