I think that this is the best course after all. Will attempt in the next day or two and report back my findings. I hate this ..... I hate this ..... I hate this ......

Sorry, had to get it out of my system!

 

Glenn the Depressed

 

 

LOL go ahead get it out hahahaha I know exactly how you feel

 

NOTE: If your problem occurs after the Re-install i you may be experiencing hard drive failure (Very doubtfull) but its possible. The hard drive stores information in sectors (Clusters) if some information gets written in these clusters or bad sectors it can cause problems. Again very doubtful that's your case but just throwing it out there. There is software online where you can perform sector checks in DOS usually if not many is found it can patch it up lol and allow the information to be writing on a good sector.

 

 

Also you mentioned running windows xp 32bit SP3 again XP 32bit does utilize 4gb i belive its limit is 3gb so that extra gb stick on your motherboard is not being used (you will a 64bit operating system to utilize all 4gb)

 

 

 

The problem with this statement is that it gives the impression that the cut off point when it comes to memory lies at the 4GB mark. Less memory than this and you're fine with 32-bit, but any more memory and you need a 64-bit OS to make advantage of it. The confusion arises because people take the term memory to mean RAM, and this can lead to some expensive mistakes as people buy PCs loaded with 4GB of RAM and a 32-bit OS, only to later realize they can't make use of all the RAM they bought.

With 4gb of ram that's already loads more memory than fs9 actually needs to run smoothly. If that tests ok and other programes access it correctly then the problem is only with fs9. Backup ALL your addons: airports, afcads, scenery, flightplans, saved flights, your fs9.cfg etc. Everything.

Kill fs9 and re-install a fresh clean copy. Then rebuild your fs9 historically. That is do not start with your most recent addons. Start with the earliest addons. Adjust your fs9.cfg as you go along to keep pace with the changes.

Next time you do an image make sure you have included the parts of the disc that fs9 needs to see in order to retain its integrity.

With 4gb of ram that's already loads more memory than fs9 actually needs to run smoothly. If that tests ok and other programes access it correctly then the problem is only with fs9. Backup ALL your addons: airports, afcads, scenery, flightplans, saved flights, your fs9.cfg etc. Everything.

Kill fs9 and re-install a fresh clean copy. Then rebuild your fs9 historically. That is do not start with your most recent addons. Start with the earliest addons. Adjust your fs9.cfg as you go along to keep pace with the changes.

Next time you do an image make sure you have included the parts of the disc that fs9 needs to see in order to retain its integrity.

 

Thanks,

I'm in the process of backing up the FS9 folder right now to a USB external drive. I have about 138 GB ti transfer so it's going to take awhile via USB. When I create an image, I have always imaged the who disk, including the operating system. That was to prevent this from happening. When I recover, I recover the who disk so as to everything intact. It has always worked before so I've been stumped as to what happened. As some posters have suggested, I think another program updated itself and corrupted the paths that FS9 needed to run.

Before you reinstall it might be worth it (if you haven't already) to go into the Scenery Library and uncheck (i.e. inactivate) ALL of your add on scenery (including the Addon Scenery layer). I have had bad scenery files cause OOM problems. Also, try going to Options/Settings/Traffic and drop your traffic slider to 0 (in case it's a bad AI aircraft).

 

Hope this helps,

Before you reinstall it might be worth it (if you haven't already) to go into the Scenery Library and uncheck (i.e. inactivate) ALL of your add on scenery (including the Addon Scenery layer). I have had bad scenery files cause OOM problems. Also, try going to Options/Settings/Traffic and drop your traffic slider to 0 (in case it's a bad AI aircraft).

 

Hope this helps,

 

I can't even get FS9 to start, so I can't go to the Scenery Library/Traffic slider. All was working well before this happened and I didn't add anything to FS9.

 

Glenn

Let us know hoew things go, an remember 4gb is more then enough fs9 wont even touch that 4th gb lol not even 3gb , XP Alone probably wont use 1gb remember a computer only uses what it needs.

 

For example the more programs you open simultaneously the more memory is used, With XP And FS9 opened together your machine doesn't come close to using up 4gb yet alone 3gb.

 

but if you plan on wanting to take effect of the 4tgb (that is if in the futer you plan on installing more programs and multitasking i would upgrade to a 64bit OS) Considering your on 32 bit that 4th gb you have there is just paper weight lol

you can also try this http://www.ntcore.com/4gb_patch.php if you haven't already open the patch tool and direct it to the fs9.exe file and see what happens, if you already started the install do it anyways to the fresh install .EXE file

you can also try this http://www.ntcore.com/4gb_patch.php if you haven't already open the patch tool and direct it to the fs9.exe file and see what happens, if you already started the install do it anyways to the fresh install .EXE file

 

Thanks for the link. I tried it but it didn't change the situation. I had already applied the 3GB patch to the boot.ini and patched FS9.exe to access additional memory. I'll try again on the new install. Pretty sure at this point that my problem is NOT memory related.

 

Glenn

Pretty sure at this point that my problem is NOT memory related.

 

That seems definite now. Have you considered the possibility of a virus of some sort?

That seems definite now. Have you considered the possibility of a virus of some sort?

 

Yes. Ran FULL virus scan and Spybot search when this first happened. That was my first suspicion. Thanks for the reply though.

 

Glenn

Hi Glenn,

 

Have you considered that the FS9.exe may possibly been corrupted / damaged during a image construction or some other file transfer process? I have in the past had to do a complete OS (XP) reinstall because of a 'lost' OS file during a disk defrag. On another occasion after a program transfer from disk to disk (no registry entry needed) it simply would not run. After a new download of said utility it would run any and everywhere I put it.

 

Mel

B) Good luck im sure things will start looking up for you,

There's a member over in the CTD Forum who has a possible solution for OOM's and is looking for beta testers. So far it has worked for many. Although I see it's only for FSX right now, it appears he will take your api.dll and modify it to eliminate OOM's. Here's the link: http://forum.avsim.net/topic/389704-fsx-oom-apidll-patcher/.

 

Best regards,

Jim

I came across this post by Oliver Pabst:

http://forum.aerosoft.com/index.php?/topic/19147-ooms-ctds-and-maybe-more/

which might conceivably cast some light on your present problem.

B) Good luck im sure things will start looking up for you,

 

Hey thanks, I really appreciate the encouragement. Thanks to the others who have commented since I last posted - but it's not your typical OOM error. This one prevents FS9 from starting correctly,.

 

I just finished copying all of my FS9 folder and associated files to an external USB drive. I"m going to copy the same information over to an internal drive tonight just to be on the safe side, so I should be able to recover files some way for sure. I'll probably start the deletion and reinstall of FS9 tomorrow.

 

Thanks again. I'll let everyone know in this post how things turn out with a fresh install.

 

Glenn