I know this might seem off topic, but since Collatz is the only alternative for ATI GPU's - I figured to ask here.

Collatz went offline last night -- and is still offline 18 hours later. Did I miss a notice about this, or did something unplanned and bad happen over there?

I figure there are Collatz folks here who might know.

---

I dont recall seeing or hearing about a scheduled downtime, so I'm guessing another WU got stuck in the server again??
;-p

---

9:25 pm Est Collatz is showing signs of life now at least I get a different message now its "cant open database"
Just tried the site forums are working now.

No -- it looks like the problem are still going on. I'm hoping that Slicker has some time to focus on the problems over there (could be more than one issue).

It would be great if he could get a second system up to operate the message base side of things.

---

The weekend looms, Collatz is already down - it is time for a change freeze Travis!!

I am thinking that Slicker may have been called out of town unexpectedly. It isn't really like him to not pre=announce an outage. And this has been now a 30 hour and counting outage over there.

Yes, one can sometimes get a phone-modem like connection to the message boards there. But there are virtually no messages getting posted and nothing from Slicker for the past couple of days.

I'm hoping that when he returns he'll be able to put things right again. It was a good post vacation 10 day run there, but that is over.

---

As others are finding ... nothing doing over at Collatz. Cannot even get the home page, most of the time.

I am still crunching and the work results are getting through, just not reporting.

Something major must have gone down yesterday, and we can assume nothing is likely to be done until Monday.

I will crunch Collatz until my cache runs out, then return to MW.

In the meantime, I will enjoy sub-10K daily RAC reports.

---

Go away, I was asleep

>I will crunch Collatz until my cache runs out, then return to MW.
My Collatz cache ran out yesterday, but can't crunch MW on that GPU as its only a 5870 and doesn't qualify.
I was only running Collatz in the first place because I couldn't get it to run MW, no matter how many copies of variouusly renamed .dlls I spread around various folders on the disk.

---

Cheers,

PeterV

.

>I will crunch Collatz until my cache runs out, then return to MW.
My Collatz cache ran out yesterday, but can't crunch MW on that GPU as its only a 5870 and doesn't qualify.

Hell I cannot even get MW to crunch on my machines now...
6.10.18 and cat 9.1... I have put the .20 app in as usual and it keeps saying there is not Nvidia device found (no shit it is ATI's)
Twin 4850's.

---

>I will crunch Collatz until my cache runs out, then return to MW.
My Collatz cache ran out yesterday, but can't crunch MW on that GPU as its only a 5870 and doesn't qualify.

Hell I cannot even get MW to crunch on my machines now...
6.10.18 and cat 9.1... I have put the .20 app in as usual and it keeps saying there is not Nvidia device found (no shit it is ATI's)
Twin 4850's.

Try cat 9.11 and 20.B ATI...I have it running on a 4890, XP32, 6.10.18...and no VPU resets yet!!

---

Click to help Seti City.

@boosted:

I had that problem with my 4870 with Cat 8.12 after upgrading BOINC from 6.6.20 to 6.10.17. I uninstalled the Cat 8.12 and installed Cat 9.5, then BOINC saw the card. I then uninstalled Cat 9.5 and reinstalled Cat 8.12 (for stability) and BOINC still saw the card.

---

Calm Chaos Forum...Join Calm Chaos Now

>I will crunch Collatz until my cache runs out, then return to MW.
My Collatz cache ran out yesterday, but can't crunch MW on that GPU as its only a 5870 and doesn't qualify.

Do you mean a 5770? The 5870 should work.

Yes, 5870.
Should work, but doesn't, plus my hd is starting to clog up with the number of copies of amd/ati*.dlls that I've copied and renamed in an attempt to get it working.
It runs Collatz like a charm. Too bad Collatz died the other day.

---

Cheers,

PeterV

.

You don't need to do the copy/rename routine any more.

Install the opti app .20b, the link that says ATI, not AMD (it's referring to the name of the DLLs, and ATI is the default for 9.1+ hence no renaming/copying).

Use the latest Catalyst drivers. I've got both 9.10 and 9.11 running just fine with Collatz and MW both, and older drivers that predate the 5xxx series of cards are going to give you wonky results.

Fire up BOINC and it should work.

---

Yes, 5870.
Should work, but doesn't, plus my hd is starting to clog up with the number of copies of amd/ati*.dlls that I've copied and renamed in an attempt to get it working.
It runs Collatz like a charm. Too bad Collatz died the other day.

I'm running numerous 5870's & 5850' & 4870's Without renaming anything, the 20b app & 9.10 or 9.11 work on all of them now like JerWA said, for me anyway. I get a VPU Error now & then but not like I used to.

Just gave it another [abortive] try. Errored all MW WUs instantly.
Possible confounding factor - its running win7-64. For reasons best known to itself, in spite of my telling the boinc install program to put boinc data in C:\boincdata, the MW WUs ended up in C:\program files\boinc\... Just checked, and my 140-odd waiting-to-upload collatz WUs are also in C:\program files\boinc\..., and the auto-d/l'd [isn't it about time you upgraded the server s/w, Travis :)] collatz opti app is in c:\boincdata. Strange...
Another possible confounding factor is that I'm running the xfx driver that came with the card which has incorporated into it CCC v20090826.2224.38413.
Shouldn't someone build an install script for this stuff?

---

Cheers,

PeterV

.

I'm also on Win7 x64, on all my machines but one (which is running 2008 R2).

Are you logged in as an admin? Running BOINC as one? Not installing as a service, right?

I can't explain what you're seeing. I've got 5 machines that have been running Win 7 for months now, including a couple running it way before RC, using BOINC Manager versions back in the 6.4 range all the way to the latest dev version and have not had this problem on any of them.

I'd suspect the driver isn't helping. Get the official 9.11 version. That may be why they all puked immediately (couldn't find the DLLs perhaps?).

Make sure you're using the latest BOINC Manager as well, 6.10.18 or whatever it may be right now. Run it, make it uninstall itself, then install again to double check the data path and such.

Maybe someone with fresher experience with the installer can shed some light on a situation in which it would use the program files path for anything other than the client itself.

PS: While tweaking the initial setup of the project, set your queue as low as possible and as soon as you add the project hit no new tasks. It may or may not sneak one by, but that'll give you time to make sure all the paths created properly, apps are in place, etc.

Edit: I couldn't find any records for the machine failing WUs, could you link it and/or a failed task? It should say why it died, if it was missing DLLs etc.

---

Uninstalled boinc 6.10.13, installed 6.10.18.
Uninstalled the xfx driver, installed 9.11.
It still put the data in c:\program files\boinc...
Still gave me the unwanted ^%*&^^&&* boinc screensaver.
Still comp. errored the MW WUs, though the first one was 'waiting to run' for at least 15mins before I got bored watching and went away [no other programs running, so no competition for boinc resources].
>logged on as root?
How do I know? None of my PCs have passwords.
How's that server upgrade going, Travis? :)
And as Collatz is still offline [I lost the batch of WUs I got during its brief return to life yesterday when I uninstalled boinc] my 5870 is sitting idle [again].

---

Cheers,

PeterV

.

Collatz is on line & has been all day as far as I know as I was getting my Caches refilled all day. Haven't had any Problems getting new work and Uploading & Reporting Finished Wu's ...

After yesterday's uninstalls/reinstalls, and with MW still not working, I tried reattaching to Collatz [its the only box that runs Collatz, and then only because it won't run MW]. 'cannot connect to server'.

---

Cheers,

PeterV

.