Auto-update not waiting for wireless to establish

[jongie]

I've recently upgraded to the latest build of v.3. In 2.7, I had a setting that prevented an attempt to auto-update untill the wireless connection had established. I can't find the equivalent in v.3, with the result that I frequently get an "update failed" message because NOD32 had tried updating too soon after the laptop had been turned on.

What is the "work round" in v.3?

Regards

John

[jongie]

I meant to add that the 'events' log file doesn't show these failed updates - I'm sure it did in 2.7? Do I get the feeling that v.3 has been "dumbed" down to make the interface nicer?

Regards

John

[webyourbusiness]

do you notice a performance hit - or is it just that the failures mean the system waits for another hour to get the updates again?

If the latter, change frequency to more frequent than an hour - say 30 or 20 minutes.

I don't know where the delay until connected is within 3.0 - I don't run it on either my work or home machine.... :blink:

[Big Apple]

{QUOTE-> I've recently upgraded to the latest build of v.3. In 2.7, I had a setting that prevented an attempt to auto-update untill the wireless connection had established. I can't find the equivalent in v.3, with the result that I frequently get an "update failed" message because NOD32 had tried updating too soon after the laptop had been turned on.

What is the "work round" in v.3?

Regards

John <-QUOTE}

Change it to 'dial-up' and it'll start the backup when a connection is established.

[jongie]

Thanks for that - I had in fact selected Dial Up as well as Regular Update. If I uncheck Regular Update, does the database only get refreshed immediately after connection is established, and then is not refreshed after that? If so, that seems to leave a hole in the protection.

John

[ASpace]

{QUOTE-> What is the "work round" in v.3? <-QUOTE}

http://www.wilderssecurity.com/showthread.php?t=202238&highlight=wireless