Javascript error in IE7 relating to SharePoint 2007′s dependence on client-side Office files.

I had Office 2007 and 2010 installed on my desktop and recently uninstalled Office 2007.  The next time I loaded our MOSS 2007 intranet homepage, I got a "Library not found" javascript error.  After debugging, the error is thrown at this line:
IMNControlObj.OnStatusChange=IMNOnStatusChange;
None of my colleagues were getting this error, but they weren’t running Office 2010.  This line is related to the NameCtrl ActiveX control in name.dll, which displays your presence information.  It is also "installed in the %ProgramFiles%Microsoft OfficeOffice14 directory on the client computer during Microsoft Office Setup."  Hence, given my recent Office configurations, a repair of Office 2010 should restore the missing files required by this javascript file.  I did a repair of Office 2010, rebooted, and the error was gone.

InfoPath’s .NET programmability features in Office 2010 won’t install with Office 2007 counterpart installed.

I uninstalled Office 2007 to get the .NET programmability features (VSTA) in Office 2010 to work.  See this Qdabra forum.  If I need to work on Office 2007-specific stuff, I’ll use my VM.

Office 2010 install error 1402

I received a pop-up dialog repeatedly when trying to empty my Deleted Items folder in Outlook 2010.  It had something to do with configuring Office 2010 for MUI.  I tried repairing the Office 2010 installation.  It gave me a 1402 error and pointed me to a registry key that didn’t exist.  After searching around, this blog entry had some good ideas: use subinacl.exe or try a secedit command.  Both will modify security settings.  The following secedit command worked for me.

From Microsoft Support:

In Windows XP, type the following command, and then press ENTER:
secedit /configure /cfg %windir%repairsecsetup.inf /db secsetup.sdb /verbose

In Windows Vista, type the following command, and then press ENTER:
secedit /configure /cfg %windir%infdefltbase.inf /db defltbase.sdb /verbose