hi richard, do you have a link or some more info on this new splitter process ?

cheers

adrian

Well, if he's aborting anything that doesn't have a deadline of at least 54 days, he's going to be mighty confused by the new splitter code.

---

63. (1) (b) "music" includes sounds wholly or predominantly characterised by the emission of a succession of repetitive beats

I'm sorry but he should be got rid of from the project. If you look at the most recent 600 task he's got over 400 of them have been aborted/cancelled by user. And funnily enough there all short units.

Off to look for other programs that will benefit from the crunching power of this machine.

---

hi richard, do you have a link or some more info on this new splitter process ?

Sent by PM - I want Bad to the Bone to do his own research if he's lurking here.

lol

thanks for the info richard

satan, i agree its kinda ok for him to mess around a bit but this systematic abuse of the system is pretty poor eh ?

hi richard, do you have a link or some more info on this new splitter process ?

Sent by PM - I want Bad to the Bone to do his own research if he's lurking here.

---

63. (1) (b) "music" includes sounds wholly or predominantly characterised by the emission of a succession of repetitive beats

He must have written a code or something to do it, because sitting there and manually canceling everything would take ages.

It wouldn't take much to change that though would it.

---

He must have written a code or something to do it, because sitting there and manually canceling everything would take ages.

It wouldn't take much to change that though would it.

He only represents the mindset of, "Im going to get to the top whether I have earned it or not", that is so pervasive in our society today. This leads to other uncivil behavior in a lot of cases, and as a result we have about 1% of our population behind bars at the moment.

---

When we finally figure it all out, all the rules will change and we can start all over again.

I'm sorry but he should be got rid of from the project. If you look at the most recent 600 task he's got over 400 of them have been aborted/cancelled by user. And funnily enough there all short units.

Off to look for other programs that will benefit from the crunching power of this machine.

Hi y'all,

I wonder if it's too late to abuse the update button and try to snag some of them shorties ;-)

@SATAN - Please don't go, just sit back and let The Osmonds help you reset your perspective with their 1971 break out hit One Bad Apple.

Okay, so in our case it's three BTTB apples, you get the point.

G'day from Texas,
John

Edit:
Y'all better watch your back. This little 4 core Vista box hostid=3954050 has broken into the top 20, and core-for-core is the top box on the project with RAC = 1375/core running the Crunch3r Vista build.

I wonder if maybe Crunch3r put in a back door to unlock the apple tweaks? :o
Explanation anyone?

---

JD, the trouble is he's overclocked it, so it doesn't matter, if it was stock config, then it would be something to remark about.

---

JD, the trouble is he's overclocked it, so it doesn't matter, if it was stock config, then it would be something to remark about.

His overclock isn't as extreme as Who?s SKT near 4GHz with 8 cores, yet this guys RAC is very close with his 4 cores at a lower speed.

Us with Wintel boxes can't run Alex code, but we are free to OC to try to level the playing field ;-) Besides, you can buy the DELL XPS 720 H2C factory overclocked and liquid cooled.

When I go to spend my credits, the merchant doesn't ask if they were "OC" earned. LOL, All is fair in BOINC land. All validated results benefit the project, that is why I am here.

My newfound philosophy is BCC: "Build it, Clock it, Crunch it".


Live Long and BOINC

---

your philosophy is a good one.

---

Y'all better watch your back. This little 4 core Vista box hostid=3954050 has broken into the top 20, and core-for-core is the top box on the project with RAC = 1375/core running the Crunch3r Vista build.

I wonder if maybe Crunch3r put in a back door to unlock the apple tweaks? :o
Explanation anyone?

On a quick comparison with some data I collected on msattler's box the CPU time reported for a result near 0.01 Angle range is scaled almost exactly to the difference in clock rate to msattler's hyper-Penryn.

msattler: 4.6 GHz, 3050 CPU seconds for 0.01 AR
3954050: 3.673 GHZ, 3900 CPU seconds for 0.01 AR

I don't think one needs to invoke an application back door.

Mark took his magic host off to other projects for a while, so its current RAC does not represent its performance.

---

Not to mention that with the recent Validator siesta, a lot of RAC's (like mine) are looking a bit weird these days. I'm hoping everything'll settle in a bit by the time of the next scheduled Tuesday outage.

---

Y'all better watch your back. This little 4 core Vista box hostid=3954050 has broken into the top 20, and core-for-core is the top box on the project with RAC = 1375/core running the Crunch3r Vista build.

I wonder if maybe Crunch3r put in a back door to unlock the apple tweaks? :o
Explanation anyone?

On a quick comparison with some data I collected on msattler's box the CPU time reported for a result near 0.01 Angle range is scaled almost exactly to the difference in clock rate to msattler's hyper-Penryn.

msattler: 4.6 GHz, 3050 CPU seconds for 0.01 AR
3954050: 3.673 GHZ, 3900 CPU seconds for 0.01 AR

I don't think one needs to invoke an application back door.

Mark took his magic host off to other projects for a while, so its current RAC does not represent its performance.

