Message boards :
Number crunching :
exclusive_app
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
I tried to make the changes on my main cruncher as recommended by Hal9000. Added <exclusive_gpu_app>notepad.exe</exclusive_gpu_app> to cc_config file. Had Boinc read the config file and it noted the exclusion of notepad.exe in the messages. Started Notepad and waited. gpu apps stopped running. I don't suppose that for some reason notepad did not close and was hung? Did you check task manager to verify it had actually shut down? Waiting for you to tell it whether to save something? Grasping at straws here. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Cliff Harding Send message Joined: 18 Aug 99 Posts: 1432 Credit: 110,967,840 RAC: 67 |
Check out what I suggested above, it works on Win7 64-bit!! Don't have to mess with app_info.xml, notepad or anything else. |
Geek@Play Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 |
Hmmm........... Been running further testing. With notepad open, gpu work continues until one of the four gpu tasks completes. Then the remaining 3 go to "Waiting to run". Those 3 cuda tasks remain in "Waiting to run" mode when Notepad is shutdown. Waiting 5 minutes they are still in that mode. Opened up notepad to edit this posting. gpu apps are running now while using notepad. Shut down Notepad. Saw the status change quickly from "Running" to "Waiting to run" then back to "running" Running now as I type this. Rebooted computer and went through the entire sequence again with the same results. I have a copy of the messages if anyone is interested in it. Thanks to everyone. Perhaps I should upgrade to the current recommended Boinc? That would be the first thing I would suggest. Boinc....Boinc....Boinc....Boinc.... |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Well, it SHOULD not be necessary... In the Client configuration Boinc wiki it lists the cpu excluding option as being new in 6.2.13 and the GPU excluding option as being new in 6.10.20.....and you are using 6.10.58. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Geek@Play Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 |
Upgraded to Boinc version 6.12.33_windows_x86_64. Tested again using the same process. Working ok now. Boinc....Boinc....Boinc....Boinc.... |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Upgraded to Boinc version 6.12.33_windows_x86_64. LOL.... The kittyman proven wrong yet again. I suppose the real test would be to reinstall 6.10.58 and try it again. But I wouldn't expect you to do that now that things seem satisfactory. Glad you got it sorted. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Geek@Play Send message Joined: 31 Jul 01 Posts: 2467 Credit: 86,146,931 RAC: 0 |
Yes it was very weird. At one time it was working completely backwards. Guess I'm going to stay on this version while the kids are here. Boinc....Boinc....Boinc....Boinc.... |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
When I did the tests elier today I used Windows 7 x64, BOINC 6.10.58 x64, Nvidia driver 26658, & v.038 Lunatics apps. I also tried with 6.12.33 & had the same results as with 6.10.58. I saw the tasks as "suspended computation", (or whatever the exact message is) instead of "waiting to run". Waiting to run is normally a task that has had some processing and it waiting to be switched back to it. Could you see all of your tasks on the machine? Maybe one was running that you didn't see? I have seem BOINC start a new task instead of resuming one that was partly processed before. Just an idea. Could be your machine just didn't want to play right with 6.10.58. I can't seem to get any version over 6.10.58 to run on an XP machine I have at home. I was banging my head on it last night and then tried it on several at work today. All were fine, just no go on the one home box. I can get boinc.exe to run form the command line, but any version of manager over 6.10.58 gives an error trying to launch it. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Sounds like some permissions were messed up, like those required for boinc.exe to list the active processes etc. Running the boinc installer for either version probably fixed them. Jason "Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions. |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
I have tried with exclusive app just for fun and it works well on my machine. BM 6.10.58 Client 6.12.22 With each crime and every kindness we birth our future. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
Sounds like some permissions were messed up, like those required for boinc.exe to list the active processes etc. Running the boinc installer for either version probably fixed them. That is a good point. All of my test machines at work I run with admin rights & UAC disabled. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.