Clear as mud?

;) I can see clearly now, the mud has gone. I can see all obstacles in my way ...

Just out of curiosity - what do you check/inspect to find the older/in-use CUDA apps?
Some file masks in the directory (like *CUDA*.*), some strings in client_state.xml, ...?

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Clear as mud?

;) I can see clearly now, the mud has gone. I can see all obstacles in my way ...

Just out of curiosity - what do you check/inspect to find the older/in-use CUDA apps?
Some file masks in the directory (like *CUDA*.*), some strings in client_state.xml, ...?

I look to see if any version of the CUDA runtime DLL is present in the project directory: cudart*.dll

I look to see if any version of the CUDA runtime DLL is present in the project directory: cudart*.dll

Success, your detection works - the CUDA is now checked by default
(I faked the file as cudart77_55_33.dll <- no, I don't have 77-bit system ;) )

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Everything seems to be present and correct and now I can see that the problem with lack of work units is not something I can fix so it's just a matter of being patient.

Everything seems to be present and correct and now I can see that the problem with lack of work units is not something I can fix so it's just a matter of being patient.

There is no "lack of work units" (at servers), the problem is not to get them assigned to you, the problem are the slow (with failures/retries) downloads.

You still have only CPU tasks from SETI.
Did you check?:
1) Make sure you have 'Use NVIDIA GPU yes' in:
http://setiathome.berkeley.edu/prefs.php?subset=project

Is BOINC 'Requesting new tasks for NVIDIA' from SETI?
Do Einstein@Home CUDA tasks 'Running, High Priority'?

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

The stock application can be persuaded to work by setting an environment variable, suggested by nVidia.

This shows how to do it in Windows 7 - you have to be running as an administrator. I haven't tested yet whether it survives a reboot. (Edit - yes, it does)

Make sure you copy the variable name exactly:

CUDA_GRID_SIZE_COMPAT

and give it the value 1 (one)

Thanks, I checked it and it works. With this variable the "computation error" was removed and my GTX 660Ti began work OK with the stock application (Win7 64, Nvidia driver 306.23). Usually I have Lunatics installer in work, but it was interesting to check - how to use 660Ti without Lunatics.

---

Thanks for the help. Just upgraded to 660ti a few weeks ago and now i can crunch data again. Cheers

I wonder if setting CUDA_GRID_SIZE_COMPAT=1 is making the Lunatics CUDA applications to run slower?

(in case someone using stock application sets this, then decides to use Lunatics and keeps/forgets CUDA_GRID_SIZE_COMPAT=1)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I wonder if setting CUDA_GRID_SIZE_COMPAT=1 is making the Lunatics CUDA applications to run slower?

(in case someone using stock application sets this, then decides to use Lunatics and keeps/forgets CUDA_GRID_SIZE_COMPAT=1)

Not as far as I can tell, I have it set on my system as I tested the fix.

---

I've got exactly the same problem as I just replaced my two 450's with two 660ti's.

Noticed there was an issue then checked in here to see what was up.

However I don't have the V4.0 of the installer only 0.37.

I realise that they have been removed for licensing issues but does anyone have a copy they could send me?

TIA.

---

Ignore that last post.

Got it running. Seems stable so far.

---