For a clean install oF FSX Deluxe and Acceleration simply install FSX from the DVD, run it, register it, and close it. Next instal Acceleration from the DVD, run FSX and regiter Acceleration. Forget about service packs at that stage.

 

If you then wnat to instal the SDK then insert the Acceleration DVD and open the SDK folder. Open the folder SP1a and run fsx_sdk_sp1a.exe. After that go back to the SDK folder and run sdk.msi.

 

Just follow the on-screen instructions.

For a clean install oF FSX Deluxe and Acceleration simply install FSX from the DVD, run it, register it, and close it. Next instal Acceleration from the DVD, run FSX and regiter Acceleration. Forget about service packs at that stage.

 

If you then wnat to instal the SDK then insert the Acceleration DVD and open the SDK folder. Open the folder SP1a and run fsx_sdk_sp1a.exe. After that go back to the SDK folder and run sdk.msi.

 

Just follow the on-screen instructions.

 

Wrong Wrong Wrong..... If you have FSX accelleration DVD that's all you have to install. From there you can install ths SDK from the accelleration disk if you're planning on using simconnect. However I found using the older SDK version of simconnect over network cause less issues with AS2012, RC4, FSrealtime and the older 530 garmin. Your choice. Also set windows to manage your page files if you are running 7x64. Setting up page files sizes and locations was fine for win95 and 98. It's no longer neccsary for newer OS systems. If anyone tell you different it'sa myth.

Are you really saying that Acceleration can be installed without FSX being installed?

Setting up page files sizes and locations was fine for win95 and 98. It's no longer neccsary for newer OS systems. If anyone tell you different it'sa myth.

Sorry, Bill, try telling that to the guys that suffer from performance issues and OOM's caused by dis-contiguous swap space that's spread all over the C-drive. Any professional IT tech or paid pc tech that is a serious FSX 'simmer' will tell you to keep the page file off the C-Drive, "fix" it at around three gig (doesn't need more) and it won't become corrupt, and it won't interfere with the OS's disk I/O. Nuff said.

 

Hi, Manny. The Task Manager will give you a good indication of what's happening, memory-wise. The lower-left part has a Resource Monitor, which will give you an idea of how your 8 gig is parceled out when FSX (at KSEA), with NGX - AS2012 - OrbX - RC4 all running - if you run Google Earth, your Internet Browser and iTunes on top of that - you should find that your memory usage is going to move the "In use" green bar to something higher than 4 gig - I've had mine as high as 4.7 gig. This is well into the potential OOM area. Another tool - a better tool, as it records a slew of whatever data you want it to - is Performance Monitor". Go to "Start" --> type in the search window that appears immediately above it - "perfmon" - without the quotes. This will launch the Performance Monitor. Highlight "Performance Monitor" in its left window. In the right window - click on the green "Plus" icon. A new window will open, go into it and browse down to find "Paging File". You should see two instances: one for the 50 or (100) MB on the C-drive, and one for the 3 gig file on your D-drive. Highlight both, and click "Add", and "OK". Move up to the memory option, click the "+", and highlight Commit Limit and Committed Bytes, adding these into the mix. If you look in that same "Memory" menu there's almost 40 other parameters to monitor your memory. I can't give you a course in memory management, but on an 8-gig machine you should probably never use swap space, and if you can use these tools, you will come to a similar conclusion. Bill is somewhat right when he says it's no longer necessary for newer OS systems - but those words com from folks that don't use the flight sim, like we do. There's one one or two other applications that use (abuse?) a pc like FSX and it's bedmates do, and that's the various breeds of AutoCad. I'm sure there are others, but it doesn't matter. Your issue now, is that you're getting OOM's, and there's only a couple of causes. Creating the two swap files, rebooting as you do create each one, should have fixed the issue, period. So - now I would download the purchased version of Memtest Pro - the 64-bit version, put it on a USB memory stick, and do a test on your physical memory before the machine boots.

 

Hope this help a bit more,

 

Cheers,

Performance Monitor"

 

Whelp! I did exactly that...but its too complex for me. Here re the screenshits..4 of em

 

1) before loading FSX.

 

 

2) Started FSX..but not selected any flight

 

 

3) Flying around FSDT ORD and Fly Tampa Midway..and I start hearing the Win 7 dings.. meaning its going to fail.

 

 

