I just tried to start FS2004, but am getting an error message "Your computer has run out of memory." Ok, it hasn't run out of memory... That said, I called Microsoft and was informed that they do NOT provide technical support for FS2004 anymore, only for FSX. This is frustrating, because I've have invested untold hours and thounsands of dollars in creating my FS2004 environment. Does anybody know of FS2004 support that is available by phone? I've spent the last 6 months rebuilding my FS2004 and don't want to go throw it all away by reinstalling just yet!

Hi,What are your system specs?

I guarantee you'll get better support right here than you would have got from Microsoft, even if they WERE still providing support for FS9.I'm going to guess you have a 32-bit operating system, right?Cheers, SLuggy

I just tried to start FS2004, but am getting an error message "Your computer has run out of memory." Ok, it hasn't run out of memory... That said, I called Microsoft and was informed that they do NOT provide technical support for FS2004 anymore, only for FSX. This is frustrating, because I've have invested untold hours and thounsands of dollars in creating my FS2004 environment. Does anybody know of FS2004 support that is available by phone? I've spent the last 6 months rebuilding my FS2004 and don't want to go throw it all away by reinstalling just yet!

Your "Out of Memory" issue is undoubtedly caused by quantities of add-ons so it isn't difficult to guess what the official answer from Microsoft would be if they did give you one.But it is usually resolvable, search this or other forums for "Out of memory" or "OOM" and you will find you are not alone.John

