IEspyad and SpywareBlaster

[Robyn]

I have IEspyad merged into the registry, I have just updated IEspyad tonight and discovered I had to run SpywareBlaster v3 again as some of the protection was removed after re-merging IEspyads lsit

Is this a conflict with the programs and am I still as safe running both of them despite the fact one removed the protection I have since re-enabled? :'(

Hi, Robyn. I had the same problem with Spybot and Spyware Blaster. My guess is that reinstalling or modifying one program can remove the kill-bits it can set into the registry. I also reenabled all protections and I haven't had a problem since. As for compatibility I have not heard of Spyad. I hope somebody else can answer your question there.

[Paul Wilders]

Looks like a database issue to me - no more, no less. Let's see if we can pont the IESpyad developer to this thread. In the meanwhile, I'd recommend enabling all protections.

regards.

paul

[eburger68]

Hi:

This is a known issue with SWB 3.0 and IE-SPYAD. The short story is that IE-SPYAD removes some invalid entries that SWB 3.0 sets and replaces them with valid ones. See this thread over at DSLR for a more complete description of what's going on:

http://www.dslreports.com/forum/rema...3441~mode=flat

Javacool is undoubtedly working on an update that will fix this.

Best,

Eric L. Howes

URL tags added to the link - paul

[Paul Wilders]

Eric,

Thanks for attending this fast - much obliged!

regards.

paul

[javacool]

Yep - this is indeed something that will be fixed for SpywareBlaster 3.1.

So no worries.

Best regards,

-Javacool

[Robyn]

Sorry about only getting back now but posted this just before I had to shut down my computer for the night! Thanks for the links and the re-assurrance that I am still protected even though I re-enable SWB after IE Spyad - I will continue to use both now, I was alarmed when I noticed the 'unprotected' item re-listed (thought something had attacked the program on me )
Thanks again to everyone.