Excellent -- not because it's not working, but excellent because maybe we can now isolate what's happening.

I'd like you to run some tests and copy/paste from your terminal into a reply message so I can take a look at the data. On your wife's computer, do the following:


That will give you a report that looks something like this:


Please copy that into a reply message so I can look at the info. (Notice how the perms are wrong for the Smart Crash Reports installed on my computer. Hopefully we'll see something similar for the MagicMenu stuff.)

Also, take a look to see if something is installed in the InputManagers for your wife's user account. To do that, do the following:

cd ~/Library/InputManagers

If that gives an error, then she doesn't have any per-user input managers and we can eliminate that as a variable. If she does, then once again type in the

ls -al *

Copy that (if it exists) into a reply message, and we'll see what perms and ownership is going on for her per-user settings.

Hopefully we'll be able to spot what's going on. Fingers crossed.

Thanks!!
John

[Kathleen-Ave-MBPro:/Library/InputManagers] kdave% ls -al *
total 16
drwxr-xr-x@ 4 root admin 136 Dec 17 19:34 .
drwxr-xr-x@ 3 kdave staff 102 Dec 17 19:34 ..
-rwxr-xr-x@ 1 root admin 434 Dec 13 21:43 Info
drwxr-xr-x@ 3 root admin 102 Dec 17 19:34 Menu Extra Enabler.bundle
[Kathleen-Ave-MBPro:/Library/InputManagers] kdave%

On ~/Library/InputManagers

I get: "no such file or directory"

Bill

Hmmm. That all looks OK.

In an earlier message you wrote:


No MagicMenu in there? Do you know where the MagicMenu code is installed?

I thought Allume used /Library/Application Support/ and /Library/InputManagers/

Prior to these tests (after my first post) I had trashed from the computer anything with Allume, Alladin, Magic, or Stuffit in the file/folder name.

I’ve had stability problems with NUDC version 5.3+ since I downloaded it many moons ago, and have gone back to using version 4.5.3 (MacBook Pro 2.16 core duo; OS 10.4.11). It behaved as erratically as Golem's eyeballs when importing data, and stacked all the imported holidays/birthdays together on January 1. A great way to begin a new year, but the source of much consternation over missed birthdays. I was surprised to see folks still downloading it. The home team must be stretched thin, and the calls for patience seem appropriate.

My question here is, since I'm upgrading to Leopard next week, is the NUDC 5.3.2 version more stable on OS 10.5 than it was on OS 10.4, and is it worth the try-out--or best wait for NH?

I pre-purchased NH almost a year ago, and am anxiously awaiting its release. iCal feels too cluttered and the cal in Entourage too clunky, though the latter will have a new interface and capability array in a few weeks with the new Office.

As frustrating as all this is, and as maddening as the delay of NH may be, I’m hoping it will be worth it in the end. I’ve been using the application since it first came out all those incarnations ago, all those buyouts ago. The interface with version 4.5.3 is still bright, cheerful, and clean. That’s the foundation for my loyalty. It is better to work with than the competition, though iCal on the iPhone is beginning to erode my loyalties.

Onward!
Terrance

As one of those who still had server problems with 5.3.2b2, I can confirm that, at least for me, they're fixed in b3. And the menu extras work fine for me, too.

I'm also eagerly awaiting Nighthawk... but UTD/contact seems to be operational on Leopard for me in the meantime.

NUDC 5.3.2 mainly addresses Leopard issues. Note that if you go into the terminal and correct the permissions issues with the InputManager's folder (there are a number of posts here about that), then the QC/QD menus in version 4 will probably work with Leopard as well. The one problem that would remain with the client is for reminders. The "quickdayd" process in v4 will most likely fail in Leopard due to changes in how the MacOS daemon() command works. That was fixed as part of v5.3.2.


and Upward! Smile

--John

The QC menu primarily, but not uniformly, takes 10-15 seconds between typing info to results. Spinning wheel plus beach ball too. Its been 3 weeks since the last post on this topic. Is this an open item or is there a fix that rectifies this problem? Thanks

Paul,

This is presently an open issue.

- Mark