Well, this about tears it!Just flew from KEWR - KIAH (Simflyers) for three hours and two minutes, was on ILS final for 15R, 15 miles out in my new Citation X when....."ErrorYour computer has run out of memory. Flight Simulator will now exit. you may not have enough free space on your hard drive. Run Disk Cleanup to free up space and then try running flight simulator again." And she shut down when I clicked ok.As I usually do, immediately before my flight, I restarted my computer. I then ran enditall and killed everything except Explorer, Smax4PNP MFC Application, Smax 4 SoundMax Control Center, MSShortcut Bar and EndItAll. I usually run MemMax to monitor memory usage which never goes above about 60% and usually runs well below 50%, but had it turned off too thanks to EndItAll.I then started up FS9, FSMeteo, Servinfo, SBRelay and initalized the VatSim setup for my flight.Specs:P4C800 Deluxe MBPentium 3.2GB CPU1GB 400 MemWinXP Pro OSFS936GB SCSI Primary harddrive with 16GB free space36GB secondary IDE 7500 harddrive with 11GB free spaceDirectX9.0BATI 9800 Pro Primary GraphicsViewsonics P815 21" Primary MonitorSamsung SyncMaster 1100 P Plus 21" Secondary MonitorDiamond Stealth II S540 PCI Secondary Graphics CardVivitron 17" third monitorCDRWCDROMLS120Std.FloppyCreative 5.1 Speaker systemLexmark Z52 PrinterTI MicroLaser Plus PrinterMustek scannerI have run the above setup for many months, or years and this is the first time I have seen this error message (And hope I never do again)Any ideas?Thanks:RTHPS: Thank Goodness for AutoSave!

There's several things I've seen which can trigger this error:~A bad bgl. Usually the error appears at startup, when the bgl is first installed, but not always.~Landclass that's not correctly installed. In a nutshell, if you install landclass in its own folder, that folder must not have a texture subfolder. The landclass.bgl(s) go into the scenery subfolder like any other normal bgl, but a texture subfolder causes problems.~An "untweaked" autogen setup. Early on it was shown that the new autogen can get "stuck" in memory. The fix involves removing the default.xml file and turning off terrain vector objects.~Manually tweaking the terrain display entries in FS9.cfg to something other than the defaults defined by the display settings.~A rogue gaugeI have a 384 meg system and have had sessions up to fourteen hours. Available memory has always stayed about 100MEGS, and my swap file never gets used. You have a number of add-ons going, so I won't speculate about those. Also, sometimes MSFS will report out of memory when it has plenty--example being the bad bgl scenario I mention above. The error message would look better if it read "This is MSFS--I have a short term memory problem" :)-John

Thanks for the information John:I will keep an eye on the items you mentioned. I just installed several downloads of Rob Gainer's mesh. He has found a bgl file or two that had errors and replaced them. I have now replaced mine with his updates. This would fit with your ideas in your reply and I hope that was the problem. The strange thing would be that the error occured when I was some distance from the areas he included in his mesh, but I guess they still could possibly cause a problem. For several hours now, I have not had the problem reoccur. I have to confess that I am ignorant of the differences in all of the different types of scenery (i.e. landclass, mesh, conventional scenery installation etc.)Thanks for your input.RTH