Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
Then you simply have to add "/3GB /USERVA=2560" to your Boot.ini.Thanks Guys
I actually still run XP with 4GB of RAM. It's only common when flying the PMDG MD-11.
Nothing worse than spending 10-20 min preping only to have a CTD as you are halfway to your destination!
Ben

Then you simply have to add "/3GB /USERVA=2560" to your Boot.ini.
It's all well explained here: http://fsdeveloper.com/wiki/index.php?title=OOM_Error
That's really necessary for FSX
If you don't use FSX SP2/XPack, you have to add the /LARGEADDRESSAWARE flag to the FSX.exe. This step is not necessary if you use SP2 or XPack...
Ben, listen to Nils. If something can cure OOMs, it's the boot.ini tweak.
Used to get OOMs on my old 2Gig config when flying into Aerosoft's Hannover. After having applied the memory tweak, I didn't get any OOMs anymore.
When I applied the boot.ini "tweak" to my system, 2Gb RAM with a 1Gb graphics card (Asus/ATI HAD3870X2), FSX became unusuable, from boot showing every sign of having run out of RAM such as spikes instead of autogen objects, jumbled aircraft and an abject inability to load textures.
Remove the boot.ini tweak, all is well again.
At some point, I'll pull my box out and check what the RAM is other than "2 x 1Gb sticks", then see if I can up it to 4Gb and try again. There's a known issue that is written about on a lot of tech sites regarding that tweak and larger graphics cards.
Ian P.
If I read the article correctly, I think it is aimed at PC's with 4 GB of RAM.
Nils said:That's really necessary for FSX
....
Incidentally, the B377 is superb. Review is well underway and will hopefully be posted in the not-too-distant future (definitely not "s**n", though).
Ian P.
