24/08/2009, 04:19 AM
Alright so I was playing FFI on the wonderswan (On oswan emulator to be precise) until BAM! I randomly get this error message from PG2
Alright so I thought it was just weird so I closed PG2 and opened again and still kept getting those messages appearing so I reinstalled it and still those messages appear.
So, um yeah I need help, also I do have NOD32, apparently one version of it considers it a virus
Although I somewhat don't think it has to do with my problem because I haven't updated NOD32 and everything's been fine until today.
Alright so I thought it was just weird so I closed PG2 and opened again and still kept getting those messages appearing so I reinstalled it and still those messages appear.
So, um yeah I need help, also I do have NOD32, apparently one version of it considers it a virus
Phoenix Labs Wrote:At least, according to NOD32.this article was posting in feburary 2008 By the way
ESET, the makers of NOD32 Antivirus, were recently added to Bluetack’s level 1 blocklist due to some P2P activity Bluetack detected from an ESET netblock. Despite assuring an ESET representative that the level 1 list was doing its intended job correctly by blocking an organization with a suspected P2P presence, and that you, our users, do indeed choose to run PeerGuardian specifically for this purpose (and that those in our community who trust ESET could very easily set an allow entry for them), Bluetack apparently got a frivolous legal threat from them.
ESET’s solution? To classify PeerGuardian as a virus.
So if you’re a user of NOD32 you will have to make sure it knows PeerGuardian isn’t a threat. Or do what I would do: switch to an antivirus that doesn’t classify legitimate applications as a virus just because it conflicts with its company’s interests. Maybe Avast, or Symantec.
Edit: It appears ESET has reconsidered their decision, and PeerGuardian will be out of their definitions in a future update.
Edit 2: I’ve been informed PeerGuardian was classified as a general malware, not as a virus.
Although I somewhat don't think it has to do with my problem because I haven't updated NOD32 and everything's been fine until today.