>4GB ram in win x86 possible?


Recommended Posts

http://www.overclock.net/t/596932/guide-make-32-bit-os-support-128gb-of-ram

legit stuff it seems.

the article says windows xp sp0 could support more than 4 gb ram but the ram limits were imposed to make server editions sell. not sure about that claim but xp era server editions could support 64gb ram so it might be true.

http://en.wikipedia.org/wiki/Windows_Server_2003

what do you guys make of this?

any patches for xp sp3?

Link to comment
https://www.neowin.net/forum/topic/1146750-4gb-ram-in-win-x86-possible/
Share on other sites

"x86 processor hardware-architecture is augmented with additional address lines used to select the additional memory, so physical address size increases from 32 bits to 36 bits. This, theoretically, increases maximum physical memory size from 4 GB to 64 GB - although the actual amount increased depends on the OS. The 32-bit size of the virtual address is not changed, so regular application software continues to use instructions with 32-bit addresses and (in a flat memory model) is limited to 4 gigabytes of virtual address space. The operating system uses page tables to map this 4-GB address space into the 64 GB of physical memory. The mapping is typically applied differently for each process. In this way, the extra memory is useful even though no single regular application can access it all simultaneously."

http://en.wikipedia.org/wiki/Physical_Address_Extension#Design

what if youre using a 64-bit CPU w/ a 32-bit OS?

i still dont think PAE is worth it, or going to work at all, based on what i read in the wiki

dont know 32 bit is just generally more reliable and fast, did see some benchmarks to that effect..

Its not a Software limitation

righto!

what if youre using a 64-bit CPU w/ a 32-bit OS? i still dont think PAE is worth it, or going to work at all, based on what i read in the wiki

OP dide say using x86 not x64 or x86-64

We've been over this numerous times. Yes it's possible to have more ram but severe limitations apply, and it's generally accepted that it provides no benefit for most situations.

Just install x64 and be done with it, or live with the architectural limitation.

not interested in either... im mainly interested in >4gb ram for xp 32bit use.

not interested in either... im mainly interested in >4gb ram for xp 32bit use.

Wow, we're STILL on this after all these years?

It's not stable. PAE has some serious issues under XP.

But you will ignore whatever is said here and do it anyway, so why even ask...

  • Like 2

cant go higher than that. dunno why you dont want to use 64bit OS, its probably faster. at least in win 7+ anyway

because big boys do it different... no really... this is just a curiosity.

Wow, we're STILL on this after all these years?

It's not stable. PAE has some serious issues under XP.

But you will ignore whatever is said here and do it anyway, so why even ask...

<snipped>

because big boys do it different... no really... this is just a curiosity.

no im not nik lousy...

PAE isn't really a consumer tool. I wasn't aware that XP could use it >.>

64bit is definitely faster for a lot of things. It's very rarely slower than 32bit, normally being on par.

There's been some right FUD posted in this thread.

ALL x86 servers in the early 00's and 90's used PAE, how do you think it was possible to have dell servers with 4xP3's and 8GB of RAM?

I've used PAE on servers since I've had them, a generic AMD server, a dell 6350, dell 2650, dell 2950 - ALL have worked perfectly fine.

As said, you can only have 4GB per program unless it uses multiple threads and I'm not aware of anything that does that properly.

Because of how fast/high end graphics cards work though you probably WILL encounter problems using them and PAE which is why it's recommended normal PCs do not use PAE, as servers have only the most basic of GPU it doesn't really matter.

Why do you want > 4GB so badly anyway?

Why do you want > 4GB so badly anyway?

that was one of the main reasons to upgrade to a 64bit system.. more ram could be addressed... if that could be done with an x86 xp already then that would be one less reason to consider while upgrading.

PAE isn't really a consumer tool. I wasn't aware that XP could use it >.>

64bit is definitely faster for a lot of things. It's very rarely slower than 32bit, normally being on par.

64bit got a lot of flak initially for being much slower... some even questioned its necessity.

some even questioned its necessity

Who? Sorry, the need for 64-bit was astoundingly obvious. Were a few things slower? Sure. But as software and drivers became optimised, that stopped being the case.

that was one of the main reasons to upgrade to a 64bit system.. more ram could be addressed... if that could be done with an x86 xp already then that would be one less reason to consider while upgrading.

PAE is a workaround, not a solution to utilizing more than 4GB of memory. That is all that needs to be said about it now.

64bit got a lot of flak initially for being much slower... some even questioned its necessity.

64-bit itself did not get flak. At least not any flak that held any credence. Windows XP 64-bit Edition was not used widely because many drivers were not created for it. Personally, I used XP 64-bit for a long while and had the pleasure of using more than 4GB of memory without any workarounds or headaches.

64-bit is mainstream now. There's no reason to question it. There's no reason to hold on to the past. It's here, it's better, just use it. Debating this many years later is the pinnacle of pointlessness.

I thought there was only "3.25gbs USEABLE" out of 4gbs in a 32bit system.

Windows is not the only thing that requires memory (hint: motherbaord resources) and typical RAM is not the only source of memory in a computer (hint: video cards).

Fixed?

vomit.

no name calling like the mod said...

:angry:

PAE is a workaround, not a solution to utilizing more than 4GB of memory. That is all that needs to be said about it now.

64-bit is mainstream now. There's no reason to question it. There's no reason to hold on to the past. It's here, it's better, just use it. Debating this many years later is the pinnacle of pointlessness.

there is no need to say that because it wasnt ever the case for creating this thread.