Well, it's back on Seti full time now......
But I'm having a little trouble on re-entry into Setiland........
After over a week of crunching ABC with no trouble, after resuming Seti, I am getting computation errors.....
Played with it a little during the week, but with my work schedule, I don't have much time to make adjustments and see the results.....
Have backed off the FSB from 460 to 458....still errors.
Will have to play with some other parameters in the bios and see if I can get it sorted again...
I think that Seti accesses RAM a bit more than ABC did, so I am betting on RAM settings or mobo/NB settings.....I think the NB is being pushed to the limit with that high a FSB....
Now that my weekend is here, I'll have a little more time to play with things, just tried LOWERING the NB voltage a notch....
Don't know if it will ever see the top 20 computers again, with all of the hot rigs entering the ring lately, but I'm sure I'll get back into the top 40 at least......gimme a week or two....

---

"Time is simply the mechanism that keeps everything from happening all at once."

Y'all better watch your back. This little 4 core Vista box hostid=3954050 has broken into the top 20, and core-for-core is the top box on the project with RAC = 1375/core running the Crunch3r Vista build.

I wonder if maybe Crunch3r put in a back door to unlock the apple tweaks? :o
Explanation anyone?

On a quick comparison with some data I collected on msattler's box the CPU time reported for a result near 0.01 Angle range is scaled almost exactly to the difference in clock rate to msattler's hyper-Penryn.

msattler: 4.6 GHz, 3050 CPU seconds for 0.01 AR
3954050: 3.673 GHZ, 3900 CPU seconds for 0.01 AR

I don't think one needs to invoke an application back door.

Mark took his magic host off to other projects for a while, so its current RAC does not represent its performance.

Well, it's back on Seti full time now......
But I'm having a little trouble on re-entry into Setiland........
After over a week of crunching ABC with no trouble, after resuming Seti, I am getting computation errors.....
Played with it a little during the week, but with my work schedule, I don't have much time to make adjustments and see the results.....
Have backed off the FSB from 460 to 458....still errors.
Will have to play with some other parameters in the bios and see if I can get it sorted again...
I think that Seti accesses RAM a bit more than ABC did, so I am betting on RAM settings or mobo/NB settings.....I think the NB is being pushed to the limit with that high a FSB....
Now that my weekend is here, I'll have a little more time to play with things, just tried LOWERING the NB voltage a notch....
Don't know if it will ever see the top 20 computers again, with all of the hot rigs entering the ring lately, but I'm sure I'll get back into the top 40 at least......gimme a week or two....

I don't think it's your rig causing compute errors. I have been getting a lot of them myself lately. Ran all sorts of memory diagnostics and back the system down to stock speeds and voltages for a bit. Still had the problems, so I assume that there are some bad work units out there. I am running chicken apps.

---

When we finally figure it all out, all the rules will change and we can start all over again.

Y'all better watch your back. This little 4 core Vista box hostid=3954050 has broken into the top 20, and core-for-core is the top box on the project with RAC = 1375/core running the Crunch3r Vista build.

I wonder if maybe Crunch3r put in a back door to unlock the apple tweaks? :o
Explanation anyone?

On a quick comparison with some data I collected on msattler's box the CPU time reported for a result near 0.01 Angle range is scaled almost exactly to the difference in clock rate to msattler's hyper-Penryn.

msattler: 4.6 GHz, 3050 CPU seconds for 0.01 AR
3954050: 3.673 GHZ, 3900 CPU seconds for 0.01 AR

I don't think one needs to invoke an application back door.

Mark took his magic host off to other projects for a while, so its current RAC does not represent its performance.

Well, it's back on Seti full time now......
But I'm having a little trouble on re-entry into Setiland........
After over a week of crunching ABC with no trouble, after resuming Seti, I am getting computation errors.....
Played with it a little during the week, but with my work schedule, I don't have much time to make adjustments and see the results.....
Have backed off the FSB from 460 to 458....still errors.
Will have to play with some other parameters in the bios and see if I can get it sorted again...
I think that Seti accesses RAM a bit more than ABC did, so I am betting on RAM settings or mobo/NB settings.....I think the NB is being pushed to the limit with that high a FSB....
Now that my weekend is here, I'll have a little more time to play with things, just tried LOWERING the NB voltage a notch....
Don't know if it will ever see the top 20 computers again, with all of the hot rigs entering the ring lately, but I'm sure I'll get back into the top 40 at least......gimme a week or two....

I don't think it's your rig causing compute errors. I have been getting a lot of them myself lately. Ran all sorts of memory diagnostics and back the system down to stock speeds and voltages for a bit. Still had the problems, so I assume that there are some bad work units out there. I am running chicken apps.

I am not quite ready to blame the WUs.....I have not looked at them all, but the few I have looked at were comp errors on my rig, but successfully completed by a wingman....

---

"Time is simply the mechanism that keeps everything from happening all at once."

Y'all better watch your back. This little 4 core Vista box hostid=3954050 has broken into the top 20, and core-for-core is the top box on the project with RAC = 1375/core running the Crunch3r Vista build.

