S Salt_Peter Jul 23, 2003 #2 Best way would probably be to identify the virus, then check if special considerations should be taken to remove/ clean a given virus. You can try here: http://vil.nai.com/vil/default.asp http://www.symantec.com/avcenter/ http://www.cert.org/other_sources/viruses.html This way, executing a W2K repair + SP won't seem like a waist of time. You might also consider booting to a recovery console using W2K CD to use the fixmbr command. http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn ol/windows2000serv/tips/recovcon.asp My point is: define what you are dealing with so as not to take unneccessary steps towards a solution. What exactly does the virus do?
Best way would probably be to identify the virus, then check if special considerations should be taken to remove/ clean a given virus. You can try here: http://vil.nai.com/vil/default.asp http://www.symantec.com/avcenter/ http://www.cert.org/other_sources/viruses.html This way, executing a W2K repair + SP won't seem like a waist of time. You might also consider booting to a recovery console using W2K CD to use the fixmbr command. http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn ol/windows2000serv/tips/recovcon.asp My point is: define what you are dealing with so as not to take unneccessary steps towards a solution. What exactly does the virus do?
