SSMS only has control over the server state polling after SP1 by editing registry, based on the link you provided. You can only change its interval but not disable it.

Did you try to browse the location where the tool was installed? Could you find any executable file there?

Could these text editor be used to open current log file?

Did you try to add one more log file and empty the existing one then?

Yes, you can. Please make sure that you have all correct paths before detaching/attaching databases. Also, make sure both have the same service pack and hotfixes.

You do have quite limit scope to filter events. For example, you can modify security audit levels from an instance properties and configure SQL Server Agent Error Logs.

My understanding is...

Could you describe how you had backup of your database?

Did you have time to read this article?

http://www.computerhope.com/issues/ch000726.htm

May it help.

Did you have chance to read this white paper?

http://www.sunbeltsoftware.com/documents/dt_vss_whitepaper.pdf

May it help.

Did you check tempdb.mdf?

If you have to use log shipping, your scenario is normal. Otherwise, you may include DBCC SHRINKDB command in your optimization.

Did you check its ownership?

Check whether or not your SQL Server Agent is running

Did you check the recovery mode of the databases on each server?

Did you have chance to read the discussion in the following link?

http://forums.databasejournal.com/archive/index.php/t-7934.html

May it help.