Hello,

trying to benefit from the ATI-versions I tried the version 0.19e that is available at zslip. I copied the three files (exe, dll, and app_info.xml) into the project-folder of M@H. Since that time all WUs are crashing immediately as you can see at http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=56103

Something that I can come up with to help finding the reason for this?

Here are the system-specs:

Windows XP 32 Bit on a Dual Core System
ATI Radeon HD 4870 (1GByte)
Catalyst 9.2

The STDOUT of the processes is not very informative (at least for me):

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>



Regards, Lothar

When you added the opti app did you turn boinc off? The ones in your que will error out usually.

Others should come along and give better help.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

When you added the opti app did you turn boinc off? The ones in your que will error out usually.

As you can see in the list of WUs for that system, I downloaded them yesterday. Because I haven't had installed the current version of Catalyse I downloaded 9.2 today and installed it. So I don't know if BOINC was down when I copied the app into the folder, but since then I even rebooted the system, so the crashed ones that you can see in the list right now are not because of BOINC running while copying the app.

Others should come along and give better help.

I hope. Having this mini-supercomputer residing in my box without doing anything than showing the standard-desktop of XP nags me ;-)


Regards, Lothar

Well you have a valid result now.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

As you are running what looks like the same 32 bit XP system I am, perhaps I can add my 2p's worth.

When you shut down BOINC Manager, you then need to start up Task Manager and look at the "Processes" tab. In there you will see that the processes are continuing to use some level of core capacity and WUs being crunched or in memory. These need to be shut down ot the current WU cache will trash.

The next step is to look for boinc.exe at the Task Manager "processes" tab. Shut this down, and, if it is running, boinctray.exe as well.

Now wait until the processes tab reports that all WU you know are running.

When these crunching processes are stopped, then be sure to add the inf_app fie, the client V0.19e and the other file.

Now restart BOINC Manager and wait to download new work, etc

Well you have a valid result now.

I use the SSSE3-optimized app. That only proves that I'm able to install optional applications but still leaves the graphical adapter unused.


Regards, Lothar

trying to benefit from the ATI-versions I tried the version 0.19e that is available at zslip. I copied the three files (exe, dll, and app_info.xml) into the project-folder of M@H. Since that time all WUs are crashing immediately as you can see at http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=56103

Something that I can come up with to help finding the reason for this?

Here are the system-specs:

Windows XP 32 Bit on a Dual Core System
ATI Radeon HD 4870 (1GByte)
Catalyst 9.2

A you don't say anything about it I suppose you did not read the instructions for getting Cat 9.2 (applies to 9.3 too) to work with the MW GPU app. You need to copy and rename some dll files as described in the supplied readme file.

ATI Radeon HD 4870 (1GByte)
Catalyst 9.2

A you don't say anything about it I suppose you did not read the instructions for getting Cat 9.2 (applies to 9.3 too) to work with the MW GPU app.

Oh, there was something after the Change-Log. I stopped reading when reaching there. Maybe the "problems-section" should be placed before the changes-log.

You need to copy and rename some dll files as described in the supplied readme file.

I've done that and after restarting the client, the VPU-recover immediately kicks in. After stopping CCC (including the kill of the process using Sysinternal's ProcessExplorer) I get the same result. I tried killing all processes belonging to ATI but the only effect is that the recover doesn't work and the screen gets dark, forcing a system-restart.


Regards, Lothar

ATI Radeon HD 4870 (1GByte)
Catalyst 9.2

A you don't say anything about it I suppose you did not read the instructions for getting Cat 9.2 (applies to 9.3 too) to work with the MW GPU app.

Oh, there was something after the Change-Log. I stopped reading when reaching there. Maybe the "problems-section" should be placed before the changes-log.

Actually it is said right in the beginning (system requirements).

You need to copy and rename some dll files as described in the supplied readme file.

I've done that and after restarting the client, the VPU-recover immediately kicks in. After stopping CCC (including the kill of the process using Sysinternal's ProcessExplorer) I get the same result. I tried killing all processes belonging to ATI but the only effect is that the recover doesn't work and the screen gets dark, forcing a system-restart.

Have you tried another driver or reinstalling it?
By the way, AMD mentions a problem with Cat 9.3 and WinXP:

NOTE: ATI Catalyst 9.3 does not work properly on Windows XP systems for ATI CAL applications, including Brook+ applications. If you are using a Windows XP system, you will need to use ATI Catalyst 9.2 or wait for a later driver.

ATI Radeon HD 4870 (1GByte)
Catalyst 9.2

NOTE: ATI Catalyst 9.3 does not work properly on Windows XP systems for ATI CAL applications, including Brook+ applications. If you are using a Windows XP system, you will need to use ATI Catalyst 9.2 or wait for a later driver.

So is 9.2 the new 9.3 then? ;-)


Regards, Lothar

Have you tried another driver or reinstalling it?

Before 8.9 was installed, I installed 9.2 just today, about 20 minutes before I posted the first message.


Regards, Lothar

Have you tried another driver or reinstalling it?

Before 8.9 was installed, I installed 9.2 just today, about 20 minutes before I posted the first message.

The versions 8.12 and 9.1 are supposed to work (on some systems WinXP systems only 8.12 appears to work, don't know why) without any modification. That are the versions you may try.

The versions 8.12 and 9.1 are supposed to work (on some systems WinXP systems only 8.12 appears to work, don't know why) without any modification. That are the versions you may try.

8.12 seems to work (9.1 is not available at the sapphiretech-website, so I can't try 9.1) Is there a specific reason why this quite old driver works and newer ones not?


Regards, Lothar

The versions 8.12 and 9.1 are supposed to work (on some systems WinXP systems only 8.12 appears to work, don't know why) without any modification. That are the versions you may try.

8.12 seems to work (9.1 is not available at the sapphiretech-website, so I can't try 9.1) Is there a specific reason why this quite old driver works and newer ones not?


Regards, Lothar

The reason is because with versions 9.2 and up, AMD/ATI renamed some of the .dlls required for the MW app to work. Previous versions have the old filenames, so they will work.

---

8.12 seems to work (9.1 is not available at the sapphiretech-website, so I can't try 9.1) Is there a specific reason why this quite old driver works and newer ones not?

The reason is because with versions 9.2 and up, AMD/ATI renamed some of the .dlls required for the MW app to work. Previous versions have the old filenames, so they will work.

Copying the DLLs with the old name let the computation start, but as I mentioned, the VPU Recover immediately recovers because the driver is regarded as being unresponsive. This stops the calculation and doesn't happen with 8.12.. I just wonder why that is.


Regards, Lothar

I have Win32 on Phenom 9850 (I wish to have 64 bit, but that's the only Win license I have), Radeon 3850 and Catalyst 8.12, 0.19e application - all works well for 3 days now, just MW server sends work very rarely. Uninstall 9.2 and try 8.12 instead.

---