I want to go back to the driver before Nvidia started to show less memory.
Does somebody know for sure on which driver the change was introduced? My logs don't go back far enough.
I've identified 195.62 as the most likely candidate, as with 197.16 it already comes up as 242 MB, but would feel better with independent verification.
Thanks a lot.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

195.62 is what I'm using and it does show all video memory.

---

I want to go back to the driver before Nvidia started to show less memory.
Does somebody know for sure on which driver the change was introduced? My logs don't go back far enough.
I've identified 195.62 as the most likely candidate, as with 197.16 it already comes up as 242 MB, but would feel better with independent verification.
Thanks a lot.

I've not done a lot of reverting, but I think you've got the right bracket.

I was about to suggest 190.38 (the first to support CUDA 2.3 DLLs) - you don't want to go back any earlier than that, whatever you do. But your Quadro FX 570M with Vista 32 imposes limitations - they didn't release 190 for that system. 195.62 seems to be the best choice:

http://www.nvidia.com/object/notebook_winvista_win7_195.62_whql.html

197.13 is the first driver that reported less memory, i asked why on Nvidia's developers Cuda forum, but got no answer from any developer, :-(

Cuda-Z and Boinc report less Memory with 197.xx drivers

Claggy

Thank you all. :)

Have gone back to 195.62 - one GPU back into the fold.

Small hiccup - windows panicked and put in the original drivers, which caused the Nvidia setup to hang. Quickly solved, just rerun the setup.

Now to running down cache to put a suitable application into the app_info file.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

Thank you all. :)

Have gone back to 195.62 - one GPU back into the fold.

Small hiccup - windows panicked and put in the original drivers, which caused the Nvidia setup to hang. Quickly solved, just rerun the setup.

Now to running down cache to put a suitable application into the app_info file.

Running down cache is purely precautionary - you shouldn't lose a thing, especially if you use the latest Lunatics Unified Installer as a starting point- Jason has been careful to put as much compatibility as possible into the app_info elements: in any event, most of the cache losses were on 64-bit systems, 32-bit is simpler.

Having said that, performing major surgery at the time when WU transfusions are readily available would be a wise precaution. And don't operate powerful editing machinery when tired ;-)

190.38 and 191.07 are fastest driver for crunching.

---

I am cruncher :)
I LOVE SETI BOINC :)

Running down cache is purely precautionary - you shouldn't lose a thing, especially if you use the latest Lunatics Unified Installer as a starting point- Jason has been careful to put as much compatibility as possible into the app_info elements: in any event, most of the cache losses were on 64-bit systems, 32-bit is simpler.

Having said that, performing major surgery at the time when WU transfusions are readily available would be a wise precaution. And don't operate powerful editing machinery when tired ;-)

Does the Lunatics installer modify anything outside of the data folder (on my machine, C:\Users\sarmitage\AppData\Local\BOINC\)? If not, couldn't one just stop the client and manager, make a copy of that folder, and then apply the changes? That way, if anything goes wrong, one could just restore the backup and not have lost anything.

-S

One of the safest things you can do without having to run down the cache is set "no new tasks" turn network communication off, then close BOINC, make a backup of the data directory, then do the editing. When you bring BOINC back up, if everything goes haywire, close BOINC, restore the backup, and try again.

Once everything looks fine, allow network and new tasks.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

One of the safest things you can do without having to run down the cache is set "no new tasks" turn network communication off, then close BOINC, make a backup of the data directory, then do the editing. When you bring BOINC back up, if everything goes haywire, close BOINC, restore the backup, and try again.

Once everything looks fine, allow network and new tasks.

OK cool, that was my understanding as well; guess it's about time I try the opp apps for CPU =)

OK cool, that was my understanding as well; guess it's about time I try the opp apps for CPU =)

With such hardware, it would be a shame not to try. :D

---

Who the hell is General Failure and why is he reading my harddisk?¿