Is This Normal In a NOD32 Scan?

When I run a full scan with NOD32, I get a bunch of these, and others very similar..........

Windows\Driver Cache\i386\dirver.cab >>CAB >>smm\6000.gpd-archive damaged - the file could not be extracted.

Is this normal also?

PS...The numerical figure in the 6000.gpd, is not always 6000. It varies

 

Yes, it's normal. It mean the archive is corrupted and thus NOD32 can't extract and analyze them.
But there're sometimes NOD32 report a corrupted file but not all the time the file is corrupted, sometimes it's in a format that NOD32 doesn't support.

 

Sorry if these are dump questions, but why is the archive corrupted. How did it become corrupted. Are the files important to the Windows operating system? By being corrupted, will this cause any kind of problems with the OS? My OS is XP Home/SP2.

 

well im sure its not corrupted, its just nod32 didnt support that kind of archieve

 

Thanks cupez80.

 

I assume some file in the archive spans over multiple volumes which causes the error.

 

Well, can't NOD32 automatically detect volumes? I think KAV and other AVs do that? Or perhaps I'm wrong!

 

It does, and if it can't find the next volume, and error occurres.

 

I just ran another full scan with NOD32, which made me come back to ask another question.

Why such a long time to complete the scan?

I have NOD32 set up with Blackspears settings. My OS is XP Home/SP2. The total files scanned were a little over 148,000. The scan took 1hr, 53min. Seems long to me for the amount of files scanned. Is it because of the time it took NOD to scan those damaged archive files that I posted in the start of my thread?

 

Maybe you have a lot of archives and runtime-packed files which take a long time for AH to emulate.

 

Hmmm. Maybe I'll disable AH, and run a test full scan just to see if there is a time difference. Even if it turns out NOD scans faster with AH disabled, I won't leave it that way. I feel better with AH enabled.