spysweeper Beta 4.0

Exactly the same as I stated earlier, though I did not have your expertise to display the above

 

well 20 Mb is still an improvement from 36Mb.

But this is enough to keep me away.

 

I was able to get a slightly newer Beta 4.0 version by submitting a support request ticket to Webroot. It too failed to initially install. There is a major problem with the new second service WRSSSDK in Beta 4.0 and very large HOSTS file such as those from HPGURU's site. WRSSSDK goes 100% busy trying to handle this large HOST file and never drops down in CPU time...therefore locking out any other program from running. This large HOSTS file is handled without a problem in V3.5.

Plus the install failure is also a result of the large HOSTS file at C:\Windows\System32\Drivers\Etc.

This is going to be a killer for many of us SS users who also use the HPGURU HOST file.

 

I just went to there web site and Asked Customer Service for the Beta Version and they sent it to me!!

And I'm a Licenced User of SS

 

IMPORTANT:::::

Here's something you should immediately check if you are using Spy Sweeper Beta 4.0.

The HOSTS file Shield and the Common Ad file Shield completely overwrote my original HOSTS file wiping out the 127.0.0.1 Localhost entry at the beginning of the file. This feature should be appending to the HOSTS file entries, NOT overwriting the entire file.

This file is located in the C:\Windows\System32\Drivers\Etc folder. The very first entry should be 127.0.0.1 Localhost.

I'm not certain if this occurred on the initial installation of Beta 4.0 or when the definitions files was updated. So you may wish to recheck it the next few times SS updates the definitions.

I have submitted this problem to Webroot.

 

Things seem to be running smoother with 4.0. Scans are less invasive and as Don also indicated, I'm not seeing CPU spikes like I did with 3.5.

 

The Beta update is back up on their site.

 

I should also mention that I rarely even use AdAware, SpyBot or MAS these days. I have yet to be in a situtation where they other 3 apps find something SS misses.

 

Is this a refreshed Build of Beta 4.0 that has been issued? I've dropped back to V3.5 because of the HOSTS file overwriting problem. The Beta is not showing up for me on their website.

 

Anyone else notice this log file showing up on their C: drive since installation? It's called "log". Contents attached.

 

prolly they'll use it for troubleshooting, like giant does.

how is this spysweeper thing for you? do you like it Taz?

 

Been pretty happy with it... as I said in an earlier post. I have yet to find a situtation in the last 6 months where SS misses anything that MSAS, SpyBot and AdAware catches.

New version seems to be running pretty well other than the log file which pisses me off.

 

Taz,

Have you instituted the HOSTS and Common Ads Shield and if so, did it overwrite your primary HOSTS file instead of appending to it? Just curious.

 

Beta 4.0.0.303 of Spy Sweeper is now available. This new Beta did correct the problem of overwriting the HOSTS file when using the Ad Shields in the HOSTS option.

It does NOT, however, correct the problem that a LARGE HOSTS file cannot be utilized....HPGURU's 39000+ entries. The BETA will not even install properly if this HOSTS file is used.

This was not a problem in V3.5.

 

TazDevl,

The LOG.TXT file does not appear to be used by Beta 4.0.0.303.