Thanks guys for the responses.For reference, I am running FS2004 with the following specs:Dell, Studio XPS 435TIntel Core i7 CPU 975 @3.33 GHzInstalled memory RAM - 3.00GBWindows 7, 64-bit op system753GB free out of 1TB harddrive (so I don't think it is "free space on the hard drive issue")I have reinitialized my paging file, so I don't think it is a RAM issue, either.I have 900 addon scenery entries currently (that only accounts for Europe, Middle East, Russia and North Africa!), but I had over 1400 entries before my hard drive crash last year, so I'd be surprised if that's it.

Thanks guys for the responses.For reference, I am running FS2004 with the following specs:Dell, Studio XPS 435TIntel Core i7 CPU 975 @3.33 GHzInstalled memory RAM - 3.00GBWindows 7, 64-bit op system753GB free out of 1TB harddrive (so I don't think it is "free space on the hard drive issue")I have reinitialized my paging file, so I don't think it is a RAM issue, either.I have 900 addon scenery entries currently (that only accounts for Europe, Middle East, Russia and North Africa!), but I had over 1400 entries before my hard drive crash last year, so I'd be surprised if that's it.

You need to patch FS9 to use more than 2GB of memory - running Win7 x64 you should have no OOM problems. Use the web to find a file called '4GB_Patch.zip' and download it. Inside the zip is '4GB_Patch.exe'. Back up your FS9.exe file and run the 4GB... program and point it at FS9.exe to patch it to be 'LargeAddressAware'. That's all it takes. Your OOM problem should go away. You aren't really running out of memory as you think of it, but that's a long story that has been told too many times on this forum.DJ

Thanks DJ. I downloaded and executed the 4GB patch; but, I still get the same error now on start up. To be clear, I've been running FS2004 on this system since February with no problems, then all of a sudden this started. Still frustrated. If you, or anyone else, has a suggestion; I'd be greatly indebted.

I would start with disabling the last 25 or so sceneries that you've added and then bringing them back one by one. Make sure you don't have any empty texture folders. If you start up with other add-ons (ASV, ASE, RC4, whatever...) running, try starting without them and seeing if the error occurs. Have you added aircraft lately? Did the problem start after? You might also check the scenery.cfg file for any corruption, and/or rebuild the FS9.cfg file... I actually had the same sort of error at one time, for unknown reasons, that went away after a while.DJ

DJ -- Thanks for the suggestions. I have tried taking the scenery.cfg file back down to the original w/o any add ons; but no luck. The error occurs as FS is "generating" the new scenery indexes.How do I "rebuild" the FS9.cfg file?

I guarantee you'll get better support right here than you would have got from Microsoft, even if they WERE still providing support for FS9.I'm going to guess you have a 32-bit operating system, right?Cheers, SLuggy

No a 64-bit system.

DJ -- Thanks for the suggestions. I have tried taking the scenery.cfg file back down to the original w/o any add ons; but no luck. The error occurs as FS is "generating" the new scenery indexes.How do I "rebuild" the FS9.cfg file?No a 64-bit system.

You can rebuild the FS9.cfg file by renaming it to something like FS9.orig and starting FS (assuming that it will start). The program will generate a new one - you will have to set up the graphics section for your card and the resolution that you like and reset any special joystick/keyboard settings that you've made. You'll find the file in 'Your login name'\AppData\Roaming\Microsoft\FS9... Also, make sure that you have UAC turned off, and are running as 'administrator'.I run FS9 on Win7 x64 just like you do, with the patched executable, and haven't seen the error you're having - the last time I encountered it was on XP Pro x32. Something has happened in the configuration of FS or your computer to cause it. Think very hard about the last thing you may have done before it started happening... I know that sounds obvious, but it may help you in tracking down the problem. Also make sure you have all Win7 patches installed. Wish I had a magic answer!DJ

You can rebuild the FS9.cfg file by renaming it to something like FS9.orig and starting FS (assuming that it will start). The program will generate a new one - you will have to set up the graphics section for your card and the resolution that you like and reset any special joystick/keyboard settings that you've made. You'll find the file in 'Your login name'\AppData\Roaming\Microsoft\FS9... Also, make sure that you have UAC turned off, and are running as 'administrator'.I run FS9 on Win7 x64 just like you do, with the patched executable, and haven't seen the error you're having - the last time I encountered it was on XP Pro x32. Something has happened in the configuration of FS or your computer to cause it. Think very hard about the last thing you may have done before it started happening... I know that sounds obvious, but it may help you in tracking down the problem. Also make sure you have all Win7 patches installed. Wish I had a magic answer!DJ

Thanks again DJ...tried rebuilding the FS9.cfg file, but to no avail. The last thing I did before the problem was using Ultimate Traffic to add additional airlines and install new freeware. Tried uninstalling, but that didn't work either. Maybe a computer thing. Oh well, guess I'll have to reinstall FS2004...pain in the a**!

Thanks again DJ...tried rebuilding the FS9.cfg file, but to no avail. The last thing I did before the problem was using Ultimate Traffic to add additional airlines and install new freeware. Tried uninstalling, but that didn't work either. Maybe a computer thing. Oh well, guess I'll have to reinstall FS2004...pain in the a**!

Just a couple of suggestions: try going into to the scenery/world/scenery directory and rename the traffic bgl(s) to xxx extensions and see if the error goes away; should that fail then if you do reinstall FS, do reinstall it outside of the 'program files' directory...DJ

Just a couple of suggestions: try going into to the scenery/world/scenery directory and rename the traffic bgl(s) to xxx extensions and see if the error goes away; should that fail then if you do reinstall FS, do reinstall it outside of the 'program files' directory...DJ

When you say "outside of the program files" directory, do you mean something like --c:\FS2004 , rather than c:\program files\microsoft games\FS2004 ?

When you say "outside of the program files" directory, do you mean something like --c:\FS2004 , rather than c:\program files\microsoft games\FS2004 ?

Correct - Win7 has some odd ideas about permissions even when you're running as administrator. Avoiding the 'program files' or 'program files (x86)' directories makes life simple.DJ

I guess it is because of the way I set up Windows so I am always the administrator (besides being the only one to use my PCs), I never seem to have the problems others report on installing games or add-ons into the Program Files or Program Files (x86) folders. It may be due to the fact that I have disabled the UAC, but I can't say for sure. More often than not, I do not install most programs into the C: folder anyway (I do have a Program Files and Program Files (x86) folders on my D: drive). I guess part of the reason why I rarely have any problems is that I try not to install much onto the C: drive outside of Windows and that is a good idea for everyone.