For no apparent reason, FS2004 suddenly refuses to load. When I start FS2004, it gets as far as "Loading scenery objects", whereupon it hangs, never loading more than 0% of the scenery objects. When I ALT+TAB out of FS2004, there is a Windows error message that says:Your computer has run out of available 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.I'm sure it's not a hard disk capacity issue--I've got 4 logical drives and none has less than 14 gigabytes of free space. I'm assuming it must be something else.I've perused similar posts here on this forum, but so far none of the advice has helped me. FS2004 worked just fine yesterday, and I haven't made any changes since then. Here's what I've tried thus far:- Restored my XP system to yesterday's configuration- Doubled my memory page file from 1 GB to 2 GB- Removed most recently installed BGLs (even though FS2004 worked fine with them before)Can anybody help?Thanks.-- WaltFlying FS2004 at 1600x1200x32Intel Pentium 4, 2.0 GHzWindows XP Pro512MB PC800 RDRAM,8100128MB ATI Radeon 9600 ProCATALYST Windows XP 3.10 video driverDirectX 9.0bViewSonic P95f+ 19 inch Ultrabrite CRT MonitorSound Blaster Audigy2 ZSCreative I-Trigue 2.1 3300 SpeakersMS ForceFeedback 2 joystick

Hi,what scenery did you install before that message came up the first time?___________________________Best Regards,Bodo M

As already stated, this is likely caused by a scenery addition...I've posted this test several times in the forum, although I never seem to get a response back either positive or negative.... I'll make the post one last time...Right after you get this error, do a "Search" for the file "scenery.dat" on the FS9 folder and all of its subfolders. Sort them by date. The most recent scenery.dat should be the one FS9 was attempting to build when the out of memory message was triggered and the date should match within a moment or two of your attempted FS9 startup.This scenery.dat will reside in the folder containing the possible "bad" bgl--and you'll be able to take it out of your scenery.cfg... As a hedge, I also move the folder to a temp location outside of the FS9 folder system.This is ONE possible solution to ONE possible problem. It has worked for me every time I've seen this error at FS9 startup when building the scenery database.Please let me know if this works... I'd like someone to respond when I offer this suggestion :)-John

Hi John,>>>"Search" for the file "scenery.dat" on the FS9 folder<<

It's possible that some bgls reside in marginal sectors of your disc, causing the problem at random. This is especially true if the most recent scenery.dat always seems to be in this folder.What I would do--go to your FS9 CD's, and restore all the default bgls in the sceneryworldscenery folder (back it up somewhere first), but remove any addon bgles from there (best way to do this is to dump the contents of the folder prior to restoring it and AFTER making a backup). Your flightplans might not be the bgls causing the issue--could be something else.I wish I could recall which CD contained the bgls in this folder, but it escapes me. However it should just take a few moments to search.-John

Thank you for the suggestion John, however I think I just fixed the problem!!The culprit wasn't a miscreant BGL, rather the problem appears to be a LAGO FSE file (*.SE2) I created yesterday using LAGO's FSE editor. Simply removing this file from the LAGO scenery folder has cured FS2004's hangup.Oddly, the mere presence of this SE2 file appears to have caused problems, as I unsuccessfully tried starting FS2004 with other situations that were nowhere near the location of this particular SE2.Thanks everyone for your help (fingers crossed).-- Walt

Interesting--hopefully your followup may help others with this issue. I know Brian Gladden recenrly ran into it...-John

I thought I knew the answer to this memory problem.....but I forgot it! :D :D ;-)

hehe.I noticed in the readme of the latest FS connect module that this release fixes a memory leak - any chance you've got the old version of FSConnect in your modules folder?Just a thought...as I recall...wait...maybe not. Dad, is that you?

I don't have FS Connect, but I've got WideServer.dll, dated 10/29/2003.-- Walt