Thanks Crunch3r.

Any 'chance' it could be boinc, I'm running 6.10.60 and when I went backwards to install it from whatever the boinc current version is I had to install it a second time so it could fix itself, or something like that.

I also can't get boinc to report tasks, I have to do them manually.

G'Day Philadelphia,

I was having the same problem as you with all work being processed before it would ask for work again.

To get your jobs to report straight away you need to create a "cc_config" file.

Open notepad and type this in

<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
</options>
</cc_config>

Save as cc_config.xml
Place the file in the Application/BOINC folder

Stop and restart BOINC client and it should report results within seconds of them finishing.

I may of gotten information about your computer incorrect before but I was only taking it off what BOINC said so you can blame BOINC.

Conan

Thanks Conan for the information, it did as you said :)

As an aside, it goes in the program data/boinc directory. Tried the Program Files/Boinc path and it didn't work.

Thanks Conan and everyone else for suggestion & thoughts, great bunch of folks.

Dan/Philly

PS - Know how you can tell I'm an old fart? I still call them directories instead of folders :)

Since you already have a cc_config.xml file just add it in to the existing one...remember we made one for your dual gpu's to work. Just add another line to the existing file. You have to put it in BEFORE the /options line, just before would be fine.

PS - Know how you can tell I'm an old fart? I still call them directories instead of folders :)

[old fart mode on]
It was Microsoft that insisted upon calling the sub-divisions folders when Windows got introduced. Us MSDOS based guys continue to call them directories regardless, just to spite Bill Gates :-)

Get a dos prompt window in Win 7 (type CMD) and you will find that DIR & VER & CD.. still work as do other commands ....

Ah the good old days. EMS386 anyone ?
[old fart mode off].

---

I iz also got icons!

PS - Know how you can tell I'm an old fart? I still call them directories instead of folders :)

[old fart mode on]
It was Microsoft that insisted upon calling the sub-divisions folders when Windows got introduced. Us MSDOS based guys continue to call them directories regardless, just to spite Bill Gates :-)

Get a dos prompt window in Win 7 (type CMD) and you will find that DIR & VER & CD.. still work as do other commands ....

Ah the good old days. EMS386 anyone ?
[old fart mode off].

It's my thread so I guess I can get off topic for just a tiny bit, plus I'm an 'old fart'.

What was the o/s before dos, and nooooooooo looking on the internet. I'm talking about pc's, not fortran or cobol, etc.

One will earn an 'old fart badge' for that one, or, if you're a youngster you're well informed.

It was from Digital Research .... CP-M/80, however it was not a "Universal" OpSys, other contenders were out there allbeit CP-M/80 was the most widespread.

That changed in 1981 when MS-DOS (or PC-DOS if an IBM machine) came out as a result of the worst Vendor Sales deal in History when Bill Gates got IBM to give him royalties for each DOS copy sold as part of a contract let by IBM for a Home PC Operating system - in perpetuity. The IBM exec running the deal thought he was on a winner, as IBM did not think DOS sales would exceed 100,000 units ... and therefore Gates was "dumb" to take royalties and not a one off copywrite fee (!).

Gates has laughed all the way to the Bank ever since .... IBM still to this day smarts over this (I worked for IBM up to 2005 in Professional Services working alongside Global Sales).

Regards
Zy
[confirmed old fart long ago :) ]

Going to clear out my Moo's cashe and move on, sucks, I was expecting about 700k a day :(

Dan it was only 7 hours between your first post and your last post, give us a chance to take some naps and analyze the data guy.

Now you know that Moo is a project that uses BOTH of your gpu's on ONE workunit, right?! This could be what you are seeing the 'stream'ing of the data between the cards so ALL of BOTH cards resources are being used on ONE workunit. When you only have one card no 'stream'ing is needed, so the numbers are zero. Remember too your two cards are NOT identical, one has 1gig of memory while the other card has 2gig of memory, this could be why the workunits are taking so long. You MIGHT be able to limit the resources thru config settings but don't quote me on that.

That is true, they are not identical

