With a 32Bit OS you always have the limit of 2GB Virtual adress space for user applications (e.g. FSX) and 2GB for the system (=4GB in total).Yes Ben, I think that was exactly the issue, although back when I applied it, the page that I got the information from said that it was for systems with 3Gb+ of total memory, including video RAM. I now know this statement to be incorrect and, indeed, some of the reason is discussed on the FSDeveloper post referred to by Nils above.
The reason I posted that comment was also because of Nils's post, where he says:
where what I believe is meant is "necessary for FSX on systems with in excess of 3Gb System RAM". Changing the /USERVA switch number - or removing it altogether and just leaving the /3GB switch - made no difference whatsoever, FSX was still unusable.
Hopefully that makes more sense?
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.
No matter how much System Ram you have installed.
By increasing the user VA, you will decrease the VA for the System (but the Video Memory is completely mapped into the System VA).
So, you can't increase the user VA much and use a graphics card with really large Video Ram under a 32Bit OS, because that will leave not much room for the OS.
OOMs are occurring because FSX is running out of virtual address space or because of a lack of contiguous memory.
That's why increasing of the user VA is necessary for FSX, but of course you have to be careful.