I wonder if maybe Crunch3r put in a back door to unlock the apple tweaks? :o
Explanation anyone?

On a quick comparison with some data I collected on msattler's box the CPU time reported for a result near 0.01 Angle range is scaled almost exactly to the difference in clock rate to msattler's hyper-Penryn.

msattler: 4.6 GHz, 3050 CPU seconds for 0.01 AR
3954050: 3.673 GHZ, 3900 CPU seconds for 0.01 AR

I don't think one needs to invoke an application back door.

Mark took his magic host off to other projects for a while, so its current RAC does not represent its performance.

Well, it's back on Seti full time now......
But I'm having a little trouble on re-entry into Setiland........
After over a week of crunching ABC with no trouble, after resuming Seti, I am getting computation errors.....
Played with it a little during the week, but with my work schedule, I don't have much time to make adjustments and see the results.....
Have backed off the FSB from 460 to 458....still errors.
Will have to play with some other parameters in the bios and see if I can get it sorted again...
I think that Seti accesses RAM a bit more than ABC did, so I am betting on RAM settings or mobo/NB settings.....I think the NB is being pushed to the limit with that high a FSB....
Now that my weekend is here, I'll have a little more time to play with things, just tried LOWERING the NB voltage a notch....
Don't know if it will ever see the top 20 computers again, with all of the hot rigs entering the ring lately, but I'm sure I'll get back into the top 40 at least......gimme a week or two....

I don't think it's your rig causing compute errors. I have been getting a lot of them myself lately. Ran all sorts of memory diagnostics and back the system down to stock speeds and voltages for a bit. Still had the problems, so I assume that there are some bad work units out there. I am running chicken apps.

I am not quite ready to blame the WUs.....I have not looked at them all, but the few I have looked at were comp errors on my rig, but successfully completed by a wingman....

Hmmm maybe something not mixing well in chicken soup?

---

When we finally figure it all out, all the rules will change and we can start all over again.

Hmmm maybe something not mixing well in chicken soup?

OMG........

After looking at a couple more of the results.........
May the kitties bite me in the butt...........I just realized......

After detaching and reattaching, the Seti projects folder had been blown away and recreated, thus nuking the optimized app.....I WAS RUNNING THE STOCK APP......
No wonder the run times seemed a little lame.........

So....I have reinstalled the opti app.....and will continue to look for the OCing problem.......

Now the kitties and I have to go and check out the other 7 rigs......they are probably all crunching stock too.....oh, the humanity......

---

"Time is simply the mechanism that keeps everything from happening all at once."

Hmmm maybe something not mixing well in chicken soup?

OMG........

After looking at a couple more of the results.........
May the kitties bite me in the butt...........I just realized......

After detaching and reattaching, the Seti projects folder had been blown away and recreated, thus nuking the optimized app.....I WAS RUNNING THE STOCK APP......
No wonder the run times seemed a little lame.........

So....I have reinstalled the opti app.....and will continue to look for the OCing problem.......

Now the kitties and I have to go and check out the other 7 rigs......they are probably all crunching stock too.....oh, the humanity......

I just had a hard drive die:( It was external and on the same firewire chain as the SETI disk. I wonder.... possible to cause program error if the app can't get to the Hard drive?

---

When we finally figure it all out, all the rules will change and we can start all over again.

Hmmm maybe something not mixing well in chicken soup?

OMG........

After looking at a couple more of the results.........
May the kitties bite me in the butt...........I just realized......

After detaching and reattaching, the Seti projects folder had been blown away and recreated, thus nuking the optimized app.....I WAS RUNNING THE STOCK APP......
No wonder the run times seemed a little lame.........

So....I have reinstalled the opti app.....and will continue to look for the OCing problem.......

Now the kitties and I have to go and check out the other 7 rigs......they are probably all crunching stock too.....oh, the humanity......

I just had a hard drive die:( It was external and on the same firewire chain as the SETI disk. I wonder.... possible to cause program error if the app can't get to the Hard drive?

I would think so, if that's where the Boinc folder was......the app would still be loaded in memory and running, but if it couldn't write checkpoints to the disk anymore or access any other needed files.....poof.....

---

"Time is simply the mechanism that keeps everything from happening all at once."

Hmmm maybe something not mixing well in chicken soup?

OMG........

After looking at a couple more of the results.........
May the kitties bite me in the butt...........I just realized......

After detaching and reattaching, the Seti projects folder had been blown away and recreated, thus nuking the optimized app.....I WAS RUNNING THE STOCK APP......
No wonder the run times seemed a little lame.........

So....I have reinstalled the opti app.....and will continue to look for the OCing problem.......

Now the kitties and I have to go and check out the other 7 rigs......they are probably all crunching stock too.....oh, the humanity......

Yup.....all 8 rigs were back on the stock app after the detach/reattach.....
Now if they will all just finish up their ABC duties and if I can get the phased quaddy back on track.....I should be able to start fixing the RAC problem....LOL...

---

"Time is simply the mechanism that keeps everything from happening all at once."