robertmiles

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About robertmiles

  • Rank
    Newbie
  1. The Spybot - Search & Destroy update today was larger that usual, but not a new version. Some symptoms of my problem that may be different from the others: High disk activity most of the time for at least a week; some due to hard faults. Something seems to be reserving blocks of memory without marking them as for a specific process; Windows Task Manager shows at least 50% of the physical memory in use when the resulting slowdowns occur, but usually not much more. The memory is shows as for specific tasks, or for the system, does not add up to 50% of the total. This apparant memory leak occurs both on my 32-bit Vista Home Premium SP2 machine, which has 2 GB physical memory and uses Ad-Aware AE, an antivirus program, and three other antispyware programs, and on my 64-bit Vista Home Premium SP2 machine, which has 8 GB and uses a different security package. On both of my machines, I usually have workunits from a number of BOINC projects running, including some for which I'm participating in the alpha tests or beta tests of new versions of their software, and also Windows Mail with a rather heavy load of read and unread newsgroup messages (probably a few hundred thousand on each machine). These BOINC projects are mostly related to medical research, and all from groups that seem more interested in getting the work done for which they need BOINC to let the public use their computers to help, than in deliberately messing up computers. Do you know any programs suitable for monitoring such memory usage under Vista SP2? Windows Task Manager has already been tried, and does not show enough information.
  2. Workaround #1 failed - Lavasoft Ad-Aware Service was not on the list. Workaround #2 failed - I was able to change the compatibility mode, but with no change in the problem. Also, mode Windows 98 SP2 was not listed; Windows 98/ME was the closest. Also, the UAC request to let me run the program in administrator mode was hidden behind the main Ad-Aware SE window, but displaying it and approving it did not help. Workaround #3 failed - Terminal Services was not on the list. It may be significant that I run these menus in Classic View mode. I'm still not sure if I have the latest version of Ad-Aware AE - is there a way to check the version number if the program won't stay open long enough to use the usual method? Also, it may be significant that Spybot - Search & Destroy 1.62 maintains a hosts file if you use the Immunize function. There's a possibility that it includes a bad entry for your update site(s). I believe I've just downloaded an update to version 1.63, so I'll see if that helps.
  3. I doubt that that's the problem I have - my virus scanner and my other three spyware scanners have no trouble getting updates for their definitions. However, I might have a variant of it that blocks only Ad-Aware SE updates, but not also its web sites. I haven't tried the work-arounds yet - I'll see if I can try them today. Is there a way to check the version number of Ad-Aware SE when the program will not stay open long enough to use the usual way?
  4. I've finished running my antivirus program and my now other three antispyware programs (avast! Antivirus, Spybot - Search & Destroy, Windows Defender, and Malwarebytes' Anti-Malware) to prepare for remote testing. Two cookies were found; not significant threats, and their removal did not help. Windows Defender told me that it had blocked an attempt to write to the hosts file, but did not say when or by what program. Telling to to allow the write did not help. No other threats were found. These results look to me like part of the fix should be to add the files to tell Windows Defender where Ad-Aware came from, and if possible, that is allowed to write to the hosts file. Could the other people who have seen this problem mention whether they also have Microsoft's Windows Defender program installed, since recent updates to that program look like at least part of the cause? I'm unable to run Ad-Aware AE long enough to check which version number I have, but I could have easily missed the last update of the software part; I know I've missed a few of the database updates.
  5. I'm interested in helping. I have two computers connected through the same IP address, with Ad-Aware AE on only one of them. The problems are on my 32-bit Vista Home Premium SP2 machine, with nearly all updates, which passed my antivirus program and my two other antispyware programs today. One thing I noticed today is that Windows Defender was blocking a hosts file update, which I'd guess was leftover from the last time I was able to run Ad-Aware AE. However, telling Windows Defender to let the hosts file change happen did not help, and neither did reinstalling Ad-Aware AE. The problems started about the time I downloaded the Vista SP2 update, Internet Explorer 8, and a software update for Windows Defender, reported a lot of newsgroups spam from a very active spammer who was able to fake some of the post headers, and did a few things I've forgotten - about a month ago. I think I joined Microsoft's group for voting on what's spyware to be blocked by Windows Defender about the same time, also.
  6. When I've seen such problems, I had to reboot before free Ad-Aware 2008 would work properly again.
  7. I was previously running free Ad-Aware 7.1.0.10 under Vista SP1, with the database update a week ago. Today, I started it, checked for available updates, and was told a software update was available. I clicked on the button to check what software updates were available, and the software update to 7.1.0.11 started running without waiting for me to approve it. I saw nothing clear on the progress of this update, but eventually it offered me the option to start a scan. I did; this scan seemed to run normally at first, but when it got to file C:\Windows\Cursors\size4_il.cur the progress of the scan stopped but the clock kept running. After a few minutes, I tried to stop the scan; this attempt to stop it was ignored. A few attempts to stop it by other means also failed. I finally managed to shut down its user interface. When I restarted its user interface and requested another scam, it refused, with an error message saying its core was still running. Waiting an hour or so, restarting its user interface, and requesting another scan only produced the same failure. Finally, I rebooted, tried again, and this time the scan ran normally and completed. It appears that the installation procedure for this update needs a few changes: 1. After the user tries to view what updates are available, show them and wait for user approval before installing 7.1.0.11. 2. Show more about the update's progress. 3. Don't allow a scan after the apparant end of this update; instead, show a message saying the user must reboot before starting a scan, and wait until this reboot is complete before allowing a scan.