PDA

View Full Version : NOD32 on demand scanner... doesn't:


SG1
August 8th, 2004, 02:51 AM
-- My original post's down further a bit --

After earlier discussion w/BlackSpear I uninstalled the AV, reinstalled it, rebooted: same thing. Scanner does not work, period.
Have run Adaware, Trojan Hunter, Hijack This, S&D and they all show nothing amiss, so... ideas, anyone?
Again, rest of NOD32 (including updates) works, except the scanner.

If this can be fixed, great, but until then or if it can't be fixed, can anyone recommend next best file scanner? Just a scanner/fixer if there is such a standalone critter, as rest of NOD32 works or seems to be OK.

---------------------------------------
Orig. post starts here:

I suddenly can't fire up the file scanner - fatal exception OC at f000:0000814d everytime, starting tonight. Do I have to reinstall the program?
And, when booting, I see comment "Trend ChipAway Virus(R) On Guard." Ah... what might that be?

Thanks for help/ideas, SG1 (Pat) - an unhappy camper w/out NOD32.
(Rest of the program seems to be functional, but for scanner). ;-(

Blackspear
August 8th, 2004, 02:56 AM
Are you able to perform a scan in "Safe Mode" ?

Cheers ;D

SG1
August 8th, 2004, 03:09 AM
BlackSpear;
You mean restart PC in safe mode, then scan? If so, no, hadn't tried that yet.
SG1 (Pat)

Blackspear
August 8th, 2004, 03:18 AM
{QUOTE-> ...You mean restart PC in safe mode, then scan? If so, no, hadn't tried that yet... <-QUOTE}

That's the one ;D

Have you also run Spybot Search and Destroy, as well as AdAware? What do they show?

Cheers ;D

SG1
August 8th, 2004, 03:19 AM
Adaware Plus and S&D show nothing found.
SG1 (Pat)

Blackspear
August 8th, 2004, 03:28 AM
{QUOTE-> ...I see comment "Trend ChipAway Virus(R) On Guard." Ah... what might that be?... <-QUOTE}

Trend ChipAway Virus(R) On Guard, is your Motherboards BIOS protection.

I would reboot into "Safe Mode" by pressing F8 on start up, and then try running a scan with Nod32: Start> All Programs> Eset> Nod32 (not the control centre)

If this doesn't work I would uninstall Nod32, including the Eset folder found in Program Files, and then reinstall Nod32.

Let us know how you go...

Cheers ;D

SG1
August 8th, 2004, 03:30 AM
Will try it; many thanks for ideas. I love this place, 'cos of so many nice, helpful folks like you. ;-)

Best, --SG1 (Pat)