Czech Dutch English French German Spanish
Home | Search | About | Forum | Login

BOINC

FAQ Service (English)

 

BOINC 6.2 - 6.12

FAQ: BOINC 6.2 - 6.12
Title: BOINC 6.2 - 6.12
Author: Jorden / John
Views: 118810
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German French English Dutch
Created: 06/06/2008 16:06:29
Last Modified: 04/11/2013 01:28:32

Contents:

Differences between BOINC 5 and BOINC 6:
(We will be adding to this FAQ when we come across questions not handled in this FAQ)

See BOINC 6 Release Notes for more information on this release.

The Big Difference: Where did BOINC install to?
BOINC 6 uses separate directories for its executables and data files. These directories cannot be merged any more as that will give problems. Data files are all the files that can be written to.

BOINC Programs directory
The default directory where BOINC will install its executables to is:
Windows 32bit: C:\PROGRAM FILES\BOINC
Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
Linux: wherever you are unpacking it/BOINC/
Macintosh: /Applications/BOINC/

BOINC Data directory
The default directory where BOINC will install the data files to is:
Windows 98/SE/ME: C:\Windows\All Users\BOINC or C:\Windows\Profiles\All Users\BOINC (*)
Windows 2000/XP: C:\Documents and Settings\All Users\Application Data\BOINC (*)
Windows Vista/Windows 7: C:\ProgramData\BOINC     (*)
Linux: wherever you unpack it/BOINC/
Macintosh OS X: /Library/Application Support/BOINC Data/

(*) This directory may well be hidden, so either put the path to it directly into Windows Explorer, or instruct Windows Explorer to show hidden files and folders.

How to do that?
For Windows 2000 + XP: See here.
For Windows Vista: See here.
For Windows 7: See here.

For Windows you can still tell the BOINC installer different paths to the directories, you don't need to follow the default paths if that's inconvenient.

Depending on the amount of data to be migrated the migration can take anywhere from a few minutes to a couple of hours. You also have to have enough space available on your hard drive for a full copy. The migration is supposed to happen only once, all the next times you upgrade BOINC it won't happen again.

For a comprehensive walkthrough on installing BOINC 6.2 on the Windows flavors, please look at this FAQ, which shows in pictures what you will come across in the installer.

Accounts
BOINC 6 will be able to run under your user name, but its installer will make new accounts specifically for BOINC when installed as a protected service: 'boinc_master', 'boinc_project', 'boinc_admins', 'boinc_users' and 'boinc_projects'.

Before BOINC can use these new accounts, the computer needs to be rebooted at the end of installing BOINC. Without it, BOINC won't work.
Make sure you closed/saved all other programs before clicking Yes on the reboot request as it will start the reboot process immediately!

It will only need this reboot when you installed BOINC for the first time or come from BOINC 4.xx and 5.x.x or had a 6.1.x version installed (including 3rd party BOINC).

Graphics and Screen Saver
The way that graphics work has changed significantly.
In BOINC 5 and before, the graphics module was built into the science application. Come BOINC 6, the science application and graphics application are two separate applications. This is done in case there are problems with the graphics, so that the task won't crash with a computation error. The graphics application may crash, but the computation continues.

Under Windows Vista the BOINC service runs on desktop 0, and the user display is sometimes desktop > 0. Under Vista a built in graphics display would not display at all.

When BOINC 6 is installed in protected mode (a service), it will only allow these new graphics applications to show the graphics or screen saver. Older applications will continue to work without a problem, they just will not show graphics or the project's screen saver. This mode also allows BOINC to run with no user logged in.

When BOINC 6 is installed in graphics compatibility mode (not a service), it will show graphics for both the older applications as well as the newer applications. This is the equivalent of multi-user mode and requires a user to be logged in.

Projects are urged though to make the new graphics applications.

Multiple selections
An enhancement in BOINC 6.2 is the possibility to select multiple tasks, projects and upload&downloads and use the menu to suspend, resume, detach, abort them. All menu options are enabled, so you can even detach multiple projects in quick succession.

Example screen shot of selecting multiple projects
Example screen shot of selecting multiple tasks


Grid View needs to be enabled to use this option.
In BOINC 6.4 this will be followed by selecting and sorting the messages of only one project.

Do's and Don'ts
- The old workaround to get the graphics and screen saver to work with a service install will no longer work. As soon as you tell this version of BOINC to use the local system account, BOINC will refuse to run.

- The screen saver will now work with the password protection set.

- Installing BOINC all in one directory will not work. The BOINC Data directory always needs to be a separate directory from the BOINC directory.

- The Windows installer has some prohibitions on where you can install BOINC, such as the root directory of any drive and protected directories in the Windows environment. If you try it anyway, you will get a warning message and be returned to the directory menu in the installer.

Vista Compatibility
BOINC 6 is fully compatible with Windows Vista and Windows 7.

Domain Controller Incompatibility
The present range of BOINC 6 is incompatible with Domain Controllers, meaning that you cannot install it on your system if it is a DC. This is because the developers used the Local Account API's instead of the Global Account API's.

A fix for this will be available in a future BOINC. When exactly is at this moment unknown. This depends on when the new installer software will be used.

In the mean time, you can still install and use BOINC 5.10.45, although this doesn't support GPUs or multi-threading applications.

BOINC 5.10.45 32bit version
BOINC 5.10.45 64bit version

Uninstalling
With BOINC 6.2 only: When you install BOINC 6.2 over a BOINC 5 version and then uninstall it through Add/Remove Programs, the Data directory is migrated back into the BOINC directory. This is done so you can always return to BOINC 5.10 without needing to move a lot of files by hand.

Once you install a newer BOINC 6 version over BOINC 6.2, then uninstall the newer version, the Data directory stays where it is. It will not migrate back into the pre-BOINC 6 position.

Stability and Problems
This version of BOINC has been tested for over 6 months and is deemed stable by the testers. Which does not mean it will run stably on your machine. If you do have problems with it, please post about it on the BOINC Dev forums, where we will be able to help you or get the developers to chime in.

If you do post there, please supply information on your computer (make and model, CPU type, video card and DirectX version if you have graphics trouble, which operating system, how you installed BOINC and any drivers information you can lay your hands on. Any errors you see, please post those as well. If you see a Blue Screen Of Death we would like to know what it says, not just that you had one.

If you have sudden trouble with a project's science applications, tell us which project it is on, which version of the application and what you have done to see if it was caused by BOINC.

Stopping BOINC when running as a service
Ways to stop BOINC 6.2.x when running as a service:

1) BOINC Manager->Advanced view->Advanced->Shut down connected client->OK->Cancel followed by BOINC Manager->File->Exit.

2) BOINC Manager->File->Exit followed by Windows Start button->Run, type net stop boinc, click OK.

3) BOINC Manager->File->Exit followed by Windows Start button->Run, type services.msc, click OK. Find BOINC in the Services applet. Right click on it, choose Stop from the drop-down menu.

To start BOINC and the service again, just go Start->Programs->BOINC->BOINC Manager link.

Quick shots
Q. I am seeing This a development version of BOINC and may not function properly in my startup messages. Should I worry?
A. No. It appears that this message slipped through. When testing of BOINC 6.2 began, this message was removed from all platforms. Apparently not from the Linux x86_64 version.

The message can safely be ignored.

Q. After installing the Linux version of BOINC 6.2 I now have two BOINC command tools in my directory, boinc_cmd and boinccmd. Which one should I use?
A. To be conform in all platforms, the underscore was removed from the name of both boinc_cmd and boinc_mgr, making them boinccmd and boincmgr. Be sure to change this in your bash scripts.

Q. When running the benchmarks, I am getting an error that says "FP benchmark ran only 0.375000 sec; ignoring; CPU benchmarks error". Is there something wrong with my CPU?
A. This means that a higher CPU-bound process is running. Check in Task Manager (or equivalent) what is taking up the CPU, stop that process, then rerun the CPU benchmarks (Advanced->Run CPU benchmarks).

Always run your benchmarks when the CPU is not in use by higher priority programs.

Q. How do I shut BOINC down now? Exiting BOINC Manager, BOINC and the applications keep on running! And how do I get it running afterwards?
A. There are a couple of ways to shut down the service.
The easiest method to shut down BOINC and get it running again is to go through BOINC Manager->Advanced view->Advanced->Shut down connected client. This will shut down the service. Next you go File->Exit to close down BOINC Manager.

To start BOINC back up, go Start->Programs->BOINC->BOINC Manager. This will start up BOINC Manager, which in turn starts the service.
 

BOINC 6: Advanced Local Preferences

FAQ: BOINC 6: Advanced Local Preferences
Title: BOINC 6: Advanced Local Preferences
Author: Jorden
Views: 85103
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 24/07/2008 12:57:38
Last Modified: 31/08/2012 18:51:16

Contents:

Since BOINC 5.8.16 BOINC Manager has had the local preferences. First only in the form of the global_prefs_override.xml file that you had to edit by hand, since 5.10.14 also in the form of a menu in the BOINC Manager.

The preferences here will override any of the same preferences you set through the web site.
Do know that those preferences you set on the web site and are not in the local preferences are not overridden!

To get to them
Open BOINC Manager->Advanced view->Advanced->(Computing) Preferences.

All changes you make to the local preferences are saved every time you press the OK button. They will be used immediately. If you just want to look in on them, but not use them, make sure you exit the preferences window with the Cancel button. Whenever you want to get rid of the local preferences and return to using the preferences from the web site, press the Clear button.

Processor usage


While computer is on batteries, a setting for laptops. When this is selected BOINC will continue to work while the laptop runs on its internal battery.

While computer is in use, when this option is selected, BOINC will always run, even when you are working on the computer. Deselect this option if you want to use the idle run option.

Only after computer is idle for 3 minutes, will only work when you have the above option not selected. It will wait for the amount of time you set here, checking in that time if there is any keyboard and mouse activity. If there isn't and the computer is idle, BOINC will start up one of the science applications. As soon as you move the mouse or hit a key on the keyboard, BOINC will suspend all applications doing calculations.

Every day between 00:00 and 00:00 (no restrictions if equal), provides a selection between what time and what time BOINC is allowed to run. For instance when you're not using the computer during the night, then you set the time between 22:00 and 08:00 .. it uses 24 hour settings (00:00 to 23:59) and will use the clock of the operating system.

Day-of-the-week override, as above but set for specific days in the week.
If you only want BOINC to run on Saturday, from 3am till 4pm, you select Saturday and set the time to 03:00-16:00. It can be selected for multiple days.

Switch between applications every 60 minutes, selects how many minutes should pass before BOINC switches between applications when attached to multiple projects. Default setting is 60 minutes.

On multiprocessors, use at most 100% of the processors, selects how many CPUs you want to use at any time. If you have a 4 core computer and want to use 3 of them, set this option to 75%.

Use at most 100% of CPU time, is the CPU Thermal Throttle System. It can be used to throttle the CPU or CPUs when your system is running very hot.


Network usage


Maximum download rate KB/sec, with this setting you can tell throttle the maximum download speed that BOINC can use to download the science applications and tasks with. Of course this also depends on what speed the project's internet connection is running at.

Maximum upload rate KB/sec, with this setting you can tell throttle the maximum upload speed that BOINC can use to download the science applications and tasks with. Of course this also depends on what speed the project's internet connection is running at.

Connect about every x days, sets the frequency that BOINC contacts the project server to upload work, download new work and report work. It is not to be used as a method to queue up more work. For that you can use the Additional work buffer. Default at 1 day, if set to zero days it'll tell BOINC that you're on an always on connection.

Additional work buffer x days (max. 10), sets the amount of work that BOINC can ask buffer additionally per project. Default at 1 day, but can be set to zero as well. When set to zero, BOINC will ask for 1 second of work, translating into one task per project.

Skip image file verification, is used for UMTS connections and other ISPs that modify or compress image files. When checked BOINC won't check for the MD5 key on the image file.

Confirm before connecting to internet, when selected this pops up a confirmation window asking you if you want to connect to the internet. Primarily used with modem connections.

Disconnect when done, when selected will silently disconnect from the internet after BOINC is done with its communications. Otherwise you will get a pop up asking you if you want to disconnect.

