In my PC I have changed the bootdrive to a brand new 320 GB.In this drive I have reinstalled a fresh copy of WIN XP Pro SP2 plus Office 2003, Acrobat, FlashGet, McAffee and Skype.Also FS 9.1 including DirectX 9C is on the drive.FS9 works OK, but ONLY in its default state.As soon as I install any 3rd party scenery I get "Out of Memory" error and FS9 aborts.The PC has 1 GB RAM installed and it is recognised at bootup by BIOS as well as seems ok in SiSoft Sandra and also in the WIN Control Panel.Any clue for a remedy is greatly appreciated.Bjorn

Could be an issue with the scenery itself, or the method you're using to install it. An out of memory error after the installation of new scenery usually happens when the .dat file is being built for that scenery. Can you give an example of scenery that's causing this issue? Can you show us your scenery.cfg entry you created for the scenery, if any? And last question, where are you placing the bgl, and where are you placing the textures?-John

Hi John,It is a possibility I did not think of that the old .dat files from my old scenery folder is making this problem so I will delete the dat file and then it should rebuild itself by FS9.Scenery install is other than that my "expertise area" :-) so I do not see any problem there but a possible corrupted .dat file.I will try the above and post the results a.s.a.p.F.y.i. any add-on scenery generates this error at the moment even my own Swedflight Pro Swedish scenery (www.swedflight.com)Bjorn

