| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the extra info about how the uninstaller (doesn't) work. I will come back with any new findings if I have problems.
|
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
The uninstaller moves the files, and the installer moves them back. Truly insane. This should only happen if you've upgraded from v5-client once-upon-a-time, and is done in case the uninstallation is due to wanting to revert-back to v5-client. If you upgrade from one v6-client to a later one, it should not move any files. Interestingly enough, it seems v6.6.21 and later should not move the files back to v5-location on uninstallation... BOINC 6.6.20 has been superseded by 6.6.21 mere hours after it launched. There are also hundreds of outstanding bugs. So, good luck. It was announced beforehand that there would be multiple v6.6.xx-releases, there the initial release is to get the new CPU/GPU-scheduler out to the public as a replacement for the mediocre scheduling in v6.4.x-clients. Various bug-fixes should come in a later release. ![]() "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ingleside, I admire your optimism, but nothing you say relates to my personal experience.
"My opinion is that 6.4.x should never have been released because of the work fetch and resource scheduler issues." - John.McLeod (principal author of the client scheduler code) |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
Ingleside, I admire your optimism, but nothing you say relates to my personal experience. What, are you saying the installer moves the files even you've never had v5 installed? "My opinion is that 6.4.x should never have been released because of the work fetch and resource scheduler issues." - John.McLeod (principal author of the client scheduler code) Well, I've never used any of the v6-clients before v6.6.20, but would guess "v6.4.x should only have been released to CUDA-users" would have been the more correct approach, since afterall they needed a new client, and running-through many of the later alpha-builds would have given more problems than v6.4.x apparently gave... As for bugs, most bugs is present in v6.2.28 (and earlier clients), so releasing a working replacement to the broken v6.4.x-scheduler atleast to me seems like the right choise. For anyone running v6.2.xx or v5.10.45, there aren't really any good reasons to upgrade at this point, except if you've got a CUDA-capable card you wants to use... ![]() "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What, are you saying the installer moves the files even you've never had v5 installed? Last time I checked, this is what the 6.2 installer does. |
||
|
|
|