[TEC] SH3+GWX 2.0 with 3GB RAM

The Butcher · 03-11-08, 09:28 PM

32bit XP should recognize a little over 3 gig. Aplications wont be able to access anything over that but the operating system and drivers can.

More is better!

Graf Paper · 03-11-08, 11:20 PM

Keep in mind my box is an older system. The mobo was purchased new in 2002. It has three 184-pin DIMM slots and each slot can use 64MB-1GB of DDR RAM at 133/266/333 MHz. Support for DDR 400 is two slots only with a max of 2GB RAM.

At the time, this was a very top-of-the-line mobo for single CPU setups with more features built into it than Darth Vader's bathroom. It's certainly proven its staying power over the years and runs almost any software you can throw at it, except for the new games that have been hitting shelves in the last year or so. Then again, SH3 was the last new PC game I purchased as it seems after that there were just the usual clones and sequels for the FPS, RTS, and MMORPG genres.

Maybe I'm just getting jaded after playing 30 years worth of video games, beginning with Pong. I still miss my Commodore-64 sometimes. But I digress...

Funny thing is the BIOS auto-detect saw the RAM as DDR 400 until I configured it in the BIOS as the DDR 333 that it is supposed to be.

With the full 3GB installed it seems to pass the memtest portion okay, but then things get a bit odd. The POST appears to progress normally, but the BIOS begins issuing error beeps and the LED indicator panel shows a general fault code (or else it's locked up because all the indicators are lit steady red.)

Right as it gets to the point where my WinXP Pro should boot, the system locks up and these three artifacts show up at the top of the screen. They're always the same three "garbage" characters, the one that stands out in my mind is a black @ symbol in a red block.

After playing through a patrol last night, I can further clarify my initial assessment. The fact that there is no lag in the harbor is a real treat for me. For once I can enjoy the experience of being on the bridge as we set sail, instead of hiding at the Nav Map, as the crowd at the quay proudly cheers us on (and that damnable band keeps playing their song...over and over and OVER).

There is only one thing that causes severe lag now, when a ship explodes after I've hit it with an eel. I mean really explode, like 'KABOOM!' from a critical hit, not the usual 'BLAMMO!' from a torp impact. I think that may be more my fault for cranking up the AA and AF a couple of notches.

Overall, having upgraded my RAM has resulted in a much richer and far smoother experience with SH3+GWX2.

03-11-08, 11:20 PM	#2
Graf Paper Ace of the Deep Join Date: Jan 2008 Location: Pacific Northwest United States Posts: 1,146 Downloads: 41 Uploads: 2	Keep in mind my box is an older system. The mobo was purchased new in 2002. It has three 184-pin DIMM slots and each slot can use 64MB-1GB of DDR RAM at 133/266/333 MHz. Support for DDR 400 is two slots only with a max of 2GB RAM. At the time, this was a very top-of-the-line mobo for single CPU setups with more features built into it than Darth Vader's bathroom. It's certainly proven its staying power over the years and runs almost any software you can throw at it, except for the new games that have been hitting shelves in the last year or so. Then again, SH3 was the last new PC game I purchased as it seems after that there were just the usual clones and sequels for the FPS, RTS, and MMORPG genres. Maybe I'm just getting jaded after playing 30 years worth of video games, beginning with Pong. I still miss my Commodore-64 sometimes. But I digress... Funny thing is the BIOS auto-detect saw the RAM as DDR 400 until I configured it in the BIOS as the DDR 333 that it is supposed to be. With the full 3GB installed it seems to pass the memtest portion okay, but then things get a bit odd. The POST appears to progress normally, but the BIOS begins issuing error beeps and the LED indicator panel shows a general fault code (or else it's locked up because all the indicators are lit steady red.) Right as it gets to the point where my WinXP Pro should boot, the system locks up and these three artifacts show up at the top of the screen. They're always the same three "garbage" characters, the one that stands out in my mind is a black @ symbol in a red block. After playing through a patrol last night, I can further clarify my initial assessment. The fact that there is no lag in the harbor is a real treat for me. For once I can enjoy the experience of being on the bridge as we set sail, instead of hiding at the Nav Map, as the crowd at the quay proudly cheers us on (and that damnable band keeps playing their song...over and over and OVER). There is only one thing that causes severe lag now, when a ship explodes after I've hit it with an eel. I mean really explode, like 'KABOOM!' from a critical hit, not the usual 'BLAMMO!' from a torp impact. I think that may be more my fault for cranking up the AA and AF a couple of notches. Overall, having upgraded my RAM has resulted in a much richer and far smoother experience with SH3+GWX2. __________________ Still sailing the high seas, hunting convoys with those who join me.

03-11-08, 09:28 PM	#1
The Butcher Loader Join Date: Nov 2007 Location: U.S.A. Posts: 85 Downloads: 40 Uploads: 0	32bit XP should recognize a little over 3 gig. Aplications wont be able to access anything over that but the operating system and drivers can. More is better!