ESS v. 3.0.560 available

[Marcos]

The delay when closing OE is caused by the messages queuing for processing. Do you experience the delay even if you don't close OE immediately but wait a couple of seconds to finish processing messages?

[ugly]

Originally Posted by Marcos

The delay when closing OE is caused by the messages queuing for processing. Do you experience the delay even if you don't close OE immediately but wait a couple of seconds to finish processing messages?

Delay exist even if you close an empty (no messages) OE.

[cdr]

Originally Posted by Marcos

The delay when closing OE is caused by the messages queuing for processing. Do you experience the delay even if you don't close OE immediately but wait a couple of seconds to finish processing messages?

Marcos,
Yes, there is a slight delay or lag, regardless of when you close OE. I never close OE while it is processing incoming e-mails. So, the lag occurs anytime at all that one closes OE. Even, as Ugly says, when OE is empty. As I stated previously, to me, it is not a major issue, but for others, it is. Thanks for your help!

[Edwin024]

Strange to see that only OE seems to have this. I use Outlook and it is as fast as it can be. In starting and closing. Haven't test it in Windows Mail because I don't use it. But for the fun of it I will do it now

Windows mail has a bit of lagging indeed too. A second or two, three. So Outlook is the best then.

[CDreier]

Originally Posted by cdr

Yes, I also have that lag time when closing OE. It almost seems like ESS takes a little time to "remove" its toolbar from OE before the program can close. Although not "elegant," it's a very minor lag I can live with.....

I wonder if there's a way to disable the anti-spam module in OE completely? I use Qurb for anti-spam and the ESET toolbar with the anti-spam icons is disabled. BTW, I tried NOD32v3 before installing SS. NOD32v3 did not have the lag problem when exiting OE. Thanks.

[Westland]

Originally Posted by CDreier

... BTW, I tried NOD32v3 before installing SS. NOD32v3 did not have the lag problem when exiting OE.

I only have NOD32v3 installed. (Never had ESS installed.) OE still has the lag problem.

[Marcin_K]

Originally Posted by cdr

upon startup this morning, the system tray icon was red and the control panel indicated something to the effect that real time scanner was disabled "by the user." Which, of course, I did not do

Same here. I've tried everything... nothing seems to help. The problem didn't occur with the previous version...

[cdr]

Originally Posted by CDreier

I wonder if there's a way to disable the anti-spam module in OE completely? I use Qurb for anti-spam and the ESET toolbar with the anti-spam icons is disabled. BTW, I tried NOD32v3 before installing SS. NOD32v3 did not have the lag problem when exiting OE. Thanks.

Marcos responds to this question--see his post (#7) in this thread, if you have not already seen it:
http://www.wilderssecurity.com/showthread.php?t=190490

[Ade 1]

Originally Posted by Marcin_K

Same here. I've tried everything... nothing seems to help. The problem didn't occur with the previous version...

Although off topic, regarding the previous post about having a red icon upon startup and realtime protection being disabled "by user", I had this problem the first time I installed ESS on my XP laptop. I noticed in the realtime protection setup, under advanced options, the last one after optimized scanning (enable realtime protection on startup) was unchecked. Having checked that and rebooted it's been fine since. Not sure if this will help.

[cdr]

Originally Posted by Ade 1

Although off topic, regarding the previous post about having a red icon upon startup and realtime protection being disabled "by user", I had this problem the first time I installed ESS on my XP laptop. I noticed in the realtime protection setup, under advanced options, the last one after optimized scanning (enable realtime protection on startup) was unchecked. Having checked that and rebooted it's been fine since. Not sure if this will help.

Ade 1,
Yes, I, too, ultimately discovered that it was unchecked--and the problem resolved completely when I checked it! Thanks for mentioning it!

[crummock]

Looks like the install with version 3.0.560 forces 'Automatic real time file system protection' off. Easily fixed when you check the setup pages.

It's happened on 3 machines that I've installed this release on so it's not just bad luck.

I can only assume that it's an oversight on the part of Eset.

[saffron]

Originally Posted by crummock

Looks like the install with version 3.0.560 forces 'Automatic real time file system protection' off. Easily fixed when you check the setup pages.

It's happened on 3 machines that I've installed this release on so it's not just bad luck.

I can only assume that it's an oversight on the part of Eset.

Don't hold your breath waiting for it to be fixed. I waited for an oversight on the part of ESET to be addressed for years. ESET always knows what its users want more than they do.

Blackspear's excellent "maximum security" settings should have been made the out-of-the-box standard in V2, and many other Wilders members said so, but ESET didn't take the slightest bit of notice. Download v2.7 right now and you'll find the settings are still the same old crap.

[Edwin024]

Eset has now tested a new version to cure the no-pictures bug in ESS. This version also closes Windows Mail two seconds sooner than with 560. I was informed that the new version (563) will be brought out soon. So I can't agree with your post, saffron.

[saffron]

Originally Posted by Edwin024

Eset has now tested a new version to cure the no-pictures bug in ESS. This version also closes Windows Mail two seconds sooner than with 560. I was informed that the new version (563) will be brought out soon. So I can't agree with your post, saffron.

Then we'll have to agree to disagree. Fixing 1 bug among the dozens reported right here in this Forum does not immediately fill me with a warm glow.

[Steel]

Originally Posted by Edwin024

Eset has now tested a new version to cure the no-pictures bug in ESS. This version also closes Windows Mail two seconds sooner than with 560. I was informed that the new version (563) will be brought out soon. So I can't agree with your post, saffron.

Did you heard anything if they push Build 563 out in front of the weekend ?

[nodyforever]

Originally Posted by Edwin024

Eset has now tested a new version to cure the no-pictures bug in ESS. This version also closes Windows Mail two seconds sooner than with 560. I was informed that the new version (563) will be brought out soon. So I can't agree with your post, saffron.

But now do they walk when mouth washes are launching versions to? Because they do not make soon everything a certain one and order a decent version?

Even that you only have spoken what is an internal version I wait that they do not gain this habit of launching a hill of versions to correct an alone bug.