Day-of-the-week override, provides a selection on which days you want BOINC to connect to the internet to communicate with the projects you are attached to. If you only want to use it on Sundays from 2am till 5pm, you select Sunday and add 02:00-17:00 in the time box. Can be selected for multiple days.

Disk and Memory usage


Use at most 100 Gigabytes disk space, set the maximum amount of disk space that BOINC can use for itself, all the projects you are attached to and all the work you download.

Leave at least 1 Gigabytes disk space, sets the minimum amount of disk space that BOINC should leave free on the disk drive. Keep in mind that on most Windows systems the page file lives on this drive as well.

Use at most 50% of total disk space, sets the maximum amount of space that BOINC can use on the total hard drive. If you have multiple partitions, this number will look at the complete hard drive size, not the partition size.

Write to disk at most every 60 seconds, sets the frequency at which BOINC will write a task's state to disk. BOINC writes its own state to disk very frequently, this option won't change that frequency. The science application does not have to follow this frequency, some follow their own frequency no matter what number you add here.

Use at most 75% of page file (swap space), sets the amount of page file that BOINC can use at maximum. it uses the page file (or swap space) to store tasks in when used in combination with the "leave tasks in memory while suspended" option.

Use at most 50% of memory when computer is in use, sets the amount of RAM that BOINC can use at maximum while the computer is in use. This can cause tasks to stop with the message "Waiting for memory".

Use at most 90% of memory when computer is idle, sets the amount of RAM that BOINC can use at maximum while the computer is idle.

Leave applications in memory while suspended, leaves the science applications in memory (page file) when BOINC switches between applications. Very useful setting for tasks that do not checkpoint and otherwise run from beginning till ending without stopping. If BOINC is stopped or the computer rebooted, the applications in memory will be unloaded and upon a restart of BOINC the tasks that don't checkpoint will still start from the beginning.
 

BOINC 7.0

FAQ: BOINC 7.0
Title: BOINC 7.0
Author: Jorden / LadyL / Trog Dog
Views: 60740
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 16/04/2012 10:22:18
Last Modified: 04/11/2013 01:28:34

Contents:

If you came here from a BOINC 4 or BOINC 5 installation, please read the BOINC 6.2 - 6.12 FAQ first!

Warning: Information for Advanced Techno-nerds and Geeks only!
For a minimum of information about BOINC 7.0, see the BOINC 7.0 Release Notes. Why isn't there more information in there? Because the developers are hesitant to give more information about BOINC as it may become too technical for you to understand.

We're in negotiation with the developers to convince them to allow us to write advanced explanations to the BOINC User Manual Wiki, primarily to show you how BOINC 7.0 really works, or why it does things differently from BOINC 6.

The negotiations are going well, we're waiting for the final answer.

In the mean time, this FAQ will have information about BOINC 7.0 that's nowhere else found.

Prerequisites:

BOINC Programs directory
The default directory where BOINC will install its executables to is:
Windows 32bit: C:\PROGRAM FILES\BOINC
Windows 64bit: C:\PROGRAM FILES (x86)\BOINC for 32bit BOINC, C:\PROGRAM FILES\BOINC for 64bit BOINC
Linux: wherever you are unpacking it/BOINC/
Macintosh: /Applications/BOINC/

BOINC Data directory
The default directory where BOINC will install the data files to is:
Windows 98/SE/ME: C:\Windows\All Users\BOINC or C:\Windows\Profiles\All Users\BOINC (*)
Windows 2000/XP: C:\Documents and Settings\All Users\Application Data\BOINC (*)
Windows Vista/Windows 7: C:\ProgramData\BOINC     (*)
Linux: wherever you unpack it/BOINC/
Macintosh OS X: /Library/Application Support/BOINC Data/

(*) This directory may well be hidden, so either put the path to it directly into Windows Explorer, or instruct Windows Explorer to show hidden files and folders.

How to do that?
For Windows 2000 + XP: See here.
For Windows Vista: See here.
For Windows 7: See here.

Domain Controller Incompatibility
The present range of BOINC 6 and 7.0 are incompatible with Domain Controllers, meaning that you cannot install it on your system if it is a DC. This is because the developers used the Local Account API's instead of the Global Account API's.

A fix for this will be available in a future BOINC. When exactly is at this moment unknown. This depends on when the new installer software will be used.

In the mean time, you can still install and use BOINC 5.10.45, although this doesn't support GPUs or multi-threading applications.

BOINC 5.10.45 32bit version
BOINC 5.10.45 64bit version

Windows 8 (RC) Compatibility
BOINC 7.0 can be run on Windows 8 RCs, but only if you installed BOINC prior to doing an upgrade installation to Windows 8. Otherwise you'll have the same problem as when installing on a domain controller, that certain limited user accounts required for BOINC cannot be made. This is to be fixed in a later version.

Completely uninstalling BOINC 7.0
(If you only want to return to BOINC 6, read "Returning to BOINC 6" below this.)
When you uninstall BOINC 7.0, the registry entries made by the installer, and the Data directory will be kept on disk. If you want to uninstall BOINC completely, make sure to follow these steps.

Returning to BOINC 6
Due to changes to how BOINC 7 writes details about work to the client_state.xml file, you can't easily return to BOINC 6 when BOINC 7 has run on your system. Not without you having made an earlier backup of the data directory, and even then it'll be troublesome. Any work you have gotten since you ran 7.0, will be 'lost' when you return to 6. Only projects that have "resend lost tasks" on will resend them to you, but not all projects do this due to the severe strain on the database. (Only Seti and Einstein have it on, I think).

So here's what you can do to return to BOINC 6 in an easier manner:
- Set No new tasks on all your projects, run all the work to completion, upload & report it.
- Uninstall BOINC.
- Go to the data directory and remove the client_state.xml and client_state_prev.xml files.
- Install BOINC 6.xx, whichever flavor you liked.
- Run that.
(- Set Allow new tasks on all your projects.)

That's all.

Stability and Problems
This version of BOINC has been tested for over 9 months and is deemed stable by the developers. Which does not mean it will run stably on your machine. If you do have problems with it, please post about it on the BOINC Dev forums, where we will be able to help you or get the developers to chime in.

If you do post there, please supply information on your computer (make and model, CPU type, video card and DirectX version if you have graphics trouble, which operating system, how you installed BOINC and any drivers information you can lay your hands on. Any errors you see, please post those as well. If you see a Blue Screen Of Death we would like to know what it says, not just that you had one.

If you have sudden trouble with a project's science applications, tell us which project it is on, which version of the application and what you have done to see if it was caused by BOINC.

So where did the Messages tab go to?
(sarcasm warning, or bad attempt at humor)
Ever since BOINC 6.12, the Messages have been hidden away from view, as they were also too scary for users. Users would perceive them as all errors, and therefore, the whole thing needed to be hidden away from view. It's now in a separate window, which can be reached by pressing CTRL + SHIFT + E simultaneously, or by navigating through Advanced view->Advanced menu->Event log.

However, you'll still see the messages then. Which may still be scary or worrisome. Therefore you should only go here when you have trouble and you're being asked by the person helping you to check what BOINC writes in the messages. And even then, probably, best not. Or as David Anderson says it:
Quote:
The event log is not intended to be read by users. The event log is for developers and testers. Information for normal users goes in the other parts of the GUI.

So, are you a normal user and do you want to stay normal? Then do not use the Event Log! No, use stdoutdae.txt instead. Way safer. :)

Differences between BOINC 6 and BOINC 7.0:

OpenCL support
This BOINC version will detect any ATI/AMD and Nvidia GPU capable of OpenCL. Newer project applications using OpenCL require that the client detects whether the GPU in your system is capable, which drivers are used, what OpenCL capability the hardware has, how much memory it has total and how much of it is free and some other things. With this information the project developer can more easily include or exclude your hardware when it comes to giving out work.

See the OpenCL FAQ for more information and projects with applications.

Simple view new skin
The Simple view has been rewritten from the ground up, all the old images (for buttons and such) are ditched, skinning is made easier, translations will now be able for the whole of the simple view.

Improved virtual machine support
Let's start with the basics first. What's a Virtual Machine?
Wikipedia writes that: A virtual machine (VM) is a "completely isolated guest operating system installation within a normal host operating system".

It allows you to run other operating systems within your own operating system, without you needing to reboot into that other operating system. So you can run for instance Windows 7 - 64bit, with a VM running Windows XP. Or you can run Ubuntu 12.04 with a VM running Mac OS X 10.7.3

This then makes it easier for projects to supply you with work, as they only have to program their applications for one platform --usually Linux. The are downsides though, one of which is that you have to install an external program, called Virtual Box. Another is that the project will send you an image file of their operating system, which will run in the virtual machine. These tend to be rather large though. Even with compression, easily over 250MB, which you still have to download.

The title in itself is not correct... it's improved Virtual Box virtual machine support, as only Virtual Box is fully supported at this time. If anyone wants to use a different virtual machine, they'll need to port the vboxwrapper application over to whichever virtual machine they use.

The new CPU + GPU scheduler and work fetch module
OK, now, you have by now noticed that your old BOINC 6 did things differently than this BOINC 7.0 does things. That's because the old 6 was deemed broken and the new 7.0 is deemed fixed, but with some bugs still included.

The REC-based scheduler
What the client does is, it keeps a record of how much CPU/GPU time a certain project has recently seen - the recent estimated credit (REC). It compares this figure with the project share that has been set. A project that has worked less than its share will get priority in both scheduling (running tasks) and work fetch. Then as it gets crunch time its REC increases and another project will get to the head of the queue. Over time you get a more or less good distribution of crunching time according to resource share.

Points of note:
- GPUs are very productive so lead to high REC. If you run GPU projects alongside CPU ones on similar shares the GPU project sees virtually no CPU.
- CPU and GPU are scheduled separately.
- A project like SETI will probably stay pretty high up in the queue, since getting tasks is hit and miss due to their bandwidth being overworked.
-- However, setting a small 'additional days' cache will help getting tasks from Seti, since BOINC will ask more often, thereby increasing your chances.
(Source: LadyL, Seti forums)

In finer detail
The CPU and GPU schedulers have been rewritten from the ground up, as is the new work fetch module. This means that work fetch will happen completely different from how you're used to it in BOINC 6. Where BOINC 6 would for instance report work and immediately ask a new task, BOINC 7.0 will try to store a couple of "ready to report" results, report them and immediately request work only when BOINC is under the value set by the Minimum work buffer.

This means that when you have left your old BOINC 6 values for "Connect to" + "Additional work" at, example given 0.1 and 1.0, that BOINC 7.0 will ask for 1.1 days worth of work and ONLY renew this cache when it's fallen under the 0.1 days worth of work limit.

Which means that it can happen that your BOINC runs empty, because 7.0 won't request new work before it has dropped below the 'minimum work' setting and will only ask for work up to the 'and additional' setting --and that only from the project that has the highest priority (worst REC to resource share ratio). Only if that project doesn't have work it will ask other projects in order of priority.

This is easily fixed though, by turning the values around. Where the old values were 0.1 + 1.0, you now go for Minimum work buffer 1.0 + Maximum additional work buffer 0.1

However, there is a bug in the software somewhere, one that's difficult to track and thus fix. This one comes into play when you run work from 2 or more projects. It'll happen that one project will be running work solely, while the others are fresh out of work.

Although, if you now leave things well alone and don't interfere, this will fix itself in due course. It seems that BOINC just needs to learn about the new idiosyncrasies of all the projects again. When you're struck by this bug, do nothing.
Allow BOINC to adjust for at least a week to its completely new settings.

When you manage to let it go, you'll find that BOINC will switch between projects and only run these exclusively for a while, before returning to running a mixture of task from different projects. All according to resource share, of course.
 

BOINC command line switches

FAQ: BOINC command line switches
Title: BOINC command line switches
Author: Jorden
Views: 77120
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 20/11/2009 22:07:51
Last Modified: 26/11/2013 04:36:02

Contents:

When you start BOINC from the command line, you can give it the following switches as extra commands. Multiple commands in a row are possible.

--abort_jobs_on_exit
When the client exits, abort and report jobs.

--allow_remote_gui_rpc
Allow remote GUI RPC connections.

--allow_multiple_clients
Allow more than one instance of the client to run per host.

--attach_project <URL> <key>
Attach to a project using the project URL and the strong account key. This requires you have an account on the project already.
E.g. Boinc --attach_project http://setiathome.berkeley.edu 1234567890abcdef1234567890abcdef


