Well I'm used to this with LHC but never had that here.
Telling this machine it had it's daily quota 2 days in a row so it is now sitting here with nothing again.
(and yes I have been here for many years now and this is one pc from the beginning)
(reached daily quota of 1 results)
Copyright © 2024 Einstein@Home. All rights reserved.
Daily Quota
)
Seti Classic Final Total: 11446 WU.
RE: That's one sick
)
How do I find out?
It seems to be running fine and even did some LHC last night.....but nothing here.
RE: That's one sick
)
Most of the errors have exit code 226 which I believe the remedy for is not to use the cpu throttle. This would be done in your preferences by going to processor usage and setting cpu time to 100%.
You also have at least one WU with an Exit status -1 (0xffffffffffffffff) which is explained:
Well thanks for your
)
Well thanks for your suggestions.
But I do have all 4 of my machines set to 100%
And I haven't used a screensaver or looked at the graphics since 2000 when I started seti classic.
I did a couple "run cpu benchmarks" and no problem there either.
Oy vey!
At least it is just my P4 2.5
(edit:I did just see this http://einsteinathome.org/account/82814/computers
I wonder why it split Magic2 in half)
Thanks again.
RE: Well thanks for your
)
You could try a project reset and maybe even a detach to see if that helps.
As far as the split, did you change/update the OS or change hardware?
RE: RE: [/b][/][/] You
)
No hardware change and this is about 6yrs old and the only one I bought at a store (HP) same XP Pro sp2.
I did just update my security suite but did that to all of the machines and it didn't cause any problems with the others.
I even tried the detach and reset before I mentioned this here.
>:- (
RE: No hardware change and
)
I think it is possible this may have something to do with the update. Especially if you did the update on the 15th or 16th since that appears to be when the "split" happened. Also you mention that it's the same XP Pro SP2 but it's listed as Microsoft Windows XP Home x86 Editon Service Pack 2, (05.01.2600.00),( even that changed slightly from the duplicate when it was reconized as another system), and since all the others except the other duplicate are XP Pro instead of Home, could be that's why the other systems didn't have problems with the update.
Could also be it has nothing to do with which OS it is, and it's just an error happening during the update or the settings were changed and need to be adusted. Because it caused the system to be reconized as another pc though, I tend to believe there was an error.
Also is this task still in the BOINC Manager and being processed?
You might want to check the stdoutdae.txt log in the BOINC folder to see if any messages were generated prior to when your last WU's were returned that might be of help.