Friday, January 19, 2007

TIPS & TRICKS: Missing Microsoft Equation Editor in Office 2004

Had a student come in today and report that Microsoft Equation was missing from the Word application. This normally shows up in Word under the Insert > Object menu. I suppose this isn't a frequently occurring problem so I didn't find anything online about how to get it back in. But, rest assured, it's easier than solving a Rubik's Cube for a Cube champion.

As long as you have the original install CD, the file for Equation Editor resides in Microsoft Office 2004 > Office. Just copy the file called Equation Editor to the same location where you have Office 2004 installed on your computer (usually, Macintosh HD > Applications > Microsoft Office 2004 > Office). I even did it with Word open and it worked. I would recommend shutting Word down and the reopening it when done. But that's it.

Good luck.

Wednesday, January 03, 2007

TIPS & TRICKS: svchost.exe -- application error the instruction at "0x745f2780"

A faculty member went home before the end-of-the-year holiday break with a brand new machine that I installed our software packages on. The machine worked perfectly when it left here. It just came back here today and he reports that the machine receives the following message:

svchost.exe -- application error the instruction at "0x745f2780" reference memory at "0x00000000". the memory could not be 'read'

There was also another message, but this was the pertinent one. As soon as the error message was closed, the machine became unusable. Since it was working just fine before it left my possession, I assumed that he installed something to break the Windows install.

I first tried booting into Safe Mode. It booted with no problems. I then turned off all startup items and booted the machine into normal Windows. Error message still came up. This was going to be a problem with the core OS. Not wanting to waste more time, I searched the web for the error message. The first hit was this [swigartconsulting.blogs.com].

Amazing, that the first hit gave me the solution. Apparently, the problem was corruption in the Windows Update process. The easy solution to try was to turn off Automatic Updates, run Windows Updates (or Microsoft Updates), then turn Automatic Updates back on. There's also a more in-depth fix listed on the website above. However, the easy one worked for me.