I recently was helped in the forum on editing config.xml file to increase the amount of down/uploads in tasks.
Now I can't find that post anymore.
And I need it again after a reinstall.
How do I change the default 2 down/uploads to 10?

Client configuration. Bookmark it.

Client configuration. Bookmark it.

I went through that one already, couldn't find my answer.. Problem is that there are too many commands, and I'm not even sure what the exact 'parameter' is I should be looking for there.


However, I found that the limitation lies in '<max_file_xfers_per_project>' (thanks to another client that had the settings configured in it).

Changing this to 8 solved my issue.

I went through that one already, couldn't find my answer.. Problem is that there are too many commands, and I'm not even sure what the exact 'parameter' is I should be looking for there.

My guess is that each project has particular issues which can be resolved by editing cc_config.xml It would make sense for the projects to have the information pertinent to that project in one of the locked threads showing at the top in their fora.

My guess is that each project has particular issues which can be resolved by editing cc_config.xml

No. cc_config.xml is the core client configuration file. In it you set either debug flags to debug the client, the connection or anything in between, or you set optional settings for proxies, which GPU to use or not use, what to ping to check the connection etc.

You set project preferences via the web site, or the app_config.xml file.
Don't confuse the latter with the app_info.xml file, as that file is exclusively used for the anonymous platform.

That there are many choices for cc_config.xml shows that this is more intricate of a program than many people believe it is.

---

I inserted the line in cc_config.xml.
It works.
It is indeed better to insert it in each project, as some projects have tasks below a few kb, while others have several tens or hundreds of MBs of tasks.
The general setting in cc_comfig works well for me though.

I inserted the line in cc_config.xml.

For future reference, it's better to make a modest/minor change to the logging options via the GUI - Ctrl+Shift+F.

This will create a complete cc_config.xml template, with tags in alphabetical order, and pre-filled with current or default values.

Then if you want something new, find the right line and edit the value. Saves mistakes typing tag names, and avoids unexpected results from duplicated lines. We've had people complain that something doesn't work, only to find they've added a duplicated line and had the effect negated by the original. Last value to be read in from the file wins.

I inserted the line in cc_config.xml.

For future reference, it's better to make a modest/minor change to the logging options via the GUI - Ctrl+Shift+F.

This will create a complete cc_config.xml template, with tags in alphabetical order, and pre-filled with current or default values.

Then if you want something new, find the right line and edit the value. Saves mistakes typing tag names, and avoids unexpected results from duplicated lines. We've had people complain that something doesn't work, only to find they've added a duplicated line and had the effect negated by the original. Last value to be read in from the file wins.

Nice!
I wished this feat could be enhanced, so I can edit values there, and possibly a copy of the client configuration wiki stored locally, for reference on what each feat does.