TonyKlein

Yes, I know, but editing boot.ini via Msconfig doesn't really present an advantage over manually editing or rreplacing boot.ini as suggested by others.

whoops, sorry...

Windows 2000 doesn't have the Msconfig utility...

OK, here's some reading: Description of the Windows 2000 Recovery Console Pay particular attention to the 'Fixboot' command. So that should be Fixboot c: if c: is the drive your boot.ini should be written to Windows 2000 - Installing the Recovery Console When Windows 2000 won't boot And here's a Google Groups thread with a few additional pointers. Good luck!

In Win XP you can boot Recovery Console and use the Bootcfg /rebuild command to repair the boot.ini. I believe in Win 2000 that's the Fixboot command. Let me Google a little to see what I can find out...

Go to Start > Run > Regedit Drill down to the HKEY_CURRENT_USER\Software\FreshDevices subkey ('folder') RIGHTclick the FreshDevices subkey, and choose 'delete' from the context menu. That will stop CCLeaner from 'detecting' the application.

Found two more lines to add. Here's the final version: [ExamDiff] LangSecRef=3024 Detect=HKCU\Software\PrestoSoft\ExamDiff Default=True RegKey1=HKCU\Software\PrestoSoft\ExamDiff\Recent Left Files RegKey2=HKCU\Software\PrestoSoft\ExamDiff\Recent Right Files RegKey3=HCKU\Software\PrestoSoft\ExamDiff\Settings|File 1 RegKey4=HCKU\Software\PrestoSoft\ExamDiff\Settings|File 2

In that case, close CCleaner should you have it open, then download Winapp2.ini if you haven't already, and place the file in the Program Files\CCLeaner folder. Open the inifile in Notepad and add the following: [ExamDiff] LangSecRef=3024 Detect=HKCU\Software\PrestoSoft\ExamDiff Default=True RegKey1=HKCU\Software\PrestoSoft\ExamDiff\Recent Left Files RegKey2=HKCU\Software\PrestoSoft\ExamDiff\Recent Right Files Save in 'File', then launch CCleaner. You ought to see ExamDiff listed in Applications > Utilities.

Comodo was tested by the folks responsible for this reputable AV testing website, and its detection was decidely poor: NOTE: Comodo test results are in fact not included into these online test resuilts; I have this information "straight from the horses's mouth" in a private AV/AT forum post. No definitive proof of it being a rogue product, although I did come across this article: http://www.emailbattles.com/archive/battle..._aadgdfdddh_ah/ Whatever the case, quality wise it is not (yet) a viable option.

Very likely, but have a look yourself: Open Regedit, and drill down to the HKEY_CURRENT_USER\Software\PrestoSoft key Check whether the subkey directly below is called "ExamDiff" without the 'Pro', and whether you have identical Recent Left Files and Recent Right Files subkeys there If so, all you need to do is indeed remove the 'Pro' Part: RegKey1=HKCU\Software\PrestoSoft\ExamDiff\Recent Left Files RegKey2=HKCU\Software\PrestoSoft\ExamDiff\Recent Right Files Keep us posted on what you find. That way we can ask TwistedMetal to add support for that version as well.

I submitted an entry for ExamDiff Pro only days ago, and it is included in the latest winapp2.ini [ExamDiff Pro] LangSecRef=3024 Detect=HKCU\Software\PrestoSoft\ExamDiff Pro Default=True RegKey1=HKCU\Software\PrestoSoft\ExamDiff Pro\Recent Left Files RegKey2=HKCU\Software\PrestoSoft\ExamDiff Pro\Recent Right Files If you're not running the Pro version, you'll need to adapt the registry paths, but with the help of the above that shouldn't be too hard. BTW, I just noticed there's a small copy and paste error in one line of the winapp2.ini ExamDiff Pro entry: RegKey2=HKCU\Software\PrestoSoft\ExamDiff Pro\Recent Right File should be: RegKey2=HKCU\Software\PrestoSoft\ExamDiff Pro\Recent Right Files I already PM'd TwistedMetal, but until the error has been correected, you may want to edit winapp2.ini manually!

It has been suggested before, but you don't want such an option checked by default. System Restore can be a life saver indeed... Note, you can of course disable System Restore on that Slave drive. (Right-click My Computer > Properties > System Restore Tab > Settings.) That will also remove all SR files on reboot.

No prob at all, and of course welcome to the board! It's just that it's a good idea prior to posting your own proposed winapp2.ini entries to check the existing ones so as to avoid duplication.

Ah, right, yup, that would be the faster way.

Oh yes, it is (see screenshot). CCleaner very sensibly removes (only) the older Prefetch entries. However, it is NOt recommended to clean out the entire contents of the folder. Once again, it is there for a reason. Here's some reading: http://www.edbott.com/weblog/archives/000024.html

you're very welcome - glad to help.

A System Restore will not restore a Start Menu shortcut. Various ways to recreate one. Here's one: Rightclick your start button, and choose "Explore all users" or "Explore" (depending you want the shortcut to appear in every user's Start Menu or not) Drill down to the location you want the shortcut to appear in, rightclick an empty spot > New > Shortcut, and you're off. Even easier, you can also simply grab the shortcut you moved with the RIGHT mouse button, and drag it to your Start Button. After a sec, the Start Menu will pop up. Keeping the Right mouse button depressed, drag the shortcut to the preferred location, relaease the mouse button, then choose 'copy here' from the context menu.

Kaspersky is currently among the very best you can get, detection wise. That includes trojans and spyware, areas where some other AVs are often less than fully competent... Personally, I use a Nod32 AV + BOclean AT. (+ LooknStop firewall + Ghost Security Suite for kernel level Application and Registry protection) Everything works together just fine, and I'm extremely happy with the combination. That said, everyone is sure to have his or her pet program, so these are just my 2 cts...

Try using System Restore to revert your system to a moment in time just before this happened.

Also, it's IMHO NOT a good idea to have CCLeaner delete the contents of the Ad-Aware Quarantine folder by default: This folder serves a very useful purpose: notably, in case of AAW accidentally identifying a legitimate file as malware, it allows you to safely restore it. Also, more generally speaking, log files are there for a purpose, and they can be extremely informative, as well as helpful in resolving issues. Again, I really feel I have to advise against blindly nuking anything that happens to have a *.log extension...

That is normal, as your Desktop Recycle Bin is a (registry based) so called NameSpace object. It is good to know, but it seems a bit of a hassle to edit winapp2.ini for an isolated occurrence such as this one...

Not sure whether that would make a difference, but at the moment I'm not at my own computer, and I have no time to check it myself right now. Feel free to give it a try yourself. You will however need the |REMOVESELF parameter to remove the folder.

Excellent, thanks. Looking forward to it.

Glad to hear you like it.

As I said, not that I'm aware off. It may well be possible to write a vbs script to accomplish just that, but that's not something I'm comfortable with. Maybe someone else?