Is there a link with more detailed instructions (for dummies) on adding the 3gig switch to windows AND fs9? I'm fine with editing the boot file, just not exactly what to put in. I got brand new 2x2 sticks coming in, so I'll try out the switch.

http://forums.flightsim.com/fswiki/index.php/OOM_Error

http://forums.flightsim.com/fswiki/index.php/OOM_Error

Forgive me if I missed it, but it seems to only tell you how to set it in your boot file, as I understand it you must enable it in your fs9.exe file too?

Red, have a look here:http://forums1.avsim.net/index.php?showtop...6&hl=uservaHope it helps.I've seen no OOM since I applied it.

Red, have a look here:http://forums1.avsim.net/index.php?showtop...6&hl=uservaHope it helps.I've seen no OOM since I applied it.

Great, thanks a lot. I applied both the .exe fix and the 3gig switch in boot.ini. Is there a way to tell that this has been done properly? Under system properties, it still reads that I have 3.25Gigs of RAM available, should it show more now or no?

it still reads that I have 3.25Gigs of RAM available, should it show more now or no?

No, it's fine. Mine shows 3.5.

Is there a way to tell that this has been done properly?

Yes, there is, not simple though.You would have to use Sysinternals Process Explorer, enable column Virtual Size (under Process Memory), and observe your VS of the FS9.exe process.If the process manages to cross the 2GB mark usage and FS doesn't crash, tweak is good. If it OOMs before it reaches 2GB, tweak is no good.EDIT: And I just noticed I repeat myself. Months in separation though...

I'm now using Win 7 64 bit but when I was on XP 32 bit I had a two or three OOMs after short flights in the PMDG 747 and MD11 using FS9. By short I mean London HR to Geneva and Manchester to Zurich. Both Geneva and Zurich airports are by FSDreamteam so were suspects at one point.Then I read a suggestion (I forget where) to not have Virtual Memory fixed, as I had but to let Windows manage it. So I set it to zero, rebooted, then set it to Windows managing it. Since then not a single OOM in spite of then having 2GB of memory.Iain Smith

Oh my...I see, that after even months and months of telling the same story ALL over again, noone yet understands the difference between Virtual Size, Virtual Memory and Physical Memory and the actual connection between those.I'll just from now on leave you believe what you want, I am done and over with explaining.

Oh my...I see, that after even months and months of telling the same story ALL over again, noone yet understands the difference between Virtual Size, Virtual Memory and Physical Memory and the actual connection between those.I'll just from now on leave you believe what you want, I am done and over with explaining.

