Now I really need your help!

[scirious]

Well, people, now I really need your help.

As I said in some previous posts I have an old version of BSPlayer that makes NOD32 v3.0 crash badly. I've reported it to support, but they insist in telling me that nothing happens at their lab and scans is performed as it should. However, EAV always fail to do this specific scan. And only v3 as with v2.7 everything is ok.

I even tried support suggestions but it didn't work. Now I need someone that could test this file to me and report the experience. I'm running the 64-bit version of NOD in Windows Vista Ultimate 64-bit with all options at max. Could anyone test it to me, please?

TIA,
Scirious.

[ASpace]

ESET have created exclusions . Add these folders/files as excluded :

After you add them , they will look like that:
C:\Test\BSPlayer\*.*

You should manually edit them to make them look like that (with one star only):
C:\Test\BSPlayer\*

[scirious]

O know I can exclude them, but I'd like someone else to test them.

[krokodil_bb]

Known bug, I sent similar bug to eset /m.majtaz/ last week.
Scan completed successfully.

195615

[scirious]

Well, thanks. If you can complete the scan then I don't know what it might be here. I don't receive this error. My computer just hangs and becomes unusable.

How long did it take to complete the scan?

Tia,
Scirious.

[krokodil_bb]

I tested on w2ksp4, NOT vista..., eav version 3.0.566.
As I said before, eset know about this bug with nod kernel, and they must fix it. Exclusions can't help, it can be replicated with any runtime-archive exe file...

[scirious]

Did they acknowledge the bug? If so, and considering your results, I'm lead to believe that the support has, at least, lied to me. ???

[krokodil_bb]

{QUOTE-> Did they acknowledge the bug? If so, and considering your results, I'm lead to believe that the support has, at least, lied to me. ??? <-QUOTE}

No, I still haven't answers yet about this and other bugs. It's only 7 days and I'm only betatester, not pay user.

25.11.2007 I sent mail with steps how to exactly reproduce this bug /it not crash always as you may think/.
Today early morning eset posted me answer to another bug/mail that I sent 13.11.2007. So 2weeks...

If you are pay user, write to eset again and again until your problem is solved.

[epdom]

{QUOTE-> ESET have created exclusions . Add these folders/files as excluded :

After you add them , they will look like that:
C:\Test\BSPlayer\*.*

You should manually edit them to make them look like that (with one star only):
C:\Test\BSPlayer\* <-QUOTE}

Is this true for all folders one would want to mark as exclusions?.

Cheers

[ASpace]

{QUOTE-> Is this true for all folders one would want to mark as exclusions?.

Cheers <-QUOTE}

By default EA/ESS puts the exclusion in a variant \*.* (star dot star) - this means that any files in the folder won't be scanned (e.g. all files just in the folder C:\Test\ won't be scanned) . However anything in the subfolders will be test (e.g. with *.* files in C:\Test\Subfolder1\Test2\ will be scanned)

Making the exclusion in a variant \* (one star only) means that anything (files and folders + subfolders ) won't be scanned :)

You can test it and see yourself

[krokodil_bb]

7.12.2007 - Technical Support confirmed me this is a bug.