Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Same problem exists with MacAllyHelper' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Same problem exists with MacAllyHelper
Authored by: tonyboy on Nov 06, '04 05:06:32PM
I'm really glad to see this solution here.

The same problem exists with MacAlly's keyboards with multimedia keys (e.g.: the NetKey) the their "MacAllyHelper" driver.

I had come to much the same diagnosis and solution as above, and created the following AppleScript:


try
	do shell script "killall MacallyHelper"
	open application "MacallyHelper"
end try
The problem is, I hadn't found a way to run this automatically at startup, so when either I or my roommate would switch into our accounts, we'd have to manually run the script (placed in our docks for convenience).

The WinSwitch solution is interesting, but I prefer to use Apple's own FUS mechanisms -- especially if WinSwitch needs to be activated for each user account. It just seems kind of hacky...

Is there any way to change an application like MacAllyHelper into a more compatible form, like a kernel extention just by moving it to a different location and/or changing it's package information?

[ Reply to This | # ]