Nevermind.
In order to protect an older C drive, I wanted to avoid any more restarts.
In the end I couldn't resist going back and doing it right this time. All is 1.5.2.20 and normal.
Nevermind.
In order to protect an older C drive, I wanted to avoid any more restarts.
In the end I couldn't resist going back and doing it right this time. All is 1.5.2.20 and normal.
A few users posted in this thread that they think the TeaTimer function of SB 1.6.0 is what is causing the very high CPU usage when accessing new web pages in IE and even when only clicking on a 'new tab' in IE.
While I admit I have never used the TeaTimer function but rather always the SDHelper function during all past versions of SB, I'm pretty sure it is the SDHelper functionality that is causing the extremely sluggish IE response times. Proof is that TeaTimer in my 1.6.0 install has always been disabled, IE was extremely sluggish with SDHelper enabled, and then IE went back to its snappy normal speed when I disabled SDHelper (although I lost that protection, doh!).
My two bits here. I'm only guessing that there might be a small coding error in SDHelper.dll which is causing a loop type deadlock. I cannot believe that SDHelper.dll is actually using the CPU for that much intensity and time just to scan a new web page or even a new 'IE tab' when the previous versions are taken into comparison.
As in the past, I'm confident the SB programmers will correct this coding problem of SDHelper.dll soon just like they corrected the 'very slow to startup SB version' months ago.
almost everybody has a hostsfile on the computer i think, my original looks like this:
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
and if you add this under the first localhost line: 127.0.0.1 forums.spybot.info
then you can not access this forums, and other programs on the computer can not connect to the spybot forums.
malware blocks security sites and antivirus/antispyware updates in this way but the spybot hostsfile blocks sites that has malware in it and some adservers.
Last edited by blues; 2008-08-09 at 08:08.
Has anyone else noticed an issue with spybotsd160.exe, the Windows installer for 1.6.0? Near the end of the process a program runs in a console window that sends several megs of form feeds to the parallel port. Manually closing this window (and deleting the print job) after the progress bar on the installer has reached the end appears to have no ill effect on the installation. Spybot S&D 1.6.0.31 seems to run properly. I'm using Windows XP with SP2 on a Pentium 4.