I just discovered Neither this Host or this Host has received any credit since about the 8'th of March, if I remember right that's probably about the time I messed with the Application a little. By messing I just meant I changed Applications. I remember having trouble getting a couple of them running again with out erring the WU's but thought I had it straightened out.

Apparently I didn't as I now discover a week later on both Box's ... The only way it seems for these 2 Box's to receive Credit is to run the 0.17 SSE3 Application in them. If I use any of the 0.19 Applications the WU's either error out or they don't validate ... Both Host's can be seen here too ... Host 43379 & Host 43429

I did just notice something else on them though, neither 1 of them has Net.Framework 3.5 installed, just 2.0. My other Box's I installed 3.5 & they work okay with the v0.19 Applications. I'll try 3.5 in those 2 Box's later & see what happens with the when I try to use the 0.19 Applications.

Eschew on this!

No, sorry, I don't have this in any of my existing PCs;

Requirements
Minimum of a 550 Watt power supply.
(Minimum recommended power supply with +12 Volt current rating of 40 Amps.)

My HD4870 is running with only a 330 Watt PSU, but I have my fingers crossed it won't drain my electricity budget. 550 might just break the bank, let alone my PCs trying to squeeze that PSU in.

Right, break the bank. That and a cruise.

This is what I'll be cruising on around the Caribbean next week click the pic for a larger version
I doubt if I'll be able to afford another ATI card when I get back, or even an nVidia, not after the Somali pirates have been and gone.

---

The only way it seems for these 2 Box's to receive Credit is to run the 0.17 SSE3 Application in them. If I use any of the 0.19 Applications the WU's either error out or they don't validate ... Both Host's can be seen here too ... Host 43379 & Host 43429

I did just notice something else on them though, neither 1 of them has Net.Framework 3.5 installed, just 2.0. My other Box's I installed 3.5 & they work okay with the v0.19 Applications. I'll try 3.5 in those 2 Box's later & see what happens with the when I try to use the 0.19 Applications.

The .NET frame work isn't the problem (the app would crash right away if something is missing). So don't mess around with that.
I've looked through some of your unvalidated results and I found the problem. The 0.19 apps were working flawlessly on your systems. You will slap yourself in the face ;)

Check your PMs.

The only way it seems for these 2 Box's to receive Credit is to run the 0.17 SSE3 Application in them. If I use any of the 0.19 Applications the WU's either error out or they don't validate ... Both Host's can be seen here too ... Host 43379 & Host 43429

I did just notice something else on them though, neither 1 of them has Net.Framework 3.5 installed, just 2.0. My other Box's I installed 3.5 & they work okay with the v0.19 Applications. I'll try 3.5 in those 2 Box's later & see what happens with the when I try to use the 0.19 Applications.

The .NET frame work isn't the problem (the app would crash right away if something is missing). So don't mess around with that.
I've looked through some of your unvalidated results and I found the problem. The 0.19 apps were working flawlessly on your systems. You will slap yourself in the face ;)

Check your PMs.

Okay CP, I'm going to check that out now & will let you know if that was the problem or not ... Thanks

CP, I checked what you said was wrong but couldn't find anything you were talking about. So I downloaded a fresh copy of 0.19d & put it in the Milkyway Directory, downloaded 20 or so WU's but every one of them erred out.

So I installed Net.Framework 3.5 & tried it again, the WU's ran & received Credit with the 0.19d Application so for whatever reason my Box's need Net.Framework 3.5 to run the 0.19 Series of Applications properly ...

CP, I checked what you said was wrong but couldn't find anything you were talking about. So I downloaded a fresh copy of 0.19d

But on both systems 0.19b was already running and definitely also completing WUs. Only that slight misconfiguration in the app_info.xml prevented the validator from granting credits (looked up both systems, was the same problem).
As you changed back to 0.17 the problem disappeared as you most probably exchanged the faulty app_info.xml, too.

But I'm glad it works for you now.

Btw., if you want to do something else than running BOINC on the boxes you may think about using 0.19e. The system behaviour will be much smoother.

CP, I tried the 0.19e on this host & it does run a lot smoother, still had to install Net.Framework 3.5 on that Box too though in order to get it to run the Application ... Thanks

Anyone has tried the catalyst 9.3 ?

9.3 works for me with 0.19e - i had to copy/rename the 3 dlls mentioned in the readme again.

Semi-OT. I subscribed to this thread ~24hrs ago. There have been 2 posts since then, by Dudu and Holger, but I have received no notification, by PM or email, of their posts. Or does subscribing on this board work differently to every other board I've ever seen?

---

Cheers,

PeterV

.

