Ok,I downloaded and installed the free version of EEK,and ran a scan. It found 1 piece of malware and registered it as two pieces for some reason. It also reported it as being "no risk"
Here is exactly what it reported "Application.InstallDrive(A) no risk".
My options were to delete it or quarantine it,but there was no "ignore" button. Correct me if I am wrong,but if I quarantine it or delete it,my drive A will be useless.
@sneakypete You still have a floppy drive???
No, I think all it will do is prevent installations from the floppy... It will still be fine for data transfer. It's a registry hack, so it is fixable. Quarantine, if you want to, and reverse the quarantine if it is problematic.
How can it be malware,and no risk?[/size]
There are many things that are safety tweaks, that the creator or manufacturer call industry spec, but technically leave a risk vector, or programs that technically are not able to be classified as malware because their installation method gives notice... These programs are called PUPS in the industry. Risk is subjective at that level, because technically, the user approved the action ('wants' it)... It is a distinction in nomenclature.
But none of the above, to include the floppy thing are addressing your current problem - For all intents and purposes , it came up 'clean'. So you don't have a system wide problem - no viral payload was installed. That's what I was worried for.
BTW,I see no icon on my desktop to click on to run checks. Did I screw up somehow on the installation? Never heard of a security software program without an icon.[/size]
No, I'd say not... They changed their install a while ago to make it more convenient for end users, they probably changed it back the way it was. I really don't know, because once it is installed, it is portable... So I keep a live copy in my machines, and copy it out to my service thumb from there (I don't use the brandy new installation much). In fact, the copy on my service thumb updates with the rest of everything on it if the thumb finds itself to be plugged in at home (in my server).
Long story short, I dunno directly, but probably not your fault... Keep it in there and run it now and then to keep ZA honest, and be happy. Worst case, next time you'll have a back up AV ready to go if you have trouble.
Nope,I'm good. I had everything restored before I made the original post. I was just seeing if there was something I could do to prevent this from happening in the future.
Excellent. Tho I made you jump through hoops for nothing, sounds like. Better safe than sorry.

One last thing: Restart the machine and run FF... If it doesn't come back on the fresh boot, it's fer sure.
Your quick thinking and action has served you well.

PLEASE ping me when you start the new thread.[/size]
10-4