Problems building new rig-

[mtnman]

I have the OS installed, updated, etc, seems to be working real well.  I still need to do the thing with getting the memory to sync up with the MB.  Gonna do that now.

I have the HD partitioned into a "normal" C-drive, and an "Aces High" D-drive, where they boot up different, so I can still run the game without all the extra processes turned on.  Took me a while to figure out/remember how to do that...

Also haven't D-loaded the game yet, or migrated info from my old computer yet.  Can't wait to try the game without needing to run it with everything down to minimum!

The make-it or break-it problem was the PWR SW wire, which was opposite of what I thought it was.  When I turned it around, everything turned on, even with the memory in the wrong slots.

[cattb]

 glad to hear 
Cattb/Tim O

[mtnman]

I'm not so sure I have the memory settings figured out.  It looks like I have 2x2Gb sticks, but only about 3.25Gb available when I look in my system information, or when I run Belarc Advisor.

I went to the GSkill forums, found the thread dealing with my board, and made the settings changes, with no effect that I can see...

On the "game level", I managed to get loaded up and into the TA for a little bit last night.  High Res pack, 1024 textures.  Very nice!  Oooooh! Aaaaah!  All the graphics settings maxed out, viewing distance maxed, all the shadows on, etc, with no stutters, no problems, great FR's (down to mid-50's on the deck, showing 75-plus at a few thousand feet (that may show higher than my monitor refreshes anyway?)  Haven't tried the MA yet, with smoke, etc.

Quite a difference from what I'm used to.  I've been flying on Shift-F2, detail almost all the way down, viewing distance of about 1 mile, 256 textures, with FR's around 35 on the deck, 55 at altitude.  I generally couldn't see GV's unless I was right on top of them...


Would posting a DXDIAG help any of you with my memory settings?

[AirFlyer]

Sounds like your just hitting the RAM limitations of a 32-bit operating system. The only real way to fix the problem is to use a 64-bit operating system.

[mtnman]

Sounds like your just hitting the RAM limitations of a 32-bit operating system. The only real way to fix the problem is to use a 64-bit operating system.

Ahh, ok.  I don't think it's going to cause me any issues right now.

[Dragon]

The make-it or break-it problem was the PWR SW wire, which was opposite of what I thought it was.  When I turned it around, everything turned on, even with the memory in the wrong slots.

LOL, that's almost as bad as the last comp I put together, I had it all assembled, plugged it in and hit the switch on the back of the power supply and......nothing .  After checking all the wires, making sure I turned the switch the right direction, checking wires again, plugged it back in, hit the switch and .... nothing .  After WTsquealing for about 20 min, my daughter comes into the room and says "don't you have to push the power button on the front of the computer to turn it on? "  After staring at her for a few seconds  and going over in my mind what I did, I had no choice but to say "Ummm, yep, I suppose that would help" 

[gyrene81]

LOL, that's almost as bad as the last comp I put together, I had it all assembled, plugged it in and hit the switch on the back of the power supply and......nothing .  After checking all the wires, making sure I turned the switch the right direction, checking wires again, plugged it back in, hit the switch and .... nothing .  After WTsquealing for about 20 min, my daughter comes into the room and says "don't you have to push the power button on the front of the computer to turn it on? "  After staring at her for a few seconds  and going over in my mind what I did, I had no choice but to say "Ummm, yep, I suppose that would help" 

ROFLMAO 

  Thank you for sharing that embarrassing moment...been there and I empathize.

[batch]

ROFL...... several times Ive spent half hour trying to figure out why a system wont power up until it finally dawns on me that I should flip the switch on the surge protector......

goes along with the many times Ive jump started my truck because I thought I had a dead battery....... only to find out I left it in drive when I turned off the engine lol

[Getback]

I'm not so sure I have the memory settings figured out.  It looks like I have 2x2Gb sticks, but only about 3.25Gb available when I look in my system information, or when I run Belarc Advisor.

I went to the GSkill forums, found the thread dealing with my board, and made the settings changes, with no effect that I can see...

On the "game level", I managed to get loaded up and into the TA for a little bit last night.  High Res pack, 1024 textures.  Very nice!  Oooooh! Aaaaah!  All the graphics settings maxed out, viewing distance maxed, all the shadows on, etc, with no stutters, no problems, great FR's (down to mid-50's on the deck, showing 75-plus at a few thousand feet (that may show higher than my monitor refreshes anyway?)  Haven't tried the MA yet, with smoke, etc.

Quite a difference from what I'm used to.  I've been flying on Shift-F2, detail almost all the way down, viewing distance of about 1 mile, 256 textures, with FR's around 35 on the deck, 55 at altitude.  I generally couldn't see GV's unless I was right on top of them...

Yep, that is what my 4 gigs show, just 3.25.
Would posting a DXDIAG help any of you with my memory settings?

[Masherbrum]

ROFL...... several times Ive spent half hour trying to figure out why a system wont power up until it finally dawns on me that I should flip the switch on the surge protector......

goes along with the many times Ive jump started my truck because I thought I had a dead battery....... only to find out I left it in drive when I turned off the engine lol

Nice!