I don't know for sure what is going on. I just got several new n-body units for my Mac mini Core Duo running Tiger (10.4) and they are continuing to error out within seconds. The separation units are fine and everything works on my Core 2 Duo under Leopard (10.5). No rush, just thought you might want to know. Thanks.

I just noticed that it was running version .82. If that makes a difference, what do I need to do to update to either .84 or .88 or whatever works?

I don't know for sure what is going on. I just got several new n-body units for my Mac mini Core Duo running Tiger (10.4) and they are continuing to error out within seconds. The separation units are fine and everything works on my Core 2 Duo under Leopard (10.5). No rush, just thought you might want to know. Thanks.

I just noticed that it was running version .82. If that makes a difference, what do I need to do to update to either .84 or .88 or whatever works?

You need to be using 0.84 on OS X 10.4 The problem was apparently OpenMP support wasn't added until Leopard so the multithreaded 0.82 ones don't work (the 32bit one was supposed to target 10.4). I just noticed I forgot to mark the old ones thought.

OK, thanks. Will this be automatic or do I need to reset, detach and reattach, or something else?

OK, thanks. Will this be automatic or do I need to reset, detach and reattach, or something else?

Should be

Well, it automatically updated to version 84 but it still errors out in about 5 seconds on a Mac mini Core Duo running Tiger (10.4). The separation units are still fine. Fortunately, the time lost is negligible.

How can i get mor of these tasks? i only get 1- this task is finished after 10 seconds, then i have to wait 1 minute for a new one.
it would be fine to get 100 of these tasks or so...

Off topic but, I couldn't post a new thread.

I have a question about: task duration correction factor which can be seen by me in a finished work unit when I select my computer ID.

I thought I read somewhere here that the # won't go below a (1) when I view mine they are sitting at 0.022553 how did this happen?

Off topic but, I couldn't post a new thread.

I have a question about: task duration correction factor which can be seen by me in a finished work unit when I select my computer ID.

I thought I read somewhere here that the # won't go below a (1) when I view mine they are sitting at 0.022553 how did this happen?

The n-body tasks were wwaaaayyy off on the estimated run time. I'm guessing they still are, but I haven't had any of those since the new server went up. I would have an estimate of 4-6 hours and they would run 30 min to 40+ hours.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Thanks for your reply!