-
Tuttle: You feelings mirror many over at Wilders (including me to an extent.) I do not believe the proxy was the way to go for the client/workstation version. And based on how little response Eset is giving to the biggest proxy thread, I don't hold much hope for them to listen to us. They "know" better...
-
New build available 3.0.621. Many enhancements and bug fixes. (I haven't had the chance to update yet...)
http://www.wilderssecurity.com/showthread.php?t=195309
-
Have version 3 since it appeared. Clean installed, as HAN advises. Find it best to do with programs that are deeply embedded in the OS.
No problems at at all so far. Left all settings at default. To me this is a major advantage of this suite. I don't want to forever make rules, approve some obscure .dlls when I have no clue what they are, etc. Maybe the suite is aimed at consumers who just do not want to keep fiddling with their computers but just use them. I agree that configuration of ESS seems more difficult and less flexible than other suites I tried. But then, it is less intrusive.
-
I've been running 3.0.621 for a few days, and there are no problems to report :)
-
Yeah, 621 is several steps forward. I'm getting closer to deploying it to the PCs at work... :)
-
I have been unable to install 3.0.621 - I get an error message that -
"Another application has exclusive access to the file ...\NOD32\...|\cache.ndb - please shut down all other applications, then click Retry".
But it is impossible achieve this. Any suggestions?
Edit: Also, if I try to uninstall 3.0.560, I get the same error message.
-
I decided to do an uninstall and then a clean install of this one, because of what was said about upgrading. Did you try doing it that way?
-
Nick - that's precisely the problem I have described in my edit: when I try to uninstall 3.0.560 first, I get the same error message about cache.ndb
-
Problem fixed - it was necessary to stop the Eset service and HTTP Server in the Admin control panel before uninstalling the old version and installing 3.0.621
-
FWIW... I installed version 3 build 621 on both of my home PCs this past weekend. As recommended above, I did a "clean" installation (I uninstalled 2.7, rebooted and then deleted the C:\Program Files\ESET folder.)
So far so good! Version 3 seems to run just as smooth as it's predecessor. (I did make several setting changes from the default installation setup. I tweaked things like the Real-time scanning settings, on-demand scanning settings and default scanning targets.)
Don't forget that as a time saver, your individual tweaked settings can be exported as an XML file and saved. I used my export file from one PC to setup the 2nd one. Saved a bunch of time!
Finally, I was quite concerned that Eset made a bad decision when they implimented a local proxy into version 3. Some software firewalls do not handle local proxies well at all. But I am glad to say that ZoneAlarm seems to handle the proxy just fine. Which is coooooollllllll! :D