NOD32 Command-Line Scanner Bug

The NOD32 command-line scanner has a bug by which it fails to scan any files at all if a path is specified which ends in "*.*" (that is, scan all files in a specified folder). I have attached a screen shot which illustrates this.

It seems that NOD32 will scan all files in a folder only if you omit the "*.*". This is plain weird. Unfortunately, it also causes a problem to programs that run NOD32 in this way: the screen shot shows the result when a file compressor program (Archive XP) tries to scan files using NOD32.

 

This issue will be resolved in the beta and, of course, the next program component update.

 

Thank you.