NOD32 v.4 (beta) and wireless connections

[Zyrtec]

I've been trying this beta ver. on a spare laptop I have and I've noticed that the problem caused by NOD32 trying to update the virus database BEFORE a wireless connection can be established has NOT yet been addressed.
(At Windows boot)

This problem plagued version 3.0 of NOD32.

Is it going to be fixed on this version or not?


P.S.: Marcos, please, this time respond to this inquiry.

Thank you,

Carlos

[pondlife152]

Yes, I'm testing V4 on my laptop too, and have noticed this. It does try again to update after an hour, but if you do not keep the laptop running this long, you have to manually force an update.

Perhaps you can add an option to the logon event, a user set delay so that logon +1 minute, for example, could be used in the scheduler.

[philby]

Have you tried unchecking "automatically detect settings" under internet options > connections > LAN ?

This reduced my boot lag from about 3 minutes to 30 seconds worst case.

This is probably not the issue you were referring to, but if it is then I hope this helps.

Philby

[pondlife152]

No it isn't a lag as such, it just seems that NOD wants to connect before the wireless connection has been fully enabled. It's just a matter of a few seconds at most. A small delay before NOD checks for an update after logon would overcome this.

Thanks for the info anyway.

[Brambb]

This might be a work around for your problem.

- Start --> run --> gpedit.msc
- Local computer policy --> computer configuration --> administrative templates --> System --> Logon (for vista, xp should be similiar)
- Enable 'Always wait for the network at computer startup and logon'

-{ Quote: "I've been trying this beta ver. on a spare laptop I have and I've noticed that the problem caused by NOD32 trying to update the virus database BEFORE a wireless connection can be established has NOT yet been addressed.
(At Windows boot)

This problem plagued version 3.0 of NOD32.

Is it going to be fixed on this version or not?


P.S.: Marcos, please, this time respond to this inquiry.

Thank you,

Carlos" }-

[Marcos]

-{ Quote: "No it isn't a lag as such, it just seems that NOD wants to connect before the wireless connection has been fully enabled. It's just a matter of a few seconds at most. A small delay before NOD checks for an update after logon would overcome this.

Thanks for the info anyway." }-

There's already a 1-minute delay, but it seems that it's not enough for some of you. We'll consider tuning it up a bit.

[pondlife152]

Okay, thanks for looking into it.

[war59312]

Yeah why not 5 minutes, should cover older PCs too.

-{ Quote: "This might be a work around for your problem.

- Start --> run --> gpedit.msc
- Local computer policy --> computer configuration --> administrative templates --> System --> Logon (for vista, xp should be similiar)
- Enable 'Always wait for the network at computer startup and logon'" }-Nice workaround.

Only problem really I see with enabling this is that wireless is known for not being too stable so if your wireless connection happens to be out at boot-up windows will take forever to log-in, back to the win2k days.. Ouch!

[Clweb]

Why not:
if update failed because network error, the retry every 5 minutes until success. Then update at the configured frequency (1 hour default).