Memory usage beyond 32Bit limitations of Windows OS


Recommended Posts

I would like to stress again, that on Windows XP x64 (excluding the IA-64 version), Windows Vista x64, and Windows 7 x64, WOW64 IS NOT EMUALTION. The processor is switched into 32bit compatibility mode and the 32bit thread is executed in 32bit mode. The only time WOW64 ever emulates, is when running x86 instructions on IA-64 editions of Windows. I'm fairly sure none of you are using IA-64 processors (Itanium 2), so the issue is entirely moot.

The biggest disadvantage is availability of Softwares (which is big) and some hardware drivers ( sad for that dude without TV tuner drivers). Windows XP x64 uses a compatability layer called WOW64, to emulate a 32bit Operating System. (Source here). Without WOW, you can't operate 32Bit apps :p not sure about Win7 though. Again selection of 32/64Bit is a user preference and cannot be forced. As long as there are users willing to use x86, MS will continue to release x86 of Win7 and Win8 and Win9.

Big deal, MS uses professional term for it's artificial means "WOW" (also GBs for wow files) and I don't :p I'm addressing main problem, "RAM usage" if I choose 64BIT of XP, I'll have to address "slow buggy 32Bit usage".

windows 7 64bit runs WOW64 also and you can run any 32bit program you want and so what if ther is not as many 64bit apps as 32bit they still run on windows 7 64bit just fine and as for hardware well compatibility rate is almost nothing now i would assume the guy with the TV tuner has an old ass one from 2002 or something so that is a NON issue. and WOW64 has no overhead at all not today, and also right now winows 7 RC is FREE to use till march of 2010 so going 64bit is FREE

oh windows XP X64 is not that good so i would not use it that is why microsoft hardly acknowledge it today

There is a reason why we have a pagefile, and that's for memory redundancy. Windows needs to expand the pagefile depending on usage. So if you have 4GB's of memory and you dedicate 512MB's to it, then Windows will only have 512MB's of pagefile space to work with. My pagefile is at 5GB's at the moment and I have 8GB's of memory, and my computer runs ridiculously fast.

What you are suggesting offers no one any improvements and you are only joking yourself. If someone has 4GB's of memory or more, they can go to x64 without any problems. And like Pandya pointed out, WOW64 is not an emulation layer, but it's just a compatibility mode which has nearly 0% overhead.

To everyone who thinks this will benefit them, it won't, and you will get better "performance" just by going to x64, not just by the extra RAM which will be available to you (if you have 4GB's or more), but the extra CPU instructions and extra security.

JunkMail is misleading people and his suggestion should be avoided.

The biggest disadvantage is availability of Softwares (which is big) and some hardware drivers ( sad for that dude without TV tuner drivers). Windows XP x64 uses a compatability layer called WOW64, to emulate a 32bit Operating System. (Source here). Without WOW, you can't operate 32Bit apps :p not sure about Win7 though. Again selection of 32/64Bit is a user preference and cannot be forced. As long as there are users willing to use x86, MS will continue to release x86 of Win7 and Win8 and Win9.

Big deal, MS uses professional term for it's artificial means "WOW" (also GBs for wow files) and I don't :p I'm addressing main problem, "RAM usage" if I choose 64BIT of XP, I'll have to address "slow buggy 32Bit usage".

This is where you are wrong. Microsoft will force the upgrade, just like they forced Windows 32-bit, and they needed to do that to expand the hardware requirements that was needed. While we might not be there yet, it's much easier to start the transition earlier so that when it comes to software/hardware that requires x64, they can do it without much problem.

RAM is dirt cheap, software is getting bigger, and there are programs which are x64 and will easily eat 8GB's of RAM easily (think video editing). Even in x64, a pagefile or swap partition will still be needed, just incase a program has a memory leak, you can spot the problem before your system crashes.

Windows cannot expand pagefile beyond limitations set by administrator and what good is a pagefile for a system with too much RAM? its a space hog (I turned it off ages back) :D Pandya pointed out WOW64 is NOT an emulation layer :p

Anyone using 32Bit Apps on 64Bit OS with WOW emulation, will get the same overhead as of putting RamDisk on Ram :p

People are smart and know what information is misleading, hehe you and me cannot mislead anyone smart :p

This is where you are wrong. Microsoft will force the upgrade, just like they forced Windows 32-bit, and they needed to do that to expand the hardware requirements that was needed. While we might not be there yet, it's much easier to start the transition earlier so that when it comes to software/hardware that requires x64, they can do it without much problem.

RAM is dirt cheap, software is getting bigger, and there are programs which are x64 and will easily eat 8GB's of RAM easily (think video editing). Even in x64, a pagefile or swap partition will still be needed, just incase a program has a memory leak, you can spot the problem before your system crashes.

Well I don't see MS forcing us to use x64 for 5+ years (Unless Microsoft want to hit hammer on his toe and want users to run away). Its obvious Microsoft wants you to keep on buying new hardware and incur more costs but people are smart. You're making 64Bit a big hype its not that important for home users

