I've found that while Speedfan works in many instances, there are times where is doesn't. For example, it works great on my Intel DG33FB motherboards, but not on the very similar DG35EC boards. It also doesn't work on my Dell laptops, or on my Supermicro motherboard based system. So, for whatever reason it seems somewhat hit or miss. By work, I mean the ability to control anything. It seemed to install properly on all the systems, but when it is executed, it just shows temps and such, but no ability to control anything. Not knocking it, at all, and when it works I love it, because it is a better option than the limited or worse options that come with most system boards.

That just about reflects my experience with Speedfan. Much rather rely on something that has a physical electrical connection, even if it is a fan speed controller with thermistors stuck with thermal adhesive to things like the heatsinks.

I've found that while Speedfan works in many instances, there are times where is doesn't. For example, it works great on my Intel DG33FB motherboards, but not on the very similar DG35EC boards. It also doesn't work on my Dell laptops, or on my Supermicro motherboard based system. So, for whatever reason it seems somewhat hit or miss. By work, I mean the ability to control anything. It seemed to install properly on all the systems, but when it is executed, it just shows temps and such, but no ability to control anything. Not knocking it, at all, and when it works I love it, because it is a better option than the limited or worse options that come with most system boards.

The directory with all the AP 5.03 files is:

Index of /sah/download_fanout

and the direct links are:

astropulse_5.03_windows_intelx86.exe

ap_graphics_5.03_windows_intelx86.exe

libfftw3f-3-1-1a_upx.dll

The bit of the app_info for v5 AP is:

<app>
<name>astropulse_v5</name>
</app>
<file_info>
<name>astropulse_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>ap_graphics_5.03_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
<file_ref>
<file_name>astropulse_5.03_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_graphics_5.03_windows_intelx86.exe</file_name>
<open_name>graphics_app</open_name>
</file_ref>
</app_version>

You'll need to overwrite your section for astropulse, or add it as an addition,
I'm got entries for v5 AP as well as the last version, so i still get resends.

Claggy

Compliments to Richard for correcting my mistakes in the app_info earlier

Edit: changed the link to AP Graphics

this brings up an interesting question...

simply put, why can't someone take work unit "a" from machine "a" and put into into machine "b" and have machine "b" crunch that work unit and report it....