Even though the amount of CPU used is really low. BOINC still doesn't use the avg_ncpus properly, so changing it to a very reasonable number like 0.02 means that BOINC goes a little SNAFU. I changed mine to the following:
<avg_ncpus>0.9</avg_ncpus>
<max_ncpus>1</max_ncpus>
<cmdline>n1 f10</cmdline>

Bugger me if I didn't try f60 and the wu came to an almost crawl...comparatively speaking. LOL

I've been trying your settings for the last day or so & variations of it, but in the end it always ends up that I have only 2 Regular WU's running along with 2 Waiting Milkyway WU's & 1 Running Milkyway WU. So from what I can see it takes 2 complete Cores to run 1 Milkyway WU on the ATI Card.

Its messed up really, I have 6 box's running the ATI Cards & can give them all the same settings in the app file but after awhile all 6 box's might be running different from the rest. 1 box might be not even be running any Milkyway WU's, their just sitting there Waiting.

Also yesterday I had 1 Box that refused to ask for or call for more WU's, if I manually Updated the Project it just said 0 work asked for. I tried everything to get it to call for work & finally after about 12 hours it did call for some more ... Goofy at best is Ali I can say ... :)

9.3 works for me with 0.19e - i had to copy/rename the 3 dlls mentioned in the readme again.

But you run Vista AFAIK. I'm a little worried about this part of the cat 9.3 release notes:

Known Issues Under the Windows XP Operating System
* In this Catalyst 9.3 release, the Compute Abstraction Layer (CAL) driver will not function properly under Windows XP

---

But you run Vista AFAIK. I'm a little worried about this part of the cat 9.3

Yes, Vista 64Bit

and with BOINC 6.6.17 my problem with "million" active tasks seems to be healed a little - actually i have only 8 tasks active while 3 were really crunched, none in high priority mode. seems it now depends on the number of cpus set in cc_config - still strange

Does anybody know of settings I can put in the App File that will keep the ATI Card from taking over the whole CPU to where no Regular WU's are running but just 1 Milkyway WU running. The problem from what I can see is all the Waiting To Run WU's that seem to build from 0 up to 5 or 6 or even more, the more Waiting WU's the more they take over the CPU to where no Regular WU's are running.

Does anybody know of settings I can put in the App File that will keep the ATI Card from taking over the whole CPU to where no Regular WU's are running but just 1 Milkyway WU running. The problem from what I can see is all the Waiting To Run WU's that seem to build from 0 up to 5 or 6 or even more, the more Waiting WU's the more they take over the CPU to where no Regular WU's are running.

Reducing the MW resource share should do it. 25% MW on a Quad should be enough. And resetting the debts of the BOINC client doesn't hurt either (put the line "<zero_debts>1</zero_debts>" to the options in the cc_config.xml).

Does anybody know of settings I can put in the App File that will keep the ATI Card from taking over the whole CPU to where no Regular WU's are running but just 1 Milkyway WU running. The problem from what I can see is all the Waiting To Run WU's that seem to build from 0 up to 5 or 6 or even more, the more Waiting WU's the more they take over the CPU to where no Regular WU's are running.

Reducing the MW resource share should do it. 25% MW on a Quad should be enough. And resetting the debts of the BOINC client doesn't hurt either (put the line "<zero_debts>1</zero_debts>" to the options in the cc_config.xml).

Thanks, I put the "<zero_debts>1</zero_debts>" in the cc_config.xml file but it just said it wasn't recognized when I started BOINC up again and the Debts wasn't zeroed either according to BoincDV, I lowered the resource share too & will see if the ATI Card behaves better now.

Any news on a ATI GPU app for Linux? I have spare cards, but only my linux comp left to put them in...

Any news on a ATI GPU app for Linux? I have spare cards, but only my linux comp left to put them in...

Unfortunately not. Don't have time at the moment. And as long there is no support of ATI cards from the BOINC client one would have to put quite some OS dependent stuff into the app. Could last some weeks.
Let's see what comes faster, a Linux version from me or ATI support of the client ;)

What's the anonymous platform mechanism? I thought I followed the instructions correctly but I wasn't getting any GPU activity so then i read the readme file again and it said install using the anonymous platform mechanism but idk what that is. I extracted the files then stopped BOINC and the processes then copied the extracted files into the milkyway@home project, but it isn't using the GPU. Am i supposed to delete the old app, how does BOINC know to switch? I have a 3870. Sorry if I'm just being stupid. Help?

Hi,

the optimized app doesent work.

My System:

Intel Core quad q6600 / windows vista SP1 / ATI Radeon HD 3870

Tried sse2, sse4.1 and win32_sse2

stopped boinc
deleted milkyway_0.19_windows_intelx86
copied astronomy_0.19_ATI_SSE2e, app_info and brook.dll
started boinc

system downloaded milkyway_0.19_windows_intelx86 and works with this old app

What is my mistake?

---