I would never want nasty memory hogging softwares in my system but if a single light weight software wants to access more memory beyond i know, 64Bit is NOT a must after this solution :p PageFile is on RAM but if that is low, users can always add more pagefiles to hard disk (will this solve your memory leaking crap?)

Edited by JunkMail
I would like to stress again, that on Windows XP x64 (excluding the IA-64 version), Windows Vista x64, and Windows 7 x64, WOW64 IS NOT EMUALTION. The processor is switched into 32bit compatibility mode and the 32bit thread is executed in 32bit mode. The only time WOW64 ever emulates, is when running x86 instructions on IA-64 editions of Windows. I'm fairly sure none of you are using IA-64 processors (Itanium 2), so the issue is entirely moot.

What you're missing is that there is a lot more to running 32-bit software than simply executing instructions. This is something we've been through a billion times before.

WOW64 emulates the 32-bit kernel (internally by providing thunks for the kernel and kernel-mode functions (like most of Win32)).

WOW64 emulates the 32-bit Windows environment (internally by running the 32-bit NT API (ie ntdll) and all 32-bit system libraries on top of the emulated kernel.)

WOW64 emulates the 32-bit registry (internally by redirecting or reflecting the calls to places in the 64-bit registry.)

WOW64 emulates the 32-bit file system (internally by redirecting calls to places in the 64-bit file system.)

All in all it only amounts to a few percent overhead, and isn't a good excuse not to go 64-bit (the benefits of doing so may even cancel out the overhead).

What you are suggesting offers no one any improvements and you are only joking yourself.

[...]

JunkMail is misleading people and his suggestion should be avoided.

Why do you lie? If someone insists on running a 32-bit OS, then JunkMail's suggestion DOES offer improvements. You may not personally like it, but it's a fact. People would be better off going 64-bit, but it's still a fact.

irc is fast and jumping over keyboard won't get you beating satisfaction (slower is better for this type of topic)

There was a reason why I mentioned (64Bit users get out) in the sub-title of this topic :) (its not to insult 64 bit users but to make 32bit users comfortable)

Edited by JunkMail
Windows cannot expand pagefile beyond limitations set by administrator and what good is a pagefile for a system with too much RAM? its a space hog (I turned it off ages back) :D Pandya pointed out WOW64 is NOT an emulation layer :p

Anyone using 32Bit Apps on 64Bit OS with WOW emulation, will get the same overhead as of putting RamDisk on Ram :p

No they won't because placing a ramdisk into your ram seriously reduces the effectiveness of superfetch.

If you want to use more RAM than 3GB, then use 64Bit OS?

Yes

or install RamDisk plus + set pagefile path to it?

No. That is an utterly ridiculous suggestion that would offer no performance benifits at all. Not to mention running a ramdisk still wouldn't make the OS address more than the 4GB limit without PAE enabled.

You guys are just jealous because his ideas are better than yours.

:laugh: thats absurd. I run Windows 7 X64 with 8GB of ram and it runs slick as anything, I don't need Junkmail's ideas because whatever way you cut it, even if I did run a ramdisk application, I would still lose 4 gigs of my memory in X86 windows without enabling PAE

The point, Frank and Tony, is that if you have a 32-bit OS and, say, 6GB RAM, you'll only be able to use 3.25 of it directly. The rest will be completely useless and just sit there. With a RAM disk driver, you can use the other 2.75GB as a RAM disk, which is at least better than nothing (although spending $50 on the software is a bit silly).

It might be a bit silly, but it's perfectly possible. So why be so damn hard on JunkMail?

The point, Frank and Tony, is that if you have a 32-bit OS and, say, 6GB RAM, you'll only be able to use 3.25 of it directly. The rest will be completely useless and just sit there. With a RAM disk driver, you can use the other 2.75GB as a RAM disk, which is at least better than nothing (although spending $50 on the software is a bit silly).

It might be a bit silly, but it's perfectly possible. So why be so damn hard on JunkMail?

Because this is a hardware limit, not software.

