Hi all this is the message I just got while doing a flght from CYOW to CYYZ using the great add-on scenery from FLight Ontario. I have never had this happen before even with lower end systems.I am running a P4 3.0 Ghz with 1 Gig of ram..surely this is more than enough. is it possible I have a memry leak somewhere . I need help with this one big time!!

There may be a problem with your pagefile. Possible conditions might include:1. Pagefile too small2. No pagefile at all3. The pagefile is a dynamic pagefile (Windows managed) and the hard drive on which the pagefile exists is full.That said, I've never had FS9 run out of memory or use more than 1 GB of RAM. Although I have had it use as much as 700-800MB, so your mileage may vary. If you don't have a pagefile, then running out of RAM is a realistic possibility. I don't know what kind of video card you have in your rig (presumeably a decent one if it's a P4 3.0Ghz), but if you have alot of AGP memory in use, that could be gobbling up a fair slice of your memory too - especially if you're running 3rd party scenery in tandem with an aircraft like Flight 1's ATR 72-500 which is very texture memory intensive. You can monitor memory usage for FS9.exe via Task Manager or Perfmon (for a more accurate picture). Perfmon will graph memory usage over time. You'll want to look at the "Private Bytes" for FS9.exe. To see if something is leaking, your best bet is to place the sim in windowed mode, under a "stable" condition (parked at the gate with engines running or something) and just leave it there for a few hours and watch the perfmon graph. Some increase in memory is to be expected, but if you find that your memory footprint goes from 500MB to 800MB w/ no input from you, that's a pretty solid indication of a leak.Also, make sure you start FS with the minimum amount of software running in the background. I've seen XP run on as little as 70MB. More typical is around 100-120MB in a "clean configuration". If your baseline footprint before you start FS is 200+, you might have problems. Lastly, make sure your memory is actually being *detected*. Sometimes a loose or defective module will cause a stick of memory to go unnoticed by the OS: so you could be running on less memory than you think you have. Control Panel | System should report to you the amount of physical RAM Windows "sees". That information is also available on the Performance tab of Task Manager (Total Physical Memory).If you're running Windows 98 - all bets are off w/ anything having to do with memory management :)J

This message can also be caused by a bad bgl, whether it is an AFCAD file, scenery file--whatever.It's also been known to happen when Landclass or photoreal is not installed correctly. In the case of Landclass, if you place it in its own folder, the folder structure is as follows:Carson City Landclass---------------------Scenery----------------------------Carson City.bglNO TEXTURE SUBFOLDER should be created for landclass scenery, and landclass bgl's should not reside in the same folder as any other bgl to keep things safe. Photoreal scenery can have a texture folder, but it must contain all the textures associated with the project. If the author forgets even one, FS2004 may have problems.Bad AFCAD files can cause problems 100's of miles away, especially if they conflict with other add-on scenery.Hope this helps...-John

just to update u the actual message is "windows has run out of available memory" and the culprit seems to be the way i have installed Flight Ontario's Toronto area scenery. here is how it is set up on my computer I have the actual scenry in a folder call ed FS2004 add-ons wihin FS9 and within that folder I have the scenery and texture file. For ontario landclass i have the scenery bgl files installed in the FS9 add-on scenry folder and the texture files in the Add on texture folder...is this setup correct becuase I have tried diffewrent flight with the Flight 1 ATR with other complicated addon sceneries and this problem has not occurred.

"For ontario landclass i have the scenery bgl files installed in the FS9 add-on scenry folder and the texture files in the Add on texture folder..."And that would be your problem. Create a seperate folder for the landclass files for your new add-on. Make sure that new landclass folder has a Scenery folder (which will hold the landclass files) but does not have a Texture folder in it. As stated, having a Texture folder along with the Scenery folder of a landclass add-on is what causes the memory leak.Cheers,Greg