From: John Doe on 28 Nov 2009 18:59 I made a copy, using all default settings. Strangely/surprisingly, it did not have to jump out of windows during the process. Now I will format drive C and use the boot CD to recover. Be back in a minute (hopefully not from the abyss).
From: Fishface on 28 Nov 2009 19:24 John Doe wrote: > Have you used it? Yes! I got my extended family and friends using it, and I made my employer buy it. > Does it automatically hide the copy so that any operational > partitions on the target drive remain the same letter? Uh, what? It creates a file, not a hidden partition. The file can be on another drive, or a network drive, or a DVD set, or, cough, a CD set. I guess you could have a hidden partition. TweakUI would hide a drive letter, as I recall. > Does it make a recovery boot CD? Yes. You can make a bootable pen drive, too. > Does it work with SSD drives? I don't see why not. > I will try it and post the answers to those questions and more...
From: John Doe on 28 Nov 2009 20:30 I am going to reply by starting a new thread. Whenever the importance of this particular dialogue is, the subject is of great value (to me).
From: Steven J. on 1 Dec 2009 13:36 On Nov 28, 1:29 pm, Ray K <raykos...(a)optonline.net> wrote: > Fishface wrote: > > Ray K wrote: > >> AdAware, Spybot, AVG and Avast all give my system a clean bill of health. > > > Try this one: > >http://www.malwarebytes.org/mbam.php > > I just finished scanning with it. Upon completion, it also gave a clean > bill of health. > > However, while it was scanning, AVG interrupted the scan three times. > The first time the message said WIN32: Patched LF [Trj]. Once I deleted > it, the malwarebytes scan resumed by itself until it next halted at > WIN32: Malware-gen. I deleted it and the scan resumed, halting a final > time at WIN32: Patched LF [Trj](yes, same message as the first time). > > It's almost like AVG was detecting problems in malwarebytes program. > > Ray What was happening with that was when MalwareBytes was accessing the infected file, AVG detected it detecting the file and put up a notification before MalwareBytes reported the infection. If you have what I think you have, the file that is affected with this particular virus is atapi.sys which is a required system file and why MalwareBytes and AVG wouldn't delete it. You need to replace the atapi.sys file on the infected installation with one from a Windows CD or from a known clean system - replace the one in C:\Windows \system32\drivers folder and in C:\Windows\ServicePackFiles\i386. I recommend pulling the drive and slaving the drive to a known clean computer and going from there. Cleanest tip is to reinstall the OS. Another tip: Don't have 2 actual anti-virus programs installed on your computer at the same time (re: AVG and Avast) Remove 1 - my suggestion is to choose Avast over AVG. Take care,
First
|
Prev
|
Pages: 1 2 3 4 Prev: Molex to Sata power cable Next: Change memory timing (1T or 2T) on Intel DP35DP? |