I just don't see why people don't upgrade to 64 bit. I mean the only reason not to is if you use 16 bit applications. Even then those can be used in a VM. Personally i've been on 64bit for 2 years and I have yet to find an application which doesn't work.

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

    • No registered users viewing this page.
  • Posts

    • Google Chrome 149.0.7827.156 (offline installer) by Razvan Serea The web browser is arguably the most important piece of software on your computer. You spend much of your time online inside a browser: when you search, chat, email, shop, bank, read the news, and watch videos online, you often do all this using a browser. Google Chrome is a browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier. Use one box for everything--type in the address bar and get suggestions for both search and Web pages. Thumbnails of your top sites let you access your favorite pages instantly with lightning speed from any new tab. Desktop shortcuts allow you to launch your favorite Web apps straight from your desktop. Chrome has many useful features built in, including automatic full-page translation and access to thousands of apps, extensions, and themes from the Chrome Web Store. Google Chrome is one of the best solutions for Internet browsing giving you high level of security, speed and great features. This update includes 33 security fixes. [N/A][516496659] Critical CVE-2026-12437: Use after free in WebShare. Reported by Google on 2026-05-25 [N/A][516947912] Critical CVE-2026-12438: Inappropriate implementation in WebView. Reported by Google on 2026-05-27 [N/A][519728275] Critical CVE-2026-12439: Use after free in Digital Credentials. Reported by Google on 2026-06-03 [N/A][519731619] Critical CVE-2026-12440: Use after free in DigitalCredentials. Reported by Google on 2026-06-03 [N/A][520157118] Critical CVE-2026-12441: Use after free in File Input. Reported by Google on 2026-06-05 [N/A][521950423] Critical CVE-2026-12442: Use after free in Passwords. Reported by Google on 2026-06-09 [N/A][522566295] Critical CVE-2026-12443: Use after free in Web Authentication. Reported by Google on 2026-06-11 [N/A][513160088] High CVE-2026-12444: Out of bounds read in Chromoting. Reported by Google on 2026-05-14 [N/A][513199795] High CVE-2026-12445: Use after free in Extensions. Reported by Google on 2026-05-14 [N/A][513313107] High CVE-2026-12446: Insufficient data validation in Passwords. Reported by Google on 2026-05-14 [N/A][513405023] High CVE-2026-12447: Heap buffer overflow in WebRTC. Reported by Google on 2026-05-15 [N/A][513458233] High CVE-2026-12448: Inappropriate implementation in WebView. Reported by Google on 2026-05-15 [N/A][513480539] High CVE-2026-12449: Use after free in Chromoting. Reported by Google on 2026-05-15 [N/A][514531776] High CVE-2026-12450: Inappropriate implementation in Media. Reported by Zhixin Tu on 2026-05-19 [N/A][514741076] High CVE-2026-12451: Use after free in DigitalCredentials. Reported by Google on 2026-05-19 [N/A][515462244] High CVE-2026-12452: Use after free in Downloads. Reported by Google on 2026-05-21 [N/A][516448843] High CVE-2026-12453: Insufficient validation of untrusted input in Input. Reported by Google on 2026-05-25 [N/A][516926968] High CVE-2026-12454: Race in Safe Browsing. Reported by Google on 2026-05-27 [N/A][517069848] High CVE-2026-12455: Use after free in Tab Strip. Reported by Google on 2026-05-27 [N/A][517124587] High CVE-2026-12456: Insufficient validation of untrusted input in Extensions. Reported by Google on 2026-05-27 [N/A][517153117] High CVE-2026-12457: Insufficient data validation in Extensions. Reported by Google on 2026-05-27 [N/A][517258337] High CVE-2026-12458: Incorrect security UI in Passwords. Reported by Google on 2026-05-27 [N/A][517406035] High CVE-2026-12459: Inappropriate implementation in Serial. Reported by Google on 2026-05-28 [N/A][517484284] High CVE-2026-12460: Insufficient policy enforcement in File System Access. Reported by Google on 2026-05-28 [N/A][517727318] High CVE-2026-12461: Out of bounds read in WebRTC. Reported by Google on 2026-05-29 [N/A][517916024] High CVE-2026-12462: Use after free in Media. Reported by Google on 2026-05-29 [N/A][518042749] High CVE-2026-12463: Inappropriate implementation in Views. Reported by Google on 2026-05-30 [N/A][519358344] High CVE-2026-12464: Use after free in Browser. Reported by Google on 2026-06-03 [N/A][520189702] High CVE-2026-12465: Insufficient validation of untrusted input in Metrics. Reported by Google on 2026-06-05 [N/A][520199394] High CVE-2026-12466: Heap buffer overflow in WebRTC. Reported by Google on 2026-06-05 [N/A][520202726] High CVE-2026-12467: Use after free in Extensions. Reported by Google on 2026-06-05 [N/A][521485244] High CVE-2026-12468: Inappropriate implementation in Updater. Reported by Google on 2026-06-08 [N/A][521618871] High CVE-2026-12469: Uninitialized Use in GPU. Reported by Google on 2026-06-09 Important to know! The offline installer links do not include the automatic update feature. Download web installer: Google Chrome Web 32-bit | Google Chrome 64-bit | Freeware Download: Google Chrome Offline Installer 64-bit | Direct Link | 131.0 MB Download: Google Chrome Offline Installer 32-bit | Direct Link | 119.0 MB Download page: Google Chrome Portable Download: Chrome ARM64 | Direct Link View: Chrome Website | Release Notes Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • they couldnt do W11 LTSC so the support lasts longer....
    • The fact that the pref is not enabled by default tells you that what you see is what you get...for now. Hopefully the final version will have all the quirks ironed out.
    • It's enterprise, not consumer. And "...affected scenarios involve third-party software..." Would be good to know that in headline, not way down in the article. Instead, you lead with Windows update, which is not very helpful and misleading, IMHO. Just saying.
  • 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
      503
    2. 2
      +Edouard
      173
    3. 3
      PsYcHoKiLLa
      97
    4. 4
      Steven P.
      85
    5. 5
      ATLien_0
      71
  • Tell a friend

    Love Neowin? Tell a friend!