Ken,I found out accidentally that if I start FS autostart it will tell me that something like 760 K are free after reorg. If I shut down FS9 and restart as soon FS autostart it will now tell me that 816 k are free. If again I shut down FS9 and start FS autostart again I will get another figure close to the 816 K.So should I systematically start FS autostart twice or is it the control figures that are not accurate ?Roger

The memory stats come directly from the operating system. Maybe running flight sim the first time causes the OS to do more memory reorganization since it is so large.I might take a look at my memory defrag and see if there is something I can do there in the next update.

I have made exactly the same observation. When starting FS9 the first time with FS Autostart, it tells me I have approx 380 MB (out of 512 MB) free memory available. This is the same, no matter If I have rebooted the system before or not.But when I start FS9 with FS Autostart a second time, right after I have closed the first FS9 session, then I have around 410 MB of memory available. This is the case, no matter, if I have startet FS9 the first time with or without FS Autostart.Wolfgang

Services that might have been paged out to virtual ram on the first FS9 start may not be returned to physical ram on the FS9 close. Therefore more physical ram may be available. Only when apps need the functions might they be paged back to physical ram even though enough space exists.I guess . . .

True...but the memory defrag should have done this job also.

I seem to remember someone mentioned at some point that Windows hates to have "wasted" memory. It will try to use up a certain amount of free RAM just by doing nothing. Prior to FS9 being loaded a portion of the system RAM may be doing this "nothing task". However after FS9 is loaded, all available memory is allocated to this. If you then quit FS9 and then load it up again, Windows hasn't had time to grab the RAM for doing nothing.Is my understanding of this correct or have I got the wrong end of the stick along the line?

A similar thing happens when using MemTurbo...If I click "Recover Ram" it recovers about 226M Then "Scrub Ram" it recovers more than 328 out of 512...