counterspy question

[Fly]

It's a program I use.

A very good one.

I have noticed that merging of definition updates is taking more and more time. Minutes ! It's much slower than it used to be.

Does anyone have an explanation ?

[Bubba]

{QUOTE-> Does anyone have an explanation ? <-QUOTE}Eric Howes commented yesterday @ the Sunbelt Froum in this (http://beta.sunbelt-software.com/viewtopic.php?t=7792) thread concerning update slowdowns.

{QUOTE-> The updates are occasionally slow because everyone is currently downloading full definitions -- every update. Once we roll out incremental updates (expected in the next week), then update times should be much quicker.

Best,

Eric L. Howes <-QUOTE}

[eburger68]

Bubba:

The bit you quoted actually applies to the VIPRE beta users, not CounterSpy. The problem for both VIPRE and CounterSpy users is that the CounterSpy def updates are huge and those huge updates are causing problems both on the server side and on the client side-- it's simply a question of size. VIPRE users are affected by the huge CounterSpy updates because VIRPE defs (which are much smaller) are pulled from the same server.

In the next few weeks we will be rolling out VIPRE AntiVirus + AntiSpyware as well as CounterSpy Antispyware 3.0. Both use definitions that are much, much smaller than current CounterSpy defs. Even the full VIPRE defs take less time right now than the incremental CounterSpy defs. Once we implement incremental defs for VIPRE (expected in the next week), the difference will be even more dramatic.

So, yes, we know that defs have gotten somewhat painful of late for CounterSpy users, but that is about to change. Until we roll out these new programs/versions, I would recommend CounterSpy users force a "full update" if they encounter problems ("File >> Download Full Definition").

Best,

Eric L. Howes

[Bubba]

{QUOTE-> Bubba:

The bit you quoted actually applies to the VIPRE beta users

~snip~

So, yes, we know that defs have gotten somewhat painful of late for CounterSpy users <-QUOTE}Combine all of what was said above Fly (http://www.wilderssecurity.com/member.php?u=74533) and hopefully that's the answer to your query.

[GES/POR]

{QUOTE-> Bubba:

The bit you quoted actually applies to the VIPRE beta users, not CounterSpy. The problem for both VIPRE and CounterSpy users is that the CounterSpy def updates are huge and those huge updates are causing problems both on the server side and on the client side-- it's simply a question of size. VIPRE users are affected by the huge CounterSpy updates because VIRPE defs (which are much smaller) are pulled from the same server.

In the next few weeks we will be rolling out VIPRE AntiVirus + AntiSpyware as well as CounterSpy Antispyware 3.0. Both use definitions that are much, much smaller than current CounterSpy defs. Even the full VIPRE defs take less time right now than the incremental CounterSpy defs. Once we implement incremental defs for VIPRE (expected in the next week), the difference will be even more dramatic.

So, yes, we know that defs have gotten somewhat painful of late for CounterSpy users, but that is about to change. Until we roll out these new programs/versions, I would recommend CounterSpy users force a "full update" if they encounter problems ("File >> Download Full Definition").

Best,

Eric L. Howes <-QUOTE}

Do you a date when CS 3.0 will be released to the public? Also is there a beta for dat or just vipre?

[eburger68]

GES/POR:

Barring unforeseen problems, I would guess that VIPRE will be released in the next 2-3 weeks, with CounterSpy 3.0 to follow shortly after that. So, we're close.

Eric L. Howes
Sunbelt Software