Do these write errors seem normal to you? I have not seen them before on other scanned machines.

LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-9a0f8e934dbb0258\_15___\_0__M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-9a0f8e934dbb0258\_15___\@_M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-9a0f8e934dbb0258\_15___\@_M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-9a0f8e934dbb0258\_15___\@_M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-9a0f8e934dbb0258\_15___\__M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-add11679d175460b\_15___\_0__M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-add11679d175460b\_15___\__M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-add11679d175460b\_15___\__M_
LibClamAV Error: ERROR: failed to create file: c:\docume~1\fredch~1\locals~1\temp\clamav-add11679d175460b\_15___\__M_

Regards,

Fred Chateau

that's a MSI unpacking error, not to worry about

hi!

i have similar error-messages until i updated to 0.88.5 yesterday for the
c:\windows\temp-directory. the scan repeats endless.

fyi: i (have to..) use win98SE

greetings,

frank

clamav tries to unpack msi files with ole2 (office) extractor, since the signature is the same the doc extractor fails because filenames are wrong,
I've added a different logic like first try to use cabextractor then ole2 but doesn't work always

I have independently duplicated this error on WindowsXP Professional,
Windows 2000 and Windows98SE.

In some of the errors messages I saw forward slashs which looked like
a path seperator instead of back slashs.

Hope this helps.

windows works with both slash and backslash as path separator the problem is that since names are almost garbage is very likely you get name clashing, original clamav ignores it and overwrites without checking, I've changed it on win32 and it gives an error when a name clashes instead ignoring it that is a potential security issue (think a virus and then a non virus with same name that overwrites it)
my suggestion is just ignore it or disable ole scan at all, I've seen very few virus as word macros in the last times

hmmm...

>>my suggestion is just ignore it or disable ole scan at all, I've seen
>>very few virus as word macros in the last times

never mind, but this is not a good idea i think. makes the scanner half as useful.
...and "very few word-macro-viruses" means there ARE some outside in the dark...
...and all the virus-programmers reading this forum thank you for this hint...

frank

not quite true. Office 200 and higher have strict macro protection policy and would render those macro-viruses useless.

again, never mind! it is not my intention to make you angry
you make a good job here to give us folks such a good scanner for free, no need to
discuss this!

but if there is a functionality with this ole-scan in the software and it causes some
"strange" error- oder warning-messages (it calms me down that i`m not alone with this
errors...) it is helpful for you to have a feedback about this i think.
if this kind of scanning is not needed in daily life then its not clear for me why you
implemented it?

but its ok for me to ignore the warnings if you say "forget it, not important.", much better
than "oh my god, your system is heavily corrupted, do a 'format c:\'..."

frank

"forget it, not important."

thanks a lot, i`m glad i don´t have to worry about it

frank

Printing thousands of bullshit messages does matter. There's no way I can see the meaningful
messages in a forest of crap.

these messages are not "bullshit". Although not critical, they should not happen under normal circumstances and printing them helps us fix problems. Only a few users report them so it is not a widespread problem.

I took your previous response "forget it" to mean that it wasn't important enough to fix.
As long as it's on the fix list, I'm satisfied.

not so easy indeed, a partial fix is already in, but doesn't applies always, m$ decided to make .msi files like ole2 container just like office document, but really they are a sort of cab archives