--check_all_logins
For idle detection, check remote logins too.

--daemon
Run as daemon (Unix). When installed as a service on Windows, starting Boinc will automatically start the service. It won't on Unix.

--detach
Detach from console (Windows). This closes the command line window that otherwise stays open when you start Boinc.

--detach_project <URL>
Detach from a project.

--dir <path>
Use given directory path as BOINC home directory.

--exit_after_app_start N
Exit N seconds after an application starts.

--exit_after_finish
Exit right after finishing a job.

--exit_before_start
Exit right before starting a job.

--exit_before_upload
Exit right before starting an upload.

--exit_when_idle
Exit when there are no tasks.

--fetch_minimal_work
Get only one task per CPU core or GPU.

--file_xfer_giveup_period N
Give up on file xfers after N sec.

--get_daily_xfer_history
Show network traffic history.

--gui_rpc_port <port>
Port for GUI RPCs. Default port is 31416.

--help
Show command line switch options.

--launched_by_manager
Client was launched by Manager.

--master_fetch_interval N
Limiting or increasing period of master retry.

--master_fetch_period N
Reload master URL after N RPC failures.

--master_fetch_retry_cap N
Exponential backoff limit.

--no_gui_rpc
Don't allow GUI RPC, don't make socket.

--no_gpus
Don't check for GPUs.

--no_info_fetch
Suppresses the fetch of project list and of current client version #. Use when running on grid nodes. (New in 6.11.8)

--no_priority_change
Run apps at same priority as client.

--pers_giveup N
Giveup time for persistent file xfer.

--pers_retry_delay_max N
Max for file xfer exponential backoff.

--pers_retry_delay_min N
Min for file xfer exponential backoff

--redirectio
Redirect stdout and stderr to log files. Else they'll output to the command window.

--reset_project <URL>
Reset (clear) a project.

--retry_cap N
Exponential backoff limit.

--run_cpu_benchmarks
Run the CPU benchmarks.

--run_by_updater
Set by updater.

--saver
Client was launched by screensaver.

--sched_retry_delay_max N
Max for RPC exponential backoff.

--sched_retry_delay_min N
Min for RPC exponential backoff.

--show_projects
Show attached projects.

--skip_cpu_benchmarks
Don't run CPU benchmarks.

--start_delay X
Delay starting apps for X secs.

--unsigned_apps_ok
Allow unsigned apps (for testing).

--update_prefs <URL>
Contact a project to update preferences.

--version
show version info.
 

BOINC Installer: Error reading setup initialization file

FAQ: BOINC Installer: Error reading setup initialization file
Title: BOINC Installer: Error reading setup initialization file
Author: Jorden
Views: 71622
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 30/05/2010 01:32:22
Last Modified: 30/05/2010 01:32:22

Contents:

It can happen that when you have downloaded the installer file and try to run it, that you get the error Error reading setup initialization file.

This is caused by the BOINC installer not being able to unpack its temporary files in your Temporary Internet files folder. So clean this folder out, delete as much as possible there. Also delete the BOINC installer file.

Then download it again from the BOINC website and start the installation. You'll find it will now install without problems.
 

BOINC Manager cannot connect to a client

FAQ: BOINC Manager cannot connect to a client
Title: BOINC Manager cannot connect to a client
Author: Jorden
Views: 83400
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 09/10/2008 19:22:31
Last Modified: 18/02/2011 11:39:03

Contents:

You will get the pop up with the message BOINC Manager cannot connect to a client when:

1. You did not allow boinc.exe and boincmgr.exe through your firewall. These two parts of BOINC need to be able to talk to each other on TCP port 31416. Usually putting boinc.exe and boincmgr.exe in your firewall's trusted zone fixes this. Just restart BOINC afterwards.

2. The client was stopped for whatever reason and only BOINC Manager was kept running. Exit BOINC Manager and restart it to see if this fixes your problem.

3. Another program has taken up port 31416. In this case you will have to figure out which program does this and exit it, then make sure that BOINC starts earlier than the other program.

4. You had a GPU of some brand in your PC, have since removed it, but didn't uninstall and clean out its drivers. Best do so, to get BOINC to work with you.
 

BOINC Manager command line switches.

FAQ: BOINC Manager command line switches.
Title: BOINC Manager command line switches.
Author: Jorden
Views: 53080
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 29/03/2012 09:18:12
Last Modified: 29/03/2012 09:19:50

Contents:

Usage: boincmgr [/h] [--verbose] [/a] [/s] [/n <str>] [/g <str>] [/p <str>] [/b <str>] [/i] [/c] [/m]

Code:
/h --help               --> Show this help message.
--verbose               --> Generate verbose log messages. 
/a --autostart          --> BOINC Manager was started by the operating system automatically. 
/s --systray            --> Startup BOINC Manager so only the system tray icon is visible.
/n --namehost=<str>     --> Host name or IP address. 
/g --gui_rpc_port=<str> --> GUI RPC port number. 
/p --password=<str>     --> Password.
/b --boincargs=<str>    --> Startup BOINC with these optional arguments. 
/i --insecure           --> Disable BOINC security users and permissions. 
/c --checkskins         --> Set skin debugging mode to enable skin manager error messages. 
/m --multiple           --> Multiple instances of BOINC Manager allowed. 
 

BOINC? What is that?

FAQ: BOINC? What is that?
Title: BOINC? What is that?
Author: Jorden
Views: 86611
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German French English Dutch
Created: 29/08/2007 15:27:06
Last Modified: 29/08/2007 15:27:06

Contents:



BOINC stands for Berkeley Open Infrastructure for Network Computing.

The BOINC client doesn't crunch anything. It is a managing program, with which you can attach to scientific projects to download their applications and work.

It consists of 3 major parts:
- the Boinc daemon. This is the actual program that runs in the background.
- the Boinc Manager. This is the Graphical User Interface with which you can control the daemon.
- the Boinc screen saver. This shows the screen saver of the science application, if there is one built in in the science project's application. If not, it shows the standard Boinc screen saver.

The science applications of the various projects do the actual 'crunching'.

If you want to see Dr. David Anderson explain it to you, please follow this link to YouTube.
 

BOINCCMD command line switches

FAQ: BOINCCMD command line switches
Title: BOINCCMD command line switches
Author: Jorden
Views: 79147
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 20/11/2009 22:20:43
Last Modified: 04/06/2012 09:39:06

Contents:

The BOINCCMD program is the command line control program for BOINC. While you can start the BOINC client with its own set of switches, you can set these only once.

The BOINCCMD program allows you to control BOINC multiple times, especially useful for when you lack a GUI (BOINC Manager). Multiple commands per line are possible.

Usage: Boinccmd --command1 --command2 --command3

--lookup_account URL email passwd
Used to check up on your account and get your authenticator key and details sent to you.

--create_account URL email passwd name
Used to make an account at a project, using password such and so, your email address and what nickname to go on the account. Usage: boinccmd --create_account http://setiathome.berkeley.edu joe@email.com RoVeR12 Joe .. Watch out with case sensitivity on password!

--project_attach URL auth
Attach to project using your authenticator key.

--join_acct_mgr URL name passwd
Attach to an account manager.

--quit_acct_mgr
Quit using your current account manager.

--get_state
Show entire state.

--get_results
Show tasks. BOINC 6.12 and before.

--get_tasks
Show tasks. BOINC 7.0 and later.

--get_simple_gui_info
Show status of projects and active tasks.

--get_file_transfers
Show file transfers.

--get_project_status
Show status of all attached projects.

--get_disk_usage
Show disk usage per project attached.

--get_proxy_settings
Show proxy settings.

--get_messages [ seqno ]
Show messages, if need be output per sequence number.

--get_message_count
Show largest message sequence number.

--get_host_info
Shows details about your host, such as CPU used, Network name, operating system, disk size, etc.

--version, -V
Show core client version.

--result url task_name operation
Job operation options = suspend | resume | abort | graphics_window | graphics_fullscreen

--project URL operation
Project operation options = reset | detach | update | suspend | resume | nomorework | allowmorework

--file_transfer URL filename operation
File transfer operation options = retry | abort

--set_gpu_mode
Sets GPU mode. Options always | auto | never

--set_run_mode mode duration
Set run mode for given duration mode = always | auto | never

--set_network_mode mode duration
Set run mode for given duration mode = always | auto | never

--set_proxy_settings
Set up your proxy settings.

--run_benchmarks
Run CPU benchmarks.

--read_global_prefs_override
(Re-)Read the global_prefs_override.xml file.

--quit
Quit running the BOINC client.

--read_cc_config
(Re-)read the client configuration file (cc_config.xml).

--set_debts URL1 std1 ltd1 [URL2 std2 ltd2 ...]
Used to (re-)set the short term and long term debts of any given project. Usage: boinccmd --set_debts http://setiathome.berkeley.edu 0 0 (to reset the short term and long term debts on Seti@Home).

--get_project_config URL
Unknown

--get_project_config_poll
Unknown

--network_available
Unknown

--get_cc_status
Unknown
 

Boinc_x.x.x_windows_intelx86.exe is not a valid Win32 application

FAQ: Boinc_x.x.x_windows_intelx86.exe is not a valid Win32 application
Title: Boinc_x.x.x_windows_intelx86.exe is not a valid Win32 application
Author: Jorden
Views: 71148
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 06/03/2010 15:47:28
Last Modified: 06/03/2010 15:47:28

Contents:

This message occurs when the download is incomplete or corrupt. A glitch along the way in the internet connection. It may seem as if everything of the file is there, but if you only miss a couple of bytes, it may seem that the download was completed correctly, when it wasn't.

It also happens when your temporary internet files directory is full.

So try these two simple steps:

1. Delete your temporary internet files.

2. Download the file again, if you have the chance save it to a different directory (folder or map) than you're used to.
(try right clicking on the link and doing a Save As.. that way you can specify what path to save to, not have it go automatically to your temporary internet files folder).
 

Can I hide BOINC from view?

FAQ: Can I hide BOINC from view?
Title: Can I hide BOINC from view?
Author: Jorden
Views: 89217
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German English
Created: 15/12/2006 22:21:39
Last Modified: 15/12/2006 22:21:39

Contents:

Q: Is it possible to completely remove BOINC icon from system tray to prevent others to mess with it, and let the BOINC do its work in background, totally invisible?

A: Yes. You can install BOINC as a service and not allow Boinc Manager to load on Wndows start up. This way BOINC always runs, even when no one is logged in on the computer.


Use the third option.


Uncheck "Launch BOINC when logging on".
 

Computing is suspended - requested by operating system

FAQ: Computing is suspended - requested by operating system
Title: Computing is suspended - requested by operating system
Author: Jorden
Views: 61459
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 17/06/2011 18:16:48
Last Modified: 17/06/2011 18:16:48

Contents:

This means the OS is about to hibernate or suspend. It should be in this state only briefly (until the OS suspends).

You can make sure BOINC is fully stopped in time with the Suspend work if no mouse/keyboard activity in last X minutes preference. Make sure it will kick in a minute or two before the OS is allowed to go to hibernation, this to allow for all disk writes to happen before OS sleep.
 

Einstein: Got server request to delete file XXXXXX

FAQ: Einstein: Got server request to delete file XXXXXX
Title: Einstein: Got server request to delete file XXXXXX
Author: Mike Hewson
Views: 61384
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 04/06/2011 11:43:33
Last Modified: 04/06/2011 11:45:05

Contents:

Einstein@Home uses a BOINC feature, not used ( to date ) by other projects, called locality scheduling. The thrust of the concept is to try to reduce overall bandwidth usage by avoiding unnecessary downloads. This is contributor friendly as bandwidth cost and availability varies widely worldwide, so we seek to be inclusive at the low end of capacity with this tactic. Scheduling is tuned to a per-machine basis i.e. this is the 'locality' part of the phrase. Here's an apprentice baker's tour :

In essence you get given an unsliced loaf of bread ( data ), then a sequence of instructions in the workunits to slice it up, and one returns the slices as you go. Worldwide there are quite a number of distinct loaves about, a constantly varying pool as the project tasks are met. You'll be sharing workunits with other holders (your wingmen) of identical/cloned loaves. The wingman idea is to reduce the impact of instance errors by duplicating processing. A quorum is at least you and your wingman, but may be more for a given slice/task depending on how things go. (We used to have minimum quorums of three and four when I first turned up, presumably experience has shown fewer is OK.)

