when is a bug a bug?

[Umfriend]

No, a bit of a pain uninstalling/installing. I put the new version on another computer which has only MSSE for security and it seems OK. Neither MSSE nor FSC turns a hair. Can we draw a conclusion from this?

TO me that says FSC might be working. It'd require more testing with other security suits to be sure.

Aside from cjolley's comment, *if* a security suits causes this behaviour (white screen capture) _and_ does not log it anywhere, then that I would consider a real bug or, more likely, bad spec.

On cjolley's comment, really? It is the constructive attitude of course but may be very time consuming given the number of potentially conflicting programs out there? I for one would not test my software with all security suits (unless I wrote a virus or something).

[VJ]

No, a bit of a pain uninstalling/installing. I put the new version on another computer which has only MSSE for security and it seems OK. Neither MSSE nor FSC turns a hair. Can we draw a conclusion from this?

I would say that FSC seems to be working, and not doing anything to upset MSSE.

The company who wrote the software needs to work WITH the security software companies to find out WHY it is setting them off (assuming that is really what's happening). Then work out a solution with them.
Sitting around trying to figure out who to assign blame to doesn't help get the problem solved.

True... But as an end user, you are sometimes stuck when companies blame each other. In this case, FSC should contact the security software to work out what is causing the behaviour, but the end user is still stuck with the problem.

Aside from cjolley's comment, *if* a security suits causes this behaviour (white screen capture) _and_ does not log it anywhere, then that I would consider a real bug or, more likely, bad spec.

Yes, that option also just hit me: it could be a bug in the security software. For sure it should log if it deliberately blocked a progam. But if it causes another program to crash, something is wrong.
From FSC reply, it sounded like they are aware that they have an issue/conflict with some security softwares. It would be nice for them to admit this, and to say they are working on the problem (as cjolley said).

On cjolley's comment, really? It is the constructive attitude of course but may be very time consuming given the number of potentially conflicting programs out there? I for one would not test my software with all security suits (unless I wrote a virus or something).

I assume they test against the most common ones, and the move on to beta testers.

[cjolley]

On cjolley's comment, really? It is the constructive attitude of course but may be very time consuming given the number of potentially conflicting programs out there? I for one would not test my software with all security suits (unless I wrote a virus or something).

Well, I would hope there is just one conflict that is causing it. Once they figure out what that is then they can work around it.
And I wouldn't test against them all either.