We suspect Anniversary free edition Adaware's live AdWatch giving FP when we open Omnipage Pro 16......run every scan in the book, Adaware & McAfee, cant find anything......yet when we turn on AdWatch live & start Omnipage, it reports win32backdoorsdbot......new machine running WXP Pro, full McAfee virus & firewall......tried lots of things......pretty sure it has to be the way Omnipage activates &/or loads....

Have now turned off AdWatch live & getting on with our work!

Hey, ho....

Hi CHC!

Thanks for posting!
We will investigate this issue further.

Regards,

LS Pekka

Hi again CHC!

I tried to reproduce the issue testing with Omnipage 16 Professional and also with the Omnipage Service Pack 1 (English) installed (Omnipage Pro 16.1) but I could not reproduce the issue. Would it be possible for you to provide some more information regarding at which exact moment the detection of the win32.backdoor.sdbot object occurs when using Omnipage 16 Pro?

Regards,

LS Pekka

Yes......having just re-activated it with a new activation number from their US server.......having read around this a bit, suspect it is something to do with the reaction of their server in the US and the program itself.....

Cheers

Colin

Hi!

OK, If that is the root of the issue i´ll hope it sorts out

Forgive me, but I think you're missing the point.....it seems this FP is all to do with servers & clients (we're not techies), & so we won't be using AdAware because it keeps alerting with this FP & then 'cleaning' this perfectly good program from our boot sequence........it's AdAware's FP, not us or good old Omnipage.....

Hi CHC!

As we haven´t been able to reproduce the issue would it be possible for you to post the Process Watch (one of the Ad-Watch Live modules) log file that would allow us to pinpoint the file process that is detected as win32.backdoor.sdbot and blocked? The log file can be accessed via the Ad-Watch Live interface, under "Process". Then click on the "Export Detailed Log" link. Se image below.



Regards,

LS Pekka