Posts by Martin

1) Message boards : News : MilkyWay@home Down (Message 65252) Posted 24 Sep 2016 by Martin Post: Very similar. "No tasks available"
2) Questions and Answers : Getting started : Linking computers (Message 65195) Posted 20 Sep 2016 by Martin Post: I have been running MW@H for about 2 years on one computer. I have just bought another machine and downloaded BOINC and MW@H. Unfortunately, I miss-typed my email address and the erroneous address was accepted. When I try to enter the correct address, the system tells me that the correct address is already in use, and will not change that on the new computer. They now have different user ID's. How can I change the email address on the new machine to match that of my other machine, and then get the system to accept that they should both use the same user ID?
3) Message boards : Number crunching : GPU problem (Message 64626) Posted 8 Jun 2016 by Martin Post: I have a laptop computer onto which I have loaded BOINC and MW@H. I find that the computer has an AMD/ATI GPU, not used by MW@H. My problem is that the MW@H is only asking for GPU work units, and not receiving any: 08/06/2016 07:48:19 \| Milkyway@Home \| Sending scheduler request: To fetch work. 08/06/2016 07:48:19 \| Milkyway@Home \| Requesting new tasks for AMD/ATI GPU 08/06/2016 07:48:22 \| Milkyway@Home \| Scheduler request completed: got 0 new tasks How do I convince MW@H to forget about the (in this case) useless GPU and to ask for CPU work units? I have tried suspending GPU operation, to no avail.
4) Message boards : News : New Separation Modfit Version 1.36 (Message 62566) Posted 14 Oct 2014 by Martin Post: Jake I am also running a Win32 system, and just had 3 more ModFit 1.36 tasks downloaded. So far there have been no 1.34 or 1.36 tasks which have run on my system. I am just about to put a block on receiving more until you can find what is wrong with it and correct the problem.[/u]
5) Message boards : News : New Separation Modfit Version 1.36 (Message 62500) Posted 7 Oct 2014 by Martin Post: Sorry Jake. I am getting exactly the same result as with V1.34. Immediate (0.00 sec CPU time) fail as a computational error, reporting: (unknown error) - exit code -1073741515 My computer is a Dell XP machine with a 2-core Intel CPU, and no GPU. So far, no ModFit task under 1.34 or 1.36 has even looked as though it might run.
6) Message boards : News : New Version of Separation Modfit 1.34 (Message 62471) Posted 5 Oct 2014 by Martin Post: In the last couple of days I have had 24 Modfit 1.34 tasks downloaded to my computer. So far one has yet to run, and the other 23 failed immediately (0.00 sec CPU time) with "Unknown error - exit code -1073741515". I am using a Dell XP machine with a 2-core processor. I don't think MOdfit 1.34 likes my computer!
7) Message boards : Number crunching : Milkyway@Home preventing other applications from running (Message 62405) Posted 26 Sep 2014 by Martin Post: Alan I was aware that the N-body tasks took over both cores. What I was really worried about was the fact that they did not release after the 60 minute period, when tasks were scheduled to switch. I just wanted to check that this behaviour was normal, and Mikey assures me that it is. No further problems......yet.
8) Message boards : Number crunching : Milkyway@Home preventing other applications from running (Message 62401) Posted 25 Sep 2014 by Martin Post: Thanks, Mikey I thought that I had done something wrong. I will wait a month or two to see how it pans out.
9) Message boards : Number crunching : Milkyway@Home preventing other applications from running (Message 62399) Posted 25 Sep 2014 by Martin Post: I have recently started processing MW@H wu's, in addition to two other BOINC applications. I am using a Dell computer with a 2-core processor. My computing preferences are set so that each of the three applications should have a 33.33% resource share, and that there should be a switch between tasks every 60 minutes. However.... One a MW@H wu starts being processed it will not switch to another task, with the result that the other 2 applications are getting no processor time at all. Is this behaviour on the part of MW@H normal? or have I missed a switch which would control this power grab? Any assistance on this will be gratefully received.