BOINC 6.3.17 for windows is available.

I think the funczion of bersion .17 ist like the Version .16.

Here are the changes for 6.3.16

* client: if "leave in memory" pref changes, quit suspended tasks
* manager: fix disk display when talking to pre-6.3 client
* MGR: More thorough validity checking to prevent crashes
* client: restore support for max_ncpus preference. This and max_ncpus_pct can both be specified. If both are specified, we take the min
* LIB: Fix the windows callstack dump routine for Visual Studio 2008
* WINSETUP: Don't allow parent permissions to be inhertied from the parent directory when we setup the data directories permissions
* WINSETUP: Include a fix for the ALLUSERS flag so that based on the user preference, the installation settings are honored
* MGR: Have the SkinManager parse the correct spelling of 'organization'.
* MGR: Add a new tab status to the Simple GUI for when the client has been instructed to delay starting applications via the <delay_start> option in cc_config.xml
* WINSETUP: When the shortcut to BOINC Manager remove the minimize flag, it apparently was causing the small manager window. The '/s' parameter already takes care of minimizing the window
* LIB: The max cpu preferences was named 'max_cpus' and not 'max_ncpus' back in the day
* client: the max percent needs to be based on the max cpu preference not the total number of CPUs if we are actually calculating the min of both of them

Seems to run fine on Vista64.
Let's see how it does after some time and some task switches...

---

pixelicious.at - my little photoblog

6.3.17 seems ok so far, But I've had little time to observe it. I installed it last night but had other things to do and have only been awake 10 minutes today.

6.3.16 had a display bug which I found within the first hour of testing it. Hence the quick release of 6.3.17 same day as 6.3.16.

There are not many scheduler changes in these over 6.3.15 so they should remain stable, most changes were minor tweeks or cosmetic and some fine tuning on the communication between manager and client and the screen redraw to reduce flicker. That was the cause of phanton lines appearing in task display or lines appearing with wrong status of task in 6.3.15 and 6.3.16, harmless but not desired for a public release. I've done quite a few extensive combinations of tasks, projects and loads in 6.3.15 with no signs of it not keeping the proper number of tasks running.

One thing semi-fixed is the startup of manager, like after exit or a reboot, previously if you started it closed, then opened it from the icon the window size was small, not the size you left it. Now it should remain the size you left it, but the position still drifts. At least it is easier to just move the window a little than have to move and resize each time. They will continue to try to figure out why windows can;t remember the position.

It is probably safe to run this version.

You should really wait for a release memo to appear on the alpha email list before posting a version is out on public message boards. 5 of the last 8 versions were not the best and some had major flaws.

This is more for krunchin Keith

When I start BOINC now, I see

10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <checkpoint_debug>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <coproc_debug>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <cpu_sched>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <cpu_sched_debug>

Also, I keep getting the dialog box to join a project every time the manager starts up (though this build it was the account manager). I already have it attached to BAM!, so why would it be asking to reattach? I did go through and rejoin the BAM! today and the BOINC manager window auto minimized on me as soon as I clicked finish.

Running on Server 2008 x64, installed the 64bit BOINC to its own directories (d:\Datax64 and d:\progx64)

both went away after restarting BOINC. this time. strange.

Now BOINC is quiting on me a few seconds after launching. The manager will stay open with "connecting to local host". If I leave it own, about a min later, it'll reconnect for about 1 sec, then again loose connection. In the task manager, I see BOINC.exe running only for that one second. I am going back to 6.3.15

15 did the same thing, went back to 14, and it *seems* stable again

This is more for krunchin Keith

When I start BOINC now, I see

10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <checkpoint_debug>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <coproc_debug>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <cpu_sched>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <cpu_sched_debug>

Also, I keep getting the dialog box to join a project every time the manager starts up (though this build it was the account manager). I already have it attached to BAM!, so why would it be asking to reattach? I did go through and rejoin the BAM! today and the BOINC manager window auto minimized on me as soon as I clicked finish.

