Welcome to MilkyWay@home

Posts by Temujin

1) Message boards : News : Old ATI applications deprecated (Message 47236)
Posted 9 Apr 2011 by Temujin
Post:
......there are other ATI enabled projects as well and boinc tends to switch between them in a complete irational/retareded way, sometimes suspending a WU that's ~98% done... so there you go, we need checkpoints. :)

This also happens when you set 'Use GPU while computer is in use' set to no.
Another reason for checkpoints
2) Message boards : Number crunching : Computation error on all tasks, help please (Message 36864)
Posted 1 Mar 2010 by Temujin
Post:
wild guess but have you copied the 3 /windows/system32/atical*.dll files to amdcal*.dll ?
3) Message boards : Number crunching : iPhone (Message 36168)
Posted 31 Jan 2010 by Temujin
Post:
>BoincPHP5-GUI

I've used that for a number of years. It's how I monitor my home machines when I'm at work (and vice versa)
It's a pity it hasn't been developed recently
4) Message boards : Number crunching : Problem with tiny cache in MW (Message 34023)
Posted 30 Nov 2009 by Temujin
Post:
I am happy here if work units going to be 4 times bigger, as told on the front page.

Working well here, thanks Travis
5) Message boards : Number crunching : New Dr in the House (Message 33400)
Posted 20 Nov 2009 by Temujin
Post:
Congratulations Travis
6) Message boards : Number crunching : v0.20 issues win32 (Message 32291)
Posted 11 Oct 2009 by Temujin
Post:
i tried to reinstall 0.20b The result can be seen here: http://festplatte.aon.at/a/filemanager.get/11746831/0.20b.JPG
I switched back to 0.20, that works. But if anyone has an idea how to fix it, i would prefer to use the newer app.

you've installed the 0.20b_ATI version of the app, do you have the ati version of the dlls??


Hmm, i'm running astronomy_0.20_ATI_SSE2, it works fine. Do i need different dll's?
Actual settings can be seen her: http://festplatte.aon.at/a/filemanager.get/11784532/0.20.JPG
Did i miss something?

You haven't missed anything for how you're running now with v0.20, all looks to be working fine :)

But before, when you tried version 0.20b, you installed the ati version of the app. In this case ati means you have 3 ati*.dll in the system32 directory and i think that's where you went wrong.
I suspect you have 3 amd*.dll files instead, which would mean you should install the amd version of the app
7) Message boards : Number crunching : v0.20 issues win32 (Message 32283)
Posted 11 Oct 2009 by Temujin
Post:
"Cluster Physik" wrote:
You are running WindowsXP, therefore Catalyst 8.12 is recommended. That also means you have to use the Win32_amd or Win32_SSE2_amd version (not the ones with "_ati" at the end). That is all said in the readme by the way.


I suspect some of the people having trouble with v0.20b may be running the wrong app for their catalyst version, so I thought this could do with highlighting :)
8) Message boards : Number crunching : v0.20 issues win32 (Message 32282)
Posted 11 Oct 2009 by Temujin
Post:
i tried to reinstall 0.20b The result can be seen here: http://festplatte.aon.at/a/filemanager.get/11746831/0.20b.JPG
I switched back to 0.20, that works. But if anyone has an idea how to fix it, i would prefer to use the newer app.


you've installed the 0.20b_ATI version of the app, do you have the ati version of the dlls??
9) Message boards : Number crunching : Crunching CPU/GPU 0.20 together?? (Message 31494)
Posted 25 Sep 2009 by Temujin
Post:
....but I ask this because in SETI you can do it and with anonimous platforms, e.g.:
- Astropulse 5.05 (CPU)
- Seti 6.03 (CPU)
- Seti 6.08 (CUDA/GPU)

Seti can do it because they have different application versions that can be specified together in the one app_info.xml file.

Currently the MW opti apps for CPU and GPU are the same version (v0.20) so only 1 can be specified in app_info.xml.

A workaround could be to locally rename one of the apps as v0.19 (lets say rename the CPU opti app), that would allow both to be specified in app_info.xml (GPU as v0.20 and CPU as v0.19)

I've not tried the above and have no idea if it would work but it sounds plausible to me

try at your own risk
10) Message boards : Number crunching : Using the MW ATi application, Q & A (Message 28716)
Posted 1 Aug 2009 by Temujin
Post:
Also, if I try to install the 8.12 version (or any of the 9.x versions at guru3d), the install stops mid-stream and I get a message saying that it's unable to find a driver compatible with my software. The only option is to ack the message and exit the install.
Hi Mark