4) And then I move to downtown..Aerosoft city OOM!

 

The line that shows the %age of my page file is at the bottom..which means, its not running out of page file space...right? The c:Page file is only 50 so that is on top..almost 100%..but the F: Drive..its right at the bottom..somehwere like 10% usage.

What's the actual message, Manny?

Is FSX large address aware, or do we need to set it up for that?

Message is a pop up

 

"Your computer has run out of available memory. Please restart flight simulator and select different graphic scenery or traffic settings".

 

 

And this time I had deslected Aerosoft's city (Chicago)..but it took a tad longer than with that city scenery...but it eventually happened.

 

What's the actual message, Manny?

 

BTW.. What is the difference between standby and Free? ITs when I run out of "Free" that I get that OOM message.

Also committed Limit and commmited

bytes = 100% on that performance monitor... And its always 100% even if I get out of FSX..like I got out of FSX with that OOM..and its still at 100% commit

OK.. Try moving - increasing - the swap on C: back up to 3 gig, and deleting the swap on F: This should not make any difference, but I'll eat my shorts if it works!

 

"Standby" and "free" are Windows terms. Also I think the Commit Limit is the max physical memory plus the page file, and committed bytes, under Windows is always at max whatever it should be.

 

http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx

Sorry, Bill, try telling that to the guys that suffer from performance issues and OOM's caused by dis-contiguous swap space that's spread all over the C-drive. Any professional IT tech or paid pc tech that is a serious FSX 'simmer' will tell you to keep the page file off the C-Drive, "fix" it at around three gig (doesn't need more) and it won't become corrupt, and it won't interfere with the OS's disk I/O. Nuff said.

 

Not sure what tech guys you're talking to but you're being mis informed. I've allowed windows to manage my page file since XP and never had ant corrupt or dis-contigious swap space. OOM's are not cause my page file or physical memory size. It's the allocated space allowed by the OS artchetecture. That's why using a 32 bit OS we used the 3gig switch to combat OOM's. Where it would basically rob peter to pay paul. Or it would take away allocated space for video and add to system memery. To help eliminate OOM's. In a 32 bit OS once allocated memeroy space exceeded One gig, OOM would occured no mater how much physical memory or page file size you set. x64 bit systems allow greater than one gig memory along with the the FSX sp1 exe or FSX accel exe, you should have no OOM's.

Message is a pop up

 

"Your computer has run out of available memory. Please restart flight simulator and select different graphic scenery or traffic settings".

 

Gah!!! So much confusion and angst could have been prevented had those silly programmers simply provided a non-misleading error message! It should have stated:

 

"Your computer has run out of available virtual address space. Please restart... etc."

 

Virtual Address Space does not equal Physical Memory

OOM's are not cause my page file or physical memory size.

In a 32 bit OS once allocated memeroy space exceeded One gig, OOM would occured no mater how much physical memory or page file size you set.

x64 bit systems allow greater than one gig memory along with the the FSX sp1 exe or FSX accel exe, you should have no OOM's.

 

I'm just going to let those words stand, Bill, and not argue, but merely point you to Mark Russinovitch's blog here:-

 

http://blogs.technet.com/b/markrussinovich/archive/2008/07/21/3092070.aspx

Try moving - increasing - the swap on C: back up to 3 gig, and deleting the swap on F: This should not make any difference, but I'll eat my shorts if it works!

 

Interested in Manny's response... particularly if it makes a difference. :Big Grin: (just joking Paul... greatly appreciate the info you posted in this thread).

 

Is FSX large address aware, or do we need to set it up for that?

 

Look here: http://www.flightsim.com/vbfs/showthread.php?236654-FSX-Large-Address-Aware and here: http://www.flightsim.com/vbfs/showwiki.php?title=OOM-Error

 

Btw... wondering if the mod "Loki" is the same Loki from MS Flight...

 

-Rob

Interested in Manny's response... particularly if it makes a difference. (just joking Paul..

:LMAO: :LMAO: :LMAO:

 

You and me, too, Rob..!

_________________________________________________________________________________________________

 

...and just to add another resource for Manny, dealing with cleaning up the paging file, and also creating a new one, though system-managed.

 

http://support.microsoft.com/kb/892610