I was not aware that Woo used both cards to crunch 1 WU since two of them are running at the same time, or at least in BOINC they show two running at the same time.

Dan I am now back to dual AMD 5770's in one machine and have TWO units running at the same time!!! I have no idea why but that is what it is doing, the cards are IDENTICAL and I have rebooted several times! Each unit says it will take about 60 minutes, which is normal for a 5770. We will see!!

It was from Digital Research .... CP-M/80, however it was not a "Universal" OpSys, other contenders were out there allbeit CP-M/80 was the most widespread.

That changed in 1981 when MS-DOS (or PC-DOS if an IBM machine) came out as a result of the worst Vendor Sales deal in History when Bill Gates got IBM to give him royalties for each DOS copy sold as part of a contract let by IBM for a Home PC Operating system - in perpetuity. The IBM exec running the deal thought he was on a winner, as IBM did not think DOS sales would exceed 100,000 units ... and therefore Gates was "dumb" to take royalties and not a one off copywrite fee (!).

Gates has laughed all the way to the Bank ever since .... IBM still to this day smarts over this (I worked for IBM up to 2005 in Professional Services working alongside Global Sales).

Regards
Zy
[confirmed old fart long ago :) ]

One of the areas that CP-M/80 lived on was under the Atari ST 16 bit computer. The Atari OS was known as TOS (The Operating System) and used P-M/80 with a GUI stuck on to make it run smoother.

That OS lived in the Atari until it's demise during the 1990, and meant I had little in the way of a learning curve when I bought in to Win98 SE.

Never played with DOS, and really do not like it. Also don't like the Win Registry. When the Atari had several hard drives and a new application was put on a drive. The application stayed within it's own folder on that hard drive, whatever it's number/letter designation. No shared .DLLs and no writing to the boot drive on a registry.

[Another old fart confirmed]

In spite of my better judgement, I decided to 'allow new tasks', received 1 download, suddenly, instead of running two tasks it was running one task (running 0.05 cpu's + 2.00 ATI GPU's (device 0)) Before it was running 2 tasks with +1.00 gpu (device 0) and another (device 1)
...
My question (not to anyone in particular) is why did 'allowing new tasks' suddenly tell the computer to run one work unit instead of two and use both gpu's to do it, when stopping/starting BOINC didn't, even when it involved setting changes????

Simply put, the "x ATI GPU" resource requirement comes from our scheduler and it's based on the number of cards BOINC Client reports in that scheduler request. So if you have one card and get some work, they will be set to require "1 ATI GPU". If you now happen to add a second one, any new tasks retrieved will get "2 ATI GPU" requirement as soon as you fetch more work. However, BOINC Client will not change the existing tasks so they will retain the, now incorrect, "1 ATI GPU" requirement.

Running two Moo tasks at the same time is not a good idea since they both will use both of your cards and that'll certainly affects performance, if they don't fail in funny ways. I believe it's best to reset project to fetch new tasks anytime one adds or removes cards. (Actually, since we have resending enabled, you will get sent the same tasks you had but now with correct card # requirement.)

This is because D.net Client that we use always detects and uses all cards it can find (regardless of what BOINC Client thinks) and that's why it's important that we correctly tell BOINC Client how many cards we use. Otherwise it might overcommit your resources and cause performance problems.

-w

I have been watching boinc and it hit me that boinc was finishing a wu in ~15 minutes but not being reported that way at Moo,

What's the rush? :) Completed workunits will get reported back during next fetch and in larger batches. Okay, having no-new-tasks enabled will affect this but it's still probably better to manually report completed tasks once all of the are done.

Using option is not recommended because that increases load on our servers. Better let BOINC Client report back on it's own time. At least during normal times.

Look at the difference between WU's, between the actual UTC times, they agree with the times boinc was showing when I watched them crunching and the wall clock, but the run/cpu times don't.
Could it be a Moo problem? Can I detach from the project and download the Moo program again without screwing things up, or is it even necessary?

