@GuitarBob
it's not easy they are almost the same type of file, right now I try first to use cab code, then I fail back to ole2
but it seams that the cab code cannot handle all cab files, so I'll get rid of this messages or try to workaround it.
I've already tried to fix it, but I cannot make random names for extracted files, since the ole2 scanner
wouldn't work anymore (office docs need to have specific file names when extracted)

Okay, so I let the scan finish. I'm not sure how long it took. I'm guessing around 3 hours. It did, in fact, finish and at the end there were 29 viruses found...Now what? Clamwin is configured to quarentine the files. Is that enough? And, still, why so many error messages?

since the cab code skips the archive, so it's passed to the ole2 code that doesn't pick the correct filenames to extract and since there are a lof of garbage in file names, clamav tries to sanitize it by replacing invalid chars by a _, this causes a lot of name clashes, but I preferred to warn instead of silent ignoring.
Right now the possibilities are two:
a) get rid of the message and ignore it
b) try to generate a random valid name for each file that cannot be created (this may be difficult since the code is almost filename dependent)

I've noticed that when I get these messages, there are a lot of them, and they are all together in a directory. Maybe you could start counting them as you scan a directory, and when there are X number of OLE2 counts, you could assume this is the problem (no viruses) in that directory and do something then. Set count to zero for each directory.

How does some of the other AV software handle this?

Regards,

The abstract at the ClamAV Web site says they have "built-in support for RAR (2.0), Zip, Gzip, Bzip2, Tar, MS OLE2, MS Cabinet files, MS CHM (Compressed HTML), MS SZDD." So this includes OLE2 and MS Cab files. Did we lose the OLE2/MS CAB capability in conversion to ClamWin?

BTW, isn't the CAB format strictly Microsoft's? In other words, won't this apply only to Microsoft directories--Windows, Excel, Word, etc.? If that is true, it might help you, Sherpya.

Regards,

off course not, cab and ole2 stuff is the same of original clamav except the trick to scan first as cab, so also original clamav
will have these issues, but the name clash in file creation is not so common like in windows since windows has limited chars in filenames
while unix doesn't allow only /
the unix version silently overwrites the files if the name clashes I've simply decided to report the problem instead of ignoring it