smaggiotto
Posts: 6
Joined: 12/30/2001 From: Santa Ana, CA Status: offline
|
I still 'do' DOS so when it comes to tracking down hardware performance issues related to config stability and OS (Mac, Win, Unix) compatibility it's not easy for me to give up until I resolve a problem. I use my experience to help lots of folks but I'm in need of some myself. Indeed, I was prompted to contribute this post since I've just finished a multi-drive upgrade of my main workstation (*System 3) and did a complete fresh install of Win2k and all components. I'm running MCNA (Desert Fox, 1941) on three different machines without much success. I'll note those configs at the end. Of course, I went to the armorsite, installed all the updates to both MC's. I've tried the upgrade path with the MCNA ver. of SPWaW and did a separate install of MCLV upgraded fm 7 to 7.1 with patches. I tried pulling a copy of the MCNA dir fm that original installation over to the fresh install of the MCLV w/ upgrade & patches added beforehand, patching MCNA afterwards. These machines all run the main SpWaW & MCLV just fine. I have no adverse issues with the standard campaigns, scenarios, series, extra maps, dnld stuff, changed OOBs, etc. This CTD behavior only with 1941 happened with the first install of the original game 5.x version up to the latest, 7.1 ver. Of course, I've uninstalled and reinstalled fresh copies w/o any mods or xtras added. Clean installs of the game/OS have no effect in resolving the tendency for 1941 to CTD. I've tried the FAQ hints naturally, killing the *.prf file, turning down hardware accel, etc. Needless to say, all OS, mobo, video, sound drivers are up-to-date. No background processes running except needed OS services, nothing in SysTray either except volume control icon. No network/modem connection active. I only use AV software in manual mode, if at all. System 3 is an isolated 3D Graphics workstation running no AV software. I've seen no evidence of a memory leak present. This behavior spans DX6+ to 8.1 Sometimes I get an apparent video refresh failure where the game screen goes to black when switching between events (like when the AI is finished with its turn), usually mouse movement will refresh the area it passes over until the whole screen resolves back suddenly. Sometimes, selecting a unit and then clicking on a destination hex will cause a crash. I was able to play almost of all the first main battle (with no options) last nite for about 5 hours until it just dropped out to the desktop. I did a hard boot and opened the saved game to discover that I was back to the beginning of that first battle setup. Other times, I've played that train scenario option which crashed under various unrepeatable circumstances. It was almost like the game couldn't handle the mouse inputs via the interface or there were corrupt hexes but that didn't make sense. Sometimes just clicking on a unit generated a CTD. The farthest I've gotten along with 1941 is that road scenario where the Brits are trying to withdraw along the road, where the germans setup on the overlooking ridge line. This is totally opposite to my experience with Lost Victories, having played that through with mulitple players using the same machines. No one has been able to arrive at enough stablity to play more than 4 scenarios of the whole Desert Fox MC. I've had saved game files get corrupted during crashes so I've been manually back'n up the 3 game files so I can recover to a good set of files. The corrupted files will allow to show the intermediate cut screen without any options other than to back out to the main menu or initiate a 'kill' with Task Mgr. Is there a debugger I can run to catch any issues? I get no Dr. Watson logs/Win error msgs, etc. that I could use to initiate some kind of troubleshooting attempt. The only real similarity between these systems in their Sound Blaster cards. I have a Soundblaster AWE64 Gold under Win98SE, and the other two are running SB X-gamer (one is a Live version and the other is from the "platinum era") cards under Win2k and Win98Se respectively. I read some posts where "GMENFAN" suggests knowledge concerning SB cards known to fail with SPWaW. Is there specific info available to the community? What cards do work? I've experienced no other gaming/system issues relative to the VIA chipset/SB soundcard noted on the Creative website that might indicate the presence of driver/system incompatibility issues. I run AOE II/ UT/ Quake/ DiabloII on these machines, run various apps like 3D Studio Max, After Effects, Photoshop, Flash, etc. without experiencing stability issues like this. Being dedicated to both SP and the work that Matrix has done over the years really inhibits me from generating a req for refund over the 1941 MC, but this behavior would've had me returning the game were it any other publisher. I spoke with an MS devlpr who noted that the DX implementation in Win2k isn't optimized as well as the attention they put into the kernel of WinXP, naturally. I'm building a new Athlon XP 1800 system based on an Asus A7V333 mobo using 512mb ram running standard IDE config with a Gainward Geforce4 4200 vid card with the native mobo sound chipset which will be using the WinXP OS, so I'll see how that goes. Sorry for the long post. Hope the info helps. I'll hang onto the save/.prf files in case you want them passed along. System 1: DOS/WinNT/Win98SE PII 400 Intel SE440BX-2 mobo 384mb Crucial ram ELSA Synergy II vid card 394U2W Adaptec HA Firewire Host Adapter SB AWE 64 Gold USR internal 56k modem DX: 8.1 WinMP 7.1 IE: 5.5 Netscape 4.7 System 2: Win98SE PIII 800 Asus P3V4X mobo 384mb Crucial ram ATI Radeon 32mb vid card using onboard ATA controllers SB X-gamer Live USR internal modem DX: 8.1 WinMP 7.1 IE: 5.5 System 3: Win2k Sp2 Athlon 1.4ghz (not XP) Asus A7M266 mobo 512mb Crucial ram ELSA Gloria II (Quadro chipset) 39160 Adaptec HA Firewire HA SB X-gamer Live USR USB modem DX: 8.1 WinMP 7.1 IE: 5.5 Netscape 4.7
|