.pif mails that avast! does not says is Virus ????

[Lars-Erik]

After I got the latest DB update today (10 minutes ago) I got two mail with .pif attachments marked as [suspicous] by avast! but even when saving them there is no virus warning.

What should I do with them (does the avast! team like to check them, they have all usual virus-mail characteristics)?

BTW:  The Explorer shell extension has no "Scan..." for .pif files?  Where do you setup what files has this extension?

[igor]

Yes, if you could send them to virus(at)asw.cz, it would be nice. The warning is given just because of the suspicious extension, but obviously the virus has not been detected.

As for the shell extension... it may be a problem of Windows itself. It seems that the HKCR\* key doesn't apply for .pif files (at least on Win98).

[Lars-Erik]

Yes, if you could send them to virus(at)asw.cz, it would be nice. The warning is given just because of the suspicious extension, but obviously the virus has not been detected.

OK, mailed them both there...  Good hunting :-)

As for the shell extension... it may be a problem of Windows itself. It seems that the HKCR\* key doesn't apply for .pif files (at least on Win98).

Anything I can add to the registry to fix this (can I just add some keys, or copy them from another filetype or something like that)?

[RejZoR]

*.pif doesn't have Shell extension command under XP too...

Guess it can be achieved with manual reg editing,but currently i don't know the commands... I'll try to find out...

[igor]

Anything I can add to the registry to fix this (can I just add some keys, or copy them from another filetype or something like that)?

Go to HKCR\*\shellex\ContextMenuHandlers, copy the avast subkey and put the same (subkey) to
HKCR\piffile\shellex\ContextMenuHandlers
- hopefully it will work.

[Lars-Erik]

Go to HKCR\*\shellex\ContextMenuHandlers, copy the avast subkey and put the same (subkey) to
HKCR\piffile\shellex\ContextMenuHandlers
- hopefully it will work.

Couldn't find anything on any ContextMenuHandlers. Not even on "exefile" (and that has the "Scan..." extension in Explorer)

[igor]

I didn't mean you should substitute the asterisk for the particular file types - the key really should be HKCR\*. That should cover all files... but apparently, it doesn't work for .pif. Ask Microsoft  

[Lars-Erik]

I didn't mean you should substitute the asterisk for the particular file types - the key really should be HKCR\*. That should cover all files... but apparently, it doesn't work for .pif. Ask Microsoft  

Aha, OK, then it worked.  But shouldn't avast! set this key on Win98 by it self during installation if this is a known bug ?

[RejZoR]

I throw such *.pif files into some folder and right-click on that folder and select Scan. Not so fast,but its not too complicated and it can take you like 5 sec

[igor]

But shouldn't avast! set this key on Win98 by it self during installation if this is a known bug?

It is a known bug now, when you noticed
I didn't know it before and nobody ever complained... I think it should be easy to fix.
(And if I understand it correctly, the problem is not limited to Win9x.)