Leopard Problems - iHatePC

See this link for trouble shooting your input menu problem:
http://www.rainmakerinc.com/kb/index.php?article=87

Here's what the developer says:

> Input Menu Troubles

We are hearing from some customers about difficulties getting Spell Catcher's input method to activate, or even appear in International System Prefs. So far, most have been solved by trashing the preference file that contains your input menu configuration, restarting and then configuring it manually from scratch. To do this, navigate to your home ~/Library/Preferences/ByHost folder, trash all the files named like "com.apple.HIToolbox.#####.plist". Restart immediately. Empty the Trash once you're logged in again. Open System Preferences, International, Input Menu tab, and configure things manually.

Others report that simply toggling an input source on and off (any input source) is all that was needed to get things working properly. This makes sense as the above-mentioned preference file likely gets re-written to disk, and (hopefully) in the process any old or otherwise invalid contents or entries would be removed.

What often works is to navigate to home ~/Library/Components in the Finder, drag the Spell Catcher.component out to the Desktop, then drag it back into the Components folder, then Restart right away. This seems to get the system to "notice" the component, and that the Text Services and Component caches need to be rebuilt the next time the system starts up.

A recent posting in our forums from a customer that was having trouble in this area discovered that moving the Spell Catcher.component out of his home ~/Library/Components folder into the (top-level) /Library/Components folder was an effective solution. You'll need administrator privileges to do this, but it's worth a try if you can't find another solution.

For a few customers, the reasons they are having trouble with the input menu or input method are far more severe. I've seen two cases where incompatible-with-Leopard software is loading early (at system startup) or as a plug-in, causing all sorts of havoc. Be sure to check all your migrated-over Extensions, StartupItems, Frameworks, Components, Contextual Menu Items, PreferencePanes, ScriptingAdditions and the like. If you're seeing serious problems, clues usually appear in the Console log (/Applications/Utilities/Console).

Reply to This

Monday, December 31 2007 @ 01:12 PM PST