1)
Message boards :
Problems and Help :
Screensaver Background turns red
(Message 11360)
Posted 5324 days ago by  Kalessin
I remember some buggy graphics cards / drivers didn't support one and displayed it as the other (like, if the app requested BGR it still interpreted it as RGB). I'll check which color model the screensaver textures are using...
The funny bit of it is that 20 or 40 times the colors are pretty much perfect. But once in a 20-40 the red version is coming up. So it can not be a constant problem. Only when it has actually started red it stays with it.
At first I thought the color would change if the application found something special.
And it is really pretty too, except for the black row. Could also be an interesting feature to have a red background every 25 WUs a yellow one every 50 a green one every 100 and when you get the golden background you have just one a prime. :-))
But what I would like to know is if someone else had the same problem or if my computer is the only one!?
|
2)
Message boards :
Problems and Help :
Screensaver Background turns red
(Message 11350)
Posted 5324 days ago by Kalessin
As mentioned in the pps-sieve thread i sometimes experience the screensaver having a red background and an upmoving black row.
I didn't know how to take a screenshot of a screensaver so I waited with my digicam to take the shot.
So here are three images of the red circle version of the falling numbers.
When i tried to print screen i noticed, that the background color returned to normal after hitting the key for the 10th of a second before the screensaver made room for the normal modus.
My computer runs pps sieve along with cosmology.
Its a quad 6600@2800 with a MSI geforce 8600GT 512 MB@400Mhz Device driver of 17.9.08 7.15.11.7813
Vista home premium 64bit
Anything else?
|
3)
Message boards :
Problems and Help :
Screensaver Background turns red
(Message 11333)
Posted 5327 days ago by Kalessin
Normally the PPS Sieve starts a screensaver with a blue background and white or yellow numbers. (Nice work by the way)
But sometimes the background is red with a flickering black bar in the bottom area. Is this intentional or a bug?
If it screws up that bad, I'd blame your graphics card or drivers.
Oh, that is something I wouldn't do so easily, since I had never any problems with it. Not in games and not with any other (boinc or other) screensaver.
Even if this could be a possibility, it is not a very probable one.
|
4)
Message boards :
Problems and Help :
Screensaver Background turns red
(Message 11328)
Posted 5327 days ago by Kalessin
Normally the PPS Sieve starts a screensaver with a blue background and white or yellow numbers. (Nice work by the way)
But sometimes the background is red with a flickering black bar in the bottom area. Is this intentional or a bug?
|
5)
Message boards :
Proth Prime Search :
PPS Sieve
(Message 11206)
Posted 5335 days ago by Kalessin
I'm not really totally sure if its prime grid or even boinc, but on the first second and third look 3 pps-sieves and a cels WU glued my PC to a stillstand.
After stopping pG all was back up again working well. After reducing boinc to 3 cpus of the quad i can use it again even with PG. But it took about 2,5 hours to enter the BM and stop PG.
Even some restarts before did not help at all.
Has anybody else experienced something like that? To me its quite new, only yesterday this abnormal behaviour did start.
My other Quad is unaffected of it. Its just happily crunching the same mix.
|
6)
Message boards :
Number crunching :
BOINC crediting and benchmarking
(Message 10453)
Posted 5388 days ago by Kalessin
and very off-topic @ rytis: Is chess still alive? Were you not somehow the one who was sometimes kicking the server?
Quick off-topic note: I'm working with Joerg on Chess960. Hoping it'll be back up in September.
Thats great news good luck to you and Jörg!
|
7)
Message boards :
Number crunching :
BOINC crediting and benchmarking
(Message 10436)
Posted 5389 days ago by Kalessin
And how are things going? Have you found a favorite strategy for the future?
does anyone has by the way a statistics that shows how much % of work is delivered by the clients 6.1.0, 5.5.0, and 5.9.0?
and very off-topic @ rytis: Is chess still alive? Were you not somehow the one who was sometimes kicking the server?
|
8)
Message boards :
Number crunching :
BOINC crediting and benchmarking
(Message 10358)
Posted 5392 days ago by Kalessin
I've just spent all the time from my last post to now getting this chart ready for just the P4 3.0Ghz computers using Windows.
Great work Astro.
And another extra shudder, seeing again how unfair these cheaters are.
This is an increase in the claiming of about 100%;
voracious gang of...
|
9)
Message boards :
Number crunching :
BOINC crediting and benchmarking
(Message 10344)
Posted 5392 days ago by Kalessin
banning one or two versions of those "cheating" clients would only be effective on those numbered clients. There are now nearly a dozen freely available ones, and nothing to stop anyone with a compiler from coming up with his/her own numbers, or even just naming it the same as an official version and slipping past this kind of snare.
My experience is, that most client-cheaters at the moment do use the 6.1.0 client. (only some still use 5.5.0 or 5.9.0; of about a dozen versions I don't know, but they might certainly float through the boinc world) And yes I do know, that it is easy for those who did before, to compile a new cheater version with a standard version number.
And I know how easy it is to fake the values of the benchmark.
And still:
staying quiet regarding the cheater clients might contribute to make the cheaters think its ok to do so. Quite some of them still try to convince others that they are not cheating, but only raising the credits to their deserved height. Maybe one or two of them would recognize that noone else thinks so!
I think that projects as well as teams should clearly state that they strongly discourage any cheating.
Having the admins ban the most common cheater-clients and having a post that cheating clients are not welcome at a project would perhaps scare of a (small) part of the cheaters. (Wouldn't that be a success?) Or leave one or two cheaters without cheating tools for a while (Wouldn't that also be a success?)
And as far as I understood the disabling of clients; its I think about 20 lines of code, most of which could be copy/pasted.
jordans how to
There are reasons, why this might not be the most effective tool against cheaters. (Yes) but there is no reason not to do it.
It is something which could be done in about ten minutes. The amount of time for the cheaters would be a lot more to counteract. It would imply a statement against cheating and perhaps it will reduce cheating (a little bit for a while)
I really would hope that all projects without fixed credits would use the disabling function- besides all other effective means, we will find.
|
10)
Message boards :
Number crunching :
BOINC crediting and benchmarking
(Message 10341)
Posted 5392 days ago by Kalessin
I think it's wasted effort banning by version number. It will block some valid clients, and still allow messing with benchmarks. I think effort would be better used coming up with a real solution. Simple as that.
Ok that might be a reason, only did I think that wasting 10 Minutes time and probably reducing the cheaters by 50% (assumed) and by the way showing that cheaters were not welcome would be a good time/result ratio.
But I don't really know if ten minutes was an accurate estimate. Just guessed that from how the procedure was described.
|
