hi all

I'm having some issues with the latest client / manager.

I'm running BOINC 6.12.26 on vista home premium 32bit.

Aside from the cosmetic changes (that I know some are not happy with... and frankly I don't feel are an improvement, although I don't have a problem with the new Notices functionality), 2 key problems have occurred since moving to the new client:

1) Tasks sometimes stay in memory, when they should be killed (on exiting the manager). PLEASE NOTE that this only happens some of the time I.e. the manager is configured to kill the tasks on exit.

2) The BOINC screensaver process seems to stay in memory and takes up virtually 100% usage levels of one of my cores (I'm using an Intel quad core Q6600), even when the screensaver's not running or chosen as the default screensaver I.e. if it gets started, it doesn't stop.


As I'm typing this, I've managed to replicate the first problem, so am able to list the tasks that are still running, even after the Boinc manager has been closed:

minirosetta_2.17_windows_intelx86.exe
hadcm3n_um_6.07_windows_intelx86.exe
hadcm3n_um_6.07_windows_intelx86.exe
openMalariaA_6.52_windows_intelx86

I have found that relaunching the Boinc manager and exiting from it again does clear the tasks from memory (it just doesn't seem to do it the first time around... most of the time).

In regard to the screensaver problem, I am just bemused by this. All I can tell is that on installation, the default system screensaver is changed to Boinc. I never use this functionality and on noticing the change in screensaver, I changed the screensaver back to my own choice. I am 100% certain that this change was successful (as my choice of screensaver kicked in). However, much later on... I noticed that 1 of my CPU cores was running virtually at 100%. I simply couldn't understand what process could be running to cause this, so had a look in vista's task manager and noticed "boinc.scr". After terminating this process, the CPU usage returned to a normal idling level.

I have managed to replicate this screensaver problem too (just now). I simply went into the vista screensaver menu, selected Boinc (note that the Boinc manager and tasks are not running) then previewed it. When the screensaver popped up, it advised me that "BOINC is not loaded". Checking the system task manager reveals 2 "boinc.scr" processes running. One of these disappears when I change back to my normal (not boinc) screensaver. The one that is left is the one that keeps one of my CPU cores running at virtually 100% usage levels.

I apologise if people feel this post is verbose but I just wanted to try and describe accurately what is happening.

Any advice or guidance is welcomed.


Regards,

Gary

1) was known and is fixed already. Please try 6.12.33, available from here to see this fixed.

2) I haven't heard from yet. See if you can reproduce this with 6.12.33 as well, please. I will forward this part of your post to the developers, just in case they heard of it before. With thanks.

---

Thanks Jord for the quick response.

Will try the new build and come back to you.



Regards,

Gary

Hi Jord

Build 6.12.33 appears to have resolved both problems :D

Excellent!


Regards,

Gary

Help please someone!

First off I am sorry if this is the incorrect forum to post this in. I was trying to find installation errors and found this one.

I decided to download and install the 6.12.26 version. I was upgrading from 6.10.60.

The installer would not install and upon serching the forums, I found one that said to try installing ver 6.10.60 again and selecting repair. I did that, and then tried 6.12.26 again. It still didn't work. I tried to uninstall it and the installer would not let me do it, so upon searching the forums again, I manually uninstalled it, including the registry enteries.

Since then I have tried both 6.10 and 6.12 and neither will install. I get an error message stating "Error 1303. The installer has insufficent privileges to access this directoy: C:\Program Files\BOINC\locale. The installation cannot continue. Log on as an adminstrator or contact your system adminstrator"

Now here's the rub, I AM logged on as an adminstrator. The directory it keeps trying to access when it is created by the installer is read-only and keeps resetting itself to RO when I try to change the property. Only way I can get rid of the directory is to log on in safe mode and take ownership of the file as the adminstrator and then it allows me to delete it. Try installing again and same message. I have run spy ware and virus scans both and no issues.

Any suggestions?

I am running:

Windows XP Home Edition SP3

Solution 1: Change permissions for the All Users folder (Windows XP Professional, Windows 2000).

- If you use Windows XP Professional, temporarily disable simple file sharing:
- Choose Start > My Computer.
- Choose Tools > Folder Options.
- In the Folder Options window, select the View tab.
- In the Advanced Settings, deselect Use Simple File Sharing.
- Click OK to close the Folder Options window.
- In Windows Explorer, navigate to C:\Documents And Settings.
- Right-click the All Users folder and select Properties.
- In the All Users Properties window, select the Security tab.
- Select Administrators under Group Or User Names. If Full Control is not selected in the Permissions list, change the access control level to Full Control.
- Click Advanced.
-- For Windows XP Professional, select Replace Permission Entries On All Child Objects With Entries Shown Here That Apply To Child Objects

- Click OK. If a Security dialog appears, click Yes to continue.
- Click OK to close the All Users Properties dialog box.
- Install BOINC.
Re-enable simple file sharing:
- Select Start > My Computer.
- Select Tools > Folder Options.
- In the Folder Options window, select the View tab.
- In the Advanced Settings, select Use Simple File Sharing.
- Click OK to close the Folder Options window.

Solution 2: Change the sharing permissions.

- Choose Start > Run.
- Type %allusersprofile% in the Open textbox. Then click OK.
- Right-click the Shared Documents folder and select Properties.
- In the Shared Documents Properties window, select the Sharing tab. Select Share This Folder.
- Click Permissions, and select Everyone in Group Or User Names.
- Select Allow next to Full Control in Permissions, and then click OK.
- Click OK to close the Shared Documents Properties window.
- Install BOINC.

