Ok, I am in the same boat with the poster finding out how to bypass Microsoft's Imposed Max limitations of 4GB of PAE'd (Physical Address Extension) memory in my current Windows XP Professional SP3 x86 (32 bits). I know that Windows 2003 Server Enterprise can address up to 32 GB of RAM when the /PAE switch is used in boot.ini given the fact that Windows XP, being 32 bits *JUST* like Windows Server 2003 Enterprise 32 bits, Windows XP 32 Bits cannot address more than 4GB of RAM with /PAE. Further research done by me tells me that this is by Microsoft's Design, that its some "Licensing" crap limiting users how much ram they can have.
Now, here is my situation. I have Windows XP 32Bits installed in my computer with 8GB of RAM and only 3.5GB is being reported even with using the /PAE switch. I would like to know where can I obtain a HACK that will patch up my system (or should I say Kernel) to allocate a higher number of /PAE RAM? I know that x64 is slightly better than /PAE but I do not want to go 64 bit at this time because my computer manufacturer (HP) doesn't have drivers for Windows XP x64 (even though I do have the CD, just cant use it because of that), ahh dont even think of suggesting Windows Vista x64, I had that crap and had to remove it because it was too slow and unstable, and most of my productivity software didn't just work under it. Windows 7, forget it, I haven't tried it yet, just heard that Windows 7 is a revamped version of Windows Vista, its giving a few random problems to a few users, I dont feel like going there, if my productivity softwares didn't function under Vista, I dont have a good expectation of them functioning under Windows 7.
So.... Where is the hack (or work around) to remove Microsoft's /PAE limitations of 4GB Max RAM on 32bit Windows XP?
Note:
I am smelling as of now that the hack could be as easy as using files from the original Windows XP SP0 CD which, according to an earlier poster here, supported a /PAE greater than 4GB before Microsoft removed that functionality under SP1 without giving the users the CHOICE to re-activate it (at their own risk) (Maybe its a simple registry key that needs to be modified to allow this?).
Also, just in case if there is no way of hacking XP to support a bigger /PAE. Is there any way I can get Windows XP's System Properties to display the RAM value being reported in system BIOS? (8GB) and not just 3.5GB as current? I work as a full time computer technician and I do receive customers from time to time requesting me to remove Windows Vista x64 (or 32) and install XP downgrade (utilizing the Microsoft Downgrade Rights) in their 6/8GB RAM systems while not being able to install the 64 bits version of XP simply because I was only able to find drivers for 32 bits XP for these "Vista Only" machines, and then, even though their systems ends up much, and I mean MUCH faster than how it used to run under Vista, it is sometimes difficult explaining to the customer why XP is reporting 3.5GB of RAM when Vista used to report 8GB before. (I currently tell them about the PHYSICAL (2^32) 32Bits architectural limitations of 4 GB, and most of them understands immediately while a few of them requires a few more speeches before they are able to understand and leave me alone about it)
This project that I am trying to do in seeing if I can hack Windows XP to support a greater /PAE value other than Microsoft's Imposed /PAE limitation is only EXPERIMENTAL. 1) I just want to know HOW it can be done (I know it CAN be done due to my 32 bit Windows Server 2003 example above) 2) After I am able to accomplish this, I want to see, being the first hand witness to my self, HOW stable would this be?, 3) How higher can I go in terms of RAM without sacrificing stability/performance/issue, IF ANY. I have enough tests bench here with me, I want to do tests and tweaks on my own, I do not want to rely on some other organization, etc telling me why they feel this should'nt be done, etc. I know not all drivers will behave erratically if XP's /PAE limitations would be to be lifted, and if then, I am pretty sure I might be able to find a good work around to stabilize these drivers under these kinds of (unlimited) /PAE'd environment. Also, I know that software would have to use the /PAE'd environment to "profit" from the higher memory areas above 3.5GB and that most software will simply be operating under the 3.5GB umbrella, but what I am mostly looking here is for the privilege of "seeing" 8GB under System Properties and under Task Manager (even though if the system is truly using just 3.5GB most of the time) so customers wont bug me about this.
Thanks.