it is a what if thread..

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

    • No registered users viewing this page.
  • Posts

    • There is a default resolution setting in Settings > Display that can be changed with a click. You can also change the settings on a per-game basis. No CLI needed. Also, Steam has countless games that are not "[perpetual] alpha/beta games", so no need for the straw man. Plus you can use other stores as well. And console games (e.g. PS5) cost a fortune, which itself more than negates the price subsidy on the system, unless you plan on exclusively playing 1 or 2 games. It's true that you shouldn't buy a system that doesn't support the game(s) you want to play, but I think that's kinda obvious, and applies to every console as well as PC. I don't game in the living room and have no need of a Steam Machine, but there is a clear market segment that would find it useful.
    • RSS Guard 5.2.0 by Razvan Serea RSS Guard is a simple (yet powerful) feed reader. It is able to fetch the most known feed formats, including RSS/RDF and ATOM. It's free, it's open-source. RSS Guard currently supports Czech, Dutch, English, French, German, Italian. RSS Guard will never depend on other services - this includes online news aggregators like Feedly, The Old Reader and others. RSS Guard is developed on top of the Qt library and it supports these operating systems: Windows GNU/Linux OS/2 (eComStation) Mac OS X xBSD (possibly) Android (possibly) other platforms supported by Qt The core features of RSS Guard are: support for online feed synchronization via plugins, Tiny Tiny RSS (from RSS Guard 3.0.0). multiplatform, support for all feed formats, simplicity, import/export of feeds to/from OPML 2.0, downloader with own tab and support for up to 6 parallel downloads, message filter with regular expressions, feed metadata fetching including icons, simple Adblock functionality, customized popup notifications, Google-based auto-completion for internal web browser location bar, ability to cleanup internal message database with various options, enhanced feed auto-updating with separate time intervals, multiple data backend support, SQLite (in-memory DBs too), MySQL. is able to specify target database by its name (MySQL backend), “portable” mode support with clever auto-detection, feed categorization, drap-n-drop for feed list, automatic checking for updates, ability to discover existing feeds on websites, full support of podcasts (both RSS & ATOM), ability to backup/restore database or settings, fully-featured recycle bin, printing of messages and any web pages, can be fully controlled via keyboard, feed authentication (Digest-MD5, BASIC, NTLM-2), handles tons of messages & feeds, sweet look & feel, fully adjustable toolbars (changeable buttons and style), ability to check for updates on all platforms + self-updating on Windows, hideable main menu, toolbars and list headers, KFeanza-based default icon theme + ability to create your own icon themes, fully skinnable user interface + ability to create your own skins, “newspaper” view, plenty of skins, support for "feed://" URI scheme, ability to hide list of feeds/categories, open-source development model based on GNU GPL license, version 3, tabbed interface, integrated web browser with adjustable behavior + external browser support, internal web browser mouse gestures support, desktop integration via tray icon, localizations to some languages, Qt library is the only dependency, open-source development model and friendly author waiting for your feedback, no ads, no hidden costs. RSS Guard 5.2.0 changelog: Added: Feed auto-fetch can now also be delayed while Feral GameMode is active on Linux and startup auto-fetch is skipped when GameMode is already active. (#2265) WebEngine builds can now use RSS Guard generated proxy auto-config (PAC) rules so article/web browsing follows per-account and per-feed proxy settings more closely. (#2273) Generated PAC rules now also cover related subdomains and use Public Suffix List data, so feeds such as feeds.bbc.co.uk can also proxy resources from images.bbc.co.uk. (#2273) Standard feeds can now define extra proxy domains, useful when article images, stylesheets or other page resources are loaded from a CDN or another domain that should use the same feed proxy. (#2273) RSS Guard now asks for proxy credentials when a WebEngine page needs proxy authentication and can fill credentials from the current feed proxy when available. (#2273) Network settings again include an option to ignore all cookies, which clears stored cookies and prevents new cookies from being accepted. Standard RSS/ATOM feeds can now individually ignore cookies while downloading feed data. Stored cookies can now be deleted from the Tools menu. Custom skin colors can now override the feed list article count color separately from feed titles, including a separate highlighted color. (#2275) Settings dialog can now search across available settings and highlight matching controls. (#1754) Standard RSS/ATOM feeds can now optionally be reported as broken when they are valid but contain no articles. (#2039) Standard RSS/ATOM feeds can now override the application-wide feed connection timeout per feed. (#1023) Tray icon can now use a custom background color and unread-count text color, with an option to reuse the generated icon as the application icon. (#1973) Support for more benevolent parsing of Gemlog entries (#2295). Article list can now show when an article was received by RSS Guard. (#947) Feed deep discovery now actually scrapes all links found in the website and checks if they are feeds or not. This greatly enhances usability of the deep discovery mode and discovers many more feeds than before. (#2306) Search boxes now show a small dot when the feed or article list is hiding some items because of active filtering. (#873) Articles now have a shortcut-assignable action to open the homepage of the feed they belong to. (#2060) Fixed: Parallel feed updates no longer crash when multiple update results are processed at the same time. (64cf521) Links in WebEngine articles opened from feeds such as Kill the Newsletter now open correctly instead of being swallowed by the embedded page. (#2272) Relative article URLs resolution was kinda broken. (#2282) Clicking article URL did not work when the URL had "fragment" set. (#2293) The default proxy setting now uses Qt/system default proxy behavior instead of forcing no proxy. (e0263ad) WebEngine article loading now keeps the current feed context, so feed-specific proxy credentials remain available while the article page loads. (fdd0f00) Download: RSS Guard 5.2.0 (64-bit) | Portable | ~ 130.0 MB (Open Source) Link: RSS Guard Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This is gonna separate the creeps from the rest of the crowd.
    • "Claude, is our CEO a compete and utter fool by wasting money on AI in this already worthless Teams chat?"
  • Recent Achievements

    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      161
    3. 3
      PsYcHoKiLLa
      110
    4. 4
      Michael Scrip
      83
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!