New release, old problems:
By clicking on a link two instances of IE 6 are started. At least I understand that now: When you've already started an instance, it prevents the link to open in the same. But when nothing's open, there two instances after clicking on the link.
And I've still the same problem with BOINC + router (see BOINC Core Client - Trouble with router), but I don't think this is a BOINC problem.
____________

New release, old problems:
By clicking on a link two instances of IE 6 are started. At least I understand that now: When you've already started an instance, it prevents the link to open in the same. But when nothing's open, there two instances after clicking on the link.
And I've still the same problem with BOINC + router (see BOINC Core Client - Trouble with router), but I don't think this is a BOINC problem.

Suggest to get a second browser like Firefox or Opera and make either your preferred browser. If the behavior continues, blame BOINC, if not blame MS. I think someone found a solution though for the double feature and posted on this forum

What router problem (?).... helps if you provide link.

Not sure what the technicality is, but opened IE7 (on WXP SP2), made it the default browser, opened BOINC 5.8.15 operated the "Website" button and only 1 instance was opened. Now the virtues of IE6 v IE7.... whatever bad language one can waste on this product, it is definitely more save than browsing with IE6.
____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt

The problem with two instances of Internet Explorer 6 is still there in BOINC 5.8.16 :(
____________

The problem with two instances of Internet Explorer 6 is still there in BOINC 5.8.16 :(

If you look back a couple posts in the thread, it's not a problem with BOINC. It's a problem with the version of libCurl that is used. The libCurl programmers have been informed.

Hmm I thought I had posted this before.

I don't think libcurl has anything to do with opening browser windows. Libcurl is used to do HTTP communication from within the client, like for scheduler requests, downloads, uploads, etc. I think browser windows are opened by the library that the manager GUI is made with: wxWidgets.

Hmm I thought I had posted this before.

I don't think libcurl has anything to do with opening browser windows. Libcurl is used to do HTTP communication from within the client, like for scheduler requests, downloads, uploads, etc.

And what do you think will open an HTTP window to a browser?

Please go check for libcurl:
and I quote:

Whereas your WxWidgets say:
wxWidgets lets developers create applications for Win32, Mac OS X, GTK+, X11, Motif, WinCE, and more using one codebase. It can be used from languages such as C++, Python, Perl, and C#/.NET. Unlike other cross-platform toolkits, wxWidgets applications look and feel native. This is because wxWidgets uses the platform's own native controls rather than emulating them. It's also extensive, free, open-source, and mature.

So WxWidgets is nice for making your wallpaper look AWESOME. It won't communicate. OK?

OK... (On the "it won't communicate" part: Sounds like one Renderfarm Admin that I emailed 3 (!!) times over 6 months requesting what the feck his project was about so I could put it in my FAQs... I never got an answer.)

btw: Is there any overview of the changes between the 5.8.x releases, like the one of 5.4.x?

Change log that I'm keeping updated from Rom's emails to the alpha list.

On 5.8.15 and passing instructions from the BOINCmgr.exe to BOINC.exe in Windows shortcut during startup. I have set for daily contact of 1 hour, network activity per scheduling preference. Wanted to flush the result files none the less immediately. Since recently hitting the Update button in BOINCmgr, opens the line for 5 minutes and sends all in the Transfer Queue off. The question is: Should the command-line instruction C:ProgrammiBOINCboincmgr.exe "/b, --report_results_imediately"
achieve the same, but than whenever a result is done. Though there are no reports of syntactical errors, the sending is not taking effect. Is this only meant to function one time on startup, with completed work in transfer queue?

Makes no sense.... if "Activity > Network Activity Always Available", the result files are send immediately anyway after each job, so what was the point than to disable?

____________
Coelum Non Animum Mutant, Qui Trans Mare Currunt

Makes no sense.... if "Activity > Network Activity Always Available", the result files are send immediately anyway after each job, so what was the point than to disable?

Upload server is different than making database changes. When you upload that server keeps track of the files, but does not bring the database into the mix. When you open the database to report a result then it is a harder hit. It does not matter if you report 1 or 20, it will take about the same amount of time, and only be one database open, allowing more work to be done at a single moment, than over 20 different open and closes.

Rom's blog post on RRI.

Site is down right now, but I had the link bookmarked.