From: Spokane WA USA
Actually, waaay back when, WinAmp and SPWAW seemed to dislike each other more. Now, it's running fine - 2 gig of RAM does help, as does the Athlon64 3000+ (1.8 gHz). Throw enough resources at it, and even SPWAW will just happily sit bloating itself on the goodies. <heheheh>
Just checking now - with Supercharge (scen. ##... uhm, I forget <G>) running the preliminary bombardment, mech.exe is leeching 70-80% of the CPU, but it's not causing anything to delay or lag. (Only 17.688 meg of RAM, versus Firefox (8-14% CPU, 69.6 meg) or Winamp (2-8% CPU, 14 meg or so). It's also playing nice and giving back CPU when other programs want it. (Other tasks running: AVG antivirus, Trillian (instant messenger), Daemontools (virtual CD/DVD drives), VolumeLogic plugin for Winamp (on-the-fly automatic gain control), and a few other things. Like Task Manager. <G> 100% CPU in use, but only 569 meg or RAM.)
I suppose I could always try one of the (ancient) laptops, but the one with functioning WiFi needs some soldering on the power-plug connector. (Toshiba Satellite series - the $20 one is a Celeron 350, the free one is Celeron 400. Both have some horribly small amount of max RAM, and like unto 16 meg (or was that K?) of video RAM. Either way, WinSP:MBT was pretty sluggish.
Anyway, the only real problem now (for me, at least) is that bloody "Y" key. ("Y key, why? Y you so mean to me?") For which I'm not willing to roll drivers back and forth - guess I'll just have to be careful.
Back to Supercharge... I think I've played this before, but I don't remember for sure. I know all those little tin-plated tanks are gonna get eaten pretty badly...
Combat Mission HQ (http://www.combatmission.com/)
G-o-D's Close Combat Links (http://home.wanadoo.nl/cclinks/)