:( As long as you have put the info out there. Thanks for all the explanations.

:( As long as you have put the info out there. Thanks for all the explanations.

On more than one occasion. I would have to dig out old posts. What kinda aggrevates me that AVSIM doesn't actually care for such posts and doesn't pin them into tips and tricks forum. I wonder why. Everyone would benefit from that.

Everyone would benefit from that

That would not change much. From my longtime forums experience (also as a moderator and admin) I can tell you that 90% of visitors never care to spend a minute searching for info anywhere (even in the sticky posts). They just open up another post asking you to tell them what to do.And that doesn't go to anyone specific in this thread. Just a general eternal rule. :(

That would not change much. From my longtime forums experience (also as a moderator and admin) I can tell you that 90% of visitors never care to spend a minute searching for info anywhere (even in the sticky posts). They just open up another post asking you to tell them what to do.And that doesn't go to anyone specific in this thread. Just a general eternal rule. :(

Actually, that same observation applies likewise to the (in)famous "readme.txt" files that nearly everyone ignores......you know, the files that most often contain critical information that the user really needs to know... :(

Oh my...I see, that after even months and months of telling the same story ALL over again, noone yet understands the difference between Virtual Size, Virtual Memory and Physical Memory and the actual connection between those.I'll just from now on leave you believe what you want, I am done and over with explaining.

I assume that you're reacting to my post of Dec 31st 7-52am. If you want to make that clear, just inlcude a line or two from that post - common sense really!Now to my post. All I did was give you my experience which is also shared by several people that I communicate with. Strangely enough it came from a Microsoft Knowledge Base article. Also I never had the 3GB switch applied. I say again - from the moment of letting Windows XP 32 bit manage my virtual memory I never had another OOM, in spite of using detailed payware add-on airports, PMDG a/craft and UT Europe.It's very dangerous to think you know everything about a subject - especially when the Aces team had failed to pin down a cause.Iain Smith

I assume that you're reacting to my post of Dec 31st 7-52am. If you want to make that clear, just inlcude a line or two from that post - common sense really!Now to my post. All I did was give you my experience which is also shared by several people that I communicate with. Strangely enough it came from a Microsoft Knowledge Base article. Also I never had the 3GB switch applied. I say again - from the moment of letting Windows XP 32 bit manage my virtual memory I never had another OOM, in spite of using detailed payware add-on airports, PMDG a/craft and UT Europe.It's very dangerous to think you know everything about a subject - especially when the Aces team had failed to pin down a cause.Iain Smith

Hello Iain,I never tried to pin down the cause, but rather find the solution or at least a halfway-solution to the problem. Why I responded to your post like that:Letting windows manage virtual memory can hardly have anything to do with the real OOM - now, maybe we are here not even talking about the same OOM, who knows.I know that 2 years back, when I was extensively testing OOMs, and I am talking basically hundreds of test flights done with various configurations and memory, proved one thing and one thing only resolved that typical OOM that was occuring on my PC - letting FS9 use more than 2GB of virtual space.You started talking about virtual memory, which in no connection stands to virtual memory windows is using.The problem most of people have is when FS9 tries to load more than 2GB of memory into the system, crashing in the environment that natively allows it to use up to 2GB of VIRTUAL SPACE.Now let me put it like this: If you have 2GB of physical RAM and set your virtual memory to 2GB, manually, you will provide to windows and its programs 4GB of memory to use. The only difference between manually setting the pagefile and letting windows manage it, is that windows will do (I think) 1.5x the size of RAM = size of the pagefile. Manual setting can be anything. If you provide enough, there should be no difference, at least there were none on my system.Also I saw through the tests, when I installed 4GB of RAM, ran XP x64, with an unmodified FS9, so it could only use 2GB, I was still getting OOMs. Of course.If you go a little deeper in the whole thing, you will notice that there are basically two important memory values. Already mentioned virtual size vs working set. Working Set defines the number of pages OS is allowing at any time for the process to maintain in the physical RAM. Virtual Size for that matter is the number that defines the number of pages the process has already altogether allocated. Those pages that are not in the working set, will be saved in the page file (a very simple oversimplification). This virtual size is growing, depending on how good the scenery has been made, depending how heavy on the memory the aircraft is etc. There have been confirmed leaks in some situations (empty texture folders for LC, double AFCADs etc). The fact is, Virtual Size will keep growing if the program uses various handles all over again (and FS9 does that), when it reaches 2GB on 32bit unmodified system, it is going to crash. The general problem with FS9 is, it has problem with unloading of the handles, that is why we often see crashes, that is, I believe, what ACES wasn't able to solve.You can also deactivate Pagefile if you wish, and only if you have enough RAM. Which won't do you any good under 32bit OS. Since I am running W7 x64, I deactivated Pagefile and have been running without slightest problem already about 30 flights or so.I claim I know a lot about this subject, I would never claim to know everything.

Since I am running W7 x64, I deactivated Pagefile and have been running without slightest problem already about 30 flights or so.

Hello Word Not Allowed, interesting post! Clearly, you do know a great deal about this. I'm interested in your comment that I've quoted above. I too am now on W7 64 bit. I assume that deactivating the page file has the advantage of less accessing of the HD by Windows so helping improve performance. Any points to watch out for? Are there any limitations?Iain Smith