tekman78

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tekman78

  • Rank
    Newbie
  1. I recently installed the 7.0.1.4 version, and was getting the Service Error 6000 blah blah.... I uninstalled it and installed the 7.0.1.5 version hoping to fix this. It did not. After a little troubleshooting, and noticing it was dumping out with the 6000 error on "scanning inside archive", I figured out my problem. My McAfee VirusScan software was also set to scan archives during OnAccess scans. AdAware seems to not like to wait for the McAfee archive scan to complete, and then craps out. After changing the "scan archives" function of McAfee vScan to only scan archives for 5 seconds, vs 15, AdAware 07 can complete a full scan no problem. I am guessing though if it was to come across an archive which was very large (or larger than anything on the PC right now), it may do it again. I want to keep this function active in vScan. Maybe it could be built into AdAware that it bypasses a file after X amount of time spent trying to scan, or just allow a file to be scanned for longer. There may be something different conflicting with the 2 scans, and nothing to do with timing being too long, but those are my recommendations. This may not be everyones problem, but this was mine and my fix. Thanks, Tim
  2. also found a bug, i think a good bug for me though. i just remember in all previous versions, ad-watch was not available in the free product. i have only the free download product, which i installed and rebooted before running the program. instead of running ad-aware first, i accidentally ran ad-watch. i set all the settings and began running it. i then went and ran ad-aware, when it asked me for a serial and which product i was running. i hit cancel and proceeded to setup adaware. i rebooted and ad-watch is still starting up upon reboot and ad-aware runs no problem. i had previously installed 7.1.0.4 as an upgrade to SE, but ad-watch would not run, it said i needed the pro version. i then uninstalled and installed the 7.0.1.5 version. but the order i did things seems to allow ad-watch to run no problems. im actually not even using it, because i can't seem to make it ask me to allow or block. i want to allow the wgatray.exe app to do its thing upon reboot and ad-watch flashes after every reboot because of it, so i'm just not running it. you may want to check that out too. Tim
  3. I recently installed the 7.0.1.4 version, and was getting the Service Error 6000 blah blah.... I uninstalled it and installed the 7.0.1.5 version hoping to fix this. It did not. After a little troubleshooting, and noticing it was dumping out with the 6000 error on "scanning inside archive", I figured out my problem. My McAfee VirusScan software was also set to scan archives during OnAccess scans. AdAware seems to not like to wait for the McAfee archive scan to complete, and then craps out. After changing the "scan archives" function of McAfee vScan to only scan archives for 5 seconds, vs 15, AdAware 07 can complete a full scan no problem. I am guessing though if it was to come across an archive which was very large (or larger than anything on the PC right now), it may do it again. I want to keep this function active in vScan. Maybe it could be built into AdAware that it bypasses a file after X amount of time spent trying to scan, or just allow a file to be scanned for longer. There may be something different conflicting with the 2 scans, and nothing to do with timing being too long, but those are my recommendations. This may not be everyones problem, but this was mine and my fix. Thanks, Tim