Posts by Usuario1

21) Message boards : Number crunching : No WUs again, really dudes? (Message 89211) Posted 3 Jul 2018 by Usuario1_S Post: Wow again 48 hr to fix that, really bad up time, I'd have a serious talk with the WU admnistrator
22) Message boards : Number crunching : No WUs again, really dudes? (Message 89202) Posted 2 Jul 2018 by Usuario1_S Post: Is it that hard to have a WU server fed? Don't you have like a crap ton of proteins to fold? I think you're seriously underestimating the computing power of mobile devices and the will of people participating, this should never happen, never, come on, put some batteries on, become Vegan, you'll have lots of extra energy and health, you need scientific evidence of course, here it is: https://pastebin.com/7K8Fr8da
23) Message boards : Number crunching : No WUs for Android client (Message 89193) Posted 30 Jun 2018 by Usuario1_S Post: Normal WUs download now, took 2 days, 48 hrs of computing lost, you have to make better than that people
24) Message boards : Number crunching : No WUs for Android client (Message 89174) Posted 28 Jun 2018 by Usuario1_S Post: xD +1 thumb up This board needs the WhatsApp emojis
25) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 89161) Posted 27 Jun 2018 by Usuario1_S Post: I think it's not as light as it should be, I set BOINC to run 100% of CPUs= 1=8 Cores, and 100% of the time, the processes run on Low Priority on Win 8.1 64-bit, btu they hog the computer sometimes, not as responsive as it used to be, so please fix this, same thing on the Android client, if you make it really transparent as it used to be a few months/years ago would be better for everyone, because sometimes I need to pause the computation and I forget about it, and BOINC resumes after 1 hour later, so I'd like to avoid to pause BOINC
26) Message boards : Number crunching : No WUs for Android client (Message 89160) Posted 27 Jun 2018 by Usuario1_S Post: Ssince a about 12 hours ago, please fix this ASAP. I think the're underestimating the power of the ARM CPUs :)
27) Message boards : Number crunching : No WUs 24 hrs (Message 89022) Posted 29 May 2018 by Usuario1_S Post: Yes, I try the manual update immediately when I don't see WUs crunching, but yes I got some WUs recently again, if it's a maintenance thing it should be written so on the Notice Tab, maybe is just a shortage of WUs, for some reason
28) Message boards : Number crunching : No WUs 24 hrs (Message 89011) Posted 28 May 2018 by Usuario1_S Post: Again they stopped, updating the project won't get any WUs same as when the server simply stops sending them, like before, so why is this happening? No answer from the project people. I'll tweet them like I did before
29) Message boards : Number crunching : Error while computing - AMD Opteron (Message 88994) Posted 25 May 2018 by Usuario1_S Post: Thank you for the info mate,yes I think you're right, that group is bad, a relieve, sorry for the late response
30) Message boards : Number crunching : Not getting any... (Message 88993) Posted 25 May 2018 by Usuario1_S Post: Forgot to report, all WUs getting normal since Thursday about 0:00, Right now for me is Friday 0:44 and all normal, thanks for fixing this
31) Message boards : Number crunching : Not getting any... (Message 88966) Posted 21 May 2018 by Usuario1_S Post: Android WUs, you dirty minds xD Since today near 0:00 is maintenance thing? or what's going on?
32) Message boards : Number crunching : Error while computing - AMD Opteron (Message 88965) Posted 21 May 2018 by Usuario1_S Post: I get veery few days in my AMD FX-8370 Computing error, maybe is a compiler thing that won't use the Intel Instruction Set or expects something Intel CPUs only will give? Why would I get an error, my apps or anything never crashes really Win 8.1 64-bit fully update, including drivers
33) Message boards : Number crunching : Not getting Android WUs (Message 88964) Posted 21 May 2018 by Usuario1_S Post: Today a few hours ago, Android client stopped getting WUs, already sent a Tweet to R@H and nothing yet, I don't want to start another threat about it
34) Message boards : Number crunching : Not getting Android WUs (Message 88442) Posted 8 Mar 2018 by Usuario1_S Post: Finally WUs are arriving, happy crunching!
35) Message boards : Number crunching : Not getting Android WUs (Message 88437) Posted 6 Mar 2018 by Usuario1_S Post: Tuesday is ending and very few WUs only, no solid flow of WUs
36) Message boards : Number crunching : Not getting Android WUs (Message 88425) Posted 5 Mar 2018 by Usuario1_S Post: Monday almost over and no WUs
37) Message boards : Number crunching : Not getting Android WUs (Message 88423) Posted 5 Mar 2018 by Usuario1_S Post: I see, yeah andmight be other technical details, anyway, well I got like 3 WUs like 12 hours ago but nothing since them
38) Message boards : Number crunching : Not getting Android WUs (Message 88412) Posted 4 Mar 2018 by Usuario1_S Post: I don't see why would be a problem with Android devices, Rosetta@Home is 32-bit code, and for some reasons don't want to go 64-bit so every single Android phone can execute 32-bit code, unless it's a special situation, probably yes I think it's a empty queue omission Thanks for the suggestion but I'll wait for any changes in server status ^ \|- - - PS: See what I did there? I omitted the final dots, why? because I think it's stupid, if there are no more letters means no more words, I mean what I wrote, it's obvious, you don't need a dot to see it. Imagine how many TB of data could be saved but not putting those unnecessary points? just useless wasted storage space
39) Message boards : Number crunching : Not getting Android WUs (Message 88410) Posted 3 Mar 2018 by Usuario1_S Post: Yeah, they did the same for new year, and they promised never do that again, I wonder why? and yes they'll probably won't be on until Monday at least.
40) Message boards : Number crunching : Not getting Android WUs (Message 88406) Posted 3 Mar 2018 by Usuario1_S Post: As of 24 hours ago no WUs, please fix this? I reset the Project and nothing

Previous 20 · Next 20

Posts by Usuario1_S