First, on the results status page, the sorting resetting is a problem I reported quite a while back. However, there's an easy way around it. Bring up the results status page, sort it as you want and, to go to another page, rather than clicking on the numbers by where it says page, go up to the url in the address bar and look for &pagenum=x (it usually is at the end) and change x to the page number you want. That will go to that page with the same sorting.

As for the results status page not being current, I haven't seen that. If you are referring to work you've returned that doesn't have points yet, it probably has a status of Pending Validation which basically means that the validator tasks hasn't gotten to it yet (it normally will within a few hours if not much sooner) or there is one or more other user that need to return that result before it can validate and be awarded points. You should be able to find more on validation and quorums in the FAQ.

BOINC only allows for the three different profiles so, yes, you should ask about that on the BOINC site. However, it's been that way a long time and I doubt that would get changed. What I would suggest is that you set your default profile to run at 60% when idle time as that is your most restrictive case. Set that through the website here at WCG and assign that profile to each device (machine) you have via the website as well. Now go to the machines that you want to run at 60% always (servers) and click on Advanced-Preferences in BOINC Manager on each of those machines and set them to rum that way. That will override your default profile on just those machines. Do the same sort of thing on your machines you want running 100%. That way, if those preferences that are specific to a machine get cleared by mistake, the machine will revert to the lowest impact setting (60% when idle). Should one of your unused machines (running 100%) be needed for a worker, simply clear the preferences on it and it will run with your standard default.

This is a long-standing known bug. It was reported in October 2008. It is not browser-specific.

No don't hold breath for integration into the core client. I've scripted using 2 override files and read them in, which runs according the OS's scheduler. A number of people have asked for multiple time segments of a day and alternation of use of different resources during use and idle. Now it's either on or off. The fan noise during daytime an excellent example why multiple configs during day parts is needed.

Yes do post on the developers forum. The more do, the more chance it's heard, though there's quick repeating, that the developers don't read those forums... put it thus well formulated and argued into Trac with a ticket.

the problem with this of corse if you are wanting badges this will cut your bagde hunting down cause it will see you as mulitple members..

myself im a badge hunter as well as a cruncher.. if there wernt badges here i would probaly be working on alot of projects instead of concentrating on this one (90% share or greater)

i do have one advantage over most of you with hearing fan noise...

i have lost about 80% of my hearing so i just dont hear the fan unless its bearings are going bad and not always then... (got to take the little bonuses with every negitive in your life)

yes i would just recomend trying to use the given 3 we have to work with .. if you need more and dont care about badges and such then yes Sgt,Joe's idea would work nicely too.