PDA

View Full Version : New SpySweeper 4.0 Beta


tazdevl
May 9th, 2005, 07:02 PM
Seems a bit snappier. Nothing has gone boom.

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

feddup
May 9th, 2005, 08:22 PM
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.

tazdevl
May 9th, 2005, 08:33 PM
Yup... use your key. Will work fine.

siliconman01
May 10th, 2005, 01:29 AM
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.

siliconman01
May 13th, 2005, 04:19 PM
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.

tuatara
May 13th, 2005, 04:32 PM
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.

Notok
May 13th, 2005, 04:35 PM
Kind of a boring Beta, IMO, it works too well ;D

gerardwil
May 13th, 2005, 05:59 PM
heavy cpu activity here:

iwod
May 13th, 2005, 06:21 PM
No good than is it......

rdsu
May 13th, 2005, 06:41 PM
This beta version is more fast, but still need some work to improve and stable it...

Notok
May 14th, 2005, 12:11 AM
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 (http://www.sysinternals.com/ntw2k/freeware/procexp.shtml) 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 (http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx)
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.

Stephanos G.
May 14th, 2005, 01:38 AM
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.

Stephanos G.
May 14th, 2005, 01:48 AM
Wow , and the sweep time has decreased! Only 9 minutes I/O 28 minutes!

gerardwil
May 14th, 2005, 04:11 AM
-{ Quote: "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 (http://www.sysinternals.com/ntw2k/freeware/procexp.shtml) 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.
" }-

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

iwod
May 14th, 2005, 08:21 AM
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.

Peter2150
May 14th, 2005, 09:45 AM
I am also finding this beta much better. I was also seeing the CPU spikes with the memory shield on. One thing to look for. I still see the spikes with memory shield on as before, BUT, instead of every 15 seconds or so they now only occur every 2 or 3 minutes. What they probably did was change the frequency of the memory check.

Kaupp
May 14th, 2005, 10:18 AM
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

siliconman01
May 14th, 2005, 11:12 AM
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

Kaupp
May 14th, 2005, 11:57 AM
done.

regards
Kaupp

hayc59
May 14th, 2005, 11:57 AM
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

siliconman01
May 14th, 2005, 12:58 PM
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.

Stephanos G.
May 14th, 2005, 12:59 PM
hayc,

disable AMON. After u can install it.

hayc59
May 14th, 2005, 03:18 PM
@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

siliconman01
May 14th, 2005, 04:08 PM
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.

hayc59
May 14th, 2005, 04:30 PM
siliconman01, will do and thank you;)

siliconman01
May 15th, 2005, 08:08 AM
Here's something I just discovered with the V4.0.1.323 of Spy Sweeper...on Windows XP-SP2.

When I do a sweep and have the option set to scan Memory during the sweep, every program in memory more than triples in memory usage when it is scanned by SS. :( And it's usage size stays at the high usage value until a reboot is executed.

Anyone else seeing this ?? ???

I have "bugged" this to Webroot.

fred22
May 15th, 2005, 12:38 PM
this HOSTS problem is a real pain in the ***, WRSSSDK.exe goes nuts and it tells me the install is damaged,reinstall spysweeper...

and the support link aint working
http://support.webroot.com/ics/support/default.asp?deptID=776

Not Found
The requested URL /ics/support/default.asp was not found on this server.

::)

siliconman01
May 15th, 2005, 12:59 PM
-{ Quote: "and the support link aint working" }-

Hmmm ??? Works from my box.

Try going to www.webroot.com and then click on Support and go from there.

fred22
May 15th, 2005, 01:11 PM
it really aint working atm(for me at least)
when i click get support, im getting http://support.webroot.com/ics/support/default.asp?deptID=776
not found
if i change to dutch support the banner aint working ehehe :P
http://support.webroot.com/ics/support/default.asp?deptID=829&Banner=nl-nl

i'll keep trying ;)