For the first time in about a million years I CTDd - ("Bong!") - and got an Out of Memory message.I tried a search here and was told that one of the words is too short :( to allow a search.So I have to ask here: what do I do to correct this memory thing - cos I can

What you need to do is one of two things.A) Install the 3GB switch....http://blogs.msdn.com/ptaylor/archive/2007...ress-space.aspx:( Install a 64bit operating system, this cured my FS9 OOM errors...

I think the search limit needs 4 letters or more, meaning that when it comes to OOM, you can only search for memory, which yields lots of irrelevant posts.The two things that solve issues for me are:3gb switch installed for Win XPLargeAddressAware flag set in FS9.exe.searching for largeaddressaware actually got me to a post that had a guide to the set up process.I also make sure that for long range flights, I restart the computer after my initial prep work, so that FS runs on a clean start.Hope this helpsAh, altstiff beat me to it. Although I found it hard to find 64-bit drivers for some of the older hardware in my machine (ie wireless network cards, sound cards).

The most common causes of an OOM on my computer are:

• An empty texture directory in one of my addon scenery folders.
• A landclass file in an addon scenery folder when there is an accompanying texture folder. If there is a landclass scenery file, it needs to be in an addon scenery directory with no accompanying texture directory. If there is a texture directory, the landclass keeps looping for the textures that it can't find, and allocates memory as it loops. Just to complicate this a bit further, if the landclass has its own textures, then a texture directory can be used, but it must include ALL of the textures the landclass calls.
• I think terrain files can have the same effect as landclass files if there is an accompanying texture directory. This is because terrain files often call a slope texture and allocate memory for that texture. (I think this was the justification for one of the patches of UT Europe).

Bryn.

I took the easiest and quickest route first: ran ScanAFD, found some dupes (mostly FI UTraffic), and CTDd again, only this time it took a lot longer and I didn

Hi,I have found that certain programs eat up a lot of memory and then do not give it back when you exit that program (the Clickteam Installer Creator seems like one of those).So one thing you can do to help avoid OOM errors is to reboot your machine just before starting a long flight in FS.Hope this helps,

The most common causes of an OOM on my computer are:

• An empty texture directory in one of my addon scenery folders.
• A landclass file in an addon scenery folder when there is an accompanying texture folder. If there is a landclass scenery file, it needs to be in an addon scenery directory with no accompanying texture directory. If there is a texture directory, the landclass keeps looping for the textures that it can't find, and allocates memory as it loops. Just to complicate this a bit further, if the landclass has its own textures, then a texture directory can be used, but it must include ALL of the textures the landclass calls.
• I think terrain files can have the same effect as landclass files if there is an accompanying texture directory. This is because terrain files often call a slope texture and allocate memory for that texture. (I think this was the justification for one of the patches of UT Europe).

Bryn.

Best answer of them all Bryn. "Northridge" is on XP sp1 ? ( 64? ) Donot think a 3gb switch would even suffice unless he's on a 64 bit OS. Nobody should have a problem in any case. ( 64 os, 32 os, 2gb+, whatever ) Designed as a 32 bit app, if there's problems it normally boils down to scenery as you mentioned. People just get away with poorly managed scenery folders, but those with the vista, xp64 & > 2GB can get away with the mistake with the "3 - switch" Grains of salt. My sig. system is dead.Roman

If you have a 64bit OS you do not need the 3GB switch, you need to flag your 32bit FS9.exe to read beyong 2GB of Virtual Addres Space using the large address aware flag. 64bit OS has no VAS limit, and even a 32bit application can benifit from a 64bit OS if you tell the 32bit exe to look beyond 2GB of VAS.If you have a 32bit OS you need to do two things, set the 3GB switch in your boot ini and flag your FS9.exe to see beyond 2GB (using large address aware flag). But this will only give you 3GB of the 4GB available and is not fool proof.If you run lots of add-on's with complex airplanes into complex add-on airports and lots of AI traffic, you really should invest in a 64bit OS.I had problems with OOM errors and switching to 64bit fixed the issues for me....

What ticks me off is that I only ever had this problem at the very beginning of FS, and now it has returned years later with my highest-spec machine ever.I honestly don`t think I am doing anything differently than previous installs - wayward scenery & texture folders, new scenery or aircraft, etc - .A new OS (64bit) is out of the question.If someone would be kind enough to walk me through an XP 32bit Sp1 3Gb switch doolally...........cos I have looked at a couple of Helps on Google and my .ini text string is different from them.I spose I could cure the problem even easilier by removing 1 of my 2 2Gb sticks of memory. Or is that just sillyIncidentally, XP Home edition.

What ticks me off is that I only ever had this problem at the very beginning of FS, and now it has returned years later with my highest-spec machine ever.I honestly don`t think I am doing anything differently than previous installs - wayward scenery & texture folders, new scenery or aircraft, etc - .A new OS (64bit) is out of the question.If someone would be kind enough to walk me through an XP 32bit Sp1 3Gb switch doolally...........cos I have looked at a couple of Helps on Google and my .ini text string is different from them.I spose I could cure the problem even easilier by removing 1 of my 2 2Gb sticks of memory. Or is that just sillyIncidentally, XP Home edition.

You may find this useful - it worked well for me and I have essentially the same system:http://forums.flightsim.com/fswiki/index.php/OOM_ErrorGood luck.

You may find this useful - it worked well for me and I have essentially the same system:http://forums.flightsim.com/fswiki/index.php/OOM_ErrorGood luck.

Hey Opa, don't you also have to set the fs9.exe's flag too, (was that already mentioned), with a "editbin/LARGEADDRESSAWARE fs9.exe" command?After, I think then you can run "dumpbin/headers fs9.exe" to see that the headers contain the string..."Application can handle large (>2GB) addresses".Mark

Hey Opa, don't you also have to set the fs9.exe's flag too, (was that already mentioned), with a "editbin/LARGEADDRESSAWARE fs9.exe" command?After, I think then you can run "dumpbin/headers fs9.exe" to see that the headers contain the string..."Application can handle large (>2GB) addresses".Mark

It may have been mentioned - not sure.I also have done that (set up the large address aware on FS9.exe), using the excellent instructions here:http://www.simviation.com/cgi-bin/yabb2/Ya...239243552/15#15And finally I also use the nifty free utility called Game Booster -available here: http://www.techspot.com/downloads/4842-game-booster.htmlI find it much simpler to use than FSAutostart or any of the other utilities which shut down unecessary processes etc. prior to flying.Using all three I find I get a noticeably "smoother" FS2004 experience. I will admit that so far I have never experienced the OOM error (even prior to using these items) so cannot say one way or another if any of these "tweaks" helps anyone with that issue.They work well for me but your mileage may vary. :(

I said earlier that I hadn

I would doubt the installation of another version of Net Framework would have any impact on the situation as the various Net Framework packages are not supposed to replace other versions as the name would tend to suggest. They are separate versions as many applications use them and the applications look for specific versions.If you deleted an earlier version prior to installing the newer one, then that might be problematic.I currently have 4 or 5 versions of Net Framework installed.

BTW, if you search for "OOM Error" (without the quotes of course!) you will get a lot of "hits..." :(