Okay since you experts have this all figured out, the question is to app_info or not to app_info. My systems run either way, is there a reason to run the app_info?
Printable View
Okay since you experts have this all figured out, the question is to app_info or not to app_info. My systems run either way, is there a reason to run the app_info?
My humble advice, if you do not see an increase in production with the app_info file than your system is fine without it. I would recommend checking up on it once a day just in case the project wizards update the app. X_XQuote:
Originally Posted by Bryan
Hmmm. Well, in this case, Win 7, go toQuote:
Originally Posted by Groundhog@SETI.USA
Start->All Programs->Accessories
and Right-Click->Command Prompt
You can then select to "Run as Administrator"
I looked up your hosts over at PG and I think I've found the one with problems. It doesn't look like the same problem I had. You can get those more detailed results by looking at the results from a specific WU from your system. (Click on "Task Details" on your Task list on the PG website.)Quote:
Originally Posted by Groundhog@SETI.USA
BOINC isn't installed as a service on that machine, is it? (AKA Protected mode install...) So, I wonder why BOINC thinks it sees the device, (it wouldn't D/L GPU WU's if it didn't) but then the Project has issues accessing it. Unless, you're using Max's instructions with the app_info. So BOINC grabs the WU's even though it didn't find a GPU. But I don't think PG would report a GPU in the Hosts list if BOINC hadn't seen it. Strange.Code:<stderr_txt>
Sieve started: 4314907000000000 <= p < 4314910000000000
Thread 0 starting
Error: Creating Context. (clCreateContextFromType): Device not found.
13:53:47 (2140): called boinc_finish
</stderr_txt>
No luck with the cacls. Apparently it has been superceeded with icacls and the syntax is different. I'm not a Windows expert.Quote:
Originally Posted by Mumps
The program wasn't installed as a service. Boinc can see the GPU and I am running DNETC while I'm trying to get the PG working. Not sure what to do next. I do appreciate your working with me on this. I did try running with and without the app_info file.
GH have you tried deleting the PrimeGrid project folder to reset the project? (I call this method a Hard Reset).
If the problem is a Windows permission thing you could try changing user ownership of BOINC's folder and sub-folders. Its a minor chore to do it Microsoft's way or you can use a free registry hack called Take Ownership. I have it on my system and it works 99% of the time.
Interesting. On both my Win7 64bit systems, cacls is available and works, it just warns that it's deprecated. (Deprecated means it'll work, but don't expect it to work after the next patch/update/upgrade. :)) ) And I don't recall manually copying it across from a WinXP installation. Here's the icacls syntax...Quote:
Originally Posted by Groundhog@SETI.USA
Code:icacls C:\Windows\Temp /T /Grant boinc_project:F
icacls C:\Windows\Temp /T /Grant boinc_master:F
Question, would it be a good idea to run the "p3 b-1" in the CMD line for this challenge?
I can't see why it wouldn't... though you'd have to change your app_info file if they ever change the app...Quote:
Originally Posted by Mike029
Well, I finally resorted to a full HD wipe and fresh xp64 install. Still fail. -117.
Wow, that's some dedication, Zombie! I really feel for you. Can the guys over at PG that admin the forums help at all in a case like this? Surely they must be curious (at the very least), why their program won't run on so many rigs...
This PG seems to be such a fickle program I'm scared to change anything for fear it'll stop working. I get wu's, I crunch wu's, I better leave well enough alone.Quote:
Originally Posted by Maxwell
Have you checked your account to make sure none of them are erroring out?Quote:
Originally Posted by Mike029
I reported earlier that I was having problems with my 5970s under Win 7 Pro having a high number of wu finish as invalid. It was actually 42%. I was running CAT 10.10.
Tonight I installed CAT 10.12 Beta and my problems went away. Both machines now validating all wu just like the dual 5870s which run CAT 10.10 under Vista.
I don't know if it is a function of the 5970, Win 7 versus Vista, or the old dual Xeons versus a quad but I'm quite happy now :D
Most Excellent news. Keep that furnace stoked for the challenge. Crunch on!Quote:
Originally Posted by Bryan
That's awesome, Bryan! I would highly recommend everyone with PG "issues" to at least try the new 10/12 drivers. I just installed them on both my 58xx series rig and Kat's 48xx series rig, and they are working perfect.
Great news!:cool:
It sounds like we are ready to party very soon!!Quote:
Originally Posted by DrPop
Quote:
Originally Posted by DrPop
I installed the 10.12 drivers on 12/13 and I used driver sweeper first! Still having the same problems! This box must be cursed. :((
I think they had some bad wu's I had about a dozen that errorred out, none before, and none since. It looked like they were all version 1.36 as opposed to 1.37.
On the plus side, I installed my 570's and have gotten the first couple wu's back. My 275GTXs were doing a wu in about 1130 sec. First 2 wu's out of the 570s were done in 335 sec.
Me Likee :cool:
I just got around to testing this today. Uninstalled the old drivers, ran driver sweeper, installed 10.12 APP, and with stock settings, I have yet to get a PG error. 25 WUs without a problem...Quote:
Originally Posted by Harley
Wish we had more of those! That is about 3X faster than a 5870!!! My 5970s at 925M are doing about 1025 and the 5870s at 965 are doing 960s.Quote:
Originally Posted by Shadowlurker
Quote:
Originally Posted by Harley
YES,YES,YES!!!!!!!!!!!! Got it working. 2 more 5970's ready for the challenge! Looking good. I have them clocked at 935 with no errors.
I'm always a fan of those magical dances that get computer stuff working. Congrats!!! :cool:Quote:
Originally Posted by Harley
Quote:
Originally Posted by Maxwell
Thanks Max. \:D/
Ok, what is driver sweeper? I'll give the 10.12 a try but I guess I need to clean up the existing drivers first.
Good to hear.Quote:
Originally Posted by Harley
Driver Sweeper cleans out all the residual file from prior driver installs. Helps avoid "issues" with installs. Uninstall driver, run Driver Sweeper, install new driver. Should make it standard practice... ;)Quote:
Originally Posted by Groundhog@SETI.USA
You can download it here (go for version 2.7.5): http://www.phyxion.net/Driver-Sweeper/View-category
Okay the verdict is in: Run the app_info with count set to .5! I see a 4% increase in GPU loading AND it directly translates to 4% lower wu run times! My 5870s dropped from 960s per wu to 922s.
I also set the cmdline to p3 b-1 but I have no idea if that actually does anything. It doesn't hurt though.
Interesting. Do you think it's worth trying the opti_app on either of our rigs? Mine w/ dual 58xx and Kat's w/ dual 48xx. If you think it's worth it I'll give it a whirl tomorrow after work - I mean 4% is 4%...If we lose by that much I'd be grumpy that I didn't do it! :D
In a last-ditch effort to help anyone still having problems with the ATI cards and PG's app, here's a PM I just got from Harley, posted with his permission:
What I had - 10.12 with CCC beta. [NOTHING had worked for him at this point]
What I did - Step by step.
1) Removed 10.12 by using the 10.12 download.
2) Rebooted into safe mode.
3) Used driver sweeper in safe mode to remove remaining ati bits and pieces.
4) Rebooted normal mode.
5) Installed CCC 10.11 Accelerated Parallel Processing (APP).
6) Rebooted normal mode.
7) Downloaded and installed CCC 10.12 Accelerated Parallel Processing (APP). NOT THE BETA VERSION OF CCC.
I did this without removing any part of 10.11.
8) Rebooted.
Started Boinc and everything worked. That's it.
I hope this helps. Harley.
Any of you whizards have an app_info for ATI that will crunch both CPU and GPU? I would rather someone give me one rather than me having to actually think through it ;) Every time I try to think it gets me into trouble.
Not I, I stole somebody elses just to get my 5870 to work.
Apti App is the way to go. Thanks Bryan.
Running wu's 1 at a time took my 18 mins to complete on my Duel ATI 5870's. Running 2 at a time took me 32 mins to complete 2 so running 2 at a time knocked 4 mins off my times. Not bad
I'm running the cards at 940 Clocks 550 mem. without boosting the voltage. I'm going to run this for the next bunch of wu's to check for errors. Temps are 70 & 62.
Only program I could use to modify the clock and mem. was the Ray Adams program. CCC and Afterburner would not let me go above 900 clock or below 900 mem. What other program works to get around this problem?
MSi AfterBurner is an excellent OC tool for ATI or Nvida. One quirk though ... to drop memory down to like 450 you have to start MSI AB, drop move the slider to the left, hit apply, and then exit MSI AB. Then restart MSI AB and repeat the above till you get it where you want it. Be sure you don't check the apply settings at MSI start up or you will never get there :)Quote:
Originally Posted by Mike029