Memory usage beyond 32Bit limitations of Windows OS


Recommended Posts

As for the reasons why using a pagefile on ramdisk is stupid, there is no need for me to repeat. Brandon Live explained this perfectly further up the thread.

WRONG!

MSFT doesn't license you to use 4GB in 32Bit Client systems but you can hack it to use more:

system8189.png

The kernel includes a function ZwQueryLicenseValue to check for special values. For memory it is Kernel-WindowsMaxMemAllowedx86 and this is set to 4096 for x86 clients.

there is a crack out there to do it for you. Just search for readyfor4gb. The technically background is explained here, although I can imagine that 99% of the users here don't understand it.

It is possible, but not recommend because it doesn't solve the x86 memory issues completely.

Lets look at this logically as to why 32bit is no good with > 4gb memory.

32bit integers have a range of 4,294,967,295. This can be from 0 to 4,294,967,295 or −2,147,483,648 to +2,147,483,647.

We can't have negative memory, so lets start from 0, this gives us our magic number 4,294,967,295.

We are working with binary and not decimal here, so 1 gb = 1,024 megabytes, 1 megabyte = 1,024 kilobytes and so on.

4,294,967,295 / 1024 = 4194303.9990234375

4194303.9990234375 / 1024 = 4095.99999904632568359375

4095.99999904632568359375 / 1024 = 3.999999999068677425384521484375

What does this prove? A 32bit processor can only address just under 4gb of memory, because of this limit with 32bit ints - MagicAndre1981, you claim this hack allows you to use more, but it's just displaying the amount you have installed. It cannot physically address this extra memory, it's simply impossible. I did read the article, and I disagree with it (I am qualified enough to understand that parp).

I use 8GB of memory, and I know a few other people that do as well. Memory is so cheap nowadays that almost anyone can afford to put a large amount into their computer. Granted it may be of no use to an average home user, as opposed to a power user, but then this guide would neither.

Yeah, I was basing the argument off this apparently being for home users as the OP stated above somewhere :)

Edited by Citizen Erased
As for the reasons why using a pagefile on ramdisk is stupid, there is no need for me to repeat. Brandon Live explained this perfectly further up the thread.

Lets look at this logically as to why 32bit is no good with > 4gb memory.

32bit integers have a range of 4,294,967,295. This can be from 0 to 4,294,967,295 or −2,147,483,648 to +2,147,483,647.

We can't have negative memory, so lets start from 0, this gives us our magic number 4,294,967,295.

We are working with binary and not decimal here, so 1 gb = 1,024 megabytes, 1 megabyte = 1,024 kilobytes and so on.

4,294,967,295 / 1024 = 4194303.9990234375

4194303.9990234375 / 1024 = 4095.99999904632568359375

4095.99999904632568359375 / 1024 = 3.999999999068677425384521484375

What does this prove? A 32bit processor can only address just under 4gb of memory, because of this limit with 23bit ints - MagicAndre1981, you claim this hack allows you to use more, but it's just displaying the amount you have installed. It cannot physically address this extra memory, it's simply impossible. I did read the article, and I disagree with it (I am qualified enough to understand that parp).

Yeah, I was basing the argument off this apparently being for home users as the OP stated above somewhere :)

You should mention that this includes the pagefile. If you have a 4GB of memory and a 20GB pagefile, you're still essentially limited to 4GB of memory.

yawn yawn... nothing new here :p It works on my system so you can't make me change my head (but you can try... lol)

Wait a minute: This Chinese page shows a download link to a kernel (patched?) which enabled 128GB RAM? can this be true? http://bbs.wmzhe.com/viewthread.php?tid=71...;extra=page%3D1

Edited by JunkMail
yawn yawn... nothing new here :p It works on my system so you can't make me change my head (but you can try... lol)

JunkMail, all you have done is post crap, just cut it out. You have shut out people who have more knowledge than yourself, even a Microsoft employee who knows how Windows works better than most members on this board (and believe me, we have loads).

yawn yawn... nothing new here :p It works on my system so you can't make me change my head (but you can try... lol)

How many times do we need to say/write/shout that your solution is HALF ASSED AND USELESS !!!!!

Bonus question : How can you explain that the simple fact of replacing my 32Bits OS with a 64 Bits ( without changing a single piece on my laptop ) one enabled me to unleash the full power of my quad core with its 4GB of RAM ?

Say it with me : " If I have more than 3GB of RAM I MUST use a 64 bits OS and everything else is PLAIN RUBBISH AND USELESS !"

If you're fine with your useless solution, then good for you but don't go on teh Int3webs spreading such UNEDUCATED stuff like you're doing with this thread. Teh Int3rwebs will forever be grateful to you ! :D

...

Lets look at this logically as to why 32bit is no good with > 4gb memory.

32bit integers have a range of 4,294,967,295. This can be from 0 to 4,294,967,295 or −2,147,483,648 to +2,147,483,647.

