It's NOT imho a conflict. It's a bug (or feature? ) in Nod.
Remember that you were not able to access the file even if avast was completely disabled (so it's not a conflict).
Anyway, am glad we've sorted this out.
unfortunatly it is a conflict between Avast4 and Nod32
a few days ago I uninstalled Avast4 (to check some iNEWS problem) then installed eTrust 7 promo as my on-access scanner and unchecked both NOD32kernel and nod32kui without unloading/renaming amon.vxd..
When I tried to create eicar.com file , eTrust detected and stopped it at once..
I do not understand exactly why Avast4 - only - is conflicting with Nod32 ?
:'( :'( :'(