Running on Server 2008 x64, installed the 64bit BOINC to its own directories (d:\Datax64 and d:\progx64)

both went away after restarting BOINC. this time. strange.

Now BOINC is quiting on me a few seconds after launching. The manager will stay open with "connecting to local host". If I leave it own, about a min later, it'll reconnect for about 1 sec, then again loose connection. In the task manager, I see BOINC.exe running only for that one second. I am going back to 6.3.15

15 did the same thing, went back to 14, and it *seems* stable again

Hum...

First I suspect you have an unclosed or invalid tag in cc_config.xml before those, those are all valid tags and I have all those in my file. This might be causing all the problems.

As for x64 version it should be the same as x86, but since I do not have there could be some flaw I can't test for. I also do not use an account manager. This question would be better posted on the alpha email list.

But if we could check your cc_config first that might be a good starts, Could you PM me your entire cc_config.xml file.

first, sorry 4 the bad english.
i had a problem with my dualcore-cpu. after upgrading from 6.3.15 > 6.3.17, i had only one cpu in the messagewindow of boinc.
then i have craete the cc_config file, but nothing.
so i have look into the file "global_prefs" and have change the line "<max_cpus>x</max_cpus>" (x= number of cpu´s)manual to 2 cpu´s.
now its all ok...i have my both cpu´s again 4 crunching ;D

I hope that I could help!

the underlying logic of cpu-s changed from ncpus to max_cpus in 6.3.17

this will be used for exacter scheduling in the next versions (according to boinc-dev mailinglist some are already trying with different implementations)

the underlying logic of cpu-s changed from ncpus to max_cpus in 6.3.17

this will be used for exacter scheduling in the next versions (according to boinc-dev mailinglist some are already trying with different implementations)

Thats not exactly correct.

max_cpus was the old way before 6.X something, where in your preferences you specified # (1,2,4) of processors, to limit less than max usage. At some point it was changed to a percentage max_ncpus_pct where you specify this as a percentage 25%,50%,100% of the processors as reported by the os.

What has happened is some people run new clients on old projects only using the old preference way, not being able to set this, so the old way was added back, and combined. The client can use either way or both where it will take the minimum of the two if both are specified, always with a minimum of 1 as you cannot run with 0 cpus.

ncpus is the internal designation inside the client and also the debug flag to be used to simulate a higher number of processors for testing, so testers and developers could test the logic of having 4 cpus without actually having a quad-core.

See changeset 16281

David 22 Oct 2008
- client: restore support for max_ncpus preference.
This and max_ncpus_pct can both be specified.
If both are specified, we take the min.

It would be really nice in these threads about BOINC clients if posters would specify whether they are talking about Windows or Linux clients. I am using Linux only and have to do a lot of scrolling around to see which platform is being discussed to see if it applies to my setups....Thanks

This is more for krunchin Keith

When I start BOINC now, I see

10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <checkpoint_debug>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <coproc_debug>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <cpu_sched>
10/24/2008 11:27:15 AM||Unrecognized tag in cc_config.xml: <cpu_sched_debug>

Also, I keep getting the dialog box to join a project every time the manager starts up (though this build it was the account manager). I already have it attached to BAM!, so why would it be asking to reattach? I did go through and rejoin the BAM! today and the BOINC manager window auto minimized on me as soon as I clicked finish.

Running on Server 2008 x64, installed the 64bit BOINC to its own directories (d:\Datax64 and d:\progx64)

both went away after restarting BOINC. this time. strange.

Now BOINC is quiting on me a few seconds after launching. The manager will stay open with "connecting to local host". If I leave it own, about a min later, it'll reconnect for about 1 sec, then again loose connection. In the task manager, I see BOINC.exe running only for that one second. I am going back to 6.3.15

15 did the same thing, went back to 14, and it *seems* stable again

Do you run boinc as a service ?

