chrisj
-
Posts
11 -
Joined
-
Last visited
-
Days Won
2
Kudos
-
chrisj received kudos from VanBuran in Delay error messages on startup request
I find that eSet is always to quick to report an error that is due to the fact that it is active before the internet connection has been established. I get fed up with getting messages about not being able to reach live servers or failed to update product when I know that if I wait a few seconds for the wi-fi to sort itself out the message will usually go away. This false error message makes users feel insecure and there is a "cry wolf" aspect that if there is a real error, it might be ignored.
The ability to set a delay on the error reporting message system to check for live internet before flashing up warnings would be helpful. Even something as simple such as "waiting for live internet connection before checking" would be better than sending unhelpful error messages.
Does anybody agree with me?
-
chrisj received kudos from Mr_Frog in Delay error messages on startup request
I find that eSet is always to quick to report an error that is due to the fact that it is active before the internet connection has been established. I get fed up with getting messages about not being able to reach live servers or failed to update product when I know that if I wait a few seconds for the wi-fi to sort itself out the message will usually go away. This false error message makes users feel insecure and there is a "cry wolf" aspect that if there is a real error, it might be ignored.
The ability to set a delay on the error reporting message system to check for live internet before flashing up warnings would be helpful. Even something as simple such as "waiting for live internet connection before checking" would be better than sending unhelpful error messages.
Does anybody agree with me?
