I don't have the manifest and pdb files listed in my app_info, but BOINC doesn't delete them, so I assumed the exe asks for them to remain available, or there are references in the EXE that looks for those two files, so they don't get deleted.

I didn't know they were actually not needed. Good to know.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

app_info looks fine, and carrying on with AP r103 should be no problem,
my P3 800 @896MHz was doing AP in about 200hrs with AP r69, not tried it yet with r103,
yours should be somewhat quicker.

Claggy

1) For my Athlon XP Thoroughbred with SSE-only I chose KWSN_2.4V_SSE_MB_FFTW.exe as fastest build for this moment.
But for P3 Ak v8 will be faster probably.
That why both builds needed.
2) pdb and manifest files not needed for app run, but manifest could be required in some new Windows version someday (M$ guys seems just can't live w/o some additional "fun" like .Net features...) and pdb file contains debug info that could help collect additional info in case of app crash.

Sorry, can't post in the Number Crucher's corner due to insufficient creditworthiness. :(

Anyways, am I correct with the perception that the most recent version of MB is AK_v8 (for PIII SSE), as opposed to Crunch3er's 2.4V?

Secondly, there are two files in the AK_v8 that I'm curious about: a .PDB file and a .manifest file. Do I need to retain both of these files?

I manually merged the app_info file. It looks like this:

<app_info>
<app>
<name>astropulse</name>
</app>
<file_info>
<name>ap_5.00r103_SSE.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
<file_ref>
<file_name>ap_5.00r103_SSE.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8_win_SSE_P3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8_win_SSE_P3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8_win_SSE_P3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Does that look copacetic?

Finally, I've processed a total of 212hrs (w/ 60.909% complete) of std AP. By updating to AP 5.00r103 "midstream", did I just shoot myself in the foot?

-----------------------------------------------------------------------------

Speaking of shooting myself in the foot, I can't decede between:

accidently creating a dozen instances of myself and shooting one instance of myself in the foot (providing emergency medical care will prove futile since it will be impossible to tell between wounds that are merely bitwise copies and wounds that are pointing at some other wound saying, "that's me, over there.")

OR

shooting myself in the foot and anybody who accesses my website, or other sort of internet connection stream, will leave hobbling and cursing.

Maybe I'll just shoot myself in each toe, iteratively, until I run out of toes, then read in the next foot and repeat. If I run out of bullets, I'll continue pulling the trigger futilely because I have no exception-processing ability.

OR

Since I can't remember the syntax for anything, I spend five hours reading man pages before giving up, shoot the computer, switch to C. Then I shoot myself in the foot.

OR

% ls
foot.c foot.h foot.o toe.c toe.o
% rm * .o
rm: .o: No such file or directory
% ls
%