Hi!I just reinstalled my FS9, because I had some problems with it.I use separate partitions for my XP, backups, FS9, etc., so myFS9 is on a separate partition, which always works fine.I have 2 HDD's.But now, with no changes made to my FS9 setup, I sometimes geta "your computer does nor have enough memory" message.Very strange. I removed unnecessary programs and "unstarted"some for the XP startup.Still, the problem sometimes recurs.Any idea how this can be resolved?Grateful for any help.Thanks.Hans HermanssonSweden

I would check your virtual memory settings and make sure it's set to "System Managed Size". You could also have bad memory modules. To check your virtual memory settings right click My Computer on your desktop, select Properties, click on the Advanced Tab, Click on Settings under Performance, click on the Advanced Tab and select Virtual Memory. If it's already set at System Managed size then it is more likely a problem with the memory modules themselves. Hope this helps.Best regards,JimYoung

Hello!and thanks for your advice.I will certainly try that.Hans HermanssonSweden

Hi Hans,Do you get those messages after FS9 has been running for a long time? I recently checked FS9 for memory loss and found that on my system it does lose memory over a period of time especially if you close it out and then start it up again.

Hello!I get the problem occasionally; not in specific situations,but I think it has to do with what other programs/applications I runin between; they are probably the culprits.Thanks for your concern.Live well!/Hans

Hi again!I changed my settings to "system managed size"I also noticed that the memory use is set for "programs"where "system cache" could be used instead.Which one would you suggest?Grateful for more tips......Hansinsweden

Oddly enough, this message rarely has anything to do with the machine in question actually being out of memory. I suspect that it may have to do with other programs rather than with FS9. Do you run ASV6 or other programs based on the .NET platform? I have seen the message appear on a random basis when I've brought up ASV6, let it initialize, and then attempted to bring up FS9. A second attempt works just fine... I have no idea (well, I have ideas but they're really just guesses) what is going on but there is plenty of available memory in the system. I'm a developer by trade, and have seen this message occur as I debug new code and in no case has it actually been memory related.DJ

>Hi again!>>I changed my settings to "system managed size">>I also noticed that the memory use is set for "programs">where "system cache" could be used instead.>>Which one would you suggest?>>Grateful for more tips......>>HansinswedenDo not set memory use to "System Cache" That setting is meant for servers. While it may increase performance, since you would be cacheing system data, you risk losing data should you lose power or your system abnormally fails. Possibly to the point that you may not be able to boot. Do not try this, unless you have backups and are prepared for system restoration.

DJ,I think you are the first person who might actually get this. Neither Physical memory, nor virtual memory nor pagefiles have anything to do with this. XP is talking about memory space in my opinion, not memory amount. I too am an ex coder, then an ex-engineer. I know enough to get myself into trouble. Personally, I think that the people who are getting this message should open up their Event Viewers. I think it is a User Profile issue tied to Registry writes opposed to FS. Chances are something like svchost.exe is trying to write to registry, unable to unload the process and never fress the memory space. I bet in Event Viewer there will be messages referencing exactly this.I have been troubleshooting OOM's for over a year trying to get to the bottom of them. I have explored:Physical MemoryVirtual memory PageFile WritesLandClass filesAdd-onsNavDatadisabling app security and checking for FS within XP/3 gig toggle in boot.inibasically, IF you could have tried it I did. Then all of a sudden you get things working and a month or so later, the same flight that has worked for 30 days decides to quit with an OOM. So either, a texture has been corrupt, you can replace your entire scenery/world/texture directory with a Vanilla. Your pagefile has become corrupt OR there is something else...If you go to Event Viewr you see errors saying that a certain memory space could not be freed. There is an app on the MS site, you have to go through the validation process but it is called UPHCLEAN. I am including a fair use excerpt from the UPH read-me. Remember, this is an MS issued product, not third party so it is obviously a known issue. I am guessing it is tying back into FS possibly with an add-on like you said, While it is geared to log out's, look at how it specifically handles XP... I think the flaw is in XP and this program exposes it. Since installing it all of my registry errors in event viewer have dissapeared and I am still trying to repro an OOM. Just food for thought...Fair use excerpt:"UPHClean v1.6d readme.txtUpdated April 27, 2005 by Robin CaronSend all feedback/comments/problems to [email protected] WHAT IS UPHCLEAN================UPHClean is a service that once and for all gets rid of problems with userprofile not unloading.You are having profile unload problems if you experience slow logoff (withSaving Settings for most of the time while logging off), roaming profilesthat do not reconcile, or the registry size limit is reached.WHY DO PROFILES NOT UNLOAD?===========================Many system and service processes do work on behalf of users. When the work is done the system or service process is responsible for releasing handles it has to the user profile hive. If this is not done by the service as the user logs off the profile cannot be unloaded.This problem in code can be caused by improper coding either in Microsoft software or 3rd party software (e.g. printer drivers, virus scanner service, etc). With the information provided by the system there is no way to find out what software needs to be corrected to allow profiles to unload.This problem can be caused for a variety of reasons. While software developers are typically very careful about releasing handles, developing software that works on behalf of a logged on user is complicated. It is difficult for software developer to have full control over how the registry is accessed. Service developers might want to see KB article 199190 for more information. While it is possible to identify the service (see KB article 221833), it is sometimes difficult to track this down the specific problem code. Even when you do identify the problem code there maybe times when the developer of this code is not able to make the necessary changes. This is the reason for UPHClean -- it takes care of the problem regardless of the reason why.WHAT DOES THE USER SEE? WHAT HAPPENS TO THE PROFILE?=====================================================Windows 2000:The system attempts to unload the profile 60 times at 1 second intervals. This retry logic rarely helps so in most cases after 60 seconds of the user waiting at the Saving Settings message box the system gives up and roaming profiles are not reconciled. The number of retries can be changed to allow the user to log off faster (this can be done using the policy under Computer Configuration, Administrative Template, System, User Profiles, Maximum retriesto unload and update user profile)Windows XP and 2003:The profile is reconciled using a copy of the contents of the registry. The user is not made to wait as in Windows 2000. The problem left is that the computer cannot recover the memory the profile uses until it can be unloaded. Also in some cases (e.g. using anonymous logons) you may find that you cannot log on if the profile cannot be unloaded.WHY SHOULD I USE UPHCLEAN?==========================The concept of UPHClean is to deal with these the same way the operating system deals with other resource issues: when a task is done resources (memory, handles, etc) are automatically reclaimed. UPHClean accomplishes this simply by monitoring for users to log off and verifying that unused resources are reclaimed. If they are not it reclaims the resource and logs its action. This approach is superior as it works for any known reason that profiles do not unload and also will keep working to address new unknown issues.Another advantage to UPHClean is that no computer restart is required to install it or remove it (except on Windows NT 4). You can install and remove UPHClean to find out whether it helps with a profile unload problem or not. You can do this without having to worry about what hotfix, service pack, feature pack, etc has been installed. Set it and forget is the goal of UPHClean.