I have no problem, but someone else is now reporting that when running as a service on windows XP (32bit) version that the service is cutting out after 30 seconds.

It would be really nice in these threads about BOINC clients if posters would specify whether they are talking about Windows or Linux clients. I am using Linux only and have to do a lot of scrolling around to see which platform is being discussed to see if it applies to my setups....Thanks

Well, since there is no linux 6.3.17 client yet....I think we are talking about windows. Most options apply equally to all clients though.

First post says ...for windows...

Another post says vista64

Another says Server 2008 x64 (That is Windows)

cant run this project as a service, so no, its not.

Others on my team are asking why every thing they start BOINC a window pops up to attach to a project.

Others on my team are asking why every thing they start BOINC a window pops up to attach to a project.

Weird, I only had that with 6.3.8, or maybe it was 6.3.10.
6.3.17 runs fine here with Vista 64 SP1. I haven't seen any problems `til now...

What exactly are they doing to get the attach to project wizard pop up?

---

pixelicious.at - my little photoblog

starting the BOINC manager

Others on my team are asking why every thing they start BOINC a window pops up to attach to a project.

if they are upgrading, most likely the registry was corrupted.

My installation is always manual - extract the boinc files by /a switch
placed the extracted files in one location. Then the data files in other location. etc..etc

You must have some knowledge about MSI inorder to do manual installs. Like understading the Custom Actions, Services, etc...

Here's the registry (keyword INSTALLDIR and DATADIR):
[HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley\BOINC Setup]
"INSTALLDIR"="D:\\BOINC\\"
"LAUNCHPROGRAM"=""
"ENABLELAUNCHATLOGON"=""
"ENABLESCREENSAVER"=""
"SERVICE_DOMAIN"=""
"SERVICE_USERNAME"=""
"SETUPSTATESTORED"="TRUE"
"MIGRATIONVERSION"=""
"MIGRATION"="TRUE"
"MIGRATIONDIR"="D:\\BOINC\\"
"RETURN_REBOOTREQUESTED"="0"
"REBOOTPROMPT"=""
"RETURN_VALIDATEINSTALL"="1"
"DATADIR"="D:\\BOINC Data\\"
"ENABLEPROTECTEDAPPLICATIONEXECUTION"=""
"ENABLEUSEBYALLUSERS"="1"

Others on my team are asking why every thing they start BOINC a window pops up to attach to a project.

Weird, I only had that with 6.3.8, or maybe it was 6.3.10.

Yes, I had that with the 6.3.10, too, every time I restarted Windows and BOINC the Attach-Window did come up. I first thought it could be a missed setting during the installation, but it wasn't.
After changing to the 6.3.17 all is fine now.

---

Member of BOINC@Heidelberg and ATA!

Others on my team are asking why every thing they start BOINC a window pops up to attach to a project.

Weird, I only had that with 6.3.8, or maybe it was 6.3.10.

Yes, I had that with the 6.3.10, too, every time I restarted Windows and BOINC the Attach-Window did come up. I first thought it could be a missed setting during the installation, but it wasn't.
After changing to the 6.3.17 all is fine now.

Same here. I had 6.3.10 on this machine that I use to check the rest of my grove. Every time I selected a new machine, it would pop up a window reminding me to use BAM to select a project for most of my machines. Some would not do that weirdness, I guess since they were to old. Anyway, 6.3.17 doesn't do this any more.

I had 6.3.17 ask to attach to BAM! every time it restarted... got old real quick. Id see the windows "communicating with BAM!" then it would ask for my account info. I finally resubmitted the account info (even though in the message logs I would see it had already connected)and the message never came back.

cant run this project as a service, so no, its not.

I thought that applied only to Windows Vista.

I had 6.3.17 ask to attach to BAM! every time it restarted... got old real quick. Id see the windows "communicating with BAM!" then it would ask for my account info. I finally resubmitted the account info (even though in the message logs I would see it had already connected)and the message never came back.

So is 6.3.17 still crashing or is it running now ?