Now when your BOINC client reports in with finished work and is requesting new work, there's a bit of a conversation along the lines of 'what have you got for me in terms of the particular loaf I already have?'. Here is the logical point at which bandwidth saving is mainly enacted. The scheduler will look at what still needs to be done to that specific loaf, and attempt to issue further work for you with what you already have on hand.

Eventually loaves get fully sliced and need replacing ..... as indicated the BOINC client sorts this out by itself, once told that a given loaf is no longer needed. Effectively the E@H scheduler is saying that it wont be expecting to you to have that loaf any more, because in it's view of the total project workflows that particular loaf has gone stale. :-)

Quite a clever system really, certainly a handy option in the BOINC framework, but not every project will either need or use this locality scheduling. Hat's off to whom-so-ever thought that up and implemented it! :-)

Strictly speaking the language is that : a 'workunit' is a particular conceptual slice of bread from the one conceptual loaf within the project's data breadbin. However as the loaves are cloned to many machines, then thus sliced on each machine, that implies there exists clones of the slices too. Such clones are called 'tasks'. The scheduler looks at the reported/completed tasks at hand, and being it's job to keep track of what was sent to whom, it can thus answer the 'what to do next with what?' question. I suppose, in an perfect world with machine's matched for mojo etc, you'd only need to clone a loaf twice with these matched machines being wingmen for the entire loaf.

(Source)
 

My Boinc says it is suspended. Now what?

FAQ: My Boinc says it is suspended. Now what?
Title: My Boinc says it is suspended. Now what?
Author: Jorden
Views: 86078
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German English
Created: 14/12/2006 22:48:36
Last Modified: 14/12/2006 22:48:36

Contents:

Check if you didn't suspend BOINC:

1) Right-click on the BOINC icon in the system tray, see if there is a check before Snooze.
(This is available only on BOINC versions 5.6.x and higher. Versions before that had a suspend option in the right click menu. See 2 for that).

2) You have suspended BOINC through Boinc Manager, Activity menu, Suspend. Return it to Run based on preferences.
If you are using a 4.xx or 5.2.x version of BOINC, this can be found under the Network menu

3) You have suspended the Project. Go to the Project tab in Boinc Manager. Check the status of your project or projects. To resume a project, click on it, then click on the Resume button in the menu on the left.

4) You have suspended all of the tasks. In this case go to the Tasks tab and select each task, then press the Resume button in the menu on the left. Do this for all Tasks that are suspended.
If you are using Boinc version 4.xx or 5.2.x, you'll need the Work tab.

 

Not requesting work or reporting results / Requesting 0 seconds of work, reporting 0 completed tasks?

FAQ: Not requesting work or reporting results / Requesting 0 seconds of work, reporting 0 completed tasks?
Title: Not requesting work or reporting results / Requesting 0 seconds of work, reporting 0 completed tasks?
Author: Jorden
Views: 89259
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German English
Created: 31/10/2007 14:31:51
Last Modified: 31/10/2007 14:31:51

Contents:

Since BOINC 5.10.24 this message changed into:
Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks.

This is NOT an error message.

In general this is an informational message telling you that your system has (done) enough work from the one project or the multiple projects you are attached to.

Do not try to force BOINC into downloading work for other projects. You may well make it worse.
BOINC will switch the CPU availability between projects. When it has crunched 4 hours for one project, it will give those 4 hours back to the other project(s) you are attached to.

When you have just installed BOINC, with more than one project attached to it, it will in general (if left alone) take around 2 weeks for BOINC to learn about all your projects.

Setting a large queue size (more than 7 days), can take 4 weeks for BOINC to learn about all the work. Be patient!

-------------------------
It can also occur if one of the following applies:

1) First thing to check if you see this message is this:
Projects tab in BOINC Manager, check in the Status of the affected project that it doesn't say "Won't get new tasks" in its status.

If your project has this status, click on the project, then click on the "Allow new Tasks" button on the left hand side menu.

2) Check if your Network connection is available. In the activity menu bar, check if Network activity isn't set to Suspended.
 

Nvidia CUDA & ATI Stream (CAL) FAQ

FAQ: Nvidia CUDA & ATI Stream (CAL) FAQ
Title: Nvidia CUDA & ATI Stream (CAL) FAQ
Author: Jorden
Views: 151871
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 17/12/2008 18:12:48
Last Modified: 24/09/2012 12:29:08

Contents:

Warning!
Please read the whole FAQ first, to make sure you have all the details. Do follow the links (those blue lines) to other FAQs or to external sites for drivers and things like that. That way you don't have to ask in forums where particular parts go, such as that elusive cc_config.xml file.

Since a few people missed where the elusive cc_config.xml file comes from and where it goes, I've rewritten this FAQ to start with that information. The next person still missing the information is a dork. :-)

Using a cc_config.xml file.
In a lot of the help below I am pointing out you can use particular lines in the core client configuration, or cc_config.xml file.

By default BOINC does not come with a cc_config.xml file. You will have to make one yourself. It resides in your BOINC Data directory, whose path you can find in the BOINC start-up messages. This directory may be hidden.

* See the core client configuration FAQ for help on how to set up the cc_config.xml file.

* See the Big BOINC 6 FAQ for the default directory paths and help on how you can set up Windows so you can see hidden files and folders.

What is CUDA or CAL (Brook+)?
CUDA and CAL (Brook+), the next best thing since sliced bread... or so they want you to believe.

Both these versions are a method of doing calculations with the use of your videocard's GPU, or Graphics Processing Unit. CUDA is used by Nvidia GPUs only, while CAL is used by ATI/AMD GPUs only.

Inside the GPU there are multiple stream- or shader processors. While these are usually used to render 3D graphics in detail onto your monitor, they can also be used for doing other sorts of calculations.

That's what is being used on some of the projects running under BOINC. Using CUDA & CAL calculations will go much faster than on your CPU, since all the stream processors inside the GPU will attack the task at the same time, running all the calculations in parallel. This in contrast with how they normally run on your CPU, where one task runs on one CPU or core only, multi-threaded projects excluded.

While running work on your CPU(s) can already slow your computer down, imagine what will happen when you also run work on your GPU. It's already in use by your system to show you everything that happens on your screen, thus adding a load of work onto that, it can cause severe stability problems.

While different GPUs can be mixed used in computers, in general the work you get for projects cannot be exchanged between GPUs. Most projects use CUDA only, which cannot be done on ATI GPUs. Some projects use CAL only, which cannot be done on Nvidia GPUs.

I will be handling some of the problems you can come across, and possible solutions for them, in this FAQ.

Projects with CUDA
Albert@Home (Einstein test project) **
GPUGrid
Seti Beta *
Seti@Home *
Einstein@Home **
Milkyway@Home **
Collatz Conjecture **
Moo Wrapper **


Projects with ATI Stream (CAL)
Albert@Home (Einstein test project) **
Collatz Conjecture **
Milkyway@Home **
Moo Wrapper

* Windows only, Linux and Macintosh require 3rd party applications or are not available.
** Macintosh GPU apps available.

Absolute Minimum System Requirements
1. You will need at minimum BOINC 6.4.5 (or newer) (Windows, Linux and Macintosh).

1a. For ATI (CAL) support you need the 6.10 versions of BOINC. Get BOINC 6.10.17 from the download page.

2. You will need a CUDA capable nVidia video card with at least 256MB video RAM. For a list of CUDA capable GPUs, look at this list of cards.

2a. You will need a CAL capable ATI video card with at least 256MB video RAM. Compatible GPUs are the HD2xxx, 3xxx, 4xxx and above, or the ones on this list.

3. For 6.4.5 to 6.6.41 you will need at minimum nVidia CUDA 2.0 (177.35 and above) video card drivers.

3a. For 6.10 and later you will need at minimum nVidia CUDA 2.2 (185.85 drivers and above), but your best bet is to use the latest drivers available.
Note: The minimum memory requirement on the GPUs goes up to 384MB of video RAM from these drivers onwards.

If your present drivers are below this version, update first.
If your present drivers are below this and they're the last available for your hardware, you cannot update to 6.10; stay at the last 6.6.x version for your OS.

3b. For applications built with CAL 1.2 a minimum of Catalysts 8.12 are needed
For applications built with CAL 1.4 a minimum of Catalysts 9.3 are needed.
Check at the project (forums) which CAL version their applications are before installing these drivers!

4. When you are using a laptop and the above Nvidia drivers do not work on your system, plus the manufacturer of your laptop has not updated its drivers, you can first check Nvidia's laptop drivers to see if those work with your system. If they do not, then check Laptopvideo2Go, which seems better prepared.

5. If you are using a Macintosh computer, you need at minimum CUDA 2.3 drivers and OS X 10.5.2 (Leopard). You can get your drivers from the CUDA download site, choose Mac OS from the drop-down menu.

When you meet the above requirements and are ready to go, go attach to any of the projects that use a CUDA application at the moment. When you have done so, the application will download automatically.

My system slows down when I run CUDA or CAL. I can't work like this!
When your system runs CUDA or CAL tasks, the GPU is saturated with whatever task it is doing. A large portion of your video RAM is being used by this task as well. So of course things will slow down.

The GPU draws everything that you see on your monitor. If at the time it is busy with a lot of calculations on all its internal processors, it won't have time to draw the screen. 3D gaming will also try to saturate the GPU, so you cannot have both CUDA or CAL and the game occupy the same space at the same time.

Seti has at this time tasks that have a very low angle range (VLAR) which will slow down when they are being calculated on the GPU. This slowdown will also have its effect on your computer. A fix for this is forthcoming in a next version of the science application.

The official advice is:
- If you have a dedicated gaming rig, then do not run BOINC/CUDA/CAL at the same time you are playing your game, or only run it when you aren't gaming.
- When you love to watch DVDs or use a TV tuner, do not use BOINC/CUDA/CAL at the same time. This will impact your viewing experience. (stutters, slow-downs)
- When using a screen saver, remember that the GPU is used to render the screen saver's graphics. Just do not use a screen saver and turn off your monitor before you leave, or let it go to blank.

Ways around it?
First and foremost is to exit BOINC before you start gaming or doing your other GPU intensive thing.
BOINC Manager->File->Exit, check "stop running of science applications when exiting BOINC Manager" and click OK.
Restarting BOINC Manager will also restart the BOINC service (if you installed it that way).

Second, you can suspend BOINC before you start gaming or your other GPU intensive thing. (*)
BOINC Manager->Advanced view->Activity->Suspend.
To resume follow the same path and set it back to Run based on preferences.

