Hi everybodyI've just bought a new PC that can run FS9 pretty much maxed, and as a commisioning flight I took the MD-11 from KLAX to KJFK. Ran beautifully until the descent where it OOM-ed. Running XP32 with 2GB of ram.Here's what I was running : FS9, UT2004 at 100%, UTerrain USA, FSGenesis, RCV4, ASV6.5. Think that's it. :( I've already ordered another 2GB of ram, but after looking through some of the topics here regarding OOMs, I'm not sure if this will solve the problem. Will adding the 3GB switch and making the FS9.exe large address aware (are they the same thing?) sort this out, or is a 64-bit OS the only way forward? I'm not sure if the rest of my addons will work OK with a 64-bit system (I know my RXP gauges won't), so I might be looking at an XP32 'main OS' with FS2004 for GA and a separate XP64 OS for flying the heavies, which isn't too much of a problem as I've got plenty of HD space, although the tedium of reinstalling everything might be a little painful...Sooo, 4GB with XP32 OK, or is 4GB with XP64 the way to go? Thanks in advance.Cheers, Chris Dalgarno in sunny Australia

IMHO anything but an upgrade to 64b is an interim fix. There's nothing wrong with interim fixes, depends on your circumstance and preference.

Chris,Why don't you go all the way and get Windos 7 64. I have been using 64 bit software for years and have only experianced a few driver related issues a few years ago. For the last year or so I have not had any issues. With 4 GB of mem and 64 bit operating system I have never had an OOM issue.

Chris,Why don't you go all the way and get Windos 7 64. I have been using 64 bit software for years and have only experianced a few driver related issues a few years ago. For the last year or so I have not had any issues. With 4 GB of mem and 64 bit operating system I have never had an OOM issue.

I've tried Win 7 32 RC and liked it, but my CH yoke and pedals are gameport and Win 7 (or Vista) doesn't support them. Maybe I should get a gameport - USB adapter, I've read mixed reports that they work. Certainly would make things easier, wouldn't it?Cheers, Chris D

I can confirm that since switching to 64bit Vista I have never experienced OOM.

Well, just ebay-ed a gameport - USB adapter, if it all works OK I reckon Win7 64 may just be beckoning. Has anybody tried Win7 64? No dramas I should be aware of?Cheers, Chris D

I was testing W7 64bit (the version before RTM - public beta or something like that), worked great with FS9. Just don

Try the interim solution of the /3Gb switch AND making FS9 large address aware, as they are not the same thing as you asked...I had a couple with FS9 and 2Gb RAM before I added 2Gb more and used the switch. I haven't experienced an OOM on the box since... a couple of application hangs and so on, but never the "application has run of out memory" warning...Mid to long term, you want to look at 64bit OS... skip Vista and go straight onto W7. There must be some way of adapting your conotrollers, or you perhaps upgrade them too? Depending on the age, the potentiometers may not be what they were new... I hate the out with the old in with the new adage, but sometimes there is no way around it... (or unnecessary expense)Andrew

64 bit for me.

I can confirm that since switching to 64bit Vista I have never experienced OOM.

Same here.

Well guys, you are wrong, it has nothing to do with 32bit OS. Windows, as almost any other OS uses virtual memory. If you load application, that is bigger then your available physical memory, windows will free memory, by saving memory pages on your hard drive and loading them, if application need them. The whole proccess is complettly transparent to application, so you will not run out of memory on a 32bit system, even if you use much more than 4GB memory on 32bit system. Your available memory is actualy your physical memory(RAM)+your hard drive space(swap file). The only negativ side is performance, because hard drive is much slower than RAM. So 32bit OS limits your RAM size only, not your available memory for program. To your particular problem: you should enable windows virtual memory manegment on a hard drive and let windows manage it or make page file so big, that you will not run out of memory, where you have enough free space. It's enables per default, but many optimisation guides and programms tell you, you should disable it because of performance issue. If you don't know how to do this, just look on internet, there is more than enough websites explaining this.Roman B.

Well guys, you are wrong, it has nothing to do with 32bit OS. Windows, as almost any other OS uses virtual memory. If you load application, that is bigger then your available physical memory, windows will free memory, by saving memory pages on your hard drive and loading them, if application need them. The whole proccess is complettly transparent to application, so you will not run out of memory on a 32bit system, even if you use much more than 4GB memory on 32bit system. Your available memory is actualy your physical memory(RAM)+your hard drive space(swap file). The only negativ side is performance, because hard drive is much slower than RAM. So 32bit OS limits your RAM size only, not your available memory for program. To your particular problem: you should enable windows virtual memory manegment on a hard drive and let windows manage it or make page file so big, that you will not run out of memory, where you have enough free space. It's enables per default, but many optimisation guides and programms tell you, you should disable it because of performance issue. If you don't know how to do this, just look on internet, there is more than enough websites explaining this.Roman B.

Very well delivered RomanB. Simple is good. And it ain't gonna get much simpler that you explained.I'd like to add the following link as - in the past - utilizing the TWEAKS from this post helped me stabilize a wildly erratic XP-Pro 32bit with 2Gb RAM. Back when I was 32bit, I could fly the PMDG MD11 from Amsterdam to Houston - about 9 hours - without a problem. But, flying Amsterdam to Los Angeles? Go figure... three (3) times I tried the 12hr long haul - as I was still tweaking - and each time... without fail... OOM'City at about 200' AGL over the numbers on RWY 25L at KLAX.Funny thing... I can make the same run with the 767-300ER... never a problem completing the flight.THE LINK: http://www.simforums.com/forums/forum_posts.asp?TID=29041Cheers,Keith

Sooo, 4GB with XP32 OK, or is 4GB with XP64 the way to go? Thanks in advance.Cheers, Chris Dalgarno in sunny Australia

Can you confirm that you have the various FSX service packs installed? I use a 6g, i7-920 rig with Vista 64 and on occassion, would get the OOM error which, for the reasons you speeciy, was kind of shocking. When I got the J41, I discovered that I had some FSX SP2 issues, so I reinstalled it and haven't had any OOM problems since then. So, maybe that will help. (My only real current issue is that sometimes, usually while flying in a time compressed mode of 4X or 8X, the MD-11 or 747 will freeze. (yeah, yeah, compressed modes bad; sue me.) I usually just pretend that I want to save the flight (;) and then cancel it and everything works fine. No CTD or OOMs, just an annoying psuedo freeze).

To your particular problem: you should enable windows virtual memory manegment on a hard drive and let windows manage it or make page file so big, that you will not run out of memory, where you have enough free space. It's enables per default, but many optimisation guides and programms tell you, you should disable it because of performance issue. If you don't know how to do this, just look on internet, there is more than enough websites explaining this.Roman B.

Agreed. I'm running Win XP 32 with 2GB of RAM and had a couple of OOMs with the virtual memory fixed when operating the MD11. I then set it for Windows to manage and haven't had an OOM since.However, I have pre-ordered Win 7 and will install the 64 bit version when it arrives in a couple of weeks.Iain Smith

Can you confirm that you have the various FSX service packs installed? I use a 6g, i7-920 rig with Vista 64 and on occassion, would get the OOM error which, for the reasons you speeciy, was kind of shocking. When I got the J41, I discovered that I had some FSX SP2 issues, so I reinstalled it and haven't had any OOM problems since then. So, maybe that will help. (My only real current issue is that sometimes, usually while flying in a time compressed mode of 4X or 8X, the MD-11 or 747 will freeze. (yeah, yeah, compressed modes bad; sue me.) I usually just pretend that I want to save the flight (;) and then cancel it and everything works fine. No CTD or OOMs, just an annoying psuedo freeze).

No, I don't have any FSX service patches installed. I'm one of those die-hards using FS9. :) BTW, I use time compression a lot as well, so don't feel bad. :( Cheers, Chris D