All the DLLs in one zip file...
https://s3.amazonaws.com/SETI/nVidia+DLLs.zip

nVidia Dev. Driver 270.32
https://s3.amazonaws.com/SETI/devdriver_4.0_winvista-win7_64_270.32_general.exe

Well, I did in fact goof on the app_info edit the first time and it quickly reverted to the stock app until I stopped the process. I reinstalled the Lunatics app and then did edit the app_info correctly and started up BOINC. The program didn't complain in any way finding all the files referenced in the app_info, just that it downloaded new work, started it, finished it and then complained that there was no output file for the task. I am running 64bit Win7 with the 266.58 Nvidia driver.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Strange, I am running the same with no complaints. Windows 7 as well.

*Edit - Also, have removed the individual files for download, so you will now have to download the .zip file.

Well, I did in fact goof on the app_info edit the first time and it quickly reverted to the stock app until I stopped the process. I reinstalled the Lunatics app and then did edit the app_info correctly and started up BOINC. The program didn't complain in any way finding all the files referenced in the app_info, just that it downloaded new work, started it, finished it and then complained that there was no output file for the task. I am running 64bit Win7 with the 266.58 Nvidia driver.

"no output file for the task" is evidence that the application crashed. Go and find out what the crash was. Before you risk any more.

Edit - pick any of these.

2nd. edit - "exit code -1073741515 (0xc0000135)". Typical of an incompatible DLL.

Eck, scratch everything. I ran with the 260.99's, 266.58's and the 267.24's and everything seemed ok. Got a BSOD 0x18 error, reference_by_pointer error. Seems to be a miss match of driver and cuda dll's as it only happens when crunching. DO NOT INSTALL the 270.32's if you are a gamer. You can not enable SLi with them, texture corruption in some game, crashes in some games, but some games show better performance. Extremely beta continue at your own risk.

I'm rolling back now, I didn't have any error'd units with the new cuda, but I did have a machine crash. It's not ready for prime time yet! That's what testing is all about now I know. ;)

---

Traveling through space at ~67,000mph!

Eck, scratch everything. I ran with the 260.99's, 266.58's and the 267.24's and everything seemed ok. Got a BSOD 0x18 error, reference_by_pointer error. Seems to be a miss match of driver and cuda dll's as it only happens when crunching. DO NOT INSTALL the 270.32's if you are a gamer. You can not enable SLi with them, texture corruption in some game, crashes in some games, but some games show better performance. Extremely beta continue at your own risk.

I'm rolling back now, I didn't have any error'd units with the new cuda, but I did have a machine crash. It's not ready for prime time yet! That's what testing is all about now I know. ;)

How about DO NOT INSTALL period.

Somehow, I don't think the S@H production system is a suitable test environment. These dlls will make into the production code once those who are familiar with their use and the delta between them and the previous versions are satisfied with their stability and suitability; installing them before this is foolhardy.

---

All the DLLs in one zip file...
https://s3.amazonaws.com/SETI/nVidia+DLLs.zip

nVidia Dev. Driver 270.32
https://s3.amazonaws.com/SETI/devdriver_4.0_winvista-win7_64_270.32_general.exe

Here's a another source for these 64 bit 270.32 drivers and this one is for Vista and Windows 7.
http://www.mediafire.com/?715s7j1sntoso5x

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Hey, been working stable for days on my machine. Never had a problem with corrupted units. Strange.

I believe lunatics uses a 32-bit app regardless. I am running the 32-bit DLLs on the current (non dev.) nVidia driver. Might want to give that a try. My last 90+ WUs were good. Yesterday was over 200 until I decided to play with my card clock settings a little. Also using the most recent fftw DLL, but I don't recommend that. I will be compiling a custom version today, will let everyone know how that turns out.

If we can get another 5-10% performance increase (and stability) out of the code, that would be great. Same effect as a hardware upgrade, but at no cost.
It should be noted that at one time I did try the 170 driver. There might be something lingering on the system from that experiment that is providing the stability, however unlikely.

"no output file for the task" is evidence that the application crashed. Go and find out what the crash was. Before you risk any more.

Edit - pick any of these.

2nd. edit - "exit code -1073741515 (0xc0000135)". Typical of an incompatible DLL.

There was no compute time on those units, so they failed before they even started. Can you tell us what version of the DLLs you are running and what driver version? Also, did you use the fftw DLL?

How about DO NOT INSTALL period.

Somehow, I don't think the S@H production system is a suitable test environment. These dlls will make into the production code once those who are familiar with their use and the delta between them and the previous versions are satisfied with their stability and suitability; installing them before this is foolhardy.

