Thanks for the heads up on this. It also seems to have flagged one of
the Acrobat DLLs. Only note w/ those instructions is if you just have
regular NOD32, the paths are slightly different.
Anyway, the fix worked like a charm!
John Valenti wrote:
> Earlier today NOD32 had a virus definition file that included a false
> positive for the fah*.exe (Stanford protein folding client).
> Unfortunately, instead of quarantining the fah files, it made the
> computer non-functional. I have four dead computers here in LIR from this.
> I've finally figured out that the cause was NOD32, and this ESET
> knowledgebase article claims to have the fix:
> There is more information at the Wilder Security NOD32 forum:
Department of Sociology
316 Berkey Hall
Michigan State University
[log in to unmask]