Yeah, there's probably something wrong with the values and I'd need to debug that sometime in the future. There's no need to detach since that won't help the situation. We'd need to fix any errors in our wrapper and deploy a new version before that's any use. :) But I don't think this misreporting is that big a problem to worry about.

-w

Going to clear out my Moo's cashe and move on, sucks, I was expecting about 700k a day :(

Dan it was only 7 hours between your first post and your last post, give us a chance to take some naps and analyze the data guy.

Now you know that Moo is a project that uses BOTH of your gpu's on ONE workunit, right?! This could be what you are seeing the 'stream'ing of the data between the cards so ALL of BOTH cards resources are being used on ONE workunit. When you only have one card no 'stream'ing is needed, so the numbers are zero. Remember too your two cards are NOT identical, one has 1gig of memory while the other card has 2gig of memory, this could be why the workunits are taking so long. You MIGHT be able to limit the resources thru config settings but don't quote me on that.

That is true, they are not identical

I was not aware that Woo used both cards to crunch 1 WU since two of them are running at the same time, or at least in BOINC they show two running at the same time.

Dan I am now back to dual AMD 5770's in one machine and have TWO units running at the same time!!! I have no idea why but that is what it is doing, the cards are IDENTICAL and I have rebooted several times! Each unit says it will take about 60 minutes, which is normal for a 5770. We will see!!

That's how mine started, crunching 2 wu's, it wasn't until I changed from no new tasks to allow it to download again, that it went from crunching 2 wu's to 1 wu.

If you look at the top of this thread you'll see a picture of the two wu's crunching.

Strange for sure.

Going to clear out my Moo's cashe and move on, sucks, I was expecting about 700k a day :(

Dan it was only 7 hours between your first post and your last post, give us a chance to take some naps and analyze the data guy.

Now you know that Moo is a project that uses BOTH of your gpu's on ONE workunit, right?! This could be what you are seeing the 'stream'ing of the data between the cards so ALL of BOTH cards resources are being used on ONE workunit. When you only have one card no 'stream'ing is needed, so the numbers are zero. Remember too your two cards are NOT identical, one has 1gig of memory while the other card has 2gig of memory, this could be why the workunits are taking so long. You MIGHT be able to limit the resources thru config settings but don't quote me on that.

That is true, they are not identical

I was not aware that Woo used both cards to crunch 1 WU since two of them are running at the same time, or at least in BOINC they show two running at the same time.

Dan I am now back to dual AMD 5770's in one machine and have TWO units running at the same time!!! I have no idea why but that is what it is doing, the cards are IDENTICAL and I have rebooted several times! Each unit says it will take about 60 minutes, which is normal for a 5770. We will see!!

That's how mine started, crunching 2 wu's, it wasn't until I changed from no new tasks to allow it to download again, that it went from crunching 2 wu's to 1 wu.

If you look at the top of this thread you'll see a picture of the two wu's crunching.

Strange for sure.

Teemu gave the answer and I did notice the units were running FOREVER so I aborted the only two left and got a new one. I had switched to Collatz until Teemu fixed things, it is test time at all the Colleges and he is REALLY busy, but he seems to have fixed things already so I will be switching back today.

Fixed what? I just to run Moo on my PC with 2 5870's...no go. Same driver version as my PC with a 5850 what is running Moo fine.

Fixed what? I just to run Moo on my PC with 2 5870's...no go. Same driver version as my PC with a 5850 what is running Moo fine.

He fixed all the bad workunits.

Did you remember to load the AMD software TWICE? You have TWO gpu's, sometimes I have found it works with only one load but it usually takes twice for me. I put in one gpu, let the system find it and then reboot and load the AMD software, then I reboot again and make sure Boinc sees the card, then I shutdown and repeat the process for the 2nd gpu.

One other thing to try is to 'reset' Moo on the Projects Tab of the Boinc Manager. This forces your pc to get the newest stuff from the project but can trash some workunits in the process, that doesn't seem to be a problem with you right now as you don't have very many on that machine that are doing well anyway. I would install BOTH gpu's THEN reset and see if it works for you.

I did all that except rebooting a second time...trying that now.