Quote:
Originally Posted by Nanogrip Yeah I tried Panda as well years ago. It also sucked, and even left behind/allowed some residue of some bug behind that was caught with a better antivirus. |
Hmmmm..... I guess I'm lucky I had to format that installation and reinstall from scratch.
I did notice there was something it had left behind (In my Registry). During startup I'd get this message about a program not being able to run because it wasn't installed??? Still that doesn't mean I did a clean reinstall to eliminate something Panda left behind. Instead I installed a couple of brand new hard drives. Seems like the MBR was on what the motherboard/OS thought should have been "C:" (instead of what I thought was "C:" drive). The result was that none of the tricks to fix the MBR worked. I mean it's not like the motherboard makes have to supply clear documentation (drive assignment was not clearly labeled), or that when I called a "Tech Support" person that he really needed to have a clue! (He told me something that was wrong because that information was not in the manual... go figure!)
(See I had 3 identical drives installed before... so I couldn't tell one from the other in BIOS - When I installed I told Vista to use the drive I had labeled for it. And I was none the wiser... until the other day!)
The "Silver Lining" to the situation is that I now know without a doubt that C: drive is the "0" drive on the controller and that all of the boot files are in fact installed on that drive. Which will save me serious headaches in the future. The serendipitous element is that Panda was fully deleted.

And while Kapersky is not as frugal with system resources as NOD32 was, hopefully it will provide superior protection.