We can't have negative memory, so lets start from 0, this gives us our magic number 4,294,967,295.

We are working with binary and not decimal here, so 1 gb = 1,024 megabytes, 1 megabyte = 1,024 kilobytes and so on.

4,294,967,295 / 1024 = 4194303.9990234375

4194303.9990234375 / 1024 = 4095.99999904632568359375

4095.99999904632568359375 / 1024 = 3.999999999068677425384521484375

What does this prove? A 32bit processor can only address just under 4gb of memory, because of this limit with 32bit ints - MagicAndre1981, you claim this hack allows you to use more, but it's just displaying the amount you have installed. It cannot physically address this extra memory, it's simply impossible. I did read the article, and I disagree with it (I am qualified enough to understand that parp).

...

To be fair, you can flip the CPU's into 36bit addressing mode, which gives you access to 64GB of RAM.

Of course, relying on PAE mode on a 64bit chip running in 32Bit mode running an OS that's available in 32bit and 64bit versions is pretty stupid, unless you've got some valid reason (irreplaceable hardware that's for some reason only has 32bit drivers for Vista)

Like I said, this thread was for those running 32Bit (its quite obvious that if you're running 64Bit there are no problems).

kazuyette, You don't like it fine, don't do anything (go ahead with 64 and am I stopping you?). The point is simple here, you can use more then 4GB with this... (now you can go on denying but on my system, i know for fact it works :) )

Nothing you say can alter my head and when Win7 comes (as neowin says RTM is 13th?) then thats where things will change.

Like I said, this thread was for those running 32Bit (its quite obvious that if you're running 64Bit there are no problems).

kazuyette, You don't like it fine, don't do anything (go ahead with 64 and am I stopping you?). The point is simple here, you can use more then 4GB with this... (now you can go on denying but on my system, i know for fact it works :) )

Nothing you say can alter my head and when Win7 comes (as neowin says RTM is 13th?) then thats where things will change.

Like we have said Knowbody Cares for your stupid method of making a 32bit OS run more then 4gb of ram or more then it is allowed and the ones whoi may Care will look at your HD tune score and go WTF CPU usage 70% sorry all just run 64bit

and as other have stated windows 7 is being released in both versions and each of them you own when ya buy so it is FREE 2 fore the price of 1 TY now junk why not just go out run windows 7 X64 and then come back and apologize e when you released how stupid you was thinking the Ramdisk thing was the best thing since The Fat lady died choking on a Crumb of Bread.

your the only 1 besides that 1 other dude DDstriker who things this is a good idea and well the rest of us on Neowin are against it as most of use on neowin run 64bit version of windows of some kind or Linux 64bit variant for some of the Linux crowd on neowin oh and wont forget the Mac crowd

CAN ANYONE Confirm whether THIS PATCH for VISTAx86 and Windows7x86 WORKS???

This patch also states that you must have PAE enabled system (I've added this link to first post for the purpose of review by any new comers)

If I'm understanding this Chinese page right, It has patched kernel which makes x86 (Post 6000 NTs) to access memory upto 128GB (which is cool)

whatever good comes out of this thread is worth it

just for a while, forget ANTI-discussions here...

CAN ANYONE Confirm whether THIS PATCH for VISTAx86 and Windows7x86 WORKS???

This patch also states that you must have PAE enabled system (I've added this link to first post for the purpose of review by any new comers)

If I'm understanding this Chinese page right, It has patched kernel which makes x86 (Post 6000 NTs) to access memory upto 128GB (which is cool)

whatever good comes out of this thread is worth it

just for a while, forget ANTI-discussions here...

You shouldn't even be touching the kernel.

And no, this isn't "Anti-discussion" this is "Anti-stupidity".

...

whatever good comes out of this thread is worth it

just for a while, forget ANTI-discussions here...

NO, nothing good will come out of your stupid idea ... Well I only see one thing : some random users, because of people like you posting ridiculous and useless ideas on the internet, will believe that MS is lying to them.

NOTHING GOOD WILL COME OUT OF THIS THREAD. Why won't you get it ? I'm still puzzled ...

P.S. : How can you have trust in a dodgy patch made by a chinese John Doe instead of admitting that your solution is USELESS ? You're so stubborn.

ok that makes me sleepy again :o but still, my signature won't die for that matter, hehehe

Don't you feel that you are being a little immature? Rather than listening and embracing what is being told to you, you are ignoring us and telling people to ignore us, and like kazuyette said, you are being stubborn. I have nothing against you, just have a problem with the way you want to get around things. You want people to patch their kernels and take a chance on a half arsed idea rather than take a much simpler route by going with x64.

Do i care what you think about me? you're a fool! hahaha

I'm not forcing people am i? BUT YOU ARE! USE THE DAMN x64! You're out of your mind, those people who want to use x64 will do it without your assistance and those who want to continue with x86 will also do it without YOU!

I tell anyone to ignore ?heads who force people....

Edited by JunkMail
CAN ANYONE Confirm whether THIS PATCH for VISTAx86 and Windows7x86 WORKS???

This patch also states that you must have PAE enabled system (I've added this link to first post for the purpose of review by any new comers)

If I'm understanding this Chinese page right, It has patched kernel which makes x86 (Post 6000 NTs) to access memory upto 128GB (which is cool)

whatever good comes out of this thread is worth it

just for a while, forget ANTI-discussions here...

I don't recommend using a hacked kernel, you have no idea what they put into that thing.

Also, isn't it against the rules here to distribute modified system files?

I didn't come up with that link even if its against (someone else pointed out to that link first) and since no one stopped that dude (thought it was fair enough since it has some meaning to it with this thread's topic)

Will you stop ****ing lying? How do you know it doesn't work if you haven't tried it? It's certainly technically possible. Why don't you stay out of the thread if you don't understand the subject, instead of derailing the thread with your moronic crap and being rude to someone who was just offering a neat tip? Did a 32-bit OS rape your wife, and this is your revenge?

loooool, i couldn't stop for a while... hehe (had to read it again)

Look whats below this post, a dude feels pity for his insanity (so predictable)

Do i care what you think about me? you're a fool! hahaha

I'm not forcing people am i? BUT YOU ARE! USE THE DAMN x64! You're out of your mind, those people who want to use x64 will do it without your assistance and those who want to continue with x86 will also do it without YOU!

I tell anyone to ignore ?heads who force people....

I pity the fool.

What does this prove? A 32bit processor can only address just under 4gb of memory, because of this limit with 32bit ints - MagicAndre1981,

that's why PAE was developed

but it's just displaying the amount you have installed. It cannot physically address this extra memory, it's simply impossible.

Wrong.

I did read the article, and I disagree with it (I am qualified enough to understand that parp).

then read it again and try it your own ;)

that's why PAE was developed

Which isn't supported above 4gb in XP or the standard versions of 2003 anyway. If your running 2003 Enterprise as your primary operating system then you have bigger issues than worrying about 32bit address limits.

PAE was designed for use in server environments, it was never intended for use on desktop OSes. The fact that 32 bit drivers for most consumer hardware aren't compatible with the extra page extension size needed to address the extra memory means that there is a possibility of irrational OS behaviour. These things are disabled for a reason, and threads like this just ramp up the misinformation

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • lots of people us facebook for stuff, threads though no
    • Can you read? I've said I'm willing to pay more for a notchless (no notch) 3:2 screen.
    • Not even an OLED display on the laptops. Also it seems that the laptop design isn't the same as the Surface Ultra model. Looks like bargain bin at high prices.
    • make your own notch - it's not that hard
    • VirtualBox 7.2.10 by Razvan Serea VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD. Some of the features of VirtualBox are: Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 7.2.10 changelog: VMM: Fixed issue when CentOS 10 VM was not booting due to the message "Fatal glibc error: CPU does not support x86-64-v3" (​github:gh-642) Devices/EFI: Fixed booting issue when ARM VM had less than 1024 MiB of RAM assigned (​github:gh-679) USB: Fixed issue when it was not possible to attach USB device to headless VM on Apple Silicon/macOS 26.4.1 (​github:gh-631) Storage: Fixed issue when VIRTIO-SCSI device was not recognized as SSD device by guest system (​github:gh-634) Network: Fixed issue in E1000 emulation code which triggered debug log creation (​github:gh-645) Network: Fixed issue in E1000 emulation code which prevented OS/2 guest from booting (​github:gh-683) Linux Host: Fixed issue when VMs could not be started due to kernel oops (​github:gh-639) Linux Host and Guest: Fixed issue when kernel modules were failing to build with openSUSE 16.0 kernel Linux Host and Guest: Added initial support for kernel 7.1 Linux Host and Guest: Added extra fixes for RHEL 9.8 kernel (​github:gh-676) Linux Host and Guest: Added possibility to build source code using NASM instead of YASM as the assembler (​github:gh-520) Linux Guest Additions: Added initial support for Extended Data Control Protocol for clipboard sharing with Plasma on Wayland guests (​github:gh-33) Linux Guest Additions: Added extra fixes for preventing vboxvideo kernel module build with kernel version 7.0 and newer (​github:gh-655) OS/2 Guest Additions: Fixed issue when Shared Folders automount and clipboard sharing stopped working (​github:gh-551) Download: VirtualBox 7.2.10 | 170.0 MB (Open Source) Download: VirtualBox 7.2.10 Extension Pack | 19.1 MB View: VirtualBox Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      suprememobiles48 earned a badge
      Week One Done
    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
    • Week One Done
      Prasann earned a badge
      Week One Done
    • First Post
      Dys Topia earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      510
    2. 2
      +Edouard
      174
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Steven P.
      87
    5. 5
      ATLien_0
      70
  • Tell a friend

    Love Neowin? Tell a friend!