j
Adwatch Bug in 1.06 [RESOLVED]
Started by
jeffw_00
, Jun 04 2005 07:18 PM
#1
Posted 04 June 2005 - 07:18 PM
j
#2
Guest_Andy_veal_*
Posted 05 June 2005 - 02:41 AM
Thanks for that jeffw_00,
I will try to pass that on to Lavasoft Research and Development.
May I ask how you found this out?
HJT?
I will try to pass that on to Lavasoft Research and Development.
May I ask how you found this out?
HJT?
#3
Posted 05 June 2005 - 08:25 AM
See this thread:
http://castlecops.co...ts_2_times.html
I submitted a bug report to lavasoft via their support page on May 30th regarding this issue. So far, I received the automatic generated reply from lavasoft and...
***crickets chirping***
Hope you have better luck Andy_veal.
http://castlecops.co...ts_2_times.html
I submitted a bug report to lavasoft via their support page on May 30th regarding this issue. So far, I received the automatic generated reply from lavasoft and...
***crickets chirping***
Hope you have better luck Andy_veal.
#4
Posted 05 June 2005 - 08:39 AM
#5
Posted 21 June 2005 - 11:47 AM
umm - the two taskbar icons were a dead giveaway.
as for the details I use Mike Lin's Startup.cpl
/j
Just to confirm this occurrence of two task bar icons
for Ad-Watch under Windows XP. This is definitely
reproducible. It happens on a fresh install or an
install over a prevoius copy of Ad-Aware/Ad-Watch
SE Plus.
#6
Posted 21 June 2005 - 04:48 PM
And it is 3 weeks later, and still no response on this "bug" what so ever from Lavasoft...
Even after another email. Very disappointing.
Even after another email. Very disappointing.
#7
Guest_Andy_veal_*
Posted 22 June 2005 - 10:25 AM
I am truely sorry for this.
Though I can not help you with Lavasoft contact, I am personally not in contact with any of the Lavasoft management.
Have you all solved your problems?
My advice would be to uncheck a startup item in msconfig.
Though I can not help you with Lavasoft contact, I am personally not in contact with any of the Lavasoft management.
Have you all solved your problems?
My advice would be to uncheck a startup item in msconfig.
Edited by Andy_veal, 22 June 2005 - 10:25 AM.
#8
Posted 22 June 2005 - 03:52 PM
Hi Andy
Yes I fixed the problem a while back by removing the offending registry entry.
As an Ad-Aware "Pro" version user, I'm glad I didn't have to wait on official support
Yes I fixed the problem a while back by removing the offending registry entry.
As an Ad-Aware "Pro" version user, I'm glad I didn't have to wait on official support
Edited by hexaguano, 22 June 2005 - 03:55 PM.
#9
Guest_Andy_veal_*
Posted 26 June 2005 - 03:51 PM
I am truely sorry about this.
I hope within the future this bug can be resolved and Lavasoft can respond to their paid customers.
I hope within the future this bug can be resolved and Lavasoft can respond to their paid customers.
#10
Guest_Andy_veal_*
Posted 26 June 2005 - 03:51 PM
Since this issue appears to be resolved ... this Topic has been closed. Glad we could help.
If you're the topic starter, and need this topic reopened, please contact a staff member with the address of the thread.
Everyone else please begin a New Topic.
If you're the topic starter, and need this topic reopened, please contact a staff member with the address of the thread.
Everyone else please begin a New Topic.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users