Hi.Windows VM management is rather more involved than it appears to be on the surface. The "Out of physical memory" error can crop up, under the 'right' conditions, even if you have plenty of memory still available.You should be able to run almost anything with 1Gb of real RAM without too many problems. HD space doesn't really come into it; as long as you have at least 2Gb free and Windows is configured to use it (as described above) any more is irrelevant.If one of you guys is willing to run a small program, I can email you something that will display exactly what and how much memory is being used by a certain program. Of course, in these virus-ridden days I'll understand if you're not willing but if you are, drop me an email and I'll send you the program and tell you how to use it. It won't *fix* the problem but it may shed a little more light.Regards,Jim Keir

Bob, There is nothing in the Eaglesoft CX that requires FSUIPC. If there were we would have stated so. We would appreciate an email question before you state what the CX requires.As we all know FSUIPC is a wonderful tool but it has it's own set of issues with the FS9 patch and as far as we know Pete has addressed those issues.We have done extensive testing with a trouble free installation of the FS9 patch using the CD in the drive and we have found absolutely no problems with memory leaks on ANY of our aircraft including the Citation X.Just got off the phone with a CX user about this issue and at the end of the conversation he stated that yes he has been getting bad cluster warnings about his hard drive and mistakenly thought his problems were related to the CX.Memory leaks are hard to track down because there are so many potential sources but we can say without hesitation that our tests have revealed NO problems with the FS9 patch with CD in the drive nor have ANY memory leaks reared their ugly heads:-)

Our email response to you was as follows......We have done extensive testing with a trouble free installation of the FS9 patch using the CD in the drive and we have found absolutely no problems with memory leaks on ANY of our aircraft including the Citation X.

Our email response to you was as follows....We have done extensive testing with a trouble free installation of the FS9 patch using the CD in the drive and we have found absolutely no problems with memory leaks on ANY of our aircraft including the Citation X.

Ron Hamilton wrote:>There is nothing in the Eaglesoft CX that requires FSUIPC. If>there were we would have stated so. We would appreciate an>email question before you state what the CX requires.OK, my mistake. Sorry. >We have done extensive testing with a trouble free>installation of the FS9 patch using the CD in the drive and we>have found absolutely no problems with memory leaks on ANY of>our aircraft including the Citation X.>>Just got off the phone with a CX user about this issue and at>the end of the conversation he stated that yes he has been>getting bad cluster warnings about his hard drive and>mistakenly thought his problems were related to the CX.>>Memory leaks are hard to track down because there are so many>potential sources but we can say without hesitation that our>tests have revealed NO problems with the FS9 patch with CD in>the drive nor have ANY memory leaks reared their ugly>heads:-)I really don't know if these leaks are due to the ESDG Citation X or not...those with the problems need to isolate them. But if memory leaks only occur on a single system when a particular panel is used, it's hard to draw any conclusion other than the panel has something to do with the leak.But...the PSS experience started with the same position by the company" "we tested it here and don't see it." Only after the hue and cry of disgruntled users reached a thundersous din was any action taken. Hopefully it won't take that level of public drumbeating if your users...even a small number of them...find that the Citation X is the common denominator in a memory leak issue.RegardsBob ScottATP IMEL Gulfstream II-III-IV-V L-300Washington,DC

No - there is no "rule of thumb" for a max setting. It would depend on how much HD space you have. Use your judgement, if everything works the way you want it with the settings you have - then stick with them.If you find the system is running low on memory (or not performing the way you want) increase the allotment until you find something that both you (and your HD space) can live with.Personally, I would go with min setting + 10% (just thought those numbers off the top of my head...). That way - just in case XP chokes - it will have a 10% padding. (So that would make your max approx. 1686 {which is a little over 1.1 GB of HD space})Hope that helps - let us know if you have any questions!

>Only after the hue and cry of disgruntled users reached a thundersous din was any action taken. Hopefully it won't take that level of public drumbeating if your users...even a small number of them...find that the Citation X is the common denominator in a memory leak issue.

Thanks Dan,I will go back in and set the page file at 1686 MB and try it. The window had a recommended size of 1533 MB. I wonder where that came from or how they arrived at that recommendation. Since I have the room on the HD I will set the maxium at least to 2 GB (2000 MB) plus based on what Jim Kien wrote earlier. I'm still not clear on how to interpret the page file MB usage that is shown on the task mananger performance window, ie is that the MBs that are being written to the page file on the hard drive in addition to the 1024 MB of RAM and the MBs on the video card? I think we should note that Eaglesoft said the testing of their products were done on nVida cards. I would have probably gotten an nVida card if DELL had offered the top of the line in that department, but they didn't.When I have had the "BONG" "Out of physical memory" it was with the Citation X using downloaded weather on a flight of over an hour. Twice before the patch and once after the FS9.1 patch. I don't recall it happening with any other airplane that I have. I have an ATI 9800 pro with 128 MB, Windows XP pro/SP2, P4 3.0, 1024 RAM, with about 70 gigs left on the HD.

Daryl,Did you ever get this problem figured out? I still get it but only going into intense third party scenery.

Eric,I haven't got it lately, so there was no reason to pursue it.

Just a note here...we recently tested the CX Deluxe Version using an ATI X800 pro 256 mb card with FS9 patched on XP home with no negative results at all:-)

After increasing my Page File allocation from the default custom setting of 1533 to 2533MB's, I don't have the problem anymore. I just hope its safe to do that with your computer.

Grrr! Me too! On PMDG approach into SimFlyers KDFW. VERY -annoying- and -disappointing-. 1gb ram.