Forum > Discussion Forum
Just don't know where I am gonna end up............
Jason G:
--- Quote from: msattler on 17 Jul 2009, 12:02:56 pm ---...
VLARkill is cherry picking, pure and simple.......
Unless it can automatically return the work within the host to the CPU and not send it back to Seti for some other 'sucker' to crunch, it bites the big one. And only contributes to current Seti woes.
...
--- End quote ---
That's certainly one opinion that many might agree with, and one that has been tossed about here lately. Mine happens to be that sending work that disables user machines for normal use with flawed application implementation, drives away users, potential donors and makes for a very poor overall picture.
What needs fixing is the application, and as soon as we can get to that without all the peripheral politics continually obstructing progress, then the sooner the issue is moot. It sure as heck doesn't look like anyone else is going to be fixing it but us.
In any case, differences of opinion aside, all the best Mark, and good luck with getting things sorted.
Regards, Jason
Raistmer:
--- Quote from: msattler on 17 Jul 2009, 12:02:56 pm ---VLARkill is cherry picking, pure and simple.......
Unless it can automatically return the work within the host to the CPU
--- End quote ---
Use Rebranding tool 1.9 if you have problems with that. It's pretty simple in use, even for novice users. And we talk about 9-year of experience here.
msattler:
--- Quote from: Jason G on 17 Jul 2009, 12:34:34 pm ---
--- Quote from: msattler on 17 Jul 2009, 12:02:56 pm ---...
VLARkill is cherry picking, pure and simple.......
Unless it can automatically return the work within the host to the CPU and not send it back to Seti for some other 'sucker' to crunch, it bites the big one. And only contributes to current Seti woes.
...
--- End quote ---
That's certainly one opinion that many might agree with, and one that has been tossed about here lately. Mine happens to be that sending work that disables user machines for normal use with flawed application implementation, drives away users, potential donors and makes for a very poor overall picture.
What needs fixing is the application, and as soon as we can get to that without all the peripheral politics continually obstructing progress, then the sooner the issue is moot. It sure as heck doesn't look like anyone else is going to be fixing it but us.
In any case, differences of opinion aside, all the best Mark, and good luck with getting things sorted.
Regards, Jason
--- End quote ---
Like I think you said............
It's not the work that is flawed..........it's how it is worked on.
You folks here have done sooooooooooooooooo much more than Seti could ever give you credit for.
And I don't mean to diss Raistmer's efforts.........it's just that the work-around is a bad thing for the project.
The only solution is to find a way to crunch it properly.........which I know you are working your hearts out on it.
Although in the real world 'catch and release' is a good thing......in Seti crunching it poisons the pond.
msattler:
--- Quote from: Raistmer on 17 Jul 2009, 12:47:59 pm ---
--- Quote from: msattler on 17 Jul 2009, 12:02:56 pm ---VLARkill is cherry picking, pure and simple.......
Unless it can automatically return the work within the host to the CPU
--- End quote ---
Use Rebranding tool 1.9 if you have problems with that. It's pretty simple in use, even for novice users. And we talk about 9-year of experience here.
--- End quote ---
If and when I get the Cuda card up and running with the current drivers I will try that, or the non-VLARkill app that is available.
Your work is not unappreciated, Raistmer........you have undoubtedly spent countless hours on it.
I just dislike the premise that you can toss out what you don't like and take the rest.
That has never been the Seti way.
Jason G:
When all's said and done Mark, rest assured that none of us 'like' it, and I personally will be happiest when the necessity for any kind of workaround is gone, as that means our fixes can be introduced to stock. Until then, there are thankfully some very effective workarounds that take some end-user effort. Let's hope they're enough to cover the gap until it can be fixed properly, without all this bickering.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version