Out of Ideas

Hi Marcos,

That we are. Can you offer a solution to this problem or will it be a matter of dumping the cards and reformatting two systems from scratch, with multiple partitioning software. It's not a road I am looking forward to travelling down.

Do you know of a way I could edit the registry to disable some scan settings?

Regards

Chiana

 

Hi Chiana:

Please try running this command line:

c:\progra~1\eset\nod32.exe /local /scanmbr-

Report back your findings in triplicate.

 

Hi rumpstah,

Congratulations, you're my hero. Success!!!

[MOVE] [/MOVE]

Aren't you the clever one! You have saved me paying massive therapy bills and the loss of my hair. Thank you so much.

At least this is a temporary solution, I still suspect this is an issue with the JuztReboot card, but at least I can enable scanning.

rumpstah, go to the head of the class. Champion.

Best regards

Chiana

 

Hi Chiana:

Yay!

I want the "Platinum" star.

Actually I thought about this the other day, but I have been too busy to post (that is a good thing).

You can enable scanning with all options, just use the /scanmbr-. Since it is an external device, NOD32 is most likely confused by it and stops the scan process since it can not access.

If you uncheck boot sectors, can an On-Demand scan then be performed?

 

Hi rumpstah,

Platinum star - if it were up to me you could have that and the rest of the stars in the universe, planets included.

Happily, yes. I'll be changing all the profile options and all will be well.

The question still remains...NODv2.5 must employ a different method of scanning the MBR and boot sector for this problem to occur. But I'm happy a solution has been found.

Regards

Chiana

 

Exactomundo the same problem here, see my un-neccesary post https://www.wilderssecurity.com/showthread.php?t=82149.

 

I have the exact same problem and im not using that card, or any card of that kind.

 

OK, so as an interim solution disable Boot sectors in the on-demand scanner setup until the issue's fixed.

 

My findings in this thread https://www.wilderssecurity.com/showthread.php?t=82149, especially the last posts, might be of interest for people with this problem. It might not be a boot sector problem at all, according to the way i isolated the problem?

 

I'm back and am bumping this thread again.