|
Posted by on June 10, 2005, 12:38 am
If you were Registered and logged in, you could reply and use other advanced thread options
>
>> me@tadyatam.invalid wrote:
>>
>> >
>> >> I've run into a conflict running AdAware 1.06 on a
>> >> system with F-Prot 3.16b. AdAware locks up the system
>> >> when it tries to open a file that F-Prot detects as a
>> >> problem. F-Prot has reported a number of false
>> >> positives on this system. Both programs have the latest
>> >> updates.
>> >>
>> >> AdAware 1.06 is running fine on another system with
>> >> NOD32.
>> >>
>> >> Chas.
>> >>
>> > What problem F-Prot detected?
>> >
>> > J
>> Please give details on the issues (names of files, exact
>> text of any error messages, etc.) - we have F-Prot and
>> Ad-aware 1.06 and I've
> put
>> that combination on many clients' computers and have seen
>> no
> problems.
>> That doesn't invalidate your experience of course. It
>> would be good
> for
>> you to give us the details, though.
>>
>> Malke
>
> Win98SE with all current updates, IE 6x nothing running in
> End Task but Explorer and Systray. Epox mobo with 850
> Athlon, 512MB PC133 memory 40GB & 30GB IBM 7200 RPM ATA100
> HDDs and so on.
>
> System have been running flawlessly for a long time. Had no
> problems with AdAware 6.0 Build 181. This seems to be an
> AdAware problem because I have freeze problems with F-Prot
> disabled.
>
> Running "Perform Full System Scan" PC will hang at
> C:\Windows\System\Powerprof.dll and requires a Reset. It
> gets further before it locks up when starting with "Perform
> smart system scan" or "use custom scanning options".
>
> I'm going to uninstall 1.06 and try 1.05 to see if it
> helps.
>
> F-Prot 3.16b heuristics gets a little touchy on this
> system. For example it flags a .TXT file that I wrote with
> instructions for a Quick Launch Tool Bar Button to shut
> down the system, as a trojan! Also other false positives
> that I haven't run into before with F-Prot set to the
> maximum coverage in an on-demand scan.
>
> Chas.
>
Probably AdAware problem, unrelated to F-Prot.
My SE v1.05 (five) w/ defs R42, did hang in "Scan volumes for
ADS" mode while scanning a subdir containing known malwares
(dialers). I killed the process after about 4 min's. Ditto using
defs R40. Nothing else was running (exc. explorer and systray)
at that time.
Those malwares were detected as such by F-Prot (DOS) weeks, if
not months, ago. I would not conclude that SE v1.05 and F-Prot
interfere w/ ea other.
Ver.6 b.181 did not have that problem.
J
--
Replies to: Nherr1professor2doktor31109(at)Oyahoo(dot)Tcom
| 
XML site map