AdAware 1.06 conflict with F-Prot 3.16b

* * Chas · External Since: Aug 27, 2005 Posts: 178

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.

me · External Since: Dec 27, 2004 Posts: 201

This message is not archived

Malke · External Since: Jul 13, 2005 Posts: 15

me DeleteThis @tadyatam.invalid wrote:

> "* * Chas" wrote in
>
>
>> 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
--
"I have a cunning plan..."

Peter Seiler · External Since: Sep 10, 2005 Posts: 37

me DeleteThis @tadyatam.invalid - 10.06.2005 15:27 :

> Which F-Prot (DOS/Win's) is it?

why post ~120 quoting lines again (snipped) only for that short single
question?

--
by(e) PS

spam will be killed

Frode · External Since: May 30, 2005 Posts: 6

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Seiler wrote:
>> Which F-Prot (DOS/Win's) is it?
> why post ~120 quoting lines again (snipped) only for that short single
> question?

Amen to that. This is the first out of the last 6 or so messages in this
thread I've seen a reply in (I don't scroll down unless the actual reply
starts in my 25 line preview window).

- --
Frode

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFCqcb1Nx8IkioE8tMRAgh7AKCc5rcc8U51TgnS/YFefr4KmGghpACggway
taUyStKPWSKR6en3t9U5mko=
=X/tl
-----END PGP SIGNATURE-----

* * Chas · External Since: Aug 27, 2005 Posts: 178

"Frode" wrote in message

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Peter Seiler wrote:
> >> Which F-Prot (DOS/Win's) is it?
> > why post ~120 quoting lines again (snipped) only for that short
single
> > question?
>
> Amen to that. This is the first out of the last 6 or so messages in
this
> thread I've seen a reply in (I don't scroll down unless the actual
reply
> starts in my 25 line preview window).
> - --
> Frode
-----

I've run into this myself and I've tried to correct my own messages.
With so many different message programs it's had to control what
others do.

I mainly use OE 5.5. what line width do you recommend?

Chas.

* * Chas · External Since: Aug 27, 2005 Posts: 178

"* * Chas" wrote in message

> > >> >> >> 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.
<snip>

I installed the latest version of F-Prot for Windows 3.16c and so far
AdAwareSE 1.06 is running without a problem (running Win98SE). So far,
so good.

I installed F-Prot 3.16c over 3.16b. The new version seems to be a
little faster running an on demand scan but I didn't time the 2
versions.

Chas.