Still no joy,I deleted the scenery.dat file for the ESSA V2 scenery and let FS9 rebuild the .dat file, but with no success.This scenery (Area 39) is proven 100% stable and does not have any duplicate afcads or other strange things. It works ok in another computer.All aircraft that I add to FS9 does not cause the memory leak however at the moment I have a "clean" install with only FS 9.1 aircraft. FS is also installed from original FS 9.1 CD:s without the "CD crack"Below is my scenery.cfg file.Bjorn[General]Title=FS9 World SceneryDescription=FS9 Scenery DataClean_on_Exit=FALSE[Area.001]Title=Default TerrainTexture_ID=1Layer=1Active=TRUERequired=TRUELocal=SceneryWorldRemote=[Area.002]Title=Default SceneryLocal=SceneryBASELayer=2Active=TRUERequired=TRUERemote=[Area.003]Title=AfricaLayer=3Active=TRUERequired=FALSELocal=SceneryAfriRemote=[Area.004]Title=AsiaLayer=4Active=TRUERequired=FALSELocal=SceneryAsiaRemote=[Area.005]Title=AustraliaLayer=5Active=TRUERequired=FALSELocal=SceneryAustRemote=[Area.006]Title=Eastern EuropeLocal=SceneryEURELayer=6Active=TRUERequired=FALSERemote=[Area.007]Title=Western EuropeLocal=SceneryEURWLayer=7Active=TRUERequired=FALSERemote=[Area.008]Title=Central North AmericaLocal=SceneryNAMCLayer=8Active=TRUERequired=FALSERemote=[Area.009]Title=Eastern North AmericaLocal=SceneryNAMELayer=9Active=TRUERequired=FALSERemote=[Area.010]Title=Western North AmericaLocal=SceneryNAMWLayer=10Active=TRUERequired=FALSERemote=[Area.011]Title=OceaniaLayer=11Active=TRUERequired=FALSELocal=SceneryOcenRemote=[Area.012]Title=South AmericaLayer=12Active=TRUERequired=FALSELocal=ScenerySameRemote=[Area.013]Title=Amsterdam Aerial PhotoLayer=13Active=TRUERequired=FALSELocal=SceneryCitiesAmsterdRemote=[Area.014]Title=Anchorage Aerial PhotoLayer=14Active=TRUERequired=FALSELocal=SceneryCitiesAnchorRemote=[Area.015]Title=Atlanta Aerial PhotoLayer=15Active=TRUERequired=FALSELocal=SceneryCitiesAtlantaRemote=[Area.016]Title=Chicago Aerial PhotoLayer=16Active=TRUERequired=FALSELocal=SceneryCitiesChicagoRemote=[Area.017]Title=Dallas Aerial PhotoLocal=SceneryCitiesDallasLayer=17Active=TRUERequired=FALSERemote=[Area.018]Title=Denver Aerial PhotoLocal=SceneryCitiesDenverLayer=18Active=TRUERequired=FALSERemote=[Area.019]Title=Heathrow Aerial PhotoLayer=19Active=TRUERequired=FALSELocal=SceneryCitiesHeathrowRemote=[Area.020]Title=Hong Kong Aerial PhotoLayer=20Active=TRUERequired=FALSELocal=SceneryCitiesHongkongRemote=[Area.021]Title=Kitty Hawk Aerial PhotoLayer=21Active=TRUERequired=FALSELocal=SceneryCitiesKittyhwkRemote=[Area.022]Title=Las Vegas Aerial PhotoLayer=22Active=TRUERequired=FALSELocal=SceneryCitiesLasvegasRemote=[Area.023]Title=Los Angeles Aerial PhotoLayer=23Active=TRUERequired=FALSELocal=SceneryCitiesLaRemote=[Area.024]Title=Miami Aerial PhotoLayer=24Active=TRUERequired=FALSELocal=SceneryCitiesMiamiRemote=[Area.025]Title=New York Aerial PhotoLocal=SceneryCitiesNewYorkLayer=25Active=TRUERequired=FALSERemote=[Area.026]Title=Niagara Aerial PhotoLayer=26Active=TRUERequired=FALSELocal=SceneryCitiesNiagaraRemote=[Area.027]Title=Oshkosh Aerial PhotoLocal=SceneryCitiesOshkoshLayer=27Active=TRUERequired=FALSERemote=[Area.028]Title=Paris Aerial PhotoLayer=28Active=TRUERequired=FALSELocal=SceneryCitiesParisRemote=[Area.029]Title=Phoenix Aerial PhotoLayer=29Active=TRUERequired=FALSELocal=SceneryCitiesPhoenixRemote=[Area.030]Title=San Francisco Aerial PhotoLayer=30Active=TRUERequired=FALSELocal=SceneryCitiesSanfranRemote=[Area.031]Title=Seattle Aerial PhotoLocal=SceneryCitiesSeattleLayer=31Active=TRUERequired=FALSERemote=[Area.032]Title=St. Maarten Aerial PhotoLocal=SceneryCitiesStmaartenLayer=32Active=TRUERequired=FALSERemote=[Area.033]Title=Sydney Aerial PhotoLayer=33Active=TRUERequired=FALSELocal=SceneryCitiesSydneyRemote=[Area.034]Title=Tokyo Aerial PhotoLayer=34Active=TRUERequired=FALSELocal=SceneryCitiesTokyoRemote=[Area.035]Title=Generic LibrariesLocal=SceneryGenericLayer=35Active=TRUERequired=TRUERemote=[Area.036]Title=Vehicle LibrariesLocal=SceneryVehiclesLayer=36Active=TRUERequired=TRUERemote=[Area.037]Title=Propeller ObjectsLocal=ScenerypropsLayer=37Active=TRUERequired=TRUERemote=[Area.038]Title=Addon SceneryLocal=Addon SceneryLayer=38Active=TRUERequired=FALSERemote=[Area.039]Title=ESSA_V2Local=......ESSA_V2Remote=Active=TRUERequired=FALSELayer=39

>This scenery (Area 39) is proven 100% stable and does not have>any duplicate afcads or other strange things. It works ok in>another computer.I'm not sure if we can say that anymore. :)Try installing a different 3rd party scenery package - perhaps George Grimshaw's Boston v2 (freeware, available here at AVSIM). This will help test whether or not your computer is having a problem with *ALL* addon scenery packages, or just the ESSA one you are attempting to install. Even with the scenery working on other computers (and even your existing computer before a fresh install), things could change which might impact the scenery's stability.Another possible thing to try would be to let FS9 rebuild it's fs9.cfg file - but I doubt that it would have any bearing on the scenery system. Good luck!-Greg

