Have you checked file properties including that the user running BOINC has at least Read/Execute permmissions set for this file.

Yes. I'm admin for this system, and run all seti as admin with all permissions

Have you tried running the exe from the command line. If all is OK you should get "In ap_gfx_main.cpp: in ap_graphics_init(): Starting client." returned just to show it is working.

Just did this, and got exactly what you have above.

Have you tried recopying the file in case it is corrupt?

Tried this too. Of course, it's all sort of problematic since I haven't received any more AP's since those first two.

I also, just to cover all bases, downloaded the most recent version of 7zip, and then extracted the file to a temp directory before copying it to the setiathome folder.

I guess all I can do at this point is wait to see what happens when (and if) I get another AP WU. I just really am puzzled mightily why this has happened after never having a problem with all the other opti apps and app_info mods I've made over the years.

{EDIT} the bit about file blocking I had mentioned earlier in this thread. Both r103 and r112 have that message in the properties tab. Curiously r168 does not. But then, both 103 and 112 ran fine from the get go.

Have you checked file properties including that the user running BOINC has at least Read/Execute permmissions set for this file.

Yes. I'm admin for this system, and run all seti as admin with all permissions.

And what about the users and groups named boinc_master and boinc_project? (See the BOINC wiki)

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Yes. I'm admin for this system, and run all seti as admin with all permissions.

Please be aware that BOINC runs in a sandboxed environment and does not use the permissions of the running user to determine its own privileges. Even if you are running as Admin, the permissions on the BOINC data directory does not use Admin privs, and if the file isn't copied properly, it may not receive the proper permissions to run.

---

As an experiment today I tried extracting the file from the archive directly into the project directory and it had no permissions set. I extracted it to another folder and copied it in and it was fine - the file inherits the folder permissions, so if folder permissions have been changed and reason, copying the file into the folder may still not apply the necessary permissions.

On my EXEs I have :-

BOINC_admins all permissions set
BOINC_projects app permissions set
BOINC_users read, read&execute permissions set

You need to set these permissions on the indivual files - right click on file and select the security tab and has nothing to do with your permissions as a user.

---

GPU Users Group

The "No main program specified" error can only happen when the BOINC core client tries to start a task, and the client_state information for the linked app_version does not have the needed main_program entry. I suggest looking in client_state.xml, check whether the <app_version> section for ap_5.05r168_SSE3.exe is missing or damaged.

                                                                  Joe

One other thing I noticed.

You haven't mentioned anywhere that you restarted boinc after modifying your app_info.xml

(Just covering all possibilities) :)

---

Flying high with Team Sicituradastra.

The "No main program specified" error can only happen when the BOINC core client tries to start a task, and the client_state information for the linked app_version does not have the needed main_program entry. I suggest looking in client_state.xml, check whether the <app_version> section for ap_5.05r168_SSE3.exe is missing or damaged.

                                                                  Joe

here's the relevant section of client_state.xml:

- <app>
<name>astropulse</name>
<user_friendly_name>astropulse</user_friendly_name>
</app>
- <app>
<name>astropulse_v5</name>
<user_friendly_name>astropulse_v5</user_friendly_name>
</app>
- <app>
<name>astropulse_v505</name>
<user_friendly_name>astropulse_v505</user_friendly_name>
</app>
- <app>
<name>setiathome_enhanced</name>
<user_friendly_name>setiathome_enhanced</user_friendly_name>
</app>
- <file_info>
<name>ap_5.00r103_SSE3.exe</name>
<nbytes>0.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable />
<signature_required />
</file_info>
- <file_info>
<name>ap_5.03r112_SSE3.exe</name>
<nbytes>0.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable />
<signature_required />
</file_info>
- <file_info>
<name>ap_5.05r168_SSE3.exe</name>
<nbytes>0.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable />
<signature_required />
</file_info>

Or, is there another section I need to look at?

As an experiment today I tried extracting the file from the archive directly into the project directory and it had no permissions set. I extracted it to another folder and copied it in and it was fine - the file inherits the folder permissions, so if folder permissions have been changed and reason, copying the file into the folder may still not apply the necessary permissions.

On my EXEs I have :-

BOINC_admins all permissions set
BOINC_projects app permissions set
BOINC_users read, read&execute permissions set

You need to set these permissions on the indivual files - right click on file and select the security tab and has nothing to do with your permissions as a user.

I compared the permissions on r112 and r168 and they are identical; same as yours for both apps.

I'm wondering now if the re-copies I've done in the last day or so have "fixed" the problem I originally posted about. Of course, until I get lucky enough to score another AP WU, I won't know.

This particular snippet has been posted from Internet Explorer. It has those telltale dashes at the start of some sections......

......and it also has the extraneous space before the slash in <executable />. That same space, if present in <main_program/>, gives the error message you're reporting.

Your original posting of app_info.xml didn't have spaces, but do go back and check (open with notepad, and search for space slash. There shouldn't be any).

