Ok, I found it. In this file, I found two more references of the two exe's. I assume I can delete this part as well?
After you deleted the app_info.xml file, then restarted BOINC, just reset the project. That will clear all straggling remains about the power app that you used from the Einstein directory as well as all the files it is mentioned in.
Ah yes, that did it. The log looks good now and no more everlasting pending downloads. Even the lost work was sent back to my computer. Thanks!
Well, I'm out of work again. Nothing wrong under the Messages tab. It went perfect for a couple of days. I've reset the project and restarted BOINC and did a few manual updates. No result. Any suggestions?
EDIT: I was to fast. Downloaded 4 WU's a few seconds ago.
Well, I'm out of work again. Nothing wrong under the Messages tab. It went perfect for a couple of days. I've reset the project and restarted BOINC and did a few manual updates. No result. Any suggestions?
You obviously see this behaviour as a 'problem' when really it's not. You would seem to be supporting both Seti and E@H and you would seem to have a resource share of around 80/20 in favour of Seti, judging by the respective RACs. If E@H gets a bit more than the specified share for a while, it's not surprising that BOINC might choose to not download further E@H work until Seti has had a chance to catch up. You will know that this is likely to be the case if you request a manual update of E@H and BOINC says it is requesting 0 seconds of new work. That is perfectly normal behaviour and you should not let it concern you if your other project(s) have work.
Quote:
EDIT: I was to fast. Downloaded 4 WU's a few seconds ago.
As you found out, BOINC is perfectly capable of deciding when to get new work. The fact that you got 4 tasks is interesting as it suggests that you have rather a large cache setting. The combination of a large cache setting and a low resource share can make it harder for BOINC to properly manage things. In cases like this you can alternate between feast and famine.
Another point is that the sudden downloading of multiple tasks (if not caused by you suddenly upping your cache settings by a large amount) points to perhaps the machine suddenly coming out of a mode where BOINC considered that tasks on board might have been under deadline pressure. Being under deadline pressure will always prevent new work requests until BOINC works its way out of that mode. There are lots of possible scenarios to explain this type of behaviour and it's not always obvious as to why BOINC makes certain decisions. In my experience, it's usually best to let BOINC do its thing without undue interference. Resetting the project to try to force new work is usually the wrong thing to do.
RE: RE: RE: Ok, I found
)
Well, I'm out of work again. Nothing wrong under the Messages tab. It went perfect for a couple of days. I've reset the project and restarted BOINC and did a few manual updates. No result. Any suggestions?
EDIT: I was to fast. Downloaded 4 WU's a few seconds ago.
RE: Well, I'm out of work
)
You obviously see this behaviour as a 'problem' when really it's not. You would seem to be supporting both Seti and E@H and you would seem to have a resource share of around 80/20 in favour of Seti, judging by the respective RACs. If E@H gets a bit more than the specified share for a while, it's not surprising that BOINC might choose to not download further E@H work until Seti has had a chance to catch up. You will know that this is likely to be the case if you request a manual update of E@H and BOINC says it is requesting 0 seconds of new work. That is perfectly normal behaviour and you should not let it concern you if your other project(s) have work.
As you found out, BOINC is perfectly capable of deciding when to get new work. The fact that you got 4 tasks is interesting as it suggests that you have rather a large cache setting. The combination of a large cache setting and a low resource share can make it harder for BOINC to properly manage things. In cases like this you can alternate between feast and famine.
Another point is that the sudden downloading of multiple tasks (if not caused by you suddenly upping your cache settings by a large amount) points to perhaps the machine suddenly coming out of a mode where BOINC considered that tasks on board might have been under deadline pressure. Being under deadline pressure will always prevent new work requests until BOINC works its way out of that mode. There are lots of possible scenarios to explain this type of behaviour and it's not always obvious as to why BOINC makes certain decisions. In my experience, it's usually best to let BOINC do its thing without undue interference. Resetting the project to try to force new work is usually the wrong thing to do.
Cheers,
Gary.