Third, you can have a cc_config.xml in your BOINC Data directory that will suspend your BOINC (under Windows only, I'm afraid) automatically when any of the exclusive applications you told it to look out for is detected in main memory. (*)

To do so, set up the cc_config.xml file with the following options (example of my cc_config.xml):
Code:
<cc_config>
  <options>
     <exclusive_app>Speed.exe</exclusive_app>
     <exclusive_app>Crysis.exe</exclusive_app>
     <exclusive_app>FarCry.exe</exclusive_app>
     <exclusive_app>NFSHP2.exe</exclusive_app>
     <exclusive_app>FarCry2.exe</exclusive_app>
     <exclusive_app>Fallout3.exe</exclusive_app>
     <exclusive_app>RA3.exe</exclusive_app>
  </options>
</cc_config> 


Since BOINC 6.10.19, there is also the <exclusive_gpu_app> option, used in the same way as the <exclusive_app> option. The difference is that BOINC will then only suspend work being done on the GPU, for as long as the program defined is in memory. It will continue to do work on the CPUs.

Code:
<cc_config>
<options>
     <exclusive_gpu_app>Speed.exe</exclusive_gpu_app>
     <exclusive_gpu_app>Crysis.exe</exclusive_gpu_app>
     <exclusive_gpu_app>FarCry2.exe</exclusive_gpu_app>
</options>
</cc_config>


You can also combine the two options.

Code:
<cc_config>
<options>
     <exclusive_gpu_app>FarCry.exe</exclusive_gpu_app>
     <exclusive_app>Speed.exe</exclusive_app>
</options>
</cc_config>


You only need to tell what application name it needs to look out for, no need for the full path to the name. If you already have one, you can add the <options></options> part to your existing cc_config.xml file.

Watch out with launcher files. For example, Fallout 3 uses the Fallout 3 Launcher, which does not stay in memory after you launched the game. So do not use the launcher file as the exclusive app, but the game executable's name instead. I have tested this with the Oblivion launcher as well, here it is the other way around. If you add the Oblivion executable only, BOINC will not suspend. You will have to use the Oblivion Launcher name.

(*) There is a problem when you have your preferences set to Leave applications in memory while suspended. Any task still in the video card's RAM will stay there until you resume BOINC. Although it will not use your GPU, the amount of memory that a Seti CUDA tasks takes up (200MB+ of the VRAM) may still have impact on your other activities.

Note: BOINC 6.6 will unload the task from video memory when you suspend BOINC and the task has at least checkpointed once. Since BOINC 6.10.32, doing benchmarks will leave all applications in memory, this includes what's in the GPU's memory.

Can't I turn the damn thing off?
Yes, you can. E.g. in Seti, go to your Project preferences, edit them, take the check mark off of "Use NVIDIA GPU", save the changes. Then open BOINC Manager->Advanced view->Projects tab->select Seti->click Update.
(Of course if you're using the GPU on another project, change the preferences on and update BOINC for that project).

Some projects have a separate "Use ATI GPU" preference. Normally those with official ATI applications.

Any work that is still appointed to the GPU will still have to be done or you have to manually abort it. In the case of Seti CUDA work, this is all work appointed to the 6.08 application (BOINC Manager->Advanced view->Tasks tab, Application column). You will not receive new CUDA work, though.

Other projects have these preferences as well.

In BOINC 6.6 (and above) you have the option to deselect the GPU through your cc_config.xml file. In this case add <no_gpus>1</no_gpus> to the <options> section of the cc_config.xml file. You must exit and restart BOINC for this option to be of effect. A simple re-read of the config file won't disable the GPU.

Code:
<cc_config>
    <options>
        <no_gpus>1</no_gpus>
    </options>
</cc_config>


With BOINC 6.6.7 and above you can also go to your Seti computing preferences and state that you only want to use the GPU when the system is idle. This is the best situation to use CUDA in.

From BOINC 6.10.19 onwards, the client also has the --no_gpus command line switch. That way you can start the BOINC client in the following manner:

Code:
boinc.exe --no_gpus --detach

The extra line of --detach closes the command line window, but leaves the client running.

Seti advises that you only run CUDA when you are not doing anything else with the system.

Yesterday I used CUDA or CAL, but today when I start up BOINC it does not detect any GPUs/co-processors. When will you fix that?
This is not a BOINC problem, but something between the videocard drivers and Windows going wrong. It happens mostly on Vista and Windows 7 systems, where the driver does something illegal and the OS automatically uninstalls the driver, then reinstalls the previous OS supplied driver.

Although previous versions of BOINC would throw away any work in cache for the GPU, the latest version of BOINC (6.10.17 or above) will retain the work, until you either reinstall the drivers, or until the work times out by deadline.

I am using Remote Desktop to log in on my home-machine, but then BOINC does not detect a GPU. Can't you fix that?
This is not a BOINC problem. When using the Remote Desktop Procedure (RDP), you are using the drivers that come with the RDP. These only allow the RDP, not anything else fancy, so if you want that fixed, you'll have to yell at Microsoft. Good luck. :-)

BOINC 6.10.17 and above will stop work being done on the GPU when BOINC detects someone logging in through RDP. It will then put this work on hold until you log out of the system.

Where did the screen saver for the projects go to? All I get is the BOINC logo!
The screen saver uses the GPU to draw the OpenGL graphics on your monitor. CUDA is already using the GPU. When they would allow a screen saver at this moment, you have enormous slow downs and a higher possibility of errors. Which is why the Seti CUDA application does not come with a screen saver executable at this time. This may change in the future.

Although it has always been possible to run any screen saver together with CUDA or CAL, it is better to do this on videocards that have enough memory -- 1024MB and more.

Not all projects allow a screen saver program together with their CUDA application. The only one I know of that does so is the Einstein project. Ask other projects.

I have 4 GPUs and want to crunch on them only, leaving my CPUs free. Isn't that possible?
Yes, that is also possible, but only with BOINC 6.6 to BOINC 6.10.33 (*).
In this case, add <ncpus>0</ncpus> and <use_all_gpus>1</use_all_gpus> to the <options> section of your cc_config.xml file. Let BOINC re-read your config file and the CPUs are off and all GPUs are used. Do know that for the moment, one CPU will always be used to supply the GPU(s) with work. This is minimalistic of impact, though. About 4% per GPU and not on a constant basis. Only when tasks are swapped from disk to VRAM and back, will the CPU be used. At all other times the GPU is used.

Code:
<cc_config>
    <options>
        <ncpus>0</ncpus>
        <use_all_gpus>1</use_all_gpus>
    </options>
</cc_config>


A new option appeared in the Seti Project preferences, with which you can disable your CPU(s).
For this select:

Use Graphics Processing Unit (GPU) if available ON
Use Central Processing Unit (CPU) OFF

(*) Since BOINC 6.10.34, <ncpus>0</ncpus> again means that you disabled the <ncpus> setting. It no longer means you want to use zero CPUs, since this is counter-intuitive as all GPU applications use at least one CPU.

I have 2 GPUs in SLI, BOINC recognizes both but CUDA or CAL only crunches on one. What is up with that?
When you are using SLI, all the GPUs you have are seen as one GPU, producing one single output.

For CUDA: If you want to use the GPUs independently, you will need to disable SLI in the Nvidia Control Panel, then restart BOINC. The bridge between video cards can stay on.

Note: Since driver version 190.38, BOINC will recognize the GPUs as separate ones even if you are running in SLI mode.

For CAL: If you want to use the GPUs independently, you will need to disable SLI in the Catalyst Control Panel, then restart BOINC. The bridge between video cards can stay on.

OK, so now I disabled SLI and BOINC only recognizes one video card. What is up with that then?
Some people report that in order to have both video cards recognized and be able to use them, you can try to extend your desktop over all your videocards; if that doesn't work you need to have a monitor attached to each video card, or add a VGA dummy (requires soldering) to the VGA outlet of the other video card(s). This how-to needs no soldering.

Also set your cc_config.xml file to use the <use_all_gpus> option.

Code:
<cc_config>
    <options>
        <use_all_gpus>1</use_all_gpus>
    </options>
</cc_config>


How do I use only one of my multiple GPUs?
You can tell BOINC which GPU to ignore using the <ignore_cuda_dev>0|1|2|3</ignore_cuda_dev> and <ignore_ati_dev>0|1|2|3</ignore_ati_dev> flags in the <options> section of cc_config.xml

GPUs are counted per brand and from the first in your system to the last, while the first GPU of the same brand is designated GPU 0, the second GPU 1 etc.

So for example, you have a 3 GPU system, two Nvidia and one ATI. You only want BOINC to use the first Nvidia and the ATI, not the second Nvidia.

Code:
<cc_config>
    <options>
     <ignore_cuda_dev>1</ignore_cuda_dev>
    </options>
</cc_config>


The above code will take care of that. Put that cc_config.xml in your BOINC Data directory (or adapt it into an existing cc_config.xml file), then exit and restart BOINC.

If you want to ignore both the second Nvidia and the ATI, you use the following:

Code:
<cc_config>
    <options>
     <ignore_cuda_dev>1</ignore_cuda_dev>
     <ignore_ati_dev>0</ignore_ati_dev>
    </options>
</cc_config>


In BOINC Manager it shows that the CPU time for a CUDA task is mere seconds, but the task runs for hours. Why is this?
BOINC does not follow GPU time yet. That's planned for a future version.
For now it will only count CPU time. For CUDA and CAL this means the time it takes the CPU to transfer the task from disk into the video RAM and when the task is done, transferring it back.

The GPU will do the whole calculating of the CUDA or CAL task.

I have made my own BOINC Manager, based on BOINC 6.6, which shows both the CPU Time and the Wall-clock time columns in the Tasks tab. It's for Windows only and works with BOINC versions as far down as 6.4.5 (so on all versions capable of CUDA). You can download it in 7-Zip format from my Microsoft Skydrive.

Just unzip/unRAR to your BOINC directory and run it as is. Since it's called boincmgr76.exe it won't overwrite your original BOINC Manager. I am not supplying boinc.dll with it so not to break your existing BOINC version, but for the older versions of BOINC 6 it needs the sqlite3.dll file that's included.

A newer and updated version, built against the latest available 6.10 GUI is now also available, from here (zip compressed) and here (7-zip compressed).

A Linux version of the same file is available from Kathryn's Skydrive. Her comments:

"I've built the 32 bit Linux version of this. It's simply called boincmgr. I have no idea if it'll run on anything but my machine. I've never built binaries for distribution. It was compiled with the --enable-unicode flag for wxWidgets. My suggestion is if you want to try it, download it, check the md5sum (4fa7a16a56dadb2e26a61a81b97591ca) and then run ldd on it.

When I use CUDA or CAL, everything slows down. In Task Manager I see Explorer.exe is using up a lot of CPU cycles. Why is it doing that?
We don't know. Other than the normal slow-down caused by you using the GPU for other things than drawing the desktop, this is neither BOINC, nor the science application that is causing explorer.exe to take up CPU cycles. It is more likely that it is something local on your system.

To help out the people that are trying to help you, run FileMon and Process Explorer to see what is happening on your system. Post logs from those programs.

For some people a simple reboot made it go away.

I got a report in that updating to the CUDA 191.07 drivers may fix this problem, although this person also updated his motherboard chipset drivers. So if in doubt, try either one.

When I ran BOINC in XP as a service, it would detect the GPU. Now I have Windows Vista or Windows 7, when BOINC is installed as a service it won't detect the GPU. When will you fix that?
It is not something for BOINC to fix. This is a Microsoft security feature, where it stops your user account from running in the same session as your drivers and services are run from.

If it has to be fixed, it will have to come from Microsoft, or the GPU driver manufacturers have to find a way to run their drivers without using them as a service installation.

There's a document on this at Session 0 isolation (Word document, can be loaded in Open Office Writer, not in Wordpad).

An excerpt:
Quote:
In Microsoft® Windows® XP, Microsoft Windows Server™ 2003, and earlier versions of the Windows operating system, all services run in the same session as the first user who logs on to the console. This session is called Session 0. Running services and user applications together in Session 0 poses a security risk because services run at elevated privilege and therefore are targets for malicious agents who are looking for a way to elevate their own privilege level.

The Microsoft Windows Vista™ operating system mitigates this security risk by isolating services in Session 0 and making Session 0 noninteractive. In Windows Vista, only system processes and services run in Session 0. The first user logs on to Session 1, and subsequent users log on to subsequent sessions. This means that services never run in the same session as users’ applications and are therefore protected from attacks that originate in application code.

What Is Affected
Any applications or drivers that are installed as a service are affected by the following implications. Some drivers are loaded within operating system services or processes that are running in Session 0, and those drivers are also affected by the implications of the Session 0 changes.


What about the Macintosh and Linux versions, where are they?
CUDA finally works correctly with Mac OS 10.6.3

But as ever, if you upgrade to OS 10.6.3, 2 issues may arise:

* The upgrade may delete your login item for BOINC Manager. If this happens, BOINC will not launch automatically when you log in or restart your Mac. Just run the BOINC installer again to fix this.
* If you are running CUDA tasks, you must upgrade to version 3.0 of the CUDA drivers, which you can download here.

As far as the Linux version is concerned, BOINC 6.10.17 has CUDA and CAL support. If you run into problems and your GPU is one of the newer ones, your best run CUDA with the 185.85 drivers. I have had reports that this driver doesn't work with the Nvidia GTX 280 and above versions, though. You may want to check what Nvidia says about that.

When will ATI GPUs (or any other non-Nvidia brand GPUs) be detected?
BOINC 6.10.17 and above have ATI detection support, though this doesn't say that projects will then immediately have applications that run on your card. The biggest problem with ATI at the moment is that they do not give any support on porting over project's science applications to work with their Stream SDK. People will have to figure this out for themselves and many project administrators just do not have the time or money to learn a whole new programming interface (Brook).

However, not all is bad. On the Milkyway project one of the users has made an ATI application. It works independently of BOINC, so you do not need BOINC 6.4.5 to get it to work. Older versions will work as well. Check the threads there for more information, or go the the zslip thread for the download link.

The Collatz Conjecture project has also adopted the use of the ATI GPU.

Now really, when will BOINC support OpenCL?
OpenCL support has been in BOINC ever since it started detecting GPUs. Further hardware support should come in the future, but this has to do with what drivers you install and the accompanying OpenCL.dll -- too technical to go into here.

For minimum system requirements look:
- Here for ATI. For the OpenCL FAQ, see here.

I am continuously getting memory errors on tasks I run. A reboot didn't help. What should I do next?
Test GPU memory, with either of these apps, or both:

MemtestG80. Copy the cudart.dll and cufft.dll files from you setiathome.berkeley.edu folder to the folder where you installed MemtestG80file. You will need the old DLLs from before CUDA 2.3, cufft.dll file size = 1148kB, cudart.dll file size = 275 kB.

Run it from a command-line window (Start->Run, type cmd, click OK. In the command line window use DOS commands to navigate to the correct directory

Code:
e.g. when installed in C:\cudatest
cd\ {Enter}
cd\cudatest {Enter}
memtestg80 {Enter}

You need to enter the graphics card memory speed and GPU core speed. If you don't know what they are you can get and run GPU-Z to find out.

OCCT Perestroika 3.0.1, choose the CUDA MemTest tool in the \bin\CUDAMemTest\ directory.

Post the results in your project forum of choice.
 

OpenCL

FAQ: OpenCL
Title: OpenCL
Author: Jorden
Views: 73945
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 05/12/2009 04:36:48
Last Modified: 11/04/2012 21:20:21

Contents:

What is OpenCL?

Since the success of CUDA & Stream/CAL, everyone with a GPU has been waiting with bated breath for the next best thing: OpenCL, or Open Computing Language.

While OpenCL can be compared to CUDA or Stream/CAL, in that it will runs a program on the CPU that tells the GPU to do all the calculations, it can also be different, by using all computational hardware in your computer. This isn't yet supported in BOINC, maybe with a future version.

This means that it'll run on all your CPUs, all your GPUs and whatever else you may have lurking inside your box that does independent calculations, such as Network Processing Units.

Both Nvidia and ATI/AMD have by now released drivers for the most popular GPUs, to have them support OpenCL. Nvidia runs behind on driver maturity though. It'll be hit and miss for their drivers for a while yet.

The new BOINC 7 (tested as 6.13) has OpenCL support for ATI/AMD and Nvidia GPUs only.


Supported operating systems?

- Windows XP and above.
- Linux openSUSE™ 11.2 (32-bit/64-bit), Ubuntu® 9.10 (32-bit/64-bit), Red Hat® Enterprise Linux® 5.4 (32-bit/64-bit)
- Macintosh OS X 10.6 (Snow Leopard) and above.


Supported GPUs.

Nvidia: According to their website, all CUDA capable GPUs since 2006 have OpenCL support. I won't dispute them.

ATI/AMD: Essentially all GPUs from the 4350 onwards have some sort of OpenCL support. For a comprehensive list, check their SDK page.

Intel: The Intel GPU built into the Sandy Bridge CPU will eventually have OpenCL support. All Intel GPUs hereafter will have OpenCL support.

Supported CPUs.

Any x86 and x86-64 based CPU with at least SSE3 will work.


Other processors?

According to Khronos, OpenCL is developed and supported by: 3DLABS, Activision Blizzard, AMD, Apple, ARM, Broadcom, Codeplay, Electronic Arts, Ericsson, Freescale, Fujitsu, GE, Graphic Remedy, HI, IBM, Intel, Imagination Technologies, Los Alamos National Laboratory, Motorola, Movidius, Nokia, NVIDIA, Petapath, QNX, Qualcomm, RapidMind, Samsung, Seaweed, S3, ST Microelectronics, Takumi, Texas Instruments, Toshiba and Vivante.

So anything these developers produce that has a processing unit in your PC is an option.

Projects
Albert@Home (Einstein test project) **
Seti@Home * (through 3rd party Lunatics apps)
Seti Beta *
Milkyway@Home **
Collatz Conjecture **
POEM

* Windows only, Linux and Macintosh require 3rd party applications or are not available.
** Macintosh GPU apps available.

Is OpenCL comparable to CUDA or CAL?

Not completely. With the former technologies, an application would run on the CPU which would translate whatever was to do to kernels for the shader processors or stream processors in the GPU to work with. At that time the GPU wouldn't be able to do much of anything else, including showing you graphics output in real time, as the GPU was busy doing these intricate calculations. Using graphics, streaming video, a screen saver? until recently all that wasn't possible on CUDA/Brook+, although newer GPUs and more memory on the cards make it now possible to do just that.

OpenCL is more comparable to OpenGL (the Open Graphics Language), as it can not only do intricate calculations, but also still show you your desktop in real time, show streaming video and show real-time calculated graphics at the same time.


Are there BOINC projects yet that have an application?
A couple of projects are testing OpenCL applications, some others have them already in full production.

- Seti@Home is testing OpenCL applications for Astropulse and Multibeam.
For more info, search their Number Crunching forums for mention of the Lunatics optimized applications. (Until Seti v7 apps come out).
- Einstein has a test project, called Albert@Home that tests their BRP4 ATI OpenCL application on Windows, Macintosh and Linux!
- Primegrid is testing an ATI OpenCL application on Windows, Linux and Macintosh (Proth Prime Search (Sieve)).
- Milkyway@Home has released all their favorite applications in OpenCL 1.1 format.
- Collatz Conjecture has an OpenCL application for Mac OS X 10.5 or later and are beta testing apps for Windows and Linux.


Do I need to install anything to be able to run OpenCL?

- In the case of Nvidia GPUs, you'll need an up-to-date driver.

- In the case of ATI/AMD GPUs, you'll need an up-to-date APP driver.
In the case that your GPU cannot support the APP driver, for whatever reason, you'll need to install the ATI Stream SDK for Windows and Linux, since it contains specific libraries that are needed. You will also require Catalysts 10.4 or above. The SDK page will tell you which Catalysts are required for the latest SDK.

So far:
- SDK v2.1 needed 10.4
- SDK v2.2 needed 10.7
- SDK v2.3 needed 10.9
- SDK v2.4 needed 11.3/11/4
- SDK v2.5 needed 11.7

You will need to install this SDK as AMD does not allow that projects distribute the needed libraries on their own yet.

Macintosh OS X 10.6 has these libraries built in.


Are there any tools or demos I can use to test with?

Of course there are.

There is one very cool Tool, called GPU Caps Viewer with which you can not only test the OpenGL part of your GPU, but also the OpenCL part of your GPU and CPU. Various demos are included in the application.

On top of that it gives a lot of information about your GPU and CPU, more than CPUZ and GPUZ can give together! For instance, it shows the actual OpenCL compute capability of your hardware.


Where can I read up on this technology?

Start on Guru3D's site.
Further information (more technical) can be found on:
- AMD
- Nvidia
- Khronos
 

RAM requirements for BOINC.

FAQ: RAM requirements for BOINC.
Title: RAM requirements for BOINC.
Author: Jorden/Honza
Views: 98890
Category: 03. BOINC Client Software Questions and Answers
Available in: English Dutch
Created: 10/04/2008 00:31:50
Last Modified: 03/03/2010 22:26:40

Contents:

Honza has this table of RAM requirements for BOINC per project. (Not all projects featured yet)



Legend:
RAM means maximum RAM usage without GUI.
L is for Linux.
M is for MacOS.
"6" means that Linux sends 64-bit application; where mark is missing it *should* mean there is no application for L or M available. All other numbers apply to Windows application.

COLUMNS EXPLANATION:
Project name - may include subprojects (CPDN Slab models, Sulphur cycle model or Coupled model) or some versions of project (SETI official/unoptimalized, optimalized, Enhanced application).
no GUI - RAM usage with no GUI (graphic open Windows not opened). It doesn't says if application has GUI or doesn't; albeit most projects do.

Internet traffic
Some users have slow (dial-up) or limited bandwidth internet connection; internet traffic generated by BOINC projects may be an issue. 3 columns try to delineate demands of each project. Note that when running several projects, you need to average each upon your resource share.
1st WU - download demands on first WU which includes: application + project files (CPDN model inputs, life-science protein database etc) and finally one WU. Usually, there is no need to re-download whole again unless (i) new application is released, (ii) new input files for WUs are deployed, (iii) project reset.
1 WU down/up - first number enumerate size of the WU for download (data for analysis); number after slash is the usual size of WU for upload (tasks size).
MB/month - when running project on 24/7 basis, 100% dedicated on dual-cored CPU (be it reference machine of AMD or Intel, whatever generates more tasks - see below), traffic may considerably grows and make it almost impossible to participate for some users. In other words - users provide idle CPU cycles and HD space (see next) but also internet bandwidth.

HD space
Each project needs it's application, downloaded WU, some temporary files and intermediate tasks and it occupies HD space. [CPDN Slab and SC models were compresed and stored on local disk for option of further analysis - see the second number after slash]. Total HD space depends on how many WU are you running (see max size) and how many WU are ready to crunch (see WU down).

Times to completed 1 WU
This is not a bechmark; it gives an average numbers on reference machines. Also, numbers do change on other HW specification such as RAM speed, FSB, cache size etc. TO make numbers more accurate would only mean to make table several times larger.
AMD - reference machine is AMD64 3000+ or X2 3800+ running 2 WUs.
Intel - Pentium 4[i] at 3.6 GHz with HyperThreading on and running 2 WUs tu utilitize extra ~20% of performance.
[i]Intel - Pentium D 820
; a dual-cored CPU running 2 WUs.

Work Units (WU)
Deadline - time limit to report tasks since their download. Smaller numbers tends to give credit faster, longer period may be suitable for dial-up/non-permanent internet connections. There are much more consequences with scheduler state, possible WU cache etc, but those topics are covered elsewhere.
Quota - each project has a maximum daily WU quota per CPU (limit on how many WU can be downloaded). This mechanism prevents trashing large portion of WUs on project server from unstable computers (or project application). Note, that this number decrease when host becomes less reliable (invalid WUs) and gets to it's maximum after issue is solved.
Quorum - most projects use a redundancy to ensure that tasks are reliable; quorum is the number of tasks need in order to validate WU. Until this number is reached, credit is pending; it is granted after validation on server side.

Application/WU version
Most project are in constant development and new version of application may occur. This may change other parameters of project, such as memory usage, application size, times to complete etc.

Credit - do I need to say something there? Science matters.
 

Science applications continue running when I exit BOINC Manager.

FAQ: Science applications continue running when I exit BOINC Manager.
Title: Science applications continue running when I exit BOINC Manager.
Author: Jorden
Views: 70200
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 16/06/2008 18:02:15
Last Modified: 06/05/2010 15:38:34

Contents:

When exiting BOINC Manager you can find that the science applications continue to run. This is quite normal with BOINC 6.4 and above, even if you do not have BOINC installed as a service.

The explanation behind this is that BOINC consists of two main parts, a client (seen as boinc.exe in Windows Task Manager) and the graphical part that you do everything from, called BOINC Manager (seen as boincmgr.exe in Windows Task Manager).

Exiting BOINC Manager does not necessarily shut down the client and the science applications. Which is where the exit dialog comes into play. Here you can tell BOINC what to do, just close down BOINC Manager (the graphical part) or close everything down.


File->Exit in BOINC Manager gets you to:



Make sure that the first option is checked and if you want to see this dialog again in the future, make sure the the second option is not checked.

Have you ever made the mistake to tell the exit dialog not to show up again (second option checked), then you can reset this in Advanced->Options:


(BOINC 6.4)


(BOINC 6.6 and above)

Make sure the second option is checked, the wording can be slightly different between BOINC versions.
 

Setting percentage of CPU Time, how does it work? (CPU throttling)

FAQ: Setting percentage of CPU Time, how does it work? (CPU throttling)
Title: Setting percentage of CPU Time, how does it work? (CPU throttling)
Author: Jorden
Views: 92152
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German English
Created: 06/10/2007 02:37:48
Last Modified: 16/04/2010 16:55:47

Contents:

A new feature that comes with the latest versions of BOINC (alpha/beta versions) is the CPU Usage percentage. You will need Boinc 5.6.5 or higher for this feature to work. Versions before it will not be compliant.

How does it work?
Because BOINC does not use the Windows registry (other than for storing the positions of the graphics for the Boinc Manager GUI), plus because it is a multi platform program, it cannot use Windows specific timing APIs as other 3rd party programs such as Threadmaster use.

What it does is pause the crunching for 1 or more seconds, depending on what percentage of use you set it to. Below is a timing table that I figured out:

100%: it runs all the time.
90%: 9 second run, 1 second idle.
80%: 4 second run, 1 second idle.
70%: 3 second run, 1 second idle, 2 second run, 1 second idle, 3 second run, etc.
60%: 1 second run, 1 second idle, 2 second run, 1 second idle, 1 second run, etc.
50%: 1 second run, 1 second idle, 1 second run, 1 second idle, etc.
40%: 1 second run, 1 second idle, 1 second run, 2 seconds idle, 1 second run, etc.
30%: 1 second run, 1 second idle, 1 second run, 3 seconds idle, 1 second run, 2 seconds idle, etc.
20%: 1 second run, 4 seconds idle, 1 second run, 4 seconds idle, etc.
10%: 1 second run, 9 seconds idle.
0%: It's paused.

 

Simple explanation of the new work scheduler (version 5.8 and above).

FAQ: Simple explanation of the new work scheduler (version 5.8 and above).
Title: Simple explanation of the new work scheduler (version 5.8 and above).
Author: Jorden / John
Views: 84544
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish English
Created: 20/09/2007 21:41:01
Last Modified: 03/07/2008 02:20:39

Contents:

First, the computation deadline is: the report deadline – (queue size (or connect every X days) + project switch interval (switch projects every X minutes) + Safety Margin).

Safety Margin is either one day or 0. In the latest versions this is 0.

The round robin simulator is used to determine if any task would be reported late based on the remaining CPU time left for each task and the resource shares for the tasks from each project that has work on the client. (A low resource share project will quite often be in deadline trouble when it has work on the client).

For each task that is in deadline trouble, start the earliest deadline task that is available in that project up to the limit of CPUs. These are "High Priority" tasks.

If there are no more available CPUs, then do not continue scheduling tasks.

For each remaining CPU, schedule a task from the project with the highest short term debt. Internally track the fact that a task was scheduled from this project and deduct the task scheduling period. (this means if there are two projects with nearly identical STDs, a task will be started from each if there are enough available CPUs.

Once the schedule has been set, the enforcement occurs.

The tasks that are scheduled as high priority are scheduled immediately removing the tasks that have checkpointed most recently from memory.

For all other CPUs, wait until the task that is being un-scheduled has reached the first checkpoint after it has gotten project switch interval wall time. The task that replaces it is the one from the project with the highest Short Term Debt.

If the sum of RAM used by running tasks exceeds the amount of RAM specified, stop tasks until the amount of RAM used is below the specified amount. Note that this can leave CPUs idle.

For a lot more information on the new work scheduler, or for the technically minded among you reading this, I gladly point to the official write up.
 

Suspending computation - CPU usage is too high / CPU is busy

FAQ: Suspending computation - CPU usage is too high / CPU is busy
Title: Suspending computation - CPU usage is too high / CPU is busy
Author: Jorden
Views: 73441
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 16/04/2010 16:52:51
Last Modified: 19/10/2011 23:33:15

Contents:

This feature isn't for everyone who has been using BOINC for ages and are running it 24/7 without looking at it much.

It's built in for completely new people, people who were complaining that despite BOINC's applications running on the lowest possible priority, it taking up CPU cycles that would slow down their computer.

These people would complain about that, uninstall, leave and tell other potential crunchers negative things about BOINC. It's added to help those people, for if they come back, to see that even they are listened to.

You can easily disable the function by setting its value to zero either in BOINC Manager or at the project's computing preferences web-site. Until all projects have updated their web-code, the option may not be available through their global preferences, so check your other projects, or look at this post in the BOINC forums for which projects have updated their web-code by now.

One thing that can cause this message to show is, funnily enough, the BOINC screen saver. Because it runs through an external program, it's also seen as a non-BOINC program. This problem will be fixed in BOINC 6.12, though.

Global preferences
If you do not want to use it through the override preferences, change your Global preferences (e.g. Seti computing preferences) for the line of Suspend work if CPU usage is above 25% to 0 (zero), save the changes to the web site, then open BOINC Manager->Advanced view->Tasks tab->Select Seti->Click Update.

BOINC Advanced preferences
Open BOINC Manager->Advanced view->Advanced->Preferences->change the line While processor usage is less than 25 percent to 0 percent (zero)->click OK.

This will enable the BOINC override preferences (as long as BOINC is set to run based on preferences) for this computer only.
 

The anonymous platform (app_info.xml), what does it do? How to properly get rid of it?

FAQ: The anonymous platform (app_info.xml), what does it do? How to properly get rid of it?
Title: The anonymous platform (app_info.xml), what does it do? How to properly get rid of it?
Author: Jorden
Views: 74657
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 09/10/2009 01:24:24
Last Modified: 27/06/2011 23:55:42

Contents:

What is it? What does it do?
Through the anonymous platform file, or app_info.xml file, you tell BOINC which downloaded or self-built applications and libraries it should use and to ignore anything that it is/was sent by the project.

This is very useful to use when the project does not have their own application for your platform OS. You can then build your own (if their source code is available) and use that instead of waiting for the project to come up with the goods.

Where do they go?
The app_info.xml file and all the applications and other files pointed out in that app_info.xml file should go into the \BOINC\Projects\%project_dir%\ directory of the project you want to use these files on. BOINC needs to be restarted for the changes to take effect.

I lost all my work in progress after I added an enhanced application.
Work on your computer is registered against the present application version on your system. If the app_info.xml file does not tell which older applications it substitutes for, BOINC will throw away all the work for the older application, as it is told to only use the newer application.

How do I get rid of it, so I can run the project's application again? / I get a message that I should remove my app_info.xml file, how do I do that?
We will delete the anonymous platform file and then reset the project. Resetting the project will delete all applications, all work in progress, to be uploaded and reported.

If you still have work for the old application that you want to finish, upload & report, consider setting the project to No New Tasks through BOINC Manager. Then run your cache empty, before following the below steps.

I will show how to do it in Windows only, for now.

- Before all, exit BOINC. Usually BOINC Manager->File->Exit, check "quit running science application" on the exit dialog and click OK).
- Navigate to your BOINC Data directory. When you restart BOINC, you should see in one of the first lines where that is on your system.
-- The data directory may be hidden. In that case either set Windows Explorer to show hidden files and folders, or just type the path directly in Windows Explorer.
- Click on the Projects folder icon.
- Click on the project's folder icon.
- Find and delete the app_info.xml file.
- Restart BOINC. Usually Start->Programs->BOINC->BOINC Manager.
- In BOINC Manager go Advanced view->Projects tab->Select the project you just removed the app_info.xml file for->Click Reset, confirm you want to reset the project.
- If you set the project to No New Tasks, set it back to Allow New Tasks.

By resetting the project we clear all remnants of the anonymous platform files that are still in the client_state.xml file and other files. BOINC will download all the project specific applications again, for as far as they are available for your platform.

* If you do not delete the app_info.xml file, and do a reset, all you do then is throw away all your current work.
* If you delete the app_info.xml file but do not reset the project, the entries in the client_state.xml file about the enhanced application will:
- cause BOINC to look for that file and not find it;
- delete all your present work in progress;
- possibly try to download the enhanced application from the project's site;
- give you a lot of (strange) warning messages in your Messages tab/Event Log;
- cause BOINC to stop downloading work for that project.

Are there any examples of these app_info.xml files?
Sure, below is an example of what the app_info.xml file for the Seti Enhanced and Astropulse Optimized applications can look like.

Code:
<app_info> 
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>AK_v8b_win_SSE2.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>528</version_num>
        <file_ref>
           <file_name>AK_v8b_win_SSE2.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>


This far we tell which application to use and which older application we substitute for. We then continue with the lines below:

Code:
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
        <file_ref>
         <file_name>AK_v8b_win_SSE2.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>


In here we tell specifically what application we substitute with.
We also tell BOINC that we want to use a different application for its Astropulse work:

Code:
    <app>
        <name>astropulse_v5</name>
    </app>
    <file_info>
        <name>ap_5.03r112_SSE.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v5</app_name>
        <version_num>503</version_num>
        <file_ref>
            <file_name>ap_5.03r112_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.05r168_SSE.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
        <file_ref>
            <file_name>ap_5.05r168_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>    
</app_info>


More information and options to use in the app_info.xml file can be found in the article in the BOINC Wiki (Advanced Users).
 

What does preempted/waiting mean?

FAQ: What does preempted/waiting mean?
Title: What does preempted/waiting mean?
Author: Jorden
Views: 84470
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German English Dutch
Created: 07/01/2007 20:44:23
Last Modified: 07/01/2007 20:44:23

Contents:

Simply said, preempted (BOINC v5.8.0 and earlier) or waiting (BOINC v5.8.1 or later) means paused.

When you have multiple projects attached to BOINC and at least 2 of those projects have work, you will see that BOINC switches its crunching between those two projects. The tasks BOINC is currently working on show as Running, while the ones it was working on before show as preempted or waiting.

It is done this way to give equal CPU time to all projects, set in accordance with your resources (set through the project's preferences) and with the amount of time until your tasks reach their deadline.
 

What is Ready to report?

FAQ: What is Ready to report?
Title: What is Ready to report?
Author: Jorden
Views: 84553
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German English
Created: 28/04/2008 21:52:19
Last Modified: 18/04/2012 15:12:50

Contents:

When you're done with a task in BOINC, it uploads the data that is has collected to a directory on the project's server. Then a notice has to be sent to the database that you have finished this task with whatever outcome you had, be it that you finished it correctly, had an error or aborted it.

This notice is the "ready to report" part.
BOINC will do this automatically in 24 hours, but if you can't wait that long, open BOINC Manager, Advanced view, Projects tab, select the project the task is from and press the Update button. That reports the tasks that are ready to report immediately.

Completed work is reported at the first of:

1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message.
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set.
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)
 

Where can I download BOINC?

FAQ: Where can I download BOINC?
Title: Where can I download BOINC?
Author: Jorden
Views: 84173
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish German English
Created: 29/01/2007 17:15:00
Last Modified: 29/01/2007 17:15:00

Contents:

The recommended version for your computer and operating system can be downloaded straight from the download page. The page detects what computer/OS you have and give you the latest recommended version.

If you feel more adventurous and want to test an Alpha version of the software, go to the Download All versions page. Here you can get the latest versions for your OS.

Do know that Alpha versions are unstable. If you want to help test it, post any problems you have with this software on the BOINC Alpha email list. This list needs registration. Also see the Alpha site for other instructions.

You can also post problems with the software on the BOINC forums.
 

Why does the "to completion time" go up?

FAQ: Why does the "to completion time" go up?
Title: Why does the "to completion time" go up?
Author: Jorden
Views: 72019
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 08/02/2010 17:44:33
Last Modified: 08/02/2010 17:44:33

Contents:

People who have only just installed BOINC will often notice that the "to completion time" on tasks will go up, rather than down. This happens because your computer hasn't done anything for the affected project yet, BOINC hasn't had time yet to learn how long tasks take.

The "to completion time" is an estimate. Depending on the speed of your computer's hardware, the actual task will take less or more time than this estimate. No project can give out exact time frames for tasks, as there's no hardware configuration out there that's exactly the same as any other.

BOINC has code included with which it will learn how long tasks take in general, called the (Task) Duration Correction Factor. During the course of a couple of tasks, BOINC will learn how long they really take and more correctly show the estimated run-time by increasing or decreasing this DCF.

What can throw off BOINC's corrected estimate?
1. Far different run-time length of tasks on the same project and same science application.
2. A lot of different science applications with different tasks.
3. Using the GPU mixed with CPUs.
4. A change in the project's estimate on task run-time.
5. A change in hardware on your computer (CPU or GPU or both).
 

Windows Installer error - Internal error 2755 .1601

FAQ: Windows Installer error - Internal error 2755 .1601
Title: Windows Installer error - Internal error 2755 .1601
Author: Jorden
Views: 82917
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 29/06/2008 00:57:22
Last Modified: 29/06/2008 01:01:03

Contents:

Internal error 2755 .1601 points towards the Installer Service not being registered, as David said. It can also have as cause that your Windows Installer is outdated.

Make sure that your Windows Installer is at least version 3.1
It's called msiexec.exe and you can find it in your Windows\system32\ directory. Right click it and check its version number.

If it isn't 3.1, then you can download this version from Microsoft's pages, here. This version needs Windows 2000 with Service Pack 3 or later, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2 and Windows Server 2003.

If you have an older Windows version (98/SE/ME), you need at minimum Windows Installer version 2.0, which you can get from here.

It's also possible that your installer is corrupt. To fix this, follow these steps (Windows 2000 or above only):
1. Click START, and then click RUN.
2. In the OPEN box, Type msiexec /unreg, and then click OK
3. When this process is complete, click START, and then click RUN.
4. In the OPEN box, type msiexec /regserver, and then click OK.

Lastly, if you have at least Windows 2000 or above, go to your services applet (Start->Run, type services.msc and click OK) and check that your Windows Installer service is not disabled. By default, it should be set to Manual, not running.
 

Windows Installer error 1327: Invalid drive letter

FAQ: Windows Installer error 1327: Invalid drive letter
Title: Windows Installer error 1327: Invalid drive letter
Author: Jorden
Views: 73321
Category: 03. BOINC Client Software Questions and Answers
Available in: English
Created: 17/12/2009 14:13:00
Last Modified: 17/12/2009 14:13:24

Contents:

When you receive Error 1327: Invalid drive X: (where X: is you drive letter), try the following:

Quote:
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. In Registry Editor, locate the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
4. In the right pane, note the values in the Data field of each entry. If any value contains a drive that is not correct for your computer, right-click the entry, type c:\my documents in the Value data box, and then click OK.
5. Repeat step 4 for each entry whose Data value contains an incorrect drive.
6. Repeat steps 3 through 5 for each of the following registry keys:
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
* HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
* HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
* HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
7. Close Registry Editor.

You should now be able to start the BOINC installer and run it without problems.
 

Windows Installer Error 1706: Setup cannot find the required files / 1714: older version cannot be removed / BOINC.msi cannot be found / The feature you are trying to use is on a network resource that is unavailable / Error 1325. is not a valid short name

FAQ: Windows Installer Error 1706: Setup cannot find the required files / 1714: older version cannot be removed / BOINC.msi cannot be found / The feature you are trying to use is on a network resource that is unavailable / Error 1325. is not a valid short name
Title: Windows Installer Error 1706: Setup cannot find the required files / 1714: older version cannot be removed / BOINC.msi cannot be found / The feature you are trying to use is on a network resource that is unavailable / Error 1325. is not a valid short name
Author: Jorden
Views: 114183
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish English
Created: 19/04/2007 22:02:06
Last Modified: 26/11/2013 04:09:44

Contents:

Note: These errors occur because Windows has lost its internal path to the correct BOINC.MSI installer file. It's really a Windows problem, not so much a BOINC problem. No need to complain that BOINC needs to fix this, as BOINC cannot fix problems that are made by Windows!

It can happen that you to run into any of these errors when trying to install BOINC:

Error 1706. Setup cannot find the required files

or

C:\WINDOWS\Downloaded Installations\{DF85BFC4-9509-4AA9-824A-5C6057FA8459}\BOINC.msi cannot be found.

or

"The feature you are trying to use is on a network resource that is unavailable".

or

Error 1714: older version cannot be removed

or

Error: Configuration data for this product is corrupt

The reason for this error is that the old BOINC.msi (Microsoft Installation file) is corrupt for whatever reason. This should be easy to fix.

Error 1325. XXX is not a valid short name.

STEP 1.

When your Windows version cannot find the old MSI file, you need to reinstall the old version of BOINC that you had before you started the upgrade, and choose to repair the installation. For this you need the old BOINC version installation file. If you no longer have it, take a look at The BOINC Archive , which holds all present and older BOINC versions.

Usually you can do the repair install, then immediately install the latest version of BOINC on top of the old version. This won't be possible with BOINC 4.19 and newer versions. BOINC 4.19 does need to be uninstalled through Add/Remove Programs.
---------------

STEP 2.
Since the Windows Installer Cleanup Utility was discontinued by Windows, as it is quite powerful to use and with misuse you can wreck your Windows... they'd rather that you use their Program Install and Uninstall.


Now, if that does not work, then do use the WICUU:
Download the Windows Installer Cleanup Utility.

Run that on your computer.
The corrupt BOINC version shows up as either BOINC.msi or as a corrupt icon .msi (it'll be the top most option). Click on it to select it, then click Remove and Exit. You will need to reboot your computer now.

Then install the new version of BOINC. It should now work.

(Warning: Leave all other .msi files as they are, as else you have problems uninstalling other programs! )

(This version of the Windows Installer CleanUp Utility works correctly in all 64-bit versions of Microsoft Windows.)
--------------

STEP 3.

In case it is a BOINC 6.x.x version that went corrupt for whatever reason, do take a look at these steps on what you will need to remove manually to get rid of the older version.

The default directory where BOINC will install its executables into is:
Windows 98/SE/ME: C:\Windows\All Users\BOINC\ or C:\Windows\Profiles\All Users\BOINC\
Windows 2000/XP: C:\Documents and Settings\All Users\Application Data\BOINC\ (this may be a hidden directory)
Windows Vista: C:\ProgramData\BOINC\     (this is a hidden directory)
---------------

STEP 4.

When that doesn't work, try to uninstall BOINC through Add/Remove Programs. It's well possible you run into the same difficulties.
In this case, make sure you exited BOINC completely (no parts of it running).

Go to Start->Search->All files and folders->type boinc.msi in the search option and click Search. All the BOINC.MSI files that can be found will be shown. Select them all and delete them.

Go to Start->Run->type regedit and click OK.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Space Sciences Laboratory, U.C. Berkeley and delete this key.

Then try to install the new BOINC. If you use different than default installation paths, make sure to change them again in the installer.
---------------
When that doesn't work, or you continually have the following error: "Error: Configuration data for this product is corrupt", then follow these steps.

STEP 5 (Advanced Users -- Warning: We're going to edit the registry).

The next entry is for ADVANCED Users only.
It will deal with using the registry and manually deleting entries there. If you do not feel at ease doing this, then do NOT do it! I will not take responsibility for you breaking your own Windows due to editing other keys than I told you to edit. Also, make a backup of your registry prior to fiddling with it!

1. Open regedit by going to Start > Run and typing 'regedit'. Click OK.
1a. Alternatively on Windows Vista and 7, Start->type regedit in search->double click regedit.exe
2. Confirm that we're going to use regedit.
3. Click Edit in the top menu.
4. Click Find.
5. Type in BOINC.msi (with BOINC in capitals and msi in lower case) and click Find.
6. When an entry comes up in the registry, press Delete.
7. Confirm that you want to delete this key.
8. Press F3 to continue searching.
9. Repeat steps 6 to 8 until you see the message that you reached the end of the registry.
10. Exit regedit; File->Exit.
11. Reboot your computer.
12. Proceed with the install of BOINC.

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

STEP 6 (Advanced users only).

The next entry is for ADVANCED Users only. It will deal with using the registry and manually deleting entries there. If you do not feel at ease doing this, then do NOT do it! I will not take responsibility for you breaking your own Windows due to deleting other keys than I told you to delete. Also, make a backup of your registry prior to fiddling with it!

We will try to manually delete all traces of BOINC.

Since BOINC will have made the separate BOINC (executable) and BOINC Data directories, it's easy to delete the BOINC directory that holds the executables. So just navigate to C:\Program Files\ for 64bit Windows or C:\Program Files (x86)\ for 32bit Windows and delete the BOINC directory.

We leave the BOINC Data directory in place as it holds all your project data.

The next thing to delete is the registry entries. Please be careful here, do not delete any other entries than the following two.

Go Start->Run and type regedit, then click OK.
The registry editor will start up. First make a backup of it, by going File->Export.

Now we can delete entries that aren't needed anymore.
In the left pane of the window you need to click on the + next to HKEY_CURRENT_USER.
Next click on the + next to Software.
Then look for the entry of Space Sciences Laboratory, U.C. Berkeley
Click that one to select it, then press Delete on your keyboard.

Now we go to HKEY_LOCAL_MACHINE, click on its + to open it up.
Click on the + next to Software.
Look again for the entry of Space Sciences Laboratory, U.C. Berkeley
Click it to select it, then press Delete on the keyboard.

Now go back to My Computer, top of the list in the left pane. Select My Computer, then go Edit->Search and fill in BOINC.msi, click OK.
When it finds an entry, select the key in the left pane and click Delete.

Example given: It finds an entry at HKEY_CLASSES_ROOT\Installer\Products\(big number}\SourceList\PackageName
it will have selected PackageName in the right pane. You will have to select the entry with the big number and then press Delete.

Now press F3 on the keyboard (continue search).
Do the above for every entry of BOINC.MSI that it will find.

Close the registry editor with the X in the top right corner.

Next we'll search for old installation files of BOINC. You'd be surprised to see how many there are if you update regularly. Go Start->Search->All files and folders->type in boinc.msi and click Search.

In the right pane you'll get all the BOINC.msi files that are available on your system. When the search is done, select all of them and delete them.

That's it, BOINC is now off your system. You should reboot to make sure that the registry is read again. Then you can install your next BOINC.
---------------

STEP 7, if we really don't know what to do anymore and we don't want to reformat.

When even that doesn't work, or your patience runs out....
There's one thing I can think of that will install BOINC no matter what.
But you need to start the installation of BOINC from the command line.

NOTE: the following option is best not done with BOINC 6 or 7, due to the limited user accounts that need to be made for the client to run under.
Warning: If you run BOINC 6 or 7, skip this step.

The next example is how to install BOINC 5.10.45 (32bit) regardless of what is in the directory.

Download Boinc 5.10.45 (32bit) and save it to somewhere easy to reach, like C:\ (just the root directory).

Then go Start->Run, type cmd and hit Enter.
A command line window opens.
In the window, type cd\ {Enter}
(If the default drive isn't C:\, type C: {Enter})
Type boinc_5.10.45_windows_intelx86 /a {Enter} (there is a space between the executable and /a)

The installer should start. Make sure you do NOT write directly to the present BOINC directory though. What the /a command does is essentially unpack BOINC.
So write it to a different directory. Let's assume C:\BOINC_Temp

When it's done, exit the command line window by pressing the X.
Then navigate to the C:\BOINC_Temp directory. You see here that there are two directories made, one called Program Files and one called Windows.

The Windows directory contains the BOINC.scr file (screen saver). Copy this file to C:\Windows for Windows 98, SE, ME, XP or C:\WINNT for Windows NT or 2000.

The Program Files directory contains a sub-directory called BOINC.
Copy this complete folder (or the contents of it) to your own BOINC directory. Click Yes to overwrite, or Overwrite all.

Done! You're updated. You can now delete the BOINC_Temp directory.

 

Windows Installer Error 1905

FAQ: Windows Installer Error 1905
Title: Windows Installer Error 1905
Author: Jorden
Views: 86396
Category: 03. BOINC Client Software Questions and Answers
Available in: Spanish English
Created: 27/12/2006 13:05:46
Last Modified: 04/08/2010 16:17:13

Contents:

When you upgrade to a newer BOINC installation you can run into all kinds of errors. One is the Windows Installer Error 1905.

e.g.: Error 1905 Boinc.dll failed to unregister HRESULT -2147220472

This error can occur when an expected component of an application is not present when uninstalling of an earlier version. This can be during the actual uninstall, or during the upgrade process. The solution, when this is the cause, is to uninstall the old version manually and restart the system. If the uninstall is still failing, use the Windows Installer Cleanup Utility to get rid of the old BOINC version. It'll be in the list as a no-named entry or a corrupt one.

Do not remove any of the other .MSI entries in the list, or you will have problems uninstalling other programs!
 

Copyright © Neil Munday 2008