RAM

[bearcaat12]

is 1 GB enough to run TNCM or SFO well?

[Edge]

Use at least 2 GB's of RAM these days.

[paavo]

Try the freeawre KBOS, if it works with that then you should be ok, but as Edge stated, go with at least 2 gigs.

[tbmavengerstuka]

Use at least 2 GB's of RAM these days.

Unless you have XP 32 edition, in which case 2 gigs is optimal. XP doesn't recognize more than 2 gigs ( or doesn't utilize in many systems). If it's vista, at least 2 is correct.

[thepilot]

is 1 GB enough to run TNCM or SFO well?

I think so. Both are not hard on frames at all.
But it's generally advisable to use 2GB, shouldn't be too expesive in these days.

[jan]

Unless you have XP 32 edition, in which case 2 gigs is optimal. XP doesn't recognize more than 2 gigs ( or doesn't utilize in many systems). If it's vista, at least 2 is correct.

Not entirely true - under WinXP 32, any single application can allocate up to 2 Gigs of memory, with the OS itself technically being able to adress up to 4 Gigs (Unless you run some Server version of XP). See this link for more info: http://www.microsoft.com/whdc/system/pl ... AEmem.mspx

[tbmavengerstuka]

Unless you have XP 32 edition, in which case 2 gigs is optimal. XP doesn't recognize more than 2 gigs ( or doesn't utilize in many systems). If it's vista, at least 2 is correct.

Not entirely true - under WinXP 32, any single application can allocate up to 2 Gigs of memory, with the OS itself technically being able to adress up to 4 Gigs (Unless you run some Server version of XP). See this link for more info: http://www.microsoft.com/whdc/system/pl ... AEmem.mspx

I knew someone would say somethign about that. Here was my source:

http://msdn.microsoft.com/en-us/library/aa366778.aspx

but as a default, flight sim can only use up to 2 according to what you're saying?

[jan]

That's correct sir. Unless you apply the 3GB patch as outlined in the link I've posted earlier, WinXP can allocate a maximum of 2 Gigs of adress space to any individual application. We're both kinda right in the end.

[paavo]

That's correct sir. Unless you apply the 3GB patch as outlined in the link I've posted earlier, WinXP can allocate a maximum of 2 Gigs of adress space to any individual application. We're both kinda right in the end.

4 gigs for me shows up as 2.7 in dxdiag.

[jan]

4 gigs for me shows up as 2.7 in dxdiag.

That's a BIOS thing, the system keeps a certain amount of memory hidden from the OS to be able to do some caching and mirroring work without the OS weaving it's BSOD magic on it. The size of that memory space corresponds with the size of your gfx card's RAM and a few other things, thats why some people will find WinXP reporting anything from 3,5 to 3,0 Gigs or even less like in your case. Blame it on the x86 system architecture.

[BOOM]

I remember trying to boost my xp 32 to 3gig of ram,the pc wouldn't even boot-up

[paavo]

4 gigs for me shows up as 2.7 in dxdiag.

That's a BIOS thing, the system keeps a certain amount of memory hidden from the OS to be able to do some caching and mirroring work without the OS weaving it's BSOD magic on it. The size of that memory space corresponds with the size of your gfx card's RAM and a few other things, thats why some people will find WinXP reporting anything from 3,5 to 3,0 Gigs or even less like in your case. Blame it on the x86 system architecture.

I thought it was a limitation of a 32 bit OS.

[tbmavengerstuka]

4 gigs for me shows up as 2.7 in dxdiag.

That's a BIOS thing, the system keeps a certain amount of memory hidden from the OS to be able to do some caching and mirroring work without the OS weaving it's BSOD magic on it. The size of that memory space corresponds with the size of your gfx card's RAM and a few other things, thats why some people will find WinXP reporting anything from 3,5 to 3,0 Gigs or even less like in your case. Blame it on the x86 system architecture.

I thought it was a limitation of a 32 bit OS.

as did i