| 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: 12
|
|
| Author |
|
|
CandymanWCG
Senior Cruncher Romania Joined: Dec 20, 2010 Post Count: 421 Status: Offline Project Badges:
|
I fail to see how something that used to display correctly as Custom starts displaying as Standard because I haven't changed some key values... Furthermore, why is it that if I delete the profile and create it again with my custom attributes (the same as before), it will display correctly as Custom?
----------------------------------------No, Sekerob, not looking to pick a fight here and I appreciate your quick reply, but that explanation does not stick. Either way, I was just proposing a workaround or solution that I have already tested twice and it worked for me. Cheers! Knowledge is limited. Imagination encircles the world! - Albert Einstein ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
If it does not do what it says in the manual, then there's a bug. At one time I started off with the Standard profile (60% CPU time), set the computing to 100% and ever since never looked back... always Customs. Work around's are always handy, but not exactly ideal. Just for the sake of exercise I'll reenter the Standard key field values and see what happens... if it on next visit the device lists again as using the ''Standard'' standard... I'll sit back and let it sink.
--//-- |
||
|
|
|