XP 32 bit and 4 gigs of ram

[Wingnutt]

I have a system upgrade arriving this week, new processor, ram and MOBO.. 

I ordered 4gb of ram (2x 2gb sticks)

I understand that in many with 32 bit XP if you install 4gb (or more) of ram, XP will only SHOW that you have 2.5 or 3 GB installed..

my question is will my applications still MAKE USE of the full allotment of ram?

really dont want to switch to a 64bit OS, wayyy too many gadgets going on here, i know I would have a driver issue.

[MrRiplEy[H]]

It will show 3 to 3.5 gigs. I have a similar setup but my memory consumption never goes past 2gb to be honest. Except on OSX leopard which hogs over 3 gigs easy. But XP is much less memory intense.

[Wingnutt]

im not worried about windows needing it, no reason it should, im worried about windows keeping other programs such as FSX etc etc from being able to get full use of it.

[MrRiplEy[H]]

im not worried about windows needing it, no reason it should, im worried about windows keeping other programs such as FSX etc etc from being able to get full use of it.

Unless you install a pure 64-bit version of FSX you're not going to see any more memory playing it on 64-bit OS.

[Wingnutt]

there is only one version of FSX that I know of, there isnt a separate 64 bit version

[Getback]

I just installed 4 gigs, 2 x 2gigs, and my xp 32 bit reads 3.25 gigs.

[Wingnutt]

exactly,

but my confusion is..

is WINDOWS the only program that cannot use the full allotment..

i.e. lets say windows sees 3.... it uses say 1gb for itself ( i know it doesnt) so that means windows THINKS there is only 2gb left of available.. 

lets say other programs are using up another 500mb..   according to windows I only have 1.5 GB left, when in reality I have 2.5GB of unused ram..

will windows limit my remaining programs to using only the 1.5.. because it only sees 1.5, or will they be able to use the full 2.5

[Getback]

That's over my head Wingnutt. I'm sure some tech junkies will explain that to us.

[Wingnutt]

hope so..

I could card less if windows itself can use the full 4 GB, what kind of obscene bloated to hell install would you need going on to do such a thing.

ive noticed on other forums and such that any system analysis software you run, will in fact show the full amount of ram.. the only place it shows up as incorrect is under system info..

[BaldEagl]

I'm not positive on this by any means but simple logic tells me that if the operating system can only see x amount of RAM, then there is only x amount available to the system, including any applications.  This makes even more sense when you think in the context of virtual memory.  It means that memory allocation is limited by the O/S.

I'd be interested to hear what others see in the BIOS boot screen when the system runs a memory test on start-up.  That would tell a lot.

Like I said, I could be 100% wrong on this but if I were betting...

[MrRiplEy[H]]

You have exactly as much available from the 4gb as you see as total amount of ram in windows.

A single 32-bit application can utilize 2Gb at any given time at most. That leaves you with 1.25-1.5 Gb for _all the rest_ including OS and background applications.

Mind you, 1.5 gigs is more than most desktop computers ever have running XP. Many gamers run with 1Gb just fine.

[Wingnutt]

hmm, guess 64 bit is in my future..

and to think, i actually paided for XP   

[MrRiplEy[H]]

hmm, guess 64 bit is in my future..

and to think, i actually paided for XP   

Untill you have your first native 64-bit application or game, you have zero need for any 64-bit OS.

[Wingnutt]

gaining an extra gig of ram.. that I paid for is reason enough.

[MrRiplEy[H]]

gaining an extra gig of ram.. that I paid for is reason enough.

No. First of all you won't be able to use it practically anywhere if at all. No game you run will use one bit more of memory. No other 32-bit app will use more memory. Second you will get a world of trouble with 64-bit drivers and application compatibility for nothing. Last, going to 64-bit will bloat all the code put into it so that you end up losing that 1 gig anyway - it'll get eaten by the fatter codebase.

It's a rotten deal, trust me.