If that was the case you shouldn't be using lunatics apps or optimizations they have in place until they are added into the Seti@Home code. Your logic makes no sense. S@H's production environment is a perfect place to test performance of cuda....it uses cuda and give you varied results sizes and work loads. Each to his own. When looking to get the most out of your system, using the stock apps giving to you and the 'safe' drivers is foolhardy, or at least not often the best choice. Hence the reason you experiment.

For what it's worth it ran good up until the machine BSOD with an 0x18 error. No errored unit what so ever even cause when the BSOD happened. I think with the right mix of hardware etc it would be a good setup. Especially if you are willing to give the dev drivers a chance. However they don't enable you to use SLi and don't have the Physx software included. So it take a bit of work. The issues reported from gaming was enough to make me roll back to the beta 267.24's and the original lunatics supplied dll's.

My gaming environment is much more important to me than Seti@Home, just the way it is....

---

Traveling through space at ~67,000mph!

There was no compute time on those units, so they failed before they even started. Can you tell us what version of the DLLs you are running and what driver version? Also, did you use the fftw DLL?

Yes, they crashed before they ever got started. The problem likely was I didn't realize the Lunatics app was 32 bit. I downloaded and installed the 64bit DLL's thinking they were the correct versions because I have a 64bit version of Windows7. Probably where the DLL incompatibility arose. I experimented where I shouldn't have I think. The improvement in crunching was too enticing. I think I'll just stick with the stock Lunatics app and keep watching the website for news of the expected Fermi optimized new Lunatics client. Maybe they will also utilize these new CUDA 4.0 DLL's.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I played around with the new driver & dll's at work for a while today. Sadly no joy on the ole 8500 GT. As I was in Win7 x64 I played around with the x64 & x86 dlls. Same results either way. After 49 seconds in, splat. Since I was messing about with drivers I did take the time to upgrade to the CUDA 3.0 App tho. As I was still running the 2.0 one.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Dependency Walker is your friend for problems like the last two.

Hey, if you want a free performance bump....

Create a free micro linux instance on amazon AWS and run BOINC on it. You will get one free CPU core of computation. ;-)

Strange, I am running the same with no complaints. Windows 7 as well.

Have you deleted the old DLLs to be sure the Client uses the new ones? ;-)

Helli

---

A loooong time ago: First Credits after SETI@home Restart

Strange, I am running the same with no complaints. Windows 7 as well.

Have you deleted the old DLLs to be sure the Client uses the new ones? ;-)

Helli

You don't need to do that do you you? With the .dll selection for the apps being hardcoded in the app xml? May explain why mine ran fine until a certain point then went crazy on me.

---

Traveling through space at ~67,000mph!

...
May explain why mine ran fine until a certain point then went crazy on me.

Rename or delete the old ones and you know why.

Helli

---

A loooong time ago: First Credits after SETI@home Restart

...
May explain why mine ran fine until a certain point then went crazy on me.

Rename or delete the old ones and you know why.

Helli

Use Process Explorer to see where it's finding the DLLs it's using.

...
May explain why mine ran fine until a certain point then went crazy on me.

Rename or delete the old ones and you know why.

Helli

Use Process Explorer to see where it's finding the DLLs it's using.

I was being semi-sarcastic I had actually removed the old dll's from the folder completely along with the app xml changes. Everything ran fine on my end, up until the BSOD caused by the video card driver. But both were beta...still using the drivers, but not the cuda dlls.

---

Traveling through space at ~67,000mph!

...
May explain why mine ran fine until a certain point then went crazy on me.

Rename or delete the old ones and you know why.

Helli

Use Process Explorer to see where it's finding the DLLs it's using.

I was being semi-sarcastic I had actually removed the old dll's from the folder completely along with the app xml changes. Everything ran fine on my end, up until the BSOD caused by the video card driver. But both were beta...still using the drivers, but not the cuda dlls.

I wasn't. I confidently predicted that a task would crash during early beta testing, because I knew I was using the wrong DLLs. Instead, Windows found the right DLLs installed in a completely different part of the hard disk, and ran the task to completion for me.

There were some other files with similar naming convention that were in the toolkit. Just being lazy, I copied them all over to the project directory. Now I'm thinking the DLLs might be dependent on one of them. I will take all of the 32-Bit versions, zip them and post them shortly. Perhaps this is the reason it is working for me and not others.

*Edit: Cancel that, works fine without them.

Try reinstalling Lunatics with Astropulse off, CUDA on, and SETI set to the x32 SSE (Faster on AMD) option on. If you are running Intel, this is suboptimal, but testing it will help us understand why this is failing. Also, I dont think it will amount to a significant performance decrease.