This my host, seems to crunch all remained S5R2 WUs. And even now I don't see any evidence of S5R3 here. I'm not worry about this. I just comment this. So, please, don't worry. Sometimes any of you will have a chance to participate in S5R3 - we have more than 600 days for this yet.
Because that host is still using an app_info.xml file, so it can not get the new ones. You are still running with 4.38. The new Windows apps are 4.0x.
Because that host is still using an app_info.xml file, so it can not get the new ones. You are still running with 4.38. The new Windows apps are 4.0x.
Unless you have some first hand knowledge, this is nothing but speculation. This recent S5R2c result (of mine) was processed by v4.38 (without an app_info.xml file) after the same host had processed several S5R3 results with v4.0x apps.
Because that host is still using an app_info.xml file, so it can not get the new ones. You are still running with 4.38. The new Windows apps are 4.0x.
Unless you have some first hand knowledge, this is nothing but speculation. This recent S5R2c result (of mine) was processed by v4.38 (without an app_info.xml file) after the same host had processed several S5R3 results with v4.0x apps.
I, too, was running the beta app using app_info.xml, but I deleted it and all executables and suspended. Few days later I resumed and EaH downloaded v4.38 and sent me a S5R2 task. I have yet to see S5R3, though EaH is low priority for me right now.
You didn't understand me. I'm not running any beta-app. It works with standard apps and no manipulations has been made with it. It just works for a long-long time 24/7 so, it has a lot of _l1 and _h1 files. So the server decides to send S5R2 work that has not been completed by others. It doesn't ask me (in logs) to remove old version to receive new work - it just works hapily for about 2 years without modification in software part (except boinc upgrades). It will help me in the future to crunch some S5R3 WUs without downloading new base files.
I think it will start automatically receive a new S5R3 work when server decides it to do. And I keep an eye on it.
RE: This my host, seems to
)
Because that host is still using an app_info.xml file, so it can not get the new ones. You are still running with 4.38. The new Windows apps are 4.0x.
RE: Because that host is
)
Unless you have some first hand knowledge, this is nothing but speculation. This recent S5R2c result (of mine) was processed by v4.38 (without an app_info.xml file) after the same host had processed several S5R3 results with v4.0x apps.
RE: RE: Because that host
)
I, too, was running the beta app using app_info.xml, but I deleted it and all executables and suspended. Few days later I resumed and EaH downloaded v4.38 and sent me a S5R2 task. I have yet to see S5R3, though EaH is low priority for me right now.
You didn't understand me. I'm
)
You didn't understand me. I'm not running any beta-app. It works with standard apps and no manipulations has been made with it. It just works for a long-long time 24/7 so, it has a lot of _l1 and _h1 files. So the server decides to send S5R2 work that has not been completed by others. It doesn't ask me (in logs) to remove old version to receive new work - it just works hapily for about 2 years without modification in software part (except boinc upgrades). It will help me in the future to crunch some S5R3 WUs without downloading new base files.
I think it will start automatically receive a new S5R3 work when server decides it to do. And I keep an eye on it.