BOINC doesn't use true XML, just something that looks a bit like it. It's much more fussy about layout.

The "No main program specified" error can only happen when the BOINC core client tries to start a task, and the client_state information for the linked app_version does not have the needed main_program entry. I suggest looking in client_state.xml, check whether the <app_version> section for ap_5.05r168_SSE3.exe is missing or damaged.

                                                                  Joe

here's the relevant section of client_state.xml:

- <app>
<name>astropulse</name>
<user_friendly_name>astropulse</user_friendly_name>
</app>
- <app>
<name>astropulse_v5</name>
<user_friendly_name>astropulse_v5</user_friendly_name>
</app>
- <app>
<name>astropulse_v505</name>
<user_friendly_name>astropulse_v505</user_friendly_name>
</app>
- <app>
<name>setiathome_enhanced</name>
<user_friendly_name>setiathome_enhanced</user_friendly_name>
</app>
- <file_info>
<name>ap_5.00r103_SSE3.exe</name>
<nbytes>0.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable />
<signature_required />
</file_info>
- <file_info>
<name>ap_5.03r112_SSE3.exe</name>
<nbytes>0.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable />
<signature_required />
</file_info>
- <file_info>
<name>ap_5.05r168_SSE3.exe</name>
<nbytes>0.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable />
<signature_required />
</file_info>

Or, is there another section I need to look at?

This particular snippet has been posted from Internet Explorer. It has those telltale dashes at the start of some sections......

......and it also has the extraneous space before the slash in <executable />. That same space, if present in <main_program/>, gives the error message you're reporting.

Your original posting of app_info.xml didn't have spaces, but do go back and check (open with notepad, and search for space slash. There shouldn't be any).

BOINC doesn't use true XML, just something that looks a bit like it. It's much more fussy about layout.

Richard,

True enough, the client_state snippet was copied from my XML editor. I opened it in notepad, searched for (space)/ and found none in the AP files section. Also checked app_info for (space)/ and found none.

I really appreciate all the input I've received so far, and will dutifully check out any other ideas you all might have. The good news is, I don't feel nearly as dumb as when I first posted; I fully expected this to be something obvious I was overlooking.

The "No main program specified" error can only happen when the BOINC core client tries to start a task, and the client_state information for the linked app_version does not have the needed main_program entry. I suggest looking in client_state.xml, check whether the <app_version> section for ap_5.05r168_SSE3.exe is missing or damaged.

                                                                  Joe

here's the relevant section of client_state.xml:
...
<app>
<name>astropulse_v505</name>
<user_friendly_name>astropulse_v505</user_friendly_name>
</app>
...
<file_info>
<name>ap_5.05r168_SSE3.exe</name>
<nbytes>0.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable/>
<signature_required/>
</file_info>

Or, is there another section I need to look at?

The section most directly concerned with the error you saw should be like this:

<app_version>
    <app_name>astropulse_v505</app_name>
    <version_num>505</version_num>
    <file_ref>
        <file_name>ap_5.05r168_SSE3.exe</file_name>
        <main_program/>
    </file_ref>
</app_version>

The <main_program/> is the specific line which was missing when you saw the error, if it's there now you're probably right that when next you get an AP_v505 it will work.

                                                                 Joe

@ Richard

Do you have a flops estimate by any chance? For the other AP's we used:

Astropulse 500 flops = p_fpops x 2.25
Astropulse 503 flops = p_fpops x 2.6

---

BOINC blog

@ Richard

Do you have a flops estimate by any chance? For the other AP's we used:

Astropulse 500 flops = p_fpops x 2.25
Astropulse 503 flops = p_fpops x 2.6

Already answered: message 912609.

Basically, the project hasn't adjusted the estimates for the new stock app (big mistake, IMO), and the 505 opti is very similar performance-wise to opti 503.

So, use the same value as the one which worked best for you for 503. That original 2.6 was derived from work at Beta with my Q6600 / 9800GT combo (review beta message 36887 - but the Beta estimates, and hence multipliers, were different back then). Optimal multipliers for other processors - particularly AMDs - will likely be different, but I don't have any for testing.

Could someone please supply me with the appropriate AP505 SSE (NOT SSE3) app_info example? I am a novice app_info user and used Lunatics' unified installer originally, and have downloaded the new AP optimized app (I do not have access to their updated unified installer). I desire to get AP work units again.

---

Could someone please supply me with the appropriate AP505 SSE (NOT SSE3) app_info example? I am a novice app_info user and used Lunatics' unified installer originally, and have downloaded the new AP optimized app (I do not have access to their updated unified installer). I desire to get AP work units again.

If you download the SSE application from Lunatics, you'll find an app-info file in the package. It should be identical to the SSE3 app_info with SSE replacing SSE3 throughout, but check to be sure.

Append that app_info.xml to your existing one (using only a plain-text editor throughout), and remove the </app_info><app_info> line pair from the middle where they join. That's all.

Your instructions were spot on:-) I am now a first time app_info modifier. Thanks for your help. Rick

---