Solution 3: Correct permissions from the Command Prompt.

Use a Command Prompt window to manually assign the full administrator access that the installer needs.

- Choose Start > Run.
- Type cmd in the Open textbox. Then click OK. A Command Prompt window opens.
- In the Command Prompt window, type the following commands exactly as they appear below. Include all spaces and quotation marks, and press Enter at the end of each line:

cacls "c:\Documents and Settings\All Users" /T /E /C /G administrators:F

exit

- Install BOINC.

Solution 4: (Windows XP Professional and Home) Change the sharing permissions in Safe mode.

Restart in Safe mode:

- Restart the computer
- The second (or just before) you see the Windows Logo, press and hold down the F8 key.

Change permissions and install BOINC:

- Choose Start > Run.
- Type %allusersprofile% in the Open textbox. Then click OK.
- Right-click the Shared Documents folder, and select Properties.
- Click the Security tab.
- Select Everyone in Group Or User Names, and then select Allow next to Full Control in the Permissions. (For more information on changing permissions, see Windows Help.)
- Click Advanced, and select Replace Permission Entries On All Child Objects With Entries Shown Here That Apply To Child Objects.
- Click OK, click Yes, and then click OK to close the Shared Documents Properties dialog box.
- Select Start > Run.
- Type msconfig in the Open textbox. Then click OK. The System Configuration Utility opens.
- In the System Configuration Utility, select the General tab.
- Select Normal Startup - Load All Device Drivers And Services. Then click OK.
- Restart the computer.
- Install BOINC.

Solution 5: Turn off backup software services running on the computer before installing or upgrading BOINC.

Turn off a backup service running on the machine:

- Choose Start > Settings > Control Panel > Administrative Tools > Services
- In the right pane, select your backup service. This name varies depending on the software. See the documentation for your backup software for the name used in the Services panel.
- Right-click and select Stop from the context menu.
- Install BOINC.
- Right-click and select Start from the context menu.

---

Thank you for the suggestions but sadly none of them worked. Well, or maybe they have but now I am getting a different error message. This one says "error 1310.Error writing to file C:\Program Files\BOINC\boinc.dll. Verify that you have access to that directory" and it keeps making the boinc file read only. I have even tried renaming the directory to install to but this same message pops up saying the c:\program files\boinc\boinc.dll cannot write.

Are you installing BOINC over a network, or directly on the machine?

You can try to re-register the Windows Installer.
1. Click Start, and then click Run.
2. In the Open box, type msiexec /unreg, and then press ENTER.
3. Click Start, and then click Run.
4. In the Open box, type msiexec /regserver, and then press ENTER.

One thing it could be is that there's something not right in the registry. You could try a freeware registry scanner to check all links in the registry and fix them.

---

Hi,
I have been using Seti & then Boinc for a while, I have never seen it do this before so correct me if I am wrong. Work units on GPU cores restart from the begining when interupted by computer usage. This is with version 6.12.26 & .33, for both projects Seti and Milkyway.

Did it always do that?

Shame I really didn't notice before, if it did and this is normal please let me know.

Seems like wasted crunchin'.

Thanks for your help

That did the trick, I must have unchecked that after I updated cause I never seen it do that. Anyway, no waste on the crunchin' now - thanks again.

I ran into the problem of the BOINC download page trying to have me download the wrong client for my upgrade to 6.12.56. I have multiple machines running, most with the X64 client on them (except my mac mini and laptop). So I go to update the client on one of my X64 client installs and the download page shows the x86 client for me to download. Luckily I looked at the exe filename and saw that "x86" designator in it or I would have had another mess on my hands (did this about a year ago and had mucho problems figuring it out). How about having the main BOINC client download page either look at the client version that is running on the computer and offer the correct version up (x86 or x64), or at least giving direct links to both the x86 and x64 versions of the client as direct links for the download.

Also, since someone decided to lock out the other threads I found on this new version of the client, I would like to register my displeasure at the totally useless changes to the GUI. The notices tab is as useless as tits on a boar hog for the projects I run and a total waste of a good tab. That tab spot would be much better utilized for displaying the messages and put the notices in place of the event log. I do like the fact that it seems that they have fixed the issue of the scheduler trying to download GPU tasks when the project you are running doesn't use GPU power at all and I also assume that you have fixed it where if the user (me) doesn't want to use their GPU on a project that does utilize the GPU for crunching, the client won't keep trying to contact the servers for work. That was annoying me to no end, since I presently only participate in Rosetta and having the client contact the servers for GPU work has been pissing me off for quite a while.

As for the other changes in the GUI, I can live with (even though I'm not too fond of some of them), but making me open up a separate window to look at messages is just stupid, IMO. At least give us the choice to put swap the messages (event log) and that stupid notices tab around into each other's place.

One other thing about this "supposedly stable" version, which was brought up in this thread. Like the tasks staying in memory problem to be specific. I don't allow the screensaver to run on any of my installs, so that isn't a problem for me. But would it be advisable to upgrade to 6.12.33 on the machine I just upgraded and on my Mac Mini(OSX Snow Leopard) to make sure this doesn't become a problem?

Not to detract from your displeasure with the latest BOINC Manager, but give BoincTasks a try, in particular because you have multiple hosts.

Both Messages and Notices are tabs. It's looks are customisable, and it is purposely designed for managing multiple hosts. Although it's natively designed to run on windows it's wine compatible which means after installing wine it can be run on a linux or mac box.

---

CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1

Thank you man, I'll give it a try when I get a chance.