Hi all,

I've got myself a new rig lately. It is primarily for FSX and some FPS games. Though, FSX gets old sometimes and so i came back to my beloved Jane's titles, but not without some issues...
First of all my specs:
MB: Asus Rampage II Extreme
CPU: Intel I-7 920(DO), overclocked to 4GHz
both watercooled
RAM: Corsair DDR3 2000 MHz, 8-8-8-24
GPU: BFG GTX 285 OC 1GB (NVIDIA 191.07)
running a Matrox TripleHead2GO Digital
OS: Windows 7 64-Bit RC (last patchdate oct.15.09)
Stick: custom Talon F-15 Stick + Throttle (for the Janes sims: Logitech Force 3D)

Ok, now what happened? Last week i installed LongbowII, which kept hanging with a black screen (actually all three of them) on startup. No way to get back to Desktop. My culprit was the TH2Go as the screen resolution may have been too much to handle for Longbow II.
Too frustrated to push myself through the dance i installed Janes F-18 with it's fancy new TSH4.02 all in one installer. And guess what?
It worked perfectly. Launched the game, Janes intro , TSH intro , singlemission: carrier day landing, break turn, groove, three wire, whiping a tear out of the corner of my eye. And that is without any compatibility setting in windows and no AA slowdown!


Ok now everything is cool, right? NO
The next day i started up jf18 all screens went black just like LongbwII, no joy! Something must have changed.
TH2Go wasn't a problem (without Matrox Desktop). You don't even have to use windowed mode for the sim. I use 1600x1024 and it simply cuts off the left and right side black. Switching from overclocked settings to BIOS default changed nothing. Compatibility modes didn't help either.
Then i noticed that sometimes when i boot i get an error message that "cfp.exe" couldn't load. I googled it and found out that it is a service for COMODO firewall. I closed COMODO and there you go jf18 works. Longbow still crashed, but goes immediately back to desktop. Maybe a memory issue that i have to take a closer look at.

Bottom line: it looks like the Janes titles have probs with this cfp.exe. Giving the sims full rights in COMODO doesn't help. It's the service that crashes them

That's interesting...I've had intermittent problems with both JF-18 and LB2. Sometimes they want to work, othertimes nothing. Do you find that the sims work fine with the Defense+ engine disabled? That's the only thing I know of in COMODO that might be causing issues. The past few COMODO builds have had a lot of bugs and problems, so I'll test the sims with it disabled to see how they work out. It's a great firewall though, I'd hate to have to ditch it. Interesting find!