On Jun 17, 2007, at 1:52 AM, Niels Kobschätzki wrote:
For a few days now I have the phenomenom that in ca. 50% of the startups of Yojimbo, that a few seconds after the start the harddisk begins to work a lot and Yojimbo doesn't respond anymore (rest of the system works). Force quitting it helps
It helps with responsiveness, but I suspect it will cause other problems. Force quitting, while sometimes unavoidable, is a leading cause of file corruption.
I see the same issue you do, on a MacBook with about 1K of items in the db. The design of Yojimbo has a weakness: on the first launch after a sync, Yojimbo will hang up what may seem like a long, long time while spinning the beach ball. The rest of the computer is likely responsive. This isn't strictly a problem with your computer, its a design flaw. I'm sure future versions of Yojimbo and/or the Mac OS will address the problem. In the meantime, when launching Yojimbo, just let it settle after launch. With a bit of experience, you'll get a sense for how long it takes.
Yojimbo is a bit ahead of the curve with .Mac functionality. I really appreciate it, but the entire dotMac framework has a real version 1.0 feel to it. I look forward to the day when it shakes out. In the meantime, its a nuisance I can live with. Some perhaps, cannot. Whatever your feelings on the subject, liberal use of force-quitting is not a good idea.
b -- ------------------------------------------------------------------ This message is sent to you because you are subscribed to the mailing list <yojimbo-talk@barebones.com>. To unsubscribe, send mail to: <[EMAIL PROTECTED]> List archives: <http://www.listsearch.com/yojimbotalk.lasso> Have a feature request, or not sure if the software's working correctly? Please send mail to: <[EMAIL PROTECTED]>
