New SpySweeper 4.0 Beta

Seems a bit snappier. Nothing has gone boom.

http://www.webroot.com/beta/SpySweeperBeta40.exe

 

Are registered spysweeper users going to be able to use this beta? If so will our unlock codes work on it? I still get the "3.5 is the latest version" from webroot's site.

 

Yup... use your key. Will work fine.

 

One item to be aware of. Beta 4 will lock up if you have a large HOSTS file, say for example HPGURU's HOSTS file. The new service in Beta 4 named WRSSSDK.DLL will go 99-100% busy indefinitely. Your whole computer will come to a crawl. This has been a problem since the first build of the SS V4 Beta.

Other than that, the Beta 4 looks/works pretty good. On my system (Windows XP-SP2), it is the first version of Spy Sweeper that does not spike the CPU to 100% busy every time the memory shield runs.

 

Public release of V4.0.0.323 today 13-May-05.

https://secure.webroot.com/register/softwareupdates.asp

NOTE: Still cannot handle large HOSTS files such as HPGURU's HOSTS.

 

Since the few days i am testing the new Beta, i have not found a problem.
except is seems to have a conflict with A2 (squared) (trial)
it took me some time to have them running both on one system.

But now they do without a problem.

 

Kind of a boring Beta, IMO, it works too well

 

heavy cpu activity here:

 

No good than is it......

 

This beta version is more fast, but still need some work to improve and stable it...

 

My system was having some minor CPU usage issues that once resolved brought the SpySweeper 4 beta down to virtually no CPU usage. What really helps in pinpointing these things is to use ProcessExplorer with the symbols configured (Windows NT/2k/XP/2003 only) This gives you something that's (sometimes) human readable when you double click on a process and go to the "Threads" tab.

To configure the symbols:

• First download and install the latest Debugging Tools for Windows
• Open ProcessExplorer, click Options > Configure Symbols
• In the first box labeled "Dbghelp.dll path" enter C:\Program Files\Debugging Tools for Windows\dbghelp.dll
• In the second box labeled "Symbols path" enter srv*c:\Symbols*http://msdl.microsoft.com/download/symbols

Click "OK" and you're done. What you see won't always make sense, but sometimes it can really help. In the case of a beta I'm sure reporting what it's doing that causes so much CPU usage will be much more valuable than just the fact that it is taking up so much CPU.

 

I am impressed with the new Spysweeper version 4. Is much lighter and faster than the previous version.

And i overcame all the problems during installation with Nod32.

 

Wow , and the sweep time has decreased! Only 9 minutes I/O 28 minutes!

 

Thanks Notok, I have done that.
My AV and SS are fighting together. When I snooze my AV Spy Sweeper uses almost 0 CPU and everything works fine. I'll think about how to proceed with these to apps.
Cheers,

Gerard

 

So may be they did something right this time around. At least they lower the mem usuage And CPU usage.

Not they have to get some professional to do the interface.

I always wonder what are the chances of having spyware that AV and A2 / Ewido with firefox as browser may get in ones system.

 

The installation didn't go well here,It froze at about 90% and the CPU maxed out ,I guess it's the host file problem mentioned above

I'll stick with 3.5

 

Kaupp,

Please file a support ticket with Webroot concerning the HOSTS file problem. Maybe if Webroot gets a lot of complaints on this issue they will fix it...I've been reporting it since the very first public beta release.

http://www.webroot.com/support/?WRSID=8adebb540dfa6d015eaf8248b50b117e

 

done.

regards
Kaupp

 

ok I have a problem with the latest release??Program Version 4.0.1 [Build 323]
if i disable the engine from 'services'[because it conflict's with NOD32]slows the opening of GUI process to a halt!!
http://img157.echo.cx/img157/8499/webroot5dn.jpg
I get this message when i fire it up for updates
http://img157.echo.cx/img157/7529/webroot20jo.jpg

 

hayc59,

I do believe that the new WRSSSDK.exe service is an integral part of the new V4. Disabling it will probably render SS useless. The error you are getting is the same error that occurs if the HOSTS file is a large file...although I suspect that it is a generic error message that occurs if something goes wrong with WRSSSDK.

I suspect you will have to stay on V3.5 until the NOD32 conflict is corrected. Is it the memory scanner module of SS V4 that is causing the conflict? Perhaps you could turn off that Shield.

 

hayc,

disable AMON. After u can install it.

 

@siliconman01, thank you seems ok if i put it in 'manual mod'
and the shield is turned off and still same effect.

@Stephanos G., I have done that and seems not to effect the load
its just when services is disabled, thank you

 

hayc59,

I suggest you file a support request ticket with Webroot on this conflict problem. The support link is:

http://www.webroot.com/support/?WRS...eaf8248b50b117e

Hopefully they can resolve it shortly. Please provide them as much info as you feel is important so that they can research it.

 

siliconman01, will do and thank you