Is there any landclass being installed with that scenery?If so, make sure there is no empty texture folder.

I would guess either LandClass or you corrupt your Virtual Memory...Try letting XP rebuild its VM (Pagefile.sys)...-PaulPrimary RigLiquid CooledAMD FX-57 @ 3 gigsAsus A8NSLI-Premium2 gigs Corsair XMS PC3500LL 2 3 2 6 1TXFX 7900 GTX 690/1750XFX 7800 GTX 515/135024 inch Widescreen LCDDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1khttp://home.comcast.net/~psolk/3monitorsa.htmlAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7800 GTX 515/1350 Raid-0

One other suggestion to try--try changing "Local=......ESSA_V2" to the absolute path. MSFS may be having an issue with the way you've constructed the path there.-John

Hi John,I will do that a.s.a.p. but the path is what FS9 itself suggests when putting a scenery area in the harddisk rootfolder.Normally I have all scenery in another partition solely dedicated to scenerys, but I have just put it in the harddisk root to ensure that no other scenery installed (but deactivated) can interfere.I will make a test with the scenery installed in FS9 add-on scenery folder too and let you know if there are any positive results.Bjorn

Hi guys,I have found the root of the problem.I just copied scenery from my back-up (Acronis True Image) and appearantly the back up was partially corrupt!That is, a lot of BGL:s showed slightly different size when comparing with the original install files.When I reinstalled from the original installers all problems were fixed. Very embarrasing and I should have thought of this possibility first :-)So, I have now to reinstall som 50 add-on scenerys, will take a few hours, but I am a happy simpilot again.Thanks to all for your kind answers and suggestions.Best,Bjorn

I've had this problem for a week. I've followed all the advice from several areas to no avail. Microsoft give three solutions, none of which work. I've replaced Ram, bought a new hard drive and reinstalled XP and FS9. Still had the problem. However, I had been installing saved folders from my "Addon Scenery" folder, one at a time and registering them via the correct proceedure from within "Scenery Library" in a running FS9. Very laborious, so I started adding twenty at a time, all without a problem, so I then put in the rest,246 allup, and "Bang !"- All out of memory again, even though those other 200 odd were not yet installed via the "Scenery Library !" After a week of this,I finally noticed that I had a folder named "Scenery" amongst those 246 addon scenery folders. Now I've in the past done a fresh install of FS9 and simply dropped my saved Addon Scenery folders back in along with all my gauges, Aircraft folders,etc, without a problem. Once I renamed that "Scenery" folder within the "Addon Scenery" folder, the problem immediately disappeared, and of course, reappears if I give it it's name back. That's the worst of it over, but I don't have a clue really about.BGLs and which one of them is giving the problem. I deleted the index.dat file and it fixed it temporarily, but the problem returned. At least I can run the Sim now, but there are 1529.BGLs in that folder and I don't have the patience to rename them one at a time. Hope this info is of some use to somebody else out there. Perhaps somebody with expertise in BGLs has a few tips. Fred

