...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....
VLARkill is cherry picking, pure and simple.......Unless it can automatically return the work within the host to the CPU
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.... 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
Quote from: msattler on 17 Jul 2009, 12:02:56 pmVLARkill is cherry picking, pure and simple.......Unless it can automatically return the work within the host to the CPU 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.
I am currently running the MB_6.08_CUDA_V12_noKill_FPLim2048.exe app in cunjunction with the 1.9 rebranding that runs 2 times each day. This setup works fine.
From what I understand.....and correct me if I am wrong.......I cannot run that app right now because my friggin' Cuda card won't run on anything more current than the 182.50 drivers.......That's why it's going back to EVGA for replacement.
The 6.6.36 Boinc is going back for replacement also........but that is another whole set of issues.
... as a better bandaid....