I had this problem with my AGP 3850
The workaround is to let it fail (as it has) then manually add new hardware/Display Adaptor, select Have Disk and point it to the .inf file in the newly created ATI/SUPPORT/driver_version/XP_INF directory.
I selected the first 3850 driver and its worked fine

Its a while ago that I got mine running and the above is from memory, so it may be wrong in places but in general it should work
11) Message boards : Cafe MilkyWay : Poms Win 2nd Test (Message 28066)
Posted 20 Jul 2009 by Temujin
Post:
I don't understand why we didn't make Australia follow on :?
There's no doubt 500+ was a tall order but if anyone could reach it, its Australia, so why not enforce the follow on and then you know exactly how much you've got to get in how many sessions.
12) Message boards : Number crunching : Work Availability v2 (June 9) (Message 24742)
Posted 9 Jun 2009 by Temujin
Post:
all looking good here :)

Thanks Travis
13) Message boards : Number crunching : Compute Errors (Message 24258)
Posted 5 Jun 2009 by Temujin
Post:
The current workaround is to abort all the _3s_ WUs, close and restart boinc, and hope you get some _1s_ or _2s_ WUs next time. Its horribly manual and requires keeping an eye on boinc, which explains all the requests/demands in this thread for Travis to fix it.

Come on guys, deep breaths :)
The problem isn't with the workunits, they're fine, so Travis can't fix it.
It's a bug in Cluster Physiks GPU application as he has already pointed out.
Give him a chance and he'll sort it
14) Message boards : Number crunching : CPU Work Units Did Not Validate (Message 22055)
Posted 12 May 2009 by Temujin
Post:
open a root treminal, type
cat /proc/cpuinfo
and look if SSE3 will show up for the cpu.

All is not lost if it doesn't show SSE3.
In Linux some CPUs will list SSE3 as pni, so look for that too
15) Message boards : Number crunching : MilkyWay_GPU (Message 20247)
Posted 23 Apr 2009 by Temujin
Post:
Has anyone had any success in getting a Raedeon HD3850 AGP card to successfully crunch MW on the card? I downloaded the 9.4 hotfix for AGP cards,
Yes, I do :)
I have an old P4 running AGP HD3850 with 8.12. I didn't install the hotfix version but rather attempted to install 8.12 (which fails) then manually added new hardware and pointed it to the newly created ATI folder.
It seems the happiest of my ATI cards because it's so slow in comparison to the hd4850s and usually has WUs
16) Message boards : Number crunching : 3rd.in - optimized apps (Message 18407)
Posted 12 Apr 2009 by Temujin
Post:
The originals are still available from the Planet3dNow forum
17) Message boards : Number crunching : 3rd.in - optimized apps (Message 18111)
Posted 10 Apr 2009 by Temujin
Post:
I'd also like to add my thanks to Cluster Physik
an even more impressive achievement if it was written without having a suitable card
18) Message boards : Number crunching : Server Updates and Status (Message 17087)
Posted 28 Mar 2009 by Temujin
Post:
My i7 can crunch more than 500 MW WUs in 24 hours...

Per core?
19) Message boards : Number crunching : Server Updates and Status (Message 17038)
Posted 27 Mar 2009 by Temujin
Post:
That's good question, as BOINC doesn't recognise ATI cards as coprocessors.
For the backend a ATI-gpu-cruched Wu must be looking like a cpu-crunched WU...

That won't matter if they split to 2 different projects.
All they need to do is reduce the daily WU/CPU limit down to 500 at both projects.

For GPU milkyway there'll be 500 WUs that are 1000 times bigger than current that will keep GPUs very happy but will probably make running them on a CPU miss the deadline. Good for GPUs, bad for CPUs

And for CPU milkyway you'll have 500 WUs which will keep CPU machines busy all day but anyone running a GPU will run out PDQ. Good for CPUs, bad for GPUs.

That seems to work both ways.


20) Message boards : Number crunching : How do use the 'Select Computer....' (Message 16574)
Posted 22 Mar 2009 by Temujin
Post:
On the remote machine, do you see "unauthorised access by machine x.x.x.x" type messages?

All that is needed is -
The remote_hosts.cfg file on the remote/viewed machine to contain the IP of the local/viewing machine, stop & start boinc


Next 20

©2020 Astroinformatics Group