Try "half-split" trouble-shooting in this case. Move (not copy) half of the 1526 bgl's out of the scenery folder to a temporary location away from the FS9 folder and try again.If your problem disapears, then you know your problematic bgl is in the "moved" half-set of files. Swap the two half-sets of files and try again. Then half-split this set of files and repeat testing until you've narrowed it down, keeping only half of the files at a time. Make sure you test each set of supposidly good set of files to be certain you don't have multiple bgl proglems. Using this method, be methodic, but then it takes no time at all to find corrupt files. Once you think you removed the problematic file or two, move each set of files back into the scenery folder, one set at a time and test again. This will also help detect combination issues. Good luck...Hope this helps...AL | KCHS - Charleston AFB/Intl | Home of the USAF 437AW (~53 C-17's)-------------------------------------------------------------Game Rig:AMD64-4000+ SanDiego OC=220/440/2640 | Asus A8N-SLI Deluxe | Corsair TwinX2048-3200C2PT (2x1GB) 2.5-3-3-8/[email protected] | Evga NV 7900GT v84.56 (No OC yet)| Thermalright XP-120(mm) HSF | NV LAN@1GB | NV (SATA-I spec) Raid-0 223GB (3x80GB Samsung) (WinXP/Games) | NV (SATA-II spec) WD 320GB (Backups) | IDE-0 80GB Samsung (Archive) | Realtek AC'97 5.1 Surround | CH Yoke, TQ, & Pedals | FS9.1 | WideFS Server | FSUIPC v3.6 | FSGenesis Mesh (All) | PMDG (All) | PAI (All) | FSBuild2 | Etc...FS9 Support Rig:AMD3200+ | Gigabyte GA-7NNXP | Leadtek NV 5900 | Corsair TwinX1024-3200 (2x512MB) | Intel LAN@1GB | SiI3112 SATA-I 80GB Samsung | IDE-0 80GB IBM | JustCom 4port KVM | FS Wide Client | ActiveSky v6 | Radar Contact v4 | FS Real Time | FS Flight Keeper | FS Commander | AI Smooth

Jordanal. Thank you for the excellent advice. Had to do it twice. Got down to the last two and found that "Ms catac2.bgl" was the culprit. Restarted with all the "good" files installed and got the same problem! Went through the whole thing again, and this time got down to one named "Ms galicia7.bgl." This time a restart was successful. What a relief. Halving 1528 files only took eleven stages so your advice was brilliant and I'm very grateful to you. Pity the Microsoft Pages aren't as "Cluey" Some one there must surely be aware of the problem as they have a whole page devoted to this specific "out of memory" warning, yet they say it's literally that; "out of memory or disc space", a "Paging file or virtual memory problem" or an "XP corrupted file problem" I messed around with all three for a week and even bought a new hard drive. Not the slightest suggestion there of a "BGL" or "Scenery" problem. I'd still be at it if it wasn't for the advice given in this Forum. Does anybody know where those two Ms.bgls reside or come from? Can't find the originals on the four FS9 discs and you can't explore the Fs9 update folder(Tried it with WinRAR and the contents looked like coded stuff) Thanks again. Fred

Cool, I'm very it glad I was able to help. Sorry, but I don't recognize those two particular BGLs.AL | KCHS - Charleston AFB/Intl | USAF 437AW (~53 C-17's)FS9/Game Rig:AMD64-4000+ SanDiego OC=210/420/2520 | Asus A8N-SLI Deluxe | Corsair TwinX2048-3200C2PT (2x1GB) 2.5-3-3-8/[email protected] | Evga NV 7900GT v84.56 (1280x1024x32/4xAA/16xAF/High-Quality) | Enermax 550W PSU | Thermalright XP-120(mm) HSF | NV 1GB LAN | NV SATA-I Raid-0 223GB (3x80GB Samsung) (WinXPx64/Games) | NV SATA-II WD 320GB (Backups) | IDE-0 80GB Samsung (Archive) | Realtek AC'97 5.1 Surround | CH Yoke, TQ, & Pedals | FS9.1 (Settings max'd/60-40Vis/No-Shadows/20FPS) | WideFS v6.16 | FSUIPC v3.617 | FSGenesis Mesh (All) | PMDG (All) | PAI (All) | FSBuild2 | Etc...FS9 Support Rig:AMD3200+ | Gigabyte GA-7NNXP | Leadtek NV 5900 | Corsair TwinX1024-3200 (2x512MB) | Intel 1GB LAN | SiI3112 SATA-I 80GB Samsung | IDE-0 80GB IBM | JustCom 4port KVM | FS Wide Client | ActiveSky v6 (512x512x32bit / Wx Influanced)| Radar Contact v4.01 | FS Real Time | FS Flight Keeper | FS Commander | AI Smooth