Ok. Thanks for explaining the dialog that reports a crash.
[...] And that a firewall triggers an alarm offering the user to reject or allow an Internet connection for any program not yet configured in the firewall and that it offers the user the possibility to configure a rule for the future and stuff like that is just normal behavior of a firewall. That�s what they are supposed to do.
I would think that the warning given by the firewall is of great importance. Think of the effect that the AARD error had on marketshare.
Or that the Netware rumour spread by MS sales staff had on Netware marketshare.
Most users are more than ignorant about any and all aspects of a firewall and have a superstitious approach to them, more so than other aspects of their computers.
e.g. users that feel extra protected by running three different firewalls concurrently.
e.g. or users that feel that running a firewall (that allows outgoing HTTP requests or incoming mail) will somehow protect them from MSIE or MS-Outlook problems, etc.
So, since many (most?) users treat firewalls as some sort of protective voodoo or as an all-knowing oracle, it's very important that the operation of the firewall provide a positive psychological experience.
[...]
If you see a misbehavior here please explain.
Not having seen the crash report dialog, I was merely speculating as to a possible cause of user confusion. The explanation cleared that up.
-Lars
Lars Nooden ([EMAIL PROTECTED])
Software patents harm all Net-based business, write your MEP:
http://wwwdb.europarl.eu.int/ep6/owa/p_meps2.repartition?ilg=EN
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
