...or it's probably my fault.
Was trying to test something in-game, only to get the good old unhandled exception message, you know, the one that says this:
Unhandled Exception! in Version 1.01 Build 534
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module d3d8.dll at 001B:6DA4BA27
EAX=00000000 EBX=00000384 ECX=04395F18 EDX=0036BFF0 ESI=00000400
EDI=00368800 EBP=000003FA ESP=0012FBDC EIP=6DA4BA27 FLG=00210216
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
001B:6DA4BA27 (0x00000000 0x00000000 0x00000000 0x00000000) d3d8.dll
Awww...did you miss'im? Me neither.
Now I was just going to test some hardpoints, so nothing extravagant has changed software-wise...buuuut....
I changed my graphics card to a Radeon 1650 (from the default Xpress 200) late last year, though SFC worked fine on it as I recall. As I was able to play skirmishes afterward.
I more recently changed my monitor to an LCD Flatron L222WT. Could it be the combination of both that's preventing SFC3 from working?
Another possiblilty is telling Spybot to toggle ati2evxx startup entry off. I've been getting into that habit lately because all of my games seem to run better without it, and it's generally a nuisance memory-wise. Could it be required by SFC3? Everything else (BC, Half-Life, ect.) works just fine.