Bloodlust

Basically. 199.80.55.xxx is being blocked...

I am a bitshare user and MBAM pro always treats files hosted from that site as a false positives as it's always blocked http://bitshare.com/files/ (resolved as 199.80.55.***) While I can add a file or folder in the ignore list, I can't select a domain which I want to exclude. Like bitshare for example is always 199.80.55.xxx if MBAM can include an option to manually it that would be cool. Also, while website blocking is a bit overrated I can easily bypass it if I use any browser proxy which sort of defeats the purpose. Please at least exlude bitshare which I don't think it's a malware site since it only hosts files or include a feature which websites can be excluded manually in your next update of MBAM pro.. thanks

I have installed v1.34 to try out. For some reason when I plug in my thumbdrive/external HDD it takes 10-15 seconds for the drive to be detected and appear on my computer. Removed it and all was back to normal.

Thanks, will try it out and report back.

Hi, thanks for the reply. I am on XP SP2. Anyway, I did a scan and these 2 files only exist in the system32 folder. I did unregister/register these 2 files but not dll's but ocx. Is there a difference? Anyway, could you provide me the link which I can d/l working dlls for these 2 files?

Well, I tried to install the VB6 runtimes but it just exits prompting that the installation wasn't successful.

Thanks, I will give it a shot and feedback asap.

It seems that I can't run MBM after installing as I get a runtime error of 50003. Hijackthis gives me the same problem. According to this site http://www.angelfire.com/biz/rhaminisys/vboledll.html it seems that I have the wrong set of common controls as described here : Error message boxes saying "Unexpected error" or "Error 50003" may be symptoms of an incorrect version of the common controls being registered. Microsoft have issued at least 4 versions of comctl32.ocx and 2 of comdlg32.ocx, comct232.ocx and comct332.ocx. All the versions of each component have the same GUID but they are not compatible. This breaks the rules of COM but Microsoft allow themselves to break their own rules however much havoc it causes amongst their customers. A compiled VB program will work with the set of controls it was compiled with or later versions. However, programs complied with a newer issue of one of these OCXs will not run if an older one is registered. If a VB5 authored program on this web site has this problem it needs the VB6 versions of the controls. If that's the case, please lead me to a link which I can download the correct set thank you...