Bonjour,

Ayant suivi scrupuleusement la procédure indiquée pour joindre Rosetta, je suis tombé sur la page des "add-on" puis sur http://boinc.berkeley.edu/addon_item.php?platform=win&item=http%3A%2F%2Fmion.faireal.net%2FBES%2F où j'ai téléchargé BES (http://mion.faireal.net/BES/).
Après avoir fait joujou avec ce limiteur de CPU, j'ai pressé le bouton "unlimit all" puis "exit".

Malheureusement, les applications BOINC que j'avais limitées restent limitées à 20% du CPU, et une grosse installation que je viens de faire, Inskape, n'a pas dépassé les 20%.

J'ai un AMD à 2,7 GHz avec 1,75 Go de ram et Win XP.

Quelqu'un a-t-il une idée pour faire sauter les limitations invisibles ?

Merci

---

I believe they are saying they configured BOINC to limit to 20% of CPU, and it didn't enforce the limit.

Two things, first, you must have BOINC version 5.6 installed on your machine. The second is that you must set the client to "run based on preferences" rather then "run always".

You no longer need any add-on to limit the CPU usage. BOINC now allows you to define a CPU limit.

---

Rosetta Moderator: Mod.Sense

I may be mistaken. They may be saying they were testing with 20% of CPU and now wish to set things back to normal. Hopefully someone can translate more accurately.

---

Rosetta Moderator: Mod.Sense

Slightly better translation (the user also runs Boinc 6.4.7):

Hello,

Having scrupulously followed the procedure indicated to join Rosetta, I then came across the "add on" page at http://boinc.berkeley.edu/addon_item.php?platform=win&item=http%3A%2F%2Fmion.faireal.net%2FBES%2F where I downloaded BES (http://mion.faireal.net/BES/).

After playing around with this CPU-limiting device, I pressed the button "unlimit all" then " exit".

Unfortunately, the BOINC application that I had limited, remained limited to 20% of the CPU, and a large installation which I have just made, Inskape, did not exceed 20%.

I have a 2.7GHz AMD with 1,75Gb RAM and WinXP.

Does anyone have any idea to overcome the invisible limitations?

Merci beaucoup pour votre traduction, elle est parfaite!

Thank you very much for your translation, it's perfect!

---

If you want limit CPU, I suggest using the BOINC configuration to do so.

To resolve the current problem, I would suggest you uninstall BOINC and install it to another subdirectory on your disk drive. This will probably trick BES in to thinking it is not supposed to control the program in the new directory.

bonne chance.

---

Rosetta Moderator: Mod.Sense

Problem fixed ! Youpiiii!

I had just to stop the service "Thread Master" of Windows.
It haves no dependency.
I suppose it was be activated by BES.

Thank you very much for your replys (replies ?) I'm so bad in english...

Now, I'm going to test CPU limit by BOINC in user's preferences.

See you later

Now, I'm going to test CPU limit by BOINC in user's preferences.

A quick test shows me that control of CPU by setting preferences in my account (climat prediction) is not working (and I don't forget to valide changes on my BOINC manager). But BES works very well, better than before.

So, all of the problem becomes from Thread Master of Windows.

Good bye, and thank for yours responds.

Cocoricooo

You must update to the project where you modified the settings. And you must configure the client to "run based on preferences", rather then "